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 five counters at the top — In sync, With discrepancies, Pending publish, No internal data and Not checked — act as a filter: click one to see only those products.
| State | Counter | Meaning |
|---|---|---|
| 🟢 In sync | In sync | The internal content matches what is published. |
| 🟠 Discrepancy | With discrepancies | Internal differs from public: Amazon does not yet reflect your content. |
| 🔵 Pending publish | Pending publish | Edited in Epinium and not yet published to Amazon. |
| ⬜ No data | No internal data | The field is empty on your internal side (Central): you never worked on it, so there is nothing to compare. |
| ⚪ Unchecked | Not checked | 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). It only exists at field level. |
No internal data: an empty field is not a discrepancy
If Amazon shows content in a field you have never worked on in Seller/Vendor Central, that field is flagged as No data, not as a discrepancy, and the product counts towards the No internal data counter. This is very common in reseller catalogs, where the listing content is controlled by the brand owner: there is no point claiming from Amazon something you never published.
Read the other way round, that counter is a list of opportunities, not of problems: they are products whose SEO you have not worked on yet. Click it, open any diff and you will see what Amazon is publishing in those empty fields.
The opposite case is a discrepancy
If you have content in Central and the public listing is empty, Amazon has not applied your work: that is flagged as Discrepancy and can be claimed.
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).
- Content origin — separates what you worked on from Epinium from what came from outside (see below).
- Case-eligible only — keep only the products that already meet the criteria to open a case with Amazon (see below). It is on by default when you open the section.
- Clear filters — appears as soon as something is active and returns the view to its initial state, including the selected status counter and the +72 h filter.
Content origin: did you write it, or did it come from outside?
This filter does not look at whether the field is in sync, but at who wrote the internal value that is there right now:
- Worked in Epinium — the last change to that field came from Epinium (your manual edit, a bulk change or the AI).
- External origin — the current internal value did not come from Epinium: it was changed directly in Central or brought in by the Amazon sync.
Because it is independent from the status, it combines with the counters at the top:
| Counter + origin | What you get |
|---|---|
| With discrepancies + Worked in Epinium | You published it and Amazon has not applied it → this is what you can claim. |
| Pending publish + Worked in Epinium | All your work not yet uploaded to Amazon. |
| In sync + Worked in Epinium | Your work that did take effect. |
| With discrepancies + External origin | Discrepancies you did not create. |
In the table, fields worked from Epinium show a pencil icon next to their status, so you can see at a glance which columns are yours.
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, but the other side is still displayed: on a field flagged as No data you can see what Amazon is publishing even when you have nothing in Central.
- View in store — opens the product's public Amazon page in a new tab.
Force as pending to publish
When you have many discrepancies whose internal content is correct —you wrote it and Amazon hasn't applied it—, there's no need to edit them one by one: you can force them in bulk so they move to Pending to publish and get re-sent to Amazon.
Access: the Force as pending to publish button, top-right of the section.
It's a two-step process:
- Mark (here) — you select discrepancies and mark them as pending to publish. Nothing is sent to Amazon yet.
- Publish (in the catalog) — you go to Catalog → Products and publish the pending changes, which is what uploads them to Amazon.
What to select
- Check specific rows with the checkbox on the left —only rows in discrepancy are selectable— and the selection persists across pages.
- With no row checked, the button acts on all products matching the table's current filters (it asks for confirmation with the count).
The force dialog
Clicking the button opens a dialog where you set the scope:
- Choose which fields to re-send (Title, Item Highlights, Bullets, Description). You must pick at least one to continue.
- Optionally narrow by content origin (only what was worked in Epinium, or only external).
- Case-eligible only (>72h unapplied in Amazon) is checked by default; uncheck it to also include more recent discrepancies.
- You'll see how many products will be marked before confirming.
Only discrepant fields are forced
Even if you check every field, each product only marks the ones actually in discrepancy. A field that's already synced, pending or without internal data is ignored: empty content is never re-sent and fields that are already fine are never overwritten.
After forcing, those products move to the Pending to publish counter; the final step —sending them to Amazon— is done by publishing the changes from the catalog.
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 opens a dialog where you choose the shape of the file, and generates an Excel ready to attach to Amazon cases:
- Respects the table's active filters (connection, country, search, field and content origin).
- Includes only eligible products (in discrepancy and older than 72 h) and only the fields in discrepancy.
- Groups the rows by country, so there are no jumps from one marketplace to another between cases. A case never mixes two countries: the message is written in the marketplace's language and opened in its Central.
- The Summary sheet recaps the filters applied, the settings you chose, how many cases were exported and, if anything was left out, how many discrepancies and why.
- The file is generated in the background and arrives by email, and is also available under Downloads.
Configurable settings
Clicking the button opens a dialog with two settings. If you leave them alone, the Excel comes out exactly as before.
| Setting | What it does | Default |
|---|---|---|
| Products per case | How many ASINs are grouped into a single case, from 1 to 5. Amazon does not allow more than 5. | 5 |
| How fields are split into cases | For each field: Separate (generates its own case) or Group A / Group B (claimed together with the other fields in that group). | Separate |
Below the settings, the dialog shows you the cases that will come out — for example Title + Item Highlights · Bullet points · Description — so you see the result before exporting.
Lower the products per case if the message does not fit
The case creation form in Seller/Vendor Central accepts little text, and a case with 5 products overflows it easily. Lowering this number shortens the message.
Even so, with long fields — titles, bullet points or descriptions — it may not fit even with 1 product per case: the content itself already exceeds the limit. There you will have to trim the message by hand when pasting it.
Group the fields that go together
Title and Item Highlights are usually worked on at the same time, so claiming them in one case saves you opening two. Put them in the same group.
Bullet points and description are much longer: leave them Separate so their case does not blow up in size.
The Excel may bring fewer discrepancies than you see in the table
If you filter by field or by origin, the Excel only brings those fields: a product showing discrepancies in both title and bullets in the table may generate a single title case.
Nothing is lost — the other discrepancies stay in the table, and clearing the filter and exporting again is enough to claim them.
The button tells you before you download, in two levels: with any active filter it turns into Export filtered cases with a counter of the filters that travel to the Excel (connection, country, search, field and origin — the status counter and the +72 h toggle don't count, because the export always applies them). And when the narrowing comes from field or origin — the ones that make the file omit discrepancies you can see in the table — the button turns amber. The full detail shows on hover, is repeated inside the export dialog, and is written down in the Summary sheet of the Excel.
With the Worked in Epinium filter this is also mandatory: the case message states that you published that content, so including a field you never worked on would mean claiming something untrue from Amazon.
The most useful combination
Turn on Case-eligible only + Content origin: Worked in Epinium before exporting. That way the Excel only contains the cases that really are Amazon's responsibility: content you published that is still not applied.
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.