Preview FBA Reimbursement COGS
GET/api/amazon/unified/fba-reimbursement-cogs/preview
Shows what reimbursed-unit COGS posts for one Amazon account, without writing anything. When the account's reimbursed-unit COGS setting is off, this is what turning it on would post.
This endpoint currently requires session authentication; Personal Access Token scope support is in progress.
Returns one row per settlement period and kind (reimbursed, or reversed for a clawback) with its units, the cost that would move to the reimbursed-units COGS account (base currency), what Amazon paid (in the payout currency), the accounts the cost is credited from (the account each loss was actually expensed to), and a status: would_post, held (dated in a locked accounting period) or before_start (dated before the inventory start date, so opening balances already carry it).
Only cost already sitting in a loss account moves: the FIFO cost an inventory-ledger loss consumed, or for an inbound loss, what the recorded inbound shortage wrote off. not_moved lists every other payment grouped by reason:
waiting— not on a settlement yet and under 60 days oldsupplement— a top-up of an earlier paymentreplacement— Amazon replaced the units instead of payingcustomer_return— the unit was sold, so its cost is already in COGS on the orderinbound_before_tracking— an inbound loss Amazon paid for before inbound shipments were tracked, so no shortage was written offinbound_unrecorded— an inbound shortage Amazon paid for that was never recorded on the shipmentinbound_partial— a recorded shortage covers only some of the units the payment is forunlinked— not matched to a lossuncosted— matched to a loss that has no cost yetother— paid for a loss SKU.io does not book as an inventory loss, such as a unit lost on its way to a customer or into AWD
Query parameters:
integration_instance_id(required) — the Amazon integration ID.
Request
Responses
- 200
- 401
- 403
- 422
- 429
OK
Response Headers
Unauthenticated — the bearer token is missing, revoked, expired, or malformed. Never retry automatically; fix the credential. See the Errors guide.
Forbidden — the token lacks a required scope, the endpoint is not available to API tokens, or the user behind the token lacks the permission. A human must adjust the token scopes or user permissions; do not retry.
Unprocessable Entity
Response Headers
Rate limited — platform limit is 1,000 requests/min; individual tokens may carry lower limits. Honor the Retry-After header before retrying. See the Rate Limits guide.