Before publishing, establish a reliable product record

When to use this

For teams maintaining product information across channels and languages. This is a working method, not an audit of your store or software.

Assign ownership

Decide who confirms specifications, image rights and language review. Each field needs an authoritative source; the latest chat message is not enough.

Use stable identifiers

Keep separate stable IDs for products and variants and record channel mappings. Names can change, so do not match records by name alone. Store pack quantity, units and dimensions separately.

Verify a small sample

Choose real products including variants and multiple languages. Compare source records with page output. Record discrepancies and owners before expanding.

Definition of done

Each important field has a traceable source, update date and publication version. Missing facts stay pending instead of being invented during translation or AI generation.

Design a reusable product record

Core fields include an internal identifier, public name, model and variant, specification units, pack quantity, image version, intended use and limitations. Give each field a source, owner and confirmation date. Listings, ads and support copy should derive from the same facts. Resolve differences in the record rather than letting every page become a final version.

Define change and release order

When a specification changes, record the reason and affected variants before checking images, translations, listings and support materials. Separate drafts from published versions so edits do not silently replace live descriptions. Verify the actual pages after release and keep a discrepancy list. A spreadsheet change does not mean every channel is updated.