Understand custom orders in Customer App
The current Customer App does not provide a customer-facing control, form, or route for starting a custom order. Do not direct customers to look for a custom order option in business discovery, a menu, a cart, or checkout.
This guide does not establish custom-order creation as a Customer App journey. An order can originate outside Customer App, but an ordinary Customer App customer does not have a documented in-app creation control.
Review an existing order
The documented Order Details flow can conditionally present an existing order with a valid positive declared value. This guide does not establish its availability in every release environment. When the display appears, it can include:
- Declared value returned with the order.
- An approximate Estimated Total that the app calculates from the returned base total and declared value.
- Pickup Address from the order's business snapshot.
- Delivery Address from the order's customer snapshot.
This documented display represents an existing order, not an initiation or payment flow. The Orders list has no dedicated custom-order label. List and detail classification and amount handling can disagree for zero, invalid, missing, or conflicting declared values; do not assume the two screens are equivalent.
The displayed estimate is not proof of a quote, authorization, charge, settlement, final total, or provider result. Use the order state and authorized support channel for questions about pricing or payment.
What customers cannot do here
In the current Customer App, customers cannot:
- Open a custom-order creation form.
- Choose custom-order pickup or delivery details.
- Add custom items or a declared value.
- Draft, submit, place, pay for, or retry a custom order.
Website or Dashboard custom-order controls do not establish the same capability in Customer App.
Troubleshooting
Why is there no custom order option?
This guide does not describe a Customer App creation control. Use the ordinary business/menu journey for supported products, or contact the authorized operator/support channel when a custom request is required.
Why does Order Details show a declared value?
The documented Order Details flow can use returned order metadata to select the distinct detail presentation. This guide does not establish it in every release environment, and it does not mean the customer created the order in the app.
Why is the amount in Orders different from Order Details?
In the documented flow, the Orders card can use a base amount while the conditional detail display can add the declared value to an approximate estimate. Confirm the current order record with authorized support before treating either display as a final payable amount.
Why do the pickup and delivery labels look unexpected?
In the documented flow, those labels can use business and customer address snapshots from the order. They do not prove current geocoding, route validity, fulfillment direction, or provider status. Use authorized support to confirm the current order.
Related guides: View active and past orders · Understand order details and status · Get help with an order · Payment boundaries