Bring the systems the restaurant already runs.

Choose how your restaurant accepts online orders. Use Crave checkout with Stripe, or ask us to review a connection to your existing POS. Confirm payment eligibility and order handling before launch.

Compare checkout options

Where should your orders go?

Choose Crave checkout or keep the restaurant’s existing POS. Connect other tools alongside either option.

Checkout option 1

Use Crave checkout

You can use Stripe for online payments and do not need online orders sent to an existing POS.

What you’ll build: Build your storefront against Crave’s menu, cart, and checkout APIs. Crave runs the commerce backend; Stripe handles payments.
What you need: Start with sample data. Before going live, confirm the restaurant’s country, Stripe account eligibility, menu, and order-handling workflow.
Your next step: Run a template locally first. Then create a workspace to test with a Crave sandbox.

Start with a template

Local sample data needs no account. Live hosting and payment fees are separate.

Checkout option 2

Keep your POS

The restaurant needs online orders and payments to stay in the system it already uses.

What you’ll build: Keep your custom storefront and request a review of the connection to the restaurant’s existing system.
What you need: Send the POS name, country, location count, payment provider, and required flows: menu sync, orders, refunds, or all three.
Your next step: Get confirmation of supported capabilities, merchant approval requirements, and a per-location quote before building the integration.

Request a POS review

Opens an email draft. POS and country support require review.

Optional add-on · either checkout path

Connect another tool

You want to add loyalty, analytics, voice, or guest messaging alongside your ordering system.

What you’ll build: Scope a connection for the specific tool and workflow you need. An add-on does not replace your checkout or POS choice.
What you need: Send the tool name, API documentation if available, required data or actions, and the restaurant locations that need access.
Your next step: Confirm the connection’s permissions, implementation scope, and pricing before committing to the tool.

Discuss a tool connection

Opens an email draft. Connection availability and scope require review.

Integration questions, answered.

Open a question to see what to expect and what needs confirmation for your restaurant.

What can an integration read and update?

The scope depends on the provider and the connection you need. A menu connection, order submission, and refunds are separate capabilities. Send us your POS or tool name and required workflows so we can confirm what is supported before you build.

Who handles payments and refunds?

With Crave checkout, Stripe handles payments through the restaurant’s payment account. If you keep an existing POS and payment provider, the integration review must confirm where payments are collected and how refunds are handled. Hosting fees and payment processor fees are separate.

Which countries and account types are supported?

Support depends on the selected provider, the restaurant’s country, and its payment account. This page does not publish a confirmed country or account-type list. Send those details with your integration request so eligibility can be checked before launch. A working test setup does not confirm live-payment eligibility.

What happens if an order or payment fails?

Recovery depends on the checkout and provider connection. Before launch, the integration review needs to establish how your team checks order and payment status, handles failed submissions, and retries without creating duplicate orders or charges. Confirm these workflows for your selected connection; do not assume every provider supports the same recovery tools.

Which restaurant locations can an integration access?

Restaurant approval is required for each location. Include the locations you want to connect in your request, along with the data and actions each needs. Confirm the approved scope before enabling a production connection.

How do I disconnect an integration?

The disconnect process depends on the provider and how access was granted. Before launch, confirm who can revoke access and how pending orders, refunds, and retained data will be handled. For an existing connection, contact Crave with the provider and affected locations to confirm the steps before disconnecting.

Read the platform introduction