Product Attributes: What They Are With Examples

Product attributes are the facts that describe an item, such as its material or dimensions. Store them as named fields with consistent values so shoppers, sales channels and shopping agents can use the same information.

A catalogue clean-up starts with agreement on which fields each product needs. A chair needs measurements and upholstery details. A replacement part needs compatibility records. The useful attribute set depends on what someone must know before buying.

What Product Attributes Are

A product attribute pairs a name with a value: material is cotton, or assembled width is 80 cm. The name tells people what the fact describes. The value supplies the answer.

Attributes can be text, numbers with units, approved choices or true-or-false values. A description can explain how a jacket feels, while separate fields record its fabric composition and care instructions. Those fields let a filter find wool jackets without interpreting every description.

Product attributes in marketing support specific claims. A product page can show a verified waterproof rating, while a comparison table uses the same field to compare jackets. Avoid replacing a measured rating with a vague label such as weather-ready.

Categories decide where products belong. Attributes describe the products within them. Use the guide to product taxonomy when you need to organise that category structure.

Product Attributes Examples by Category, With Weight and Dimensions

Choose product attributes that answer the buying and fulfilment questions for each category. The following examples are hypothetical attribute sets, not specifications for actual products.

Category	Descriptive and option attributes	Measurement fields	Example values
Apparel	Size, colour family, fabric composition, fit and care instructions	Product weight, garment measurements and packed dimensions	Cotton shirt, size M, Blue, 0.25 kg product weight
Furniture	Upholstery, frame material, finish, assembly needs and seating capacity	Assembled width, depth and height, product weight and packed dimensions	Chair, oak frame, 80 cm assembled width, 12 kg product weight
Electronics	Model, storage capacity, ports, power requirements and compatibility	Product weight, physical dimensions and packed dimensions	Laptop, 512 GB storage, USB-C port, 1.4 kg product weight

Keep product dimensions separate from packed dimensions. The assembled chair’s width answers, Will it fit beside my desk? The shipping carton’s measurements answer a different question about transporting it.

Carriers use weight and package dimensions to calculate shipping quotes, including cubic-weight calculations where applicable. Record packed weight as well as product weight. A heavy box or protective packing can change the shipping figure.

Use kilograms and centimetres throughout your internal weight and dimension fields. Convert supplier measurements on import and channel measurements on export. Leave specialised units, such as watts or gigabytes, attached to their own attributes.

Colour Attributes and Colour Families

Store a standard colour family beside the brand’s colour name so filters remain useful without losing the product’s identity. A garment called ‘Harbour Mist’ can have Blue as its colour family.

Choose a controlled list for colour families and document how staff assign them. Keep the brand colour name as display text. A shopper searching Blue then finds several brands’ products, even when each brand uses a different shade name.

For multi-colour products, allow several colour-family values when those colours visibly describe the item. A blue-and-white striped shirt can appear under Blue and White, with Striped in a separate pattern field. Use Multicolour for genuinely mixed designs under a consistent rule. Don’t assign every colour visible in a tiny logo.

Keep pattern separate from colour. Floral and Checked describe designs, while Red describes colour. This avoids a filter full of incompatible choices such as Red, Floral and Harbour Mist.

Category-Specific Attributes: Fitment and Nutrition

Fitment and nutrition need category-specific fields because a general description cannot safely carry every buying condition.

For automotive fitment, use a table that connects a part to each supported vehicle configuration. Include make, model, year range, engine and body type. Preserve any supplier qualifiers, such as a chassis restriction. A single field saying ‘fits popular utes’ cannot distinguish two engines in the same model.

The Auto Care Association’s Aftermarket Catalog Exchange Standard (ACES) is a common North American format for exchanging fitment data. Australian suppliers often supply their own catalogue formats, which need mapping into your vehicle and part records. Preserve the original supplier identifiers alongside the mapped values.

A small, stable range can start in a spreadsheet with one fitment per row. A parts retailer needs product information management (PIM) built for automotive data when overlapping applications and recurring supplier updates become difficult to maintain. Select a system that imports vehicle applications, keeps exclusions and exports the mappings your storefront needs.

Food attributes include ingredients, allergens, serving size, dietary claims and nutrition information panel values. Food Standards Australia New Zealand (FSANZ) sets the labelling rules. Make online attributes match the pack exactly, including the approved formulation and allergen statements.

The FSANZ nutrition information panel guide explains per-serving and per-100 g or per-100 mL values. Store those bases separately. Record energy in kJ and nutrient quantities with their units for protein, fat, saturated fat, carbohydrate, sugars and sodium.

Store a declared gluten-free claim as an approved structured value. A gluten-free filter must read that value and the supporting product record. It must not infer the claim from low sugar or a missing ingredient. Keep the FSANZ allergen requirements beside your food-data rules.

Product Attributes Versus Product Variants

Attributes describe a product, while a variant is a specific version a customer can buy. A shirt’s cotton composition can apply to the whole product. Its size and colour options identify separate variants with their own stock records.

In a hypothetical range with four sizes and two colours, all available combinations produce eight variants. Each variant needs its own stock keeping unit (SKU) and the correct option values. Product-level attributes can be shared unless a variant changes them.

Shopify publishes a limit of three options and 2,048 variants per product. Size and colour can be option attributes. Some themes, apps and channels still have restrictions above 100 variants, so compatibility affects how the range appears outside the product editor.

Don’t create variants for every descriptive fact. Care instructions usually belong in an attribute. Create a variant when a choice changes the purchasable item, then keep its price and availability attached to that variant.

Shopify Metafields, Metaobjects, Tags and Magento Attributes

Shopify stores additional product facts in metafields, while Magento 2 uses product attributes grouped into attribute sets.

Shopify product tags are free-text labels. They suit collection rules and internal grouping, but inconsistent spelling and mixed meanings make them poor attribute filters. Tags can power filtering when carefully governed. They make poor sources for AI answers when a label doesn’t state what it measures or which variant it describes.

Use a typed metafield for a fact such as material or assembled width. Shopify supports measurement types, numbers, text, true-or-false values and references. Its Help Center lists up to 256 metafield definitions per resource type. Create definitions with validation rules before filling product values.

Metaobjects hold entries made from several fields. For example, a fabric profile can contain composition and care instructions. Products reference that profile through a metafield. Editing the shared entry updates the information those products reference, so staff don’t maintain separate copies of the same guide.

For Magento 2, Adobe documents this setup:

1. Open Stores, then Attributes, then Product and choose Add New Attribute.
2. Set the label and input type. Add allowed values for a dropdown or multiple-select field.
3. Set the attribute code, scope and relevant validation or storefront properties, then save the attribute.
4. Open Stores, then Attributes, then Attribute Set. Add the attribute to the appropriate group and save.

Adobe’s instructions for creating attributes explain those settings. Assigning the attribute to a set makes it available when editing products using that set. Check a representative product after saving to confirm the field appears with the intended values.

Required Product Attributes for Channels

Required product attributes depend on the sales channel, target country and product category. Separate a channel’s mandatory fields from optional fields in your catalogue rules.

Channel requirement	Examples	How to treat it
Google Merchant Center core fields	ID, title, description, product link, image link, price and availability	Provide accurate values for each applicable listing
Google conditional fields	Brand and product identifiers, variant grouping, colour, size or other category-specific fields	Apply the country, category and product conditions in the specification
Google recommended detail	Useful product details and additional images where optional	Add supported facts that help distinguish the item
eBay category requirements	Required item specifics, which can include brand, size or model	Complete the fields marked Required for the selected category

Google’s Merchant Center data specification identifies each field’s conditions. A missing or invalid required value can cause disapproval or limit eligibility. Don’t invent an identifier to fill an empty field.

eBay requires category-specific item specifics for new or revised listings. Its item specifics guidance separates Required from Recommended fields. Missing recommended detail can also exclude an item from matching filtered searches.

Map your internal fields to each channel’s names and accepted values. For the export and validation process, read the guide to product feed optimisation.

Auto Tagging and Image Tagging

Auto tagging tools suggest attributes from product text, while image tagging tools suggest visible attributes from photographs. Text can reveal a stated fabric composition. A photo can suggest a pattern or neckline.

Treat every suggestion as a candidate value. A photo cannot establish fibre content, electrical compatibility or an allergen claim. Lighting can distort colour, and lifestyle photos can show accessories that aren’t included with the product.

Require a person to approve suggested tags before they reach storefront filters, product feeds or the shopping agent. Keep the input source and approval status with the suggestion. Only approved values become catalogue attributes.

Use the guide to enriching catalogue data for the broader process of filling missing facts. Attribute design decides which fields receive those facts.

Designing a Product Data Model and Showing It on the Page

A product data model separates attribute definitions from product and variant values, then uses those values wherever the item is shown.

Record	What it holds	Example
Product	Shared identity and descriptive facts	Shirt family and brand
Variant	The purchasable item and changing facts	Medium, Blue, SKU and stock
Attribute definition	Name, type, units, allowed values and required categories	Assembled width, decimal, cm
Attribute value	Product or variant reference, definition reference and value	Chair A, assembled width, 80
Related record	A shared object or repeated relationship	Fabric profile or vehicle fitment row

Give each attribute a stable identifier. Validate measurements as numbers with units and use approved choices for fields such as colour family. Keep unknown separate from false or zero. Record where a value came from and who approved it.

To extract attributes from existing descriptions, first select the fields and accepted formats. Pull candidate values from the text with rules or an extraction tool. Retain the supporting sentence with each candidate value. Normalise units and have someone check the result before import. Leave missing facts empty until a reliable source supplies them.

Show the approved fields on the product detail page in the form that suits each answer. Measurements belong in a spec table. Colour choices can become swatches, while a verified dietary claim can become a badge. A size chart needs the relevant garment or body measurements and their labels.

Make the page and product feed read from the same fields. Changing an upholstery value must update both outputs. Confirm that the selected variant’s swatch, specification and feed entry describe the same purchasable item.

How AI Shopping Assistants Use Attributes

AI shopping assistants match a shopper’s request to catalogue attributes, then use matching product and variant records to explain the results.

In a hypothetical example, a shopper asks for a blue cotton shirt in medium. An assistant maps Blue to colour family, cotton to composition and Medium to the size option. It then checks that the matching variant is available. A blue shirt with stock only in small does not satisfy that request.

The assistant can explain a match using those fields: the shirt is cotton, belongs to the Blue colour family and has a medium variant available. If a required fact is missing, it needs another supported source or a follow-up question. It must not turn an absent value into a positive claim.

Start your catalogue clean-up with one representative product from each category. Agree on the required fields, enter verified values and follow them through the product page, feed and assistant answer. Fix conflicting values before applying the model across the range.