Get AWD Receipt Assessment
GET/api/purchase-orders/:purchase_order/awd-receipt-assessment
Compare an AWD purchase order's unreceived quantity with Amazon's own AWD shipment record.
purchase-orders:readGrant this scope to your token under Settings → Developer → Personal Access Tokens.
An AWD purchase order is received only from RECEIVED rows on the AWD Inventory Ledger you upload. Amazon's AWD shipment record (synced automatically) carries its own count of cases received. This endpoint sets the two against each other, per merchant SKU, and returns a verdict:
matched— nothing to reconcile.shipment_open— Amazon has not closed the shipment; receipts may still arrive.settling— Amazon closed the shipment, but no uploaded ledger reaches 7 days past the close yet (Amazon posts ledger rows late).settles_afteris the date the uploaded ledger must reach.amazon_confirms_received— Amazon received every case, but its ledger export never posted some of them.can_confirm_receivedis true: close the order with Confirm AWD Receipt.amazon_confirms_short— Amazon received fewer cases than expected and the missing cases match the ledger shortfall exactly: a real loss.can_record_shortageis true: record an inbound shortage on the order's pending inbound.needs_review— the two records disagree in a way neither close can explain (over-received SKUs, a shortfall that is not whole cases, a SKU on no order line, or part loss / part missing rows).reasonsays which.
lines lists only SKUs where the records disagree. Use verdict rather than the order's receipt status to tell a ledger gap from a genuine shortage.
Returns 422 for an order that is not bound for AWD or has no linked AWD shipment.
Authentication: Requires Bearer token.
Request
Responses
- 200
- 401
- 403
- 404
- 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.
Not found — no record with the given identifier (or the route does not exist). Verify the ID before retrying.
Unprocessable Content
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.