Preview Removal Receipt Remove Impact
GET/api/amazon/:integrationInstance/removal-shipments/:removalShipment/remove-receipt/preview-impact
Read-only preview of the allocation-demotion impact of removing this removal shipment's receipt. Because removing the receipt removes the sellable stock it added back, this behaves like a negative adjustment and returns one row per affected product: how much of the removed quantity is unallocated vs soft-allocated vs hard-allocated, plus every sales-order allocation and fulfillment (printed shipping label) the removal would disturb. Use it to decide which fulfillments to authorize voiding via void_confirmations on the remove-receipt call. Nothing is mutated. A removal that only re-adds free stock returns an empty data array.
Each row is one product the removal consumes stock for. shortfall_quantity is how much more than available the removal takes (stock goes negative if > 0); unallocated_quantity / soft_allocated_quantity / hard_allocated_quantity split the consumed quantity into free / soft-reserved / hard-allocated (label-printed). affected_allocations[] lists the consumed order allocations, highest priority first — allocation_type is soft or hard, and for hard rows fulfillment_id / carrier identify the label with carrier_void_supported / voidable_status (voidable | otherwise) saying whether it can be voided.
Authentication: Requires Bearer token.
Request
Responses
- 200
- 401
- 403
- 404
- 429
Successful response
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.
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.