Good product data is part of the interface

Consistent product information makes many interface decisions simpler. A designer cannot reliably compare attributes that mean different things from one product to the next.

Agree on the vocabulary

Define the fields that matter for browsing and comparison. Keep names, units and allowed values understandable to the people maintaining them. A shared description of what belongs in a field is more useful than expecting everyone to infer it from existing entries.

Make gaps visible

Distinguish missing information from an intentional absence. Decide how the storefront should handle both. If a card needs an image or a detail page needs a specification, the content workflow should make that requirement visible before publication.

Review a varied sample

Use products from different categories when evaluating the structure. Look for values that are technically present but not useful, such as a generic description repeated everywhere. The aim is a catalogue that supports clear comparisons and predictable page layouts, while remaining practical for people to maintain over time.