Can your paper trail explain why old stock was still being sold?
If a seller bought units 14 months ago, kept them in stock, and sold through them over time, the sourcing question is simple: can the records show that those units plausibly remained in inventory and were not replaced by unverified stock? ([Octo methodology])
That is the operational gap behind a large share of authenticity-document panic. The problem is not always that the goods are fake. The problem is that the paperwork set was built for buying, not for defending provenance.
Amazon seller-facing help pages and document requests commonly indicate that invoices and related supply-chain documents may be requested in authenticity reviews. That is the official signal relevant here. But those materials do not provide a seller-side method for reconstructing the inventory story when the buying date and selling date are far apart. [Bucket 1: Amazon seller-facing documentation]
So buyers end up arguing from memory.
Memory is not a document trail.
What is the Octo Inventory Continuity Stack?
Use this as a sourcing and document-screening method before you assume the issue is the invoice date alone.
| Layer | What to collect | What it suggests |
|---|---|---|
| 1. Source document | Supplier invoice, PO, payment record | The stock was purchased from a named source |
| 2. Receipt evidence | Receiving log, warehouse intake, 3PL check-in, FBA shipment creation | The units entered your control at a specific time |
| 3. Movement record | FBA shipment history, transfer logs, replenishment records | The inventory moved in a traceable path, not a paperwork gap |
| 4. Quantity bridge | Beginning stock, units received, units sold, units remaining or depleted | The math supports continuity across the review window |
| 5. Supplier identity check | Business identity match, brand authorization if relevant, contact consistency | The seller paper points to a real commercial source, not a loose invoice file |
This stack does not prove an appeal will succeed. It helps set the burden of proof. The weaker the continuity between purchase date and sale date, the more supporting evidence the seller needs to show.
If you are screening distributor risk upstream, the same logic applies in supplier review, not just in appeals. See Octo’s supplier assessment and monitoring approach here: supplier assessment and monitoring.
What usually breaks in these cases
Three failure patterns commonly show up in practitioner-reported cases and document reviews.
1) The invoice is real, but isolated
Sellers sometimes have a legitimate invoice but nothing around it: no intake record, no shipment trail, no stock ledger, no quantity bridge. In that situation, the invoice shows the seller bought something. It does not plausibly show the sold units came from that purchase. ([Octo methodology])
2) The quantities do not reconcile
If the invoice shows 500 units, but the account sold 900 units in the relevant period, the paper stack has a hole. That hole may have an innocent explanation such as prior stock, multiple replenishments, or a second supplier. But the quantity mismatch is still the first thing to test. Watch the stack, not any single document.
A simple example: beginning stock 300 units, new invoice 500 units, total available 800 units. If sales in the review window were 620 units and 180 units remain, the bridge is internally consistent. If sales were 900 units with no second replenishment shown, the continuity story breaks.
3) The supplier exists, but the paperwork is weak
This is common with trading companies, gray-market distributors, and invoice-only resellers. A document can look clean and still fail the credibility test if the supplier identity is thin, the contact details drift across files, or the seller cannot show a stable commercial relationship. Named third-party databases such as business registry records, customs data vendors, and brand authorization records can help screen that risk. [Bucket 2: named third-party verification sources; Bucket 4: Octo methodology]
What should you collect before the next complaint?
The best time to build continuity is before a listing gets challenged.
Keep the PO, invoice, payment proof, receiving record, and shipment record in one file set per SKU. If the product is sourced through a distributor, screen the distributor the same way you would screen a factory-facing vendor: legal entity, contact consistency, product scope, and repeatability. A supplier paper trail is only useful if the documents agree with each other.
Mini-checklist: Practical checklist
- Match each SKU to its PO, invoice, and payment proof
- Save receiving records showing when units entered your control
- Keep FBA shipment creation, transfer, or replenishment records by batch
- Build a simple quantity bridge: beginning stock + receipts - sales = ending stock
- Check that supplier name, address, and contact details are consistent across documents
- Flag any period where units sold exceed documented available inventory
- If using a distributor, verify the legal entity and product scope before a complaint forces the review
Walk away from any source that says, in effect, "the invoice should be enough" but cannot support the rest of the chain.
That is not a paperwork issue. It is a sourcing issue.
What does this Reddit signal suggest for buyers?
The r/FulfillmentByAmazon post is not evidence of a universal Amazon rule outcome. It is a high-intent seller pain signal. [Bucket 3: Reddit seller report]
The signal is this: invoice-date mismatch becomes dangerous when inventory continuity is undocumented.
That has two sourcing implications.
First, buyers who source through distributors need stronger record discipline than they think. Distributor paper can be commercially real and still be operationally weak in a review.
Second, long inventory cycles create document risk. The longer units sit, the more important it is to preserve receiving and movement records that bridge the gap between purchase and sale. ([Octo methodology])
If your current supplier stack cannot explain where today's sellable inventory came from, the problem started before the complaint.
Sources and notes
- Bucket 1 — Official: Amazon seller-facing authenticity and invoice-document request materials, referenced here only as context for the types of documents Amazon may request in seller reviews.
- Bucket 2 — Named third party: Business registry records, customs-data vendors, and brand/distributor verification sources used in supplier screening workflows.
- Bucket 3 — Seller report: r/FulfillmentByAmazon post
1tjazai— seller-reported authenticity complaint tied to invoice timing and past-365-day sales window. - Bucket 4 — Octo methodology: The Octo Inventory Continuity Stack is an internal sourcing framework for testing whether a document set tells one continuous inventory story.
This article is sourcing intelligence, not legal, customs, or regulatory advice. Consult a licensed customs broker, attorney, or specialist for compliance decisions.