Customer App experience variants
Customer App can present different experiences depending on the distributed app, the configured business scope, and the current customer journey. Use this reference to understand those visible differences without treating one experience as the default for every customer.
A screen or feature visible in one Customer App does not prove that it is included, authorized, or available in another app, business, account, order, or device context.
Experience scopes
| Experience scope | What the customer may see | Important boundary |
|---|---|---|
| Marketplace | A choice among multiple eligible businesses and their available products or services | The returned list still depends on current location, business availability, customer context, and Ordering.co authorization |
| Franchise | Businesses and choices narrowed to a franchise experience | Franchise scope does not guarantee that every business, product, or feature is available |
| Single business | A journey centered on one business | The business can still be unavailable, closed, unsupported for the current context, or missing a required choice |
| Conditional customer journey | Screens and controls narrowed by account, address, order type, schedule, business capability, device, or permission state | A visible control is presentation only; later authorization and completion remain separate |
These scopes describe customer-visible outcomes. They do not publish build, project, business, provider, or configuration identifiers.
What can vary
- Browse: available businesses, categories, products, services, and offers.
- Location and fulfillment: address requirements, delivery or pickup choices, scheduling, and availability messages.
- Account and checkout: guest or signed-in paths, required profile details, payment candidates, and order prerequisites.
- Conditional experiences: services, reservations, school ordering, gift cards, and existing-order details when supported by the current experience.
- Device presentation: platform controls, permissions, language, screen layout, and external-service handoffs.
Customer App does not establish a customer custom-order initiation flow. Do not interpret a conditional existing-order detail as an option to create a custom order.
Project selection is not a customer procedure
Some app variants include a project-selection concept. Project selection, persistence, switching, restart behavior, and cross-project cleanup are not established as a Customer App customer journey.
Use the app release provided for your experience. Do not enter, guess, switch, or share a project value to make a screen appear. A project field or a stored value does not prove that the target experience is authorized, safe, or fully loaded.
Use the current experience
Before proceeding:
- Use the Customer App release provided for your experience.
- Check the business, address, account, and order choices currently shown.
- Follow only the supported in-app path for that experience.
- Use the final visible result instead of inferring it from a control or handoff.
Do not reuse a private link, identifier, screenshot, or configuration value from another experience to reproduce a feature.
Troubleshooting visible differences
A business or product appears in one experience but not another
Check the app release provided for the experience and visible business scope first. Then check the current address, order type, schedule, and business availability. Do not assume the missing item is a loading defect or entitlement.
The app opens one business instead of a marketplace
The distributed experience may be centered on a single business. Use the navigation currently provided; do not try to force a marketplace by changing private values.
A specialized feature is missing
Treat the feature as unavailable until its business, account, order, device, and authorization prerequisites are established. A feature shown in another app or a customer's screenshot is not proof of availability.
A project field appears or the experience changes after a restart
Project selection and switching are not a supported customer procedure. Do not guess, persist, or repeat a project change to make a screen appear.
Privacy and security
Keep project, business, customer, order, payment, session, provider, and native application identifiers out of public examples, URLs, screenshots, logs, and support tickets. Share only the minimum redacted description of the visible scope and state.
Related references: Customer App overview · Customer App configuration boundaries · Startup, connection, and update states · Language, device, and accessibility considerations