Discrepancy control

Access from the menu: Catalog → Discrepancy control

Discrepancy control compares, field by field, the SEO content you work on in Amazon (your internal side in Seller/Vendor Central) against what is actually published and live on the public Amazon listing. It lets you see at a glance which products do not reflect what you optimized on the live page.

It is common to publish a change (title, bullets…) and have Amazon not apply it: it ignores it, takes days, or rewrites it with its own AI. This section tells you exactly on which products and which fields that happened.

The two sides of the comparison

Side	What it is
Internal · Central	The content stored in Epinium / Seller Central / Vendor Central (what you want shown).
Public · Amazon	The content Amazon actually shows on the product's public page (what is shown).

Fields that are compared

For Amazon these SEO fields are audited:

Field	Compared
Title	Yes
Item Highlights	Yes
Bullets (bullet points)	Yes
Description	Yes (with caveats — see below)
Search terms	No — Amazon no longer exposes public search terms, so they cannot be compared.

Description special cases

• A+ content active → the description is managed from A+ rather than the plain text, so it is considered in sync (no discrepancy is flagged).
• Vendor products → Amazon does not expose the public description on vendor, so that field shows as not checkable.

States

Each product gets an overall status (its worst field wins) and each field has its own. The counters at the top act as a filter: click one to see only those products.

State	Meaning
🟢 In sync	The internal content matches what is published.
🟠 Discrepancy	Internal differs from public: Amazon does not yet reflect your content.
🔵 Pending publish	Edited in Epinium and not yet published to Amazon.
⚪ Unchecked	Data (public or internal) has not been collected yet to compare.
⚫ Not checkable	A field this marketplace does not allow comparing (e.g. search terms, or the description on vendor).

Filters

The table toolbar offers:

• Connections — narrow to one or several Amazon accounts (Seller / Vendor).
• Countries / marketplaces — automatically limited to the selected connections.
• ASIN / SKU search — find a specific product.
• Field filter — show only products with a problem in a specific field (e.g. Title — Discrepancy).
• Case-eligible only — keep only the products that already meet the criteria to open a case with Amazon (see below).

View a product's detail

Each row has two actions:

• View diff — opens a side-by-side comparison (internal ↔ public) highlighting word by word what differs. If one side has no content, it shows "No content" instead of comparing.
• View in store — opens the product's public Amazon page in a new tab.

Amazon cases (+72h indicator)

When Amazon does not apply an SEO change you already published, the next step is to open a case in Seller/Vendor Central to claim it. A product is considered case-eligible when it remains in discrepancy and its Amazon listing has not been updated for more than 72 hours (Amazon had plenty of time to apply the change and did not).

The last-updated column shows an indicator based on age, only for products in discrepancy:

Indicator	Age	Meaning
🕒	< 24 h	Amazon may still be propagating the change.
⏳	24–72 h	Grace period.
🔴	≥ 72 h	Eligible to open a case with Amazon.

Export cases to Excel

The export cases button generates an Excel ready to attach to Amazon cases:

• Respects the table's active filters (connection, country, search, field).
• Includes only eligible products (in discrepancy and older than 72 h) and only the fields in discrepancy.
• Groups ASINs per case (Amazon allows up to 5 ASINs per case), with the current and requested text for each.
• The file is generated in the background and arrives by email, and is also available under Downloads.

How the flow works

Data requires a prior analysis

A product only shows a status once it has been analyzed. Products never audited appear as Unchecked until Epinium collects and compares their data.