Use this marketplace product compliance checklist to verify the documents, product rules, labels, claims, and approvals required before a SKU goes live. It gives sellers a repeatable workflow for checking restricted products, collecting supplier evidence, comparing marketplace requirements, and recording a clear launch decision.
Overview
Product compliance is not a single certificate or final inspection. It is the process of showing that a product can be legally offered in a specific market, accurately described, safely packaged, and accepted by the marketplace where it will be listed. Requirements can vary by product category, destination country, intended user, materials, claims, and sales channel.
Before creating a listing, separate three questions:
- Can the product be sold? Check laws, restricted-category rules, import requirements, and any required registrations or approvals.
- Can this seller offer it? Confirm brand authorization, reseller permissions, intellectual property rights, and marketplace account requirements.
- Can the listing support its claims? Match titles, images, specifications, certifications, safety statements, and marketing claims to evidence held for the exact SKU.
A marketplace approval is not necessarily proof that a product meets every legal requirement. Treat platform approval and regulatory compliance as related but separate workstreams. For complex, regulated, or cross-border products, obtain advice from an appropriately qualified compliance professional before launch.
For broader operational controls, pair this checklist with the Marketplace Account Health Checklist and the Marketplace Seller Agreement Checklist.
What to track
1. Product category and restricted-product status
Start with the product itself, not the listing copy. Record the product category, intended use, user age range where relevant, materials, power source, contents, and destination markets. Then check the marketplace's current restricted-product and approval guidance.
Flag products that may require additional review, such as those containing batteries, chemicals, food or ingestible ingredients, cosmetics, medical or wellness claims, children's features, weapons-related components, animal-derived materials, or branded goods. Do not assume that a product is unrestricted because a similar item appears in search results.
2. Documents and evidence
Create a document register for each SKU or product family. Depending on the category and jurisdiction, the relevant evidence may include:
- Manufacturer or supplier declarations
- Laboratory test reports tied to the exact product, model, or batch
- Safety, quality, or conformity certificates where applicable
- Material, ingredient, or composition information
- Battery, electrical, chemical, or transport documentation where relevant
- Product photographs showing required labels and warnings
- Country-of-origin and importer information
- Brand authorization, distribution agreements, or invoices supporting authenticity
- Insurance or business documents requested by a marketplace
Check that each document identifies the correct manufacturer, model, SKU, product version, test standard, issue date, and applicable market. A generic report for a similar product may not support the SKU you intend to sell.
3. Labels, packaging, and instructions
Review the physical product and its packaging separately from the product page. Confirm that required warnings, instructions, symbols, units of measurement, contact details, traceability information, and language versions are present where applicable. Product images should not hide, alter, or contradict required information.
Also check packaging claims. Statements such as “recyclable,” “natural,” “non-toxic,” “waterproof,” “child-safe,” or “made from recycled materials” should be used only when the seller can substantiate them and the wording is appropriate for the destination market.
4. Claims and listing accuracy
Build a claims-to-evidence log. For every material claim in the title, bullets, description, image text, comparison chart, or advertising copy, record the document or specification that supports it. Remove unsupported superlatives, health outcomes, performance promises, and environmental claims.
Make sure the listing also matches the shipped item. Differences in color, size, count, included accessories, formulation, packaging, or model number can create both customer complaints and compliance questions.
5. Marketplace comparison
Requirements should be compared before the catalog is duplicated across channels. Use a simple marketplace compliance comparison table:
| Checkpoint | Marketplace A | Marketplace B | Seller action |
|---|---|---|---|
| Restricted-category approval | Required, unclear, or not applicable | Required, unclear, or not applicable | Confirm through current seller guidance before submission |
| Required documents | List the requested evidence | List the requested evidence | Map each document to the exact SKU |
| Label and image rules | Record format and content requirements | Record format and content requirements | Prepare channel-specific assets if needed |
| Brand or authenticity review | Record approval path | Record approval path | Keep authorization and purchase records together |
| Renewal or change triggers | Record known triggers | Record known triggers | Assign an owner and review date |
Use “not confirmed” rather than “not required” when the rule has not been verified. That distinction prevents assumptions from entering the catalog.
SKU approval checklist
- Product category and intended use are documented.
- Restricted-product and marketplace approval rules have been checked.
- Supplier identity, manufacturer details, and model information are recorded.
- Required tests, certificates, declarations, and material records are available.
- Labels, warnings, instructions, packaging, and language requirements have been reviewed.
- Every material listing claim is supported by a specification or evidence file.
- Brand authorization and authenticity records are stored where relevant.
- Country-specific requirements have been reviewed for each intended destination.
- Inventory, packaging, and listing data describe the same product version.
- A named reviewer has approved or rejected the SKU.
Evidence-request template
Send suppliers a specific request rather than asking for “all compliance documents.” For example:
Please provide the current documents for product [SKU/model], including manufacturer details, applicable test reports or declarations, material or ingredient information, label and packaging images, country-of-origin information, and any marketplace-specific evidence available. Each file should identify the exact product version and include its issue date, issuing organization, and applicable market. Please also confirm whether the product, packaging, or formulation has changed since the documents were issued.
Document storage
Use one controlled folder or compliance system per product family, with a consistent naming convention such as SKU_document-type_market_version_date. Keep the source file, a review note, the document owner, expiration or review date, and the marketplace submission record together. Restrict editing permissions and retain superseded files rather than silently replacing them.
Cadence and checkpoints
Compliance checks should happen at several points, not only on launch day.
- New SKU: Complete the full checklist before inventory is committed or the listing is submitted.
- New marketplace or country: Recheck restricted categories, labeling, taxes or import documentation, claims, and seller eligibility. Use the Marketplace Expansion Readiness Checklist for the wider channel review.
- Supplier change: Confirm that the manufacturer, materials, formulation, factory, test basis, and packaging have not changed in a way that affects existing evidence.
- Packaging or artwork change: Compare the old and new files, then reassess warnings, claims, recycling statements, instructions, and product images.
- Monthly operational review: Log new listing suppressions, document requests, customer safety complaints, returns citing product mismatch, and any repeated catalog errors.
- Quarterly document review: Check owners, dates, missing files, marketplace guidance, and open corrective actions.
- Immediate review: Reassess after a regulatory notice, marketplace policy change, safety incident, supplier alert, product recall, or material complaint.
Assign one accountable owner for each SKU, even when several teams contribute information. A shared tracker should show status, last review date, next review date, unresolved issues, and the person responsible for closure.
How to interpret changes
Not every change requires the same response. Classify findings so the team can act proportionately:
- Informational: A document has a new format or a marketplace has clarified instructions, but the product and evidence remain aligned.
- Corrective: A label, image, claim, attribute, or document is incomplete and must be fixed before continuing promotion or listing.
- Blocking: The product may be restricted, evidence does not match the SKU, authorization is missing, or a safety concern is unresolved. Pause the listing or affected inventory until reviewed.
Look for patterns rather than isolated events. Several requests for the same certificate may indicate weak supplier controls. Repeated listing suppressions may point to a catalog attribute problem. A rise in returns related to size, contents, or packaging may show that the product page no longer matches the shipped version.
When a change affects multiple channels, record a single source decision and then document channel-specific actions. For example, a packaging update may require new images everywhere, while a marketplace's upload format may require a separate submission. Keep the reasoning and evidence attached to the decision.
When to revisit
Revisit this marketplace product compliance checklist before every new SKU, new country, new marketplace, supplier change, packaging change, formulation or material change, and compliance audit. A practical minimum is a monthly operational scan and a quarterly document review, with immediate checks after a marketplace rule update or product incident.
Use this launch sign-off form for each SKU:
After sign-off, preserve the evidence set used for the decision and connect it to the catalog record. If you sell across several channels, review your feed and attributes with the multi-marketplace product catalog checklist. If a connector or inventory tool is involved, confirm that compliance-critical attributes are not being dropped during synchronization by using the marketplace integration tool comparison checklist.
Compliance is easiest to manage when it is treated as a recurring catalog control rather than a one-time upload task. Keep the register current, record decisions clearly, and pause uncertain listings until the product and its evidence tell the same story.