Restaurant commerce for developers

Build custom ordering without rebuilding the restaurant logic.

APIs and SDKs for location-specific menus, modifiers, pickup scheduling, carts, and checkout. Bring your own frontend, or start with our web and mobile templates.

Explore the APIs See what you can build

For agencies and engineering teams building for restaurant brands.

Restaurant ordering has its own rules.

The menu depends on the location. Each item has choices. Pickup depends on when the restaurant can take an order. Build on APIs that make those details part of the ordering flow.

Location menus

Show the menu for the location a guest chooses, with item details and availability.

Modifiers and carts

Let guests customize items and manage an order before checkout.

Pickup scheduling

Use location time slots and ordering readiness to offer pickup times.

Checkout

Connect your cart to the restaurant’s configured checkout and payment path.

Orders

Give signed-in guests access to their order history and order details.

Integrations

Connect approved POS and payment providers where the restaurant needs them. Availability depends on the provider and location.

Your interface. A shared commerce foundation.

Build the experience your client or brand needs. Connect your website and mobile app to the same restaurant commerce APIs, so each new interface starts with menus, carts, and checkout already defined.

Choose your production path. Use Crave’s native commerce path, powered by Stripe, or connect through a supported provider when orders and payments need to stay on the restaurant’s existing system.

Provider support depends on location, capabilities, and merchant approval. Check the fit before committing to a build.

Find your integration path

Start with code. Make the experience yours.

Explore templates

Start with a Next.js or Expo template. Make the design, menu, and ordering experience your own. Explore and clone the code without an account.

Examples use sample data. Connect your restaurant before taking real orders.

Crave.js Next.js Storefront

Meet Leclerc Bakery: warm editorial design, fresh pastry photography, and a storefront that adapts from desktop to mobile web. Built on the shared Crave.js commerce core.

Next.js design preview · Try sample ordering in the template.

Explore Next.js template

Crave.js Expo Storefront

Meet Maple & Main: an American neighborhood grill, running on the Expo storefront. Browse smash burgers and crispy chicken, explore the menu, and make an order your own.

Expo app preview · Explore the read-only restaurant demo.

Explore Expo template

Your own storefront, on every screen.

Leclerc Bakery is a real public template preview. Customize the design and connect your restaurant before taking real orders.

Leclerc Bakery desktop storefront with fresh pastry photography and a sample bakery menu — One storefront, every screen. Captured from the public template’s bakery design preview.

One storefront, every screen. Captured from the public template’s bakery design preview.

Working code. Your next idea.

Clone the public Next.js template before creating an account. Use your coding tools and AI assistant to change the design, then connect your frontend to Crave Cloud’s commerce APIs.

Start with the Leclerc Bakery source

Typed commerce for your own application

Read the SDK quickstart

You own and deploy the frontend. Crave Cloud runs the commerce APIs. Full-stack self-hosting is planned through Restaurant OS early access.

One path from first request to launch.

Use the SDK for your frontend, the Console for your sandbox, and the docs for the details. Live restaurant access requires the restaurant’s approval.

Storefront SDKBuild menu, cart, and checkout experiences in TypeScript with shared restaurant-commerce types.Flutter SDKBring the same ordering flows to Flutter apps with typed Dart models.Developer ConsoleCreate an app and isolated sandbox, manage keys, and request restaurant-approved access when you are ready to connect.Crave MCP serverUse Crave tools in a compatible coding assistant to set up a sandbox, work with menus, and check launch requirements.DocumentationFollow quickstarts and API guides from your first local build through restaurant installation.

Code you own. Commerce you connect.

Start free. Connect production when you’re ready.

Start with public Next.js and Expo storefront code. Customize and self-host your storefront, and use Crave’s SDKs to connect it to commerce APIs. The managed commerce backend and production integrations are separate services.

Local development, fixture data, and isolated sandbox testing are free.

Payment begins when Crave participates in live transactions or operates a production integration. Stripe-native commerce uses transaction pricing; connected integrations are priced by live location.

Confirm pricing, provider fees, and regional availability before production activation.

Review production pricing Explore integration paths

Bring your next restaurant project.

Start with the SDK quickstart or clone a template. Test your flow in an isolated sandbox, then confirm the restaurant’s production setup.

Start building

Looking for the operator workspace? Explore Restaurant OS early access.