Keep your storefront. Connect it to everything else.
Your website, app or kiosk stays yours. Connect it once to the Ordering.co API, and Ordering.co routes menus, orders and statuses to the POS, delivery, marketplace and payment providers already in the Dashboard.
Illustrative order route
One connection in the middle of your stack
- 01Your frontWebsite, app or kiosk
- 02Ordering.co APIMenus, orders, statuses
- 03Your stackPOS, delivery, marketplaces, payments
- 04WebhooksOrder status back to your front
Already have a front end? You don't need a new one. Ordering.co sits in the middle and connects it to the tools you use.
Why Ordering.co as middleware
Build one integration instead of dozens.
Every POS, courier and marketplace has its own API, credentials and edge cases. Connect your front end to Ordering.co once and use the integrations that are already built and maintained.
One API, many destinations
Your team connects to a single, documented REST API. The POS, delivery, marketplace and payment connections behind it are already in the Dashboard.Menus come from your POS
Supported POS integrations sync menus into your project, so your website and app read one catalog instead of keeping copies in step.Statuses flow back
Webhooks and the API tell your front end when an order is accepted, prepared, picked up or delivered, so you notify customers in your own design.One Dashboard for every channel
Orders from your own front ends, marketplaces and other channels land in the same Dashboard, ready to manage, report on and export.Change providers without a rebuild
Add a courier, a marketplace or another payment gateway from the Dashboard. The connection between your front end and Ordering.co stays the same.Your accounts, your data
You connect each provider with your own account and credentials. Your menus, customers and orders stay yours.How the connection works
Your front on top. Your stack underneath. Ordering.co in the middle.
Customers order in the experience you built. Ordering.co receives the order through the API, sends it to the POS and delivery provider you choose, and returns every status change to your front end.
- Your website
- Your app
- Your kiosk
API · Dashboard · Menus, orders and statuses- POS
- Delivery
- Marketplaces
- Payments
Getting started
From sign-up to your first routed order.
Your team builds one connection. Everything else is set up from the Dashboard.
- 01Create your projectSign up at accounts.ordering.co. Your project and Dashboard are ready as soon as you log in.
- 02Connect your providersIn the Dashboard, add the POS, delivery, marketplace and payment providers you use, with your own accounts.
- 03Connect your front endYour developers send the orders placed on your website or app to your project through the Ordering.co API.
- 04Listen for statusesSet up webhooks so your front end receives every order update, then test end to end and go live.
What you can connect
Use the integrations already in the Dashboard.
Pick a category to see every provider, how it connects and what it syncs.
- 01POSWansoft, Square, Clover, Oracle Simphony, Shopify and more: menus in, orders out.
- 02POS through middlewareDeliverect, ItsaCheckmate, Stream and Mokka reach many more POS systems.
- 03DeliveryUber Direct, DoorDash Drive, Shipday, Lalamove, Stuart and your own drivers.
- 04MarketplacesUber Eats, DoorDash, Rappi and Just Eat orders in the same Dashboard.
- 05PaymentsStripe Connect, Adyen, PayPal, Mercado Pago and more than 50 gateways.
- 06Loyalty and CRMOrdering Loyalty, HubSpot through Zapier, Mailchimp and Spoonity.
- 07AnalyticsGoogle Analytics 4, Google Tag Manager, Meta Pixel and Segment.
- 08AutomationWebhooks, plugins, Zapier and WhatsApp order notifications.
For developers
Documented, server-side, ready to build on.
The same API, webhooks and plugins Ordering.co uses for its own products. Keep your API key on your server and build the connection your front end needs.
- REST API
- One base URL per project and language, authenticated with an API key in the X-Api-Key header.
- Webhooks
- Order events delivered to your own URL instead of polling.
- Plugins
- Hook-based extensions built from your Dashboard.
- MCP
- Connect AI tools to your Ordering.co account.
FAQ
Questions teams ask before connecting.
Do I have to use the Ordering.co website or apps?
No. You can keep your own website, app or kiosk and connect it to Ordering.co through the API. The Ordering.co website and apps stay available if you want them later.
Do I need to build each integration myself?
No. The integrations are already built into the Dashboard. Your team builds one connection from your front end to the Ordering.co API, then you turn on the providers you need.
Whose accounts do the integrations use?
Yours. You connect each POS, courier, marketplace or payment provider with your own account. Any fees those providers charge are billed by them.
How do order statuses reach my website or app?
Through webhooks configured in the Dashboard, or by reading orders through the API. Your front end then shows each update to the customer.
Is this the same as the middleware integrations?
No. Middleware integrations such as Deliverect or ItsaCheckmate connect Ordering.co to more POS systems. Here, Ordering.co itself is the middleware between your own front end and your providers. You can use both together.
What if the integration I need isn't listed?
Tell us which provider you use. New connections are scoped with the Ordering.co team and quoted separately as custom work.
Keep what you built. Connect what you need.
Create your project and route your first order from your own front end through Ordering.co.