Set the minimum product record
Agree the fields every sellable SKU must contain. The exact standard varies by category, but ownership and completeness rules should not.
- Product and variant identifiers
- Customer-facing name and description
- Materials, care and origin
- Dimensions, fit or technical specifications
- Category, taxonomy and filter attributes
- Approved assets and usage order
Resolve source conflicts
Supplier files, internal systems, samples and commercial notes often disagree. Define which source wins for each field and where an unresolved question is held. Do not allow the upload stage to become the place where product truth is decided.
Map channel requirements
Create a clear transformation from the source record to each channel. Record mandatory fields, character limits, accepted values, image rules and category-specific requirements. Keep the source strong enough to support several outputs.
Validate a representative set
Test simple and difficult products: the shortest name, the longest description, a product with many variants, one with incomplete supplier data and one requiring category-specific attributes.
Own errors after launch
A rejected listing should trigger two actions: resolve the live error and correct the source or rule that created it. Otherwise the same failure returns with the next collection or channel.
Related service
Explore catalogue and marketplace operations