{"id":318,"date":"2026-09-15T10:00:00","date_gmt":"2026-09-15T08:00:00","guid":{"rendered":"https:\/\/yindle.com\/?p=318"},"modified":"2026-09-21T22:01:46","modified_gmt":"2026-09-21T20:01:46","slug":"woocommerce-attributen-woordenlijst","status":"publish","type":"post","link":"https:\/\/yindle.com\/en\/woocommerce-product-attribute-glossary\/","title":{"rendered":"Managing product attributes with a fixed glossary"},"content":{"rendered":"

A catalogue becomes difficult to compare when the same attribute is entered in different ways. \u201cBlack\u201d, \u201cblack matt\u201d and \u201cMatt black\u201d may be deliberate distinctions, or three ways of writing the same value. A fixed glossary for product attributes helps employees record consistent data and makes the presentation clearer.<\/p>\n

Define the meaning before the spelling<\/h2>\n

Start with the attributes customers actually use to choose. Define what each attribute describes. \u201cSize\u201d may mean clothing size, package contents or a physical dimension. When these meanings are mixed, consistent spelling helps only to a limited extent. Create separate attributes with a clear purpose if needed.<\/p>\n

WooCommerce supports global attributes used across several products and product-specific attributes. The official product organisation documentation<\/a> describes these options. Choose global attributes when the same meaning needs to be managed across the catalogue; assess exceptions deliberately before local fields multiply.<\/p>\n

Use examples to expose uncertainty<\/h2>\n

A fictional store offers metal shelving eighty centimetres wide. One employee enters \u201c80 cm\u201d, another \u201c800 mm\u201d and a third just \u201c80\u201d. Although some values mean the same thing, the presentation is inconsistent. Choose a unit and a fixed input format, with an explanation for the customer.<\/p>\n

A glossary therefore contains more than permitted words. Include the name, meaning, unit, spelling and examples. Also define how to handle unknown values or values not yet supplied. A blank attribute is not the same as \u201cnot applicable\u201d, and an arbitrary dash can hide that difference.<\/p>\n

Make responsibility for changes explicit<\/h2>\n

Appoint someone to review new values and changes. This role need not involve an extensive approval procedure. The point is that an employee can ask whether a new value genuinely adds a substantive distinction. Without that coordination, near-identical variants will still appear.<\/p>\n

For online store development<\/a> the glossary can be used in the trial catalogue. Ask the design team to display real values, including long names and missing information. This reveals early which attributes work together and where more explanation is needed.<\/p>\n

If data comes from an external system, mapping it to store values belongs in the agreed data model<\/a>. Through an integration<\/a> values can be supplied, but someone must establish what they mean. Automatic synchronisation does not make unclear source data consistent by itself.<\/p>\n

For technical attributes, also state whether the value is a nominal designation or an exact specification. A trade size may be understood differently from a measured dimension. The glossary should explain these differences so employees do not merge values that only appear similar. Ask the product owner to confirm the meaning before cleaning up data.<\/p>\n

Clean up existing variants in a controlled way<\/h2>\n

First list the values in use and the affected products. Decide which values can genuinely be merged and which need to remain distinct. Test a change on a small, representative set. Check both the product information and any selection options<\/a> or existing references that use the attribute.<\/p>\n