Your restaurant app. Crave’s ordering engine.
Build a custom ordering website or mobile app without building the commerce backend from scratch. You create what guests see and use. Crave provides the APIs behind menus, item customization, pickup, carts, and checkout.
A bowl order is more than a product in a cart.
A guest chooses a location, picks a base, adds toppings, and selects a pickup time. Behind those few taps are restaurant rules your app needs to understand.
Crave gives your frontend a backend built around those rules, so your team can focus on the ordering experience.
Example ordering flow · An illustration of the restaurant rules, not a live ordering demo.
- 01
Choose a location
Show that restaurant’s menu.
The menu and item availability depend on where the guest orders.
- 02
Build a bowl
Apply the item’s choices and prices.
A base, extra toppings, and required choices need rules behind the interface.
- 03
Pick a pickup time
Use the location’s ordering schedule.
Pickup options depend on when that restaurant can accept an order.
- 04
Check out
Use the restaurant’s payment setup.
Connect the cart to checkout and confirm how the restaurant will receive the order.
Your interface. Crave underneath.
Think of Crave as the engine behind your ordering app. You design the experience around it and connect it through APIs.
- You build
Your website or app
The screens, brand, and guest experience. Keep your frontend code and choose where to host it.
- Crave runs
The ordering backend
Restaurant commerce APIs for menus, item choices, pickup, carts, and checkout, with managed backend hosting.
- You connect
Payments and restaurant systems
Use Stripe with Crave checkout, or request a review of a connection to the restaurant’s existing POS.
Before launch, confirm payment eligibility, integration support, and how the restaurant receives orders. Provider connections require review and restaurant approval.
Choose how the restaurant takes orders.
Your frontend stays yours. The checkout and integration setup depends on the restaurant you’re building for.
Compare checkout optionsUse Crave checkout with Stripe
For restaurants that do not need online orders sent to an existing POS. Confirm the restaurant’s Stripe eligibility and order-handling workflow before going live.
Keep an existing POS
If orders and payments must stay in the restaurant’s current system, request an integration review. Supported workflows, location requirements, and pricing need confirmation before you build.
Start with code you can make your own.
Explore a web or mobile template and run it locally with sample data. No Crave account required. When you’re ready to test a hosted backend, review the Develop plan and create a workspace.