Plan the parts of ordering that need to work together.
Explore customer ordering surfaces, the work behind an order and the systems your team needs to evaluate. The right configuration depends on the channels, locations and partners selected for your project.
01 · Build
Choose the customer ordering surface.
Start with the place customers will order, then identify the menu, store and service choices that need to be configured for that experience.
- Ordering WebExplore a branded website ordering journey for your project.
- Ordering AppsExplore the app experience and its project requirements.
- Ordering KioskExplore self-ordering touchpoints for an in-store journey.
- Ordering Call CenterExplore assisted ordering for teams that take orders by phone.
- MarketplacesExplore marketplace workflows and the commercial model they require.
- Multi-store orderingExplore how a multi-location ordering journey can be scoped.
- NewAI Ordering AgentsExplore conversational ordering surfaces and their configuration needs.
02 · Operate
Map the work behind an order.
Identify the store workflow, fulfillment handoff and team visibility your operation needs before selecting the products and connections to configure.
- Ordering MerchantExplore the order-handling workflow for stores and teams.
- Order managementReview the order states and operational touchpoints relevant to your stores.
- Multi-location operationsExplore the operating questions that emerge across locations.
- Ordering DeliveryExplore delivery operations, including the responsibilities your team keeps.
- Driver App & dispatchExplore driver-facing workflow requirements before configuring delivery.
- Third-party deliveryExplore partner delivery choices and their operational dependencies.
03 · Connect
Identify the systems that need to connect.
Use the integration layer to identify the point of sale, payment, delivery and customer systems that require a project-specific compatibility review.
- POS integrationsReview the point-of-sale connection needed for your stores.
- Payment gatewaysReview payment providers, settlement responsibilities and regional requirements.
- Delivery networksReview the delivery networks and service areas relevant to the project.
- Loyalty & CRMReview the customer-data and communication connections your operation requires.
- Analytics & reportsReview the reporting questions your team needs to answer.
- All integrationsReview the integration categories that should be evaluated for your project.
04 · Extend
Discuss how the platform should extend.
For technical teams, the extension conversation starts with the customer surface, data flow and responsibilities that the project needs to preserve.
- Ordering APIReview the API surface and implementation scope with the technical team.
- SDKs & webhooksReview event and integration requirements before choosing an implementation path.
- White labelDiscuss brand expression and customer-facing requirements for your white-label deployment.
- Reseller platformDiscuss operational and commercial responsibilities for a partner model.
- Source code licenseThe open-source frontend code included with every product.
- Custom solutionsDiscuss product and operational requirements beyond our standard products.
Planning guide
Start each product conversation with the right question.
The table organizes the questions a team can bring to the relevant product discussion. Confirm specific capabilities, availability and dependencies during solution design.
Scroll sideways to compare the product discussions.
| Planning question | Web | Apps | Kiosk | Call Center | AI Agents | Merchant | Multi-location | Delivery |
|---|---|---|---|---|---|---|---|---|
| Customer ordering journey | Discuss this topic | Discuss this topic | Discuss this topic | Discuss this topic | Discuss this topic | Discuss in another product area | Discuss in another product area | Discuss in another product area |
| Store and fulfillment workflow | Discuss in another product area | Discuss in another product area | Discuss in another product area | Discuss in another product area | Discuss in another product area | Discuss this topic | Discuss this topic | Discuss this topic |
| Technical and commercial dependencies | Discuss this topic | Discuss this topic | Discuss this topic | Discuss this topic | Discuss this topic | Discuss this topic | Discuss this topic | Discuss this topic |
One infrastructure
Use one planning map across the customer journey.
The map helps teams discuss the customer touchpoints, store workflow and connections your project needs to validate together.
- Web
- App
- Kiosk
- Phone
- AI agent
- Merchant App
- POS
- Drivers
- Loyalty & CRM
Map the platform around your operation.
Use a demo to identify the customer surfaces, operating workflows and connections that should be validated for your project.