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.
Custom-order creation is not a Customer App journey in the product source reviewed for this guide. An order can originate outside Customer App, but an ordinary Customer App customer does not have an in-app creation control.
Review an existing order
The reviewed Customer App source contains a conditional Order Details presentation for an order with a valid positive declared value. Its exact availability in the release environment has not yet been verified. When that source branch is reached, 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 source branch represents an existing-order display, not an initiation or payment flow. The Orders list has no dedicated custom-order label. Source review also found that 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 until the exact order is verified.
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 is expected in the current Customer App. 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 reviewed source can use returned order metadata to select the distinct detail presentation. This source-level behavior is still awaiting runtime and deployment verification, and it does not mean the customer created the order in the app.
Why is the amount in Orders different from Order Details?
Source review shows the Orders card using a base amount while the conditional detail branch can add the declared value to an approximate estimate. Exact list/detail behavior is still under verification. 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 reviewed source, those labels 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