Knowledge
What do retailers require before a new product can go live?
Catalog readiness is the product data and compliance work a retailer requires before it will accept a new item onto its channel: accurate attributes and images, the identifiers it uses, a mapping to its own category and attribute rules, and — for regulated goods — the compliance documentation it asks for. A product that is missing any of it is rejected or held back, which is why onboarding a new retailer is rarely just “turn it on.”
Why a product can be real and still not launchable
A product can be fully described in a supplier’s own system — a SKU, a price, a photo — and still fail the instant it is submitted to a retailer. That is because the retailer is not checking whether the product exists; it is checking whether the product, as described, matches what that retailer’s own systems and compliance program require: its own category, its own required fields, its own identifier, and its own image specifications.
“Catalog readiness” is the general term for that gap being closed — the product data being complete and correct against one retailer’s requirements, not just internally consistent.
What a retailer commonly requires before a product can go live
The specifics differ by retailer and by category, but most vendor-compliance programs check for the same handful of things before a new item is accepted.
Missing or inconsistent data in any one of these is the most common reason a submission is rejected or held, and it is usually only discovered at submission time unless it is checked beforehand.
- Accurate title, description and attributes (size, color, material, and whatever else the category requires)
- Images that meet the retailer’s own format, background and resolution rules
- A recognized product identifier — a UPC or GTIN is the most common — correctly assigned to the item
- The retailer’s own category and item identifier, which rarely matches a supplier’s internal category
- Pricing and cost data in the format and currency the retailer expects
- Compliance or certification documentation, where the category requires it (safety data, country of origin, hazardous-materials declarations)
Why it is not a one-time task
Catalog readiness is not a single checklist a product passes once. Each retailer sets its own category structure, required fields and identifier rules, so the same product can be ready for one retailer and incomplete for the next. A supplier selling into several retailers is, in effect, maintaining several different versions of “complete” for the same underlying product, and a retailer that changes its own category rules can turn an already-live product back into an incomplete one.
That is why vendor-compliance programs exist in the first place: large retailers found that the cost of bad product data on their own site or in their own supply chain — wrong images, missing safety data, an unmapped category — was high enough to justify checking for it before an item ever goes live, rather than after.
How mPorts fits in
mPorts OMS keeps one product record per item — images, categories, attributes, variants, suppliers and cost, and the identifier each retailer uses — so the readiness work for one retailer does not have to be redone from scratch for the next. Before a launch is submitted, one readiness verdict brings forward what is still missing or incomplete in your own data and mappings.
Products & catalog in mPorts OMSQuestions buyers ask
What does “catalog readiness” actually mean?
That a product’s data meets one specific retailer’s requirements for accepting a new item: accurate attributes and images, the identifier that retailer uses, a mapping to its category and attribute rules, and any compliance documentation its category requires. It is relative to that retailer, not an absolute state a product reaches once.
What happens if a product is not ready?
The retailer typically rejects or holds the submission rather than publishing incomplete or non-compliant data. Depending on the retailer and the program, that can mean a resubmission cycle, a certification test, or a penalty under the vendor-compliance agreement.
Is catalog readiness the same for every retailer?
No. Each retailer sets its own category structure, required fields, identifier rules and compliance requirements. A product that is fully ready for one retailer can still be missing something another retailer requires.
Does mPorts handle catalog readiness for us?
mPorts OMS keeps one product record per item, and shows one readiness verdict per launch so what is missing in your own data and mappings is visible before you submit, rather than after a rejection.