Retail catalog operations
Retail onboarding fails when identity, content, package and commercial fields live in separate spreadsheets with different owners. A reliable master record gives each sellable variant one stable identity, records where every fact came from and shows which channel transformations are approved before the item goes live.
Direct answer
Start with a channel-neutral product master rather than copying a marketplace template. Create one stable internal product ID and one row for every sellable variant, then map parent-child relationships without reusing IDs. Record brand, manufacturer reference, GTIN or other identifier status, product name, factual description, category, condition, variant attributes, package contents, country of origin where verified, measurements with object and method, images with rights status, and any evidence-controlled claims. Keep consumer-unit, inner-pack, case and pallet data separate. Add retailer-specific field names, allowed values, character limits and required statuses through a mapping layer so the source record remains intact. Validate identifiers, units, variant uniqueness, image URLs and controlled vocabulary before export. Compare feed or portal output with the actual product page and physical packaging, log rejected fields and correct the source rather than patching only one channel. Assign owners and update rules for product, price, availability and regulated fields. Archive submitted versions and approval receipts so later changes are traceable.
Use this before requesting a quotation
Decide what the customer can buy as one offer and assign a stable internal ID to each sellable variant. Map product family, style or model, color, size, pack count and bundle relationships explicitly. Do not create a new identity merely to fix text, and never reuse an old ID for a different product. Record discontinued and replacement status without deleting history.
Record GTIN, MPN, brand and supplier model exactly as issued, plus issuer, allocation date, check result and packaging level. Mark not assigned, pending and not applicable differently. An internal SKU is useful for operations but should not be presented as a manufacturer or GS1 identifier. Review identifier changes against current allocation rules and trading-partner requirements.
Build fields for controlled name, plain description, category, condition, composition or material wording, dimensions, weight, intended use, included items, care or setup information and country of origin where evidence exists. Store value, unit, measurement object, method, source document, owner and review date. Keep unknown values blank rather than inheriting them from a related model.
Distinguish the consumer unit from inner pack, case, shipping carton and pallet. For each level, record identifier, contained quantity, net and gross measures, dimensions, package type and marks using named methods. Reconcile hierarchy multiplication. A product dimension must not be replaced with a carton dimension, and a case GTIN must not be attached to the individual item.
List primary, alternate, detail, package and lifestyle images with file owner, rights status, represented variant, revision and approved use. Tie performance, compatibility, material, safety, sustainability, authenticity and other claims to specific evidence and allowed wording. Product-data completeness is not permission to publish an unsupported field, logo or third-party image.
Create a mapping table from source field to retailer or platform field, allowed value, format, unit, language, requirement and transformation. Validate unique IDs, variant groups, checksums, mandatory values, URL access, image match and category-specific fields. Export a test set first. Keep rejection messages with the exact submitted version and fix the authoritative source when the error is factual.
Compare the accepted feed, retailer record and visible page with the approved master and packaging. Check title, variant selection, identifiers, images, condition, dimensions, included items and evidence-controlled copy. Assign update frequency and owners separately for slow product facts and fast commercial data. Retire items deliberately and preserve prior submissions, acknowledgements and correction history.
Reusable buyer brief
Internal product ID, family ID and sellable variant: Brand, MPN, supplier model and identifier status: GTIN, packaging level, issuer and validation result: Controlled product name, category and condition: Variant attributes and parent-child relationship: Product facts, units, methods and source records: Consumer unit, inner pack, case and carton hierarchy: Image role, represented variant and rights status: Claim wording, evidence scope and approval owner: Channel field, allowed value and transformation: Test export, rejection and corrected source version: Live-page reconciliation, update owner and retirement rule:
Fill only the details relevant to your request
Before you send the request
It is the controlled set of identity, classification, variant, physical, packaging, media and descriptive facts used to create consistent product records across internal systems and trading partners.
Every sellable variant needs a stable unique internal identity. External identifier allocation and grouping depend on the product, packaging level, issuer rules and retailer specification.
It can be an export view, but a channel-neutral source is safer. Retailer columns, formats and required values change and should map from controlled facts rather than become the only record.
Assign an owner and evidence request, mark the field pending and hold the affected publication when necessary. Do not guess a GTIN, material, measurement, origin, price, availability or claim.
Keep the request specific
Retailers, marketplaces, destinations and product categories use different data and legal requirements. Google Merchant Center rules apply only when that service is used. Verify each trading partner's current specification and do not invent identifiers, measurements, origin, price, availability, rights or claims to fill a required field.
Send this checklist on WhatsAppEditorial method
MINJI separates the authoritative product record, packaging hierarchy, evidence status and channel transformation. GS1 defines interoperable product-data concepts while current Google documentation supplies a concrete channel example; neither is used to invent catalog facts.
Ready with the key details
Send the product reference, estimated quantity and destination so the conversation starts with useful context.
Continue on WhatsApp