Uber Eats: see the courier before the order is Ready

Overview

• MiniTill refreshes active Uber fulfilment/courier data through the current Uber Eats Order Fulfillment API 1.0.0 workflow.
• When Uber exposes tracking for the order, KDS can show courier state, distance, and ETA.
• Crucially, MiniTill does not require the restaurant to press Ready first before showing that courier information. If Uber supplies the tracking data early, KDS can surface it while the order is still being prepared.
• This gives the kitchen extra context—for example, seeing that a courier is already close while several minutes of preparation remain.
• Courier tracking is provider-supplied data. It may not be available for every order or at every point in the delivery lifecycle.

When to use this

• Use courier information to understand pickup pressure and sequence work, not as a replacement for the promised preparation target.

Step-by-step

1. Open the active Uber order in KDS.
2. Check courier status when shown.
3. Review distance and ETA alongside the order's remaining preparation time.
4. If the courier is close, use that information to coordinate packing/handoff while still completing the order correctly.
5. Press Ready only when the order is actually ready.

Common mistakes

• Do not assume 'no courier shown' means Uber has not assigned one; tracking may simply not be exposed yet.
• Do not mark Ready early just to make courier tracking appear—MiniTill can show tracking before Ready when Uber provides it.
• Do not treat courier ETA as perfectly fixed; it is external live data and can change.

Troubleshooting

• If courier information is absent, continue using the preparation target and refresh cycle; availability depends on Uber data.
• If tracking looks stale, confirm network/integration status and allow the normal active-order refresh to update provider data.