Order History
View, search, and manage all orders placed through your storefront. The order history responds to the same global date range filter used across all analytics pages.
Order details
Each order record includes comprehensive information:
- Customer info — Name, phone number, email (if provided).
- Items ordered — Each item with quantity, modifiers selected, and unit price.
- Financial breakdown — Subtotal, tax, discount amount & code, delivery fee, driver tip, and total.
- Order type — Pickup or delivery, with delivery address and distance if applicable.
- Payment method — Online (Stripe) or pay in person.
- Status — Current order status with timestamps.
- Internal order ID — Sequential order number for easy reference.
- Clover order ID — If POS integration is active.
- Delivery tracking — Courier delivery ID and tracking URL for courier-delivered orders.
- Special instructions — Any notes the customer added.
- Recommendation source — Whether any items were added via the recommendation engine.
Screenshot: Order history table with expandable order detail rows
Order statuses
- Pending — Order placed, awaiting confirmation.
- Confirmed — Order accepted by the restaurant.
- Preparing — Kitchen is working on the order.
- Ready — Order is ready for pickup or delivery handoff.
- Picked Up — Customer has collected the order (triggers review request for pickup orders).
- Delivered — Order has been delivered (triggers review request for delivery orders).
- Cancelled — Order was cancelled.
Delivery status tracking
For delivery orders using a courier partner (DoorDash / Uber Eats), additional delivery-specific statuses are tracked:
- Delivery requested — A courier delivery has been created.
- Driver assigned — A driver has accepted the delivery.
- Driver en route to pickup — Driver is heading to your restaurant.
- Driver at pickup — Driver has arrived.
- En route to customer — Driver is delivering the order.
- Delivered — Driver confirmed drop-off.
Note: For active courier deliveries, manual delivery status changes are blocked to prevent conflicts with the automated webhook updates.