Guide
FBA reason codes
How Skuvelo pairs each change Amazon makes to your FBA stock with Amazon's own reason code, or marks it Unmatched.
When Amazon's figure for an item at its fulfillment centers moves, because a unit was lost or found, the Amazon sync records the difference at your Amazon FBA location. The sync sees only the new figure, not why it moved. Amazon records why as a reason code in its Inventory Ledger report, and Skuvelo reads that report to bring the code across.
Where it shows
On Adjustments, every adjustment at an Amazon FBA location carries a tag under its reason:
- Amazon followed by a code, such as Amazon M or Amazon E, when Skuvelo found the report row that explains the change. The code is Amazon's own, shown exactly as Amazon wrote it. Amazon publishes no list of these codes, so Skuvelo does not translate them; the Inventory Ledger report describes them.
- Unmatched when no report row explains it yet.
Adjustments at your other locations carry no tag. Type unmatched in the search box to list only the ones still waiting for a reason.
The tag is information only: matching a report row changes no quantity, cost or plan, and an Unmatched change counts exactly as a matched one does.
How a change is paired
A report row explains an adjustment when all of these hold:
- it is an Amazon "Adjustments" row for the same Amazon connection;
- the SKU it names is the item's SKU, or an Amazon SKU the sync has matched to the item;
- its quantity is exactly the quantity of the adjustment, with the same sign;
- its date is no more than 7 days before, or 1 day after, the day the adjustment was recorded.
Each adjustment is paired with at most one report row, and each report row with at most one adjustment. When several rows qualify, the one nearest in date wins. A pairing, once made, does not change.
Why one can stay Unmatched
- Amazon has not published the row yet. Skuvelo asks Amazon for the report at most every 6 hours, and Amazon's report itself runs about a day behind, so a fresh adjustment usually shows Unmatched for a day.
- Amazon moved the count in several steps between two syncs. The sync then records one adjustment for the total, which equals none of Amazon's rows, so it stays Unmatched.
- The report row names a SKU that is neither the item's SKU nor a SKU the Amazon sync has matched to it.
- The change is older than 30 days before the connection first read the report.
Try the plan on your own stock.
Start a trial with your own sales and stock, or look around the live demo first.