Get MCF Order Match Suggestions
GET/api/amazon/unified/fulfillment-orders/:fulfillmentOrder/match-suggestions
Ranked candidate sales orders for one MCF order, scored 0–100 from the signals available: order number match (55), fulfillment reference match (45), tracking match (30), all items on the order with quantities that fit (20), partial item match (8), postcode (10), city (5), order date within 7 days (5); penalties for an already-fulfilled order (−25) and an FNSKU not mapped to a product (−20). Tiers: high (≥90 with no blockers), suggested (60–89, or any candidate that carries a blocker), weak (<60). blockers lists exactly why mapping would be rejected, so a candidate that cannot be linked is never presented as high. line_preview compares each MCF item's quantity with the order's total for that product. Empty for orders that are already mapped or not mappable. The top-level blockers array lists order-level reasons nothing can match (e.g. an FNSKU not mapped to a product, a missing destination address) — shown when the candidate list is empty.
This endpoint currently requires session authentication; Personal Access Token scope support is in progress.
Request
Responses
- 200
- 401
- 403
- 404
- 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.
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.