Keep your POS. Run online ordering on Ordering.co.

Your menu and prices come from the POS, and every online order goes straight into it. Ordering.co adds the online ordering, delivery, and customer tools a point of sale is not built for.

Direct connections
Square, Clover, Oracle Simphony, LimeTray, Wansoft, Shopify, and PulsePOS connect straight to Ordering.co.
Through middleware
ItsaCheckmate, Stream, Deliverect, and Mokka connect many more POS systems.

How your POS works with Ordering.co.

The menu comes from your POS. Orders go back to your POS. Ordering.co adds what online ordering needs in between.

Your POS

Menu route

  1. 1Import menu and prices

    Items, prices, and modifiers are pulled from your POS.

  2. 2Keep it in sync

    Webhooks switch items on or off as soon as they change in your POS, or a scheduled sync runs at the interval you choose.

Ordering.coOrdering.co
  1. 3Enrich it online

    Add what your POS does not have, such as images, categories, and subcategories, from the Ordering.co Dashboard.

Order route

  1. 4Injected into your POS

    Each online order goes straight into your POS and follows the workflow your staff already use.

  1. 5Delivery assigned

    Combine it with Ordering.co delivery to auto-assign delivery companies or your in-house drivers.

Delivery companies or in-house drivers

Order status updates in your POS and Ordering.co at the same time.

POS integrations

Choose your POS.

All integrations
  • Connect your online orders to Clover and compare the routes for marketplaces and delivery.

  • LimeTray menu and stock sync, online orders sent to LimeTray, and order status kept in step both ways.

  • Oracle Simphony menu import, online orders created as Simphony checks, and kitchen progress sent back to Ordering.co.

  • For Domino's franchisees on PulsePOS. Products and coupons synced, orders sent to PulsePOS, and status updated from the store.

  • Shopify catalog sync, online orders sent to Shopify, and order status updated from Shopify.

  • Square menu sync, online orders sent to Square, and live status updates back to your customers.

  • Toast POS connected to Ordering.co, scoped with our team for your locations and workflow.

  • Wansoft menu sync, online orders sent to Wansoft, and order status updates back to your customers.

Through middleware

Find your POS.

Ordering.co also connects to 307 POS systems through Deliverect, ItsaCheckmate, and Stream, the middleware between your POS and your online ordering. Open yours to see how it connects, or request a free direct connection.

307 POS systems

Don’t see your POS?

Request a free direct connection and tell us which POS you run.

Request a free direct connection

What syncs

What moves between your POS and Ordering.co.

01

Menu and prices

Imported from the POS and kept in sync, so you maintain one menu.
02

Availability

Items switched on or off in the POS update online through webhooks or a scheduled sync.
03

Orders

Online orders are injected into the POS and follow the workflow your staff already use.
04

Order status

Status changes update in the POS and in Ordering.co at the same time.

Connection route

Connect directly or through a partner.

Many POS systems connect to Ordering.co directly. Others connect through an integration partner that already works with your POS.

Route

Direct connection

Square, Clover, Oracle Simphony, LimeTray, Wansoft, Shopify, and PulsePOS connect straight to Ordering.co.
Partner

Integration partner

ItsaCheckmate, Deliverect, Stream, and Mokka reach many more POS systems. See them in Middleware integrations.

Don't see your POS?

Tell us which POS you use.

Tell us your POS and version, and we will show you how to connect it through an integration partner or the Ordering.co APIs.

POS and version
The exact POS product and version your locations run.
Locations
How many locations you run and which ones should go online first.
Channels
The websites, apps, kiosks, or marketplaces that should send orders to the POS.

APIs, costs, and connector boundaries

  • Start with the connector’s actual scope

    Open the POS entry that matches your product and version, then confirm menus, modifiers, prices, taxes, availability, orders, status, refunds, and sync direction. An available API is not proof that a connector supports every field or provides real-time updates. Agree retry handling, duplicate prevention, monitoring, and who owns an incident.
  • Toast API access and ordering

    Toast distinguishes partner, custom, standard, and analytics API access. Permissions depend on the integration type and approved scope. Start with its official API overview and confirm the endpoints and restaurant authorization needed for your order flow; a reporting credential does not establish order-write permission.
  • Cassa in Cloud and OnlinePOS APIs

    Cassa in Cloud documents API access for Retail Enterprise or Risto Enterprise licenses, with an API key and access token. OnlinePOS links its open API from its integrations page. Confirm credentials, available operations, and the exact license with the provider before commissioning either connector.
  • GoTab, Kounta, and CompuCash

    GoTab documents a sandbox and API credentials; Kounta publishes an API reference with authentication and resource endpoints. Review account access and object mapping before development. For CompuCash, request the provider’s current documentation for your installed version; do not substitute an unrelated POS API.
  • TISSL, Orderwise, and Petpooja

    Use TISSL’s official integration directory to start a CRM or marketing connection review. Orderwise describes a business-specific API integration route. Petpooja describes its online-order management offering. Request technical access, supported fields, licensing, and connection ownership from each provider; these sources do not establish an Ordering.co connector or an arbitrary connection between them.
  • How do Just Eat orders reach my POS?

    Review the Just Eat channel connection and the POS connector as two separate hops: marketplace to Ordering.co, then Ordering.co to the POS. Confirm store mapping, menu ownership, payment and tax mapping, acceptance, cancellations, and failed delivery to the POS. Receiving an order in Ordering.co does not prove the POS accepted it.
  • Custom integration or an OMS?

    A custom connector suits a specific data flow when you can own its implementation, monitoring, API changes, and support. An order management system (OMS) may fit broader routing and inventory coordination across channels; compare its documented workflows with your needs. Evaluate mappings, exceptions, multi-location scope, ongoing ownership, and total cost before selecting either route.
  • What fees should I budget for?

    Separate setup and custom development from recurring provider licenses, API access, per-location or volume charges, support, and future changes. Ask for a written scope and current quote from the relevant providers. There is no single verified fee for every POS-to-marketplace connection; an unpublished price is not zero.
  • When does this need a separate scope review?

    For BigCommerce–Square, Toast–Olo, TouchBistro–DoorDash, or BentoBox–Clover, verify the current connection with the named providers rather than inferring it from this directory. A Lieferando review API is separate from order intake. Pharmacy workflows, enterprise AIDC, and marketplace custom objects require their own data, permissions, and operating review; this directory does not establish medical suitability, automatic identification, or arbitrary object synchronization.

Connect your POS to online ordering.

Tell us which POS you use and how many locations you run, and we will help you plan the connection.

Product guide: Review POS and menu-sync configuration

What are you building?

Tell us and we’ll take you to the right next step.