Website overview
The Ordering.co Website is a customer-facing storefront. Customers can discover available businesses, choose products, complete checkout, and return to manage their account and orders.
The pages and controls customers see depend on Website mode, project configuration, enabled capabilities, business availability, and whether the customer is signed in. Your Website can therefore differ from the examples in this guide.
Follow the customer journey
Customers normally establish an ordering context, find an available business, choose products, review the cart, and complete the checkout steps that apply to their order. The screenshots below are illustrative. Use the labels, fields, and actions that the current Website displays.
1. Enter a location
Select the location field or the available search action, then enter and complete the requested address information. Website can request an apartment or suite, postal code, or location notes when the current configuration requires them. A selected address establishes the current shopping context; it does not confirm delivery coverage, inventory, or checkout readiness.
For current address rules and validation, see Choose a location and order type.
2. Choose an order type
Choose one of the fulfillment types currently offered by the Website, such as Delivery or Pickup. A Website can offer other configured types, including Eat in, Curbside, or Drive thru. The selection can change the businesses, menus, schedules, address requirements, fees, and checkout fields available to the customer.
3. Browse businesses returned for the current context
Website can list businesses that match the selected location, order type, and ordering time. Select a business to open its page. A listing is not a complete directory of every business connected to a project, and a business shown on one visit can be absent after the ordering context changes.
Use Browse available businesses for result cards and empty states.
4. Choose and customize products
Open an available business menu, select a product, review its current description and options, and complete any required choices before adding it to the cart. Product availability, prices, ingredients, options, limits, and instructions are determined by the current business and order context.
For the current product form, see Customize and add a product.
5. Review the cart
Open the cart to review the products, quantities, current pricing rows, and any available comments or suggested products. Update or remove a product only when the current cart exposes that action. Select Checkout only when the customer is ready to continue to the separate checkout flow.
See Manage a cart for cart-specific actions and warnings.
6. Complete checkout
At checkout, review the customer, business, fulfillment, product, and total information shown for the current order. Select only one of the payment methods currently available. A tip, coupon, cash-information field, provider prompt, or other checkout control appears only when the current order supports it.
Selecting a payment method prepares the order; selecting the final submission action is the event that requests order placement. A visible amount, payment choice, or submission button does not prove that payment or fulfillment has settled. See Complete checkout.
7. Read the submission result
After the customer submits the order, Website can show a confirmation and the returned order information. Read the displayed status and the current order details instead of treating a confirmation layout as a universal payment, acceptance, or delivery guarantee.
8. Follow the order
Open the order details or Your Orders action when it is available to review the latest returned status, saved products, totals, and fulfillment information. Status updates, messaging, maps, and driver information are conditional; a visible action is an entry point, not a delivery or communication guarantee.
For current order details and status boundaries, see Review order details and tracking.
Responsive experience
Website adapts its navigation and content to the customer's screen. Desktop layouts can show more information side by side, while mobile layouts prioritize the controls needed for the current step.
Customers can continue the same shopping journey on either layout, but the position of navigation, filters, carts, and supporting details can change.
Website modes
Website supports different customer experiences:
- Marketplace — Customers select from multiple available businesses.
- Single store — Customers enter a storefront focused on one configured business.
- Franchise — Customers can be guided into a participating franchise location.
- Kiosk — The experience is optimized for an in-person ordering context and can limit controls that are unnecessary on a kiosk.
The mode affects entry routes, business selection, navigation, and some account or fulfillment controls. It does not guarantee that every optional capability is enabled.
See Understand Website presentation modes for representative desktop and mobile journeys.
What controls the experience
Customer-visible behavior can be influenced at several levels:
- Project — Website-wide branding, navigation, languages, authentication, checkout, and enabled capabilities.
- Business — Menu content, schedules, order types, service area, prices, taxes, fees, and payment availability.
- Customer session — Saved addresses, favorites, carts, account details, and authentication state.
- Order context — Selected location, order type, schedule, business, and cart contents.
- External provider — Payment, mapping, messaging, loyalty, or other integrated handoffs.
Before testing your Website
- Test the journey in a private browser window so saved customer state does not affect the result.
- Check both desktop and mobile layouts.
- Test each order type and business schedule that your project supports.
- Use a test project or approved sandbox payment method when you need to verify checkout.
- Never place, cancel, or modify a production order only to test documentation or configuration.
When a customer sees a different result
First confirm the customer's location, selected order type, authentication state, business schedule, and active cart. If the difference remains, review the relevant project and business configuration in Dashboard.
For customer-visible support topics, configured informational pages, the Site Map, and localized footer content, see Use Help and project content pages.
Some Websites also expose public onboarding for prospective operators. See Apply as a business owner or driver when those application links are available.
Developer reference: Website URLs and deep links · Experience and configuration