> For the complete documentation index, see [llms.txt](https://kb.bevica.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.bevica.com/documentation/guides/items-and-inventory/bevica_item_attributes.md).
# Bevica Classifying Items
Classify items using Bevica fields for reporting, filtering, and workflow rules.
Bevica holds a collection of item fields that can be used to enhance product marketing related information. These are available to filter / sort on, export and use on various pages.
### Item Category Code
Use **Item Category Code** to provide the primary item classification. Set against each item, the code is copied to various item related tables/pages within the system, i.e. sales, purchase and transfer related lines, allowing for easy filtering and reporting.
Item Categories can be set up in a hierarchical structure.
### Item Card, Marketing fastTab
This area holds Bevica’s core Item Marketing information. You can associate the following information:
Blend Codes
Identify the spirit/ingredient/grape composition of a product in a standardised, queryable way. These codes help group SKUs, drive label text, compliance, and enable analytics like “% Cabernet in portfolio.” They’re typically normalized (e.g., 70CAB/30MER) rather than free text to keep data clean.\
*Examples:* `CAB100` (100% Cabernet Sauvignon), `CAB70-MER30`, `GSM` (Grenache/Syrah/Mourvèdre), `BLEND-HOUSE-RED`, `SMALT100` (single malt whisky).
***
Marketing Description
A consumer‑facing, richer description used on websites, brochures, sell sheets, or POS—more storytelling than the standard 'Description'.\
The field is initially kept in synch. with the 'Description' field unless it is manually changed.
***
Brand Codes
Short, unique identifiers for the commercial brand family under which products are marketed. They enable consistent reporting and filtering.\
*Examples:* `PENF` (Penfolds), `CHLAT` (Château Latour), `HEND` (Hendrick’s), `JWB` (Johnnie Walker Black), `CL-HOUSE` (Company House Brand).
***
Classification Codes
Define regulatory or stylistic designations that carry legal or category meaning—especially important for Old World wines and certain spirits. They support compliance, authenticity, and premiumization tiers in analytics.\
*Examples:* `DOCG`, `DOC`, `AOC`, `IGP`, `VDP.GROSSE LAGE`, `Reserva`, `Gran Reserva`, `VS`, `VSOP`, `XO`, `Single Malt`, `Blended Scotch`.
***
Countries/Regions
The country (and often the broader region) of origin used for reporting and filtering and consumer navigation. Standardised country/region values also power geographic assortment planning and route‑to‑market analytics. Typically used to denote the political country the product originated from.\
*Examples:* `FR`, `IT`, `ES`, `NZ`, `US`
Region / Subregion Codes
Granular geographic hierarchy that sits below Country/Region—used to pinpoint terroir, drive appellation rules, and surface precise filters online. Essential for provenance‑driven categories.\
*Examples:* `FR/Bordeaux/Left-Bank/Pauillac`, `IT/Piedmont/Barolo/Serralunga d’Alba`, `ES/Rioja/Rioja-Alavesa`, `US/California/Napa/Howell-Mountain`, `UK/Scotland/Speyside`.
Appellation Codes
The legally defined origin designations, tied to Region / Subregion designations. These codes are crucial for label accuracy, regulatory filings, and price positioning.\
*Examples:* `Pauillac AOC`, `Barolo DOCG`, `Rioja DOCa`, `Chianti Classico DOCG`, `Marlborough GI`, `Champagne AOC`, `Cava DO`.
***
Marketing Group Codes
Groupings used to categorise **Item Marketing Notes**, which are **extended descriptive text fields** attached to an Item record, used to store **rich marketing, tasting, production, or promotional content** that goes beyond the standard Description and Description 2 fields.
They are used for:
* Website product information
* Tasting notes
* Producer or product story
* Extended marketing copy
* “Tech sheet”–style content for sales
* Exporting to external systems (websites, mail merge, PDFs)
\
*Examples:* `ADVERITSING`, `AROMA`, `FOOD`, `MIX`, `PRODUCTION`, `TECH`.
See also: [Item Marketing Notes](/documentation/guides/items-and-inventory/item_marketing_notes.md)
***
Press Codes
Press Codes are used to categorise **Press Content** refers to a specific data area on the Item record used for managing press‑related or publication‑ready text. It is part of Bevica’s extended item‑marketing framework and is stored and handled similarly to Marketing Notes — but specifically intended for:
They are used for:
• Media / press descriptions
• Text for external publications (e.g., Harpers, Grape Press, WineGB pieces)
• Content to be exported to websites
• Import/Export routines designed for bulk content management
*Examples:* `AWARD`, `TRADEMAG 'A'`, `TRADEWEB 'X'`, `COMPETITION 'Q'`.
See also: [Item Marketing Notes](/documentation/guides/items-and-inventory/item_marketing_notes.md)
***
Drink From & Drink To
The recommended consumption window (start and end year) for optimal quality. Helps with cellar management, allocation timing, ecommerce messaging (“Drink now–2030”), and depletion strategies.\
*Examples:* `Drink From: 2026` / `Drink To: 2032` (Bordeaux left bank); `Drink From: Now` / `Drink To: 2025` (fresh rosé); `Drink From: 2030` / `Drink To: 2050` (structured Barolo).
**Best Before Dates** on batches are best managed using Item Tracking features: Rotation No, Lot No. or Serial No.
***
Style Codes
Standardised sensory/positioning tags that describe the product’s profile to aid discovery and assortment planning. Often used as filters on D2C and B2B portals.\
*Examples:* `LIGHT-CRISP-WHITE`, `FULL-BODIED-RED`, `OFF-DRY-RIESLING`, `BRUT-SPARKLING`, `PET-NAT`, `SMOKY-PEATY`, `BOTANICAL-GIN`, `NO-ALC-SPARKLING`.
***
Colour Codes
Primary visual category for wines (and sometimes spirits/RTDs) used for quick navigation and merchandising rules.\
*Examples:* `RED`, `WHITE`, `ROSÉ`, `ORANGE`, `SPARKLING-WHITE`, `SPARKLING-ROSÉ`. (For beer/spirits variants: `AMBER`, `DARK`, `CLEAR` where relevant.)
Search for each area or navigate to **Bevica Setup** to create and manage these codes prior to adding them to items.
### Item Additional Details
**Item Additional Details** page holds the following information:
* Allergens
* Waste Packaging information
* Pallet details
For more information, see [Item Additional Details](/documentation/guides/items-and-inventory/item_additional_details.md).
### User Defined Attributes
In addition to the fields above, you can define another 18 fields to use as you want on the item record. For more information, see [User Defined Item Fields](/documentation/guides/items-and-inventory/user_defined_item_fields.md).
### Marketing Notes
Marketing Notes and Item Press Notes are the different types of marketing information that can be set against your item. These codes are user defined (i.e. Tasting, Food Matching, Awards, Production information, etc). For more information, see [Item Marketing Notes](/documentation/guides/items-and-inventory/item_marketing_notes.md).
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://kb.bevica.com/documentation/guides/items-and-inventory/bevica_item_attributes.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.