29 lines
845 B
Markdown
29 lines
845 B
Markdown
# 06 Orders
|
|
|
|
Order flow for POS:
|
|
|
|
- Receive order event
|
|
- Fetch full order payload
|
|
- Accept/deny
|
|
- Resolve fulfillment issues when item(s) cannot be fulfilled
|
|
- Ready/handoff updates
|
|
- Completion/cancellation reconciliation
|
|
|
|
Typed routes:
|
|
|
|
- `GET /api/v1/uber/orders/{orderId}` (order details)
|
|
- `POST /api/v1/uber/orders/{orderId}/fulfillment-issues`
|
|
- `POST /api/v1/uber/orders/{orderId}/ready`
|
|
- `POST /api/v1/uber/orders/{orderId}/action` with action:
|
|
- `accept`
|
|
- `deny`
|
|
- `ready`
|
|
- `cancel`
|
|
- `resolve`
|
|
|
|
Retail fulfillment guidance:
|
|
|
|
- Read customer preference (`REPLACE_FOR_ME`, `SUBSTITUTE_ME`, `REMOVE_ITEM`) from order details.
|
|
- Update issue states via fulfillment endpoint (`FOUND_ITEM`, `PARTIAL_AVAILABILITY`, `OUT_OF_ITEM`).
|
|
- On `orders.fulfillment_issues.resolved` webhook, fetch latest order and continue resolution.
|