Create Shortage from Pending Inbound
POST/api/amazon-pending-inbounds/:pendingInbound/create-shortage
Create an inbound shortage record from a pending inbound.
This endpoint currently requires session authentication; Personal Access Token scope support is in progress.
Allowed only when the shortfall is a confirmed loss. For FBA, the Amazon inbound shipment must be closed and the ledger synced. For an AWD purchase order, Amazon's AWD shipment record must confirm the missing cases and they must match the ledger shortfall exactly — check can_record_shortage on Get AWD Receipt Assessment first. When Amazon instead confirms every case arrived, close the order with Confirm AWD Receipt; a shortage there would write off stock Amazon holds.
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.
Validation failed — the body is a field → messages map (Laravel shape) or the platform envelope with a stable machine-readable code. Fix the payload and resubmit.
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.