39 lines
1.2 KiB
Markdown
39 lines
1.2 KiB
Markdown
# 06 Retail Fulfillment Audit
|
|
|
|
Source checked: Uber Eats "Retail Order Fulfillment API Guide" section shared by you.
|
|
|
|
## Implemented Now
|
|
|
|
- Dedicated fulfillment issues endpoint:
|
|
- `POST /api/v1/uber/orders/{orderId}/fulfillment-issues`
|
|
- Supported issue types in validation:
|
|
- `FOUND_ITEM`
|
|
- `PARTIAL_AVAILABILITY`
|
|
- `OUT_OF_ITEM`
|
|
- Supported action types in validation:
|
|
- `REPLACE_FOR_ME`
|
|
- `SUBSTITUTE_ME`
|
|
- `REMOVE_ITEM`
|
|
- `ALTERNATIVE_ITEM`
|
|
- `SUBSTITUTION_REJECTED`
|
|
- Dedicated order-ready endpoint:
|
|
- `POST /api/v1/uber/orders/{orderId}/ready`
|
|
- Existing webhook handling includes:
|
|
- `orders.fulfillment_issues.resolved` event ingestion + signature verification + dedupe
|
|
|
|
## Existing Before
|
|
|
|
- Get order details endpoint and order actions endpoint
|
|
- Webhook ingestion and `200` acknowledgement
|
|
- Resolve flow available through generic action path
|
|
|
|
## Pending
|
|
|
|
- Exact payload field-level schema parity for all quantity/weight variants from endpoint reference
|
|
- Automated workflow engine:
|
|
- fetch order after `orders.fulfillment_issues.resolved`
|
|
- inspect `customer_ack_type`
|
|
- trigger next fulfillment action automatically
|
|
- Explicit support helper for count-vs-weight conversion rules
|
|
|