POS API integration, five restaurant APIs compared from one 20-call voice agent

It means a server-to-server connection where a finished voice order is posted into the merchant's point-of-sale through the POS vendor's public API (or private partner API), so it lands on the kitchen display and the end-of-day reports without any human re-keying. For PieLine this is live against five POS systems (Clover, Square, Toast, NCR Aloha, and Revel) and in progress for dozens more. The defining trait of real POS API integration is that the kitchen cannot tell whether the ticket came from a phone call, a tablet, or a counter register.

Because they are different at the layer that matters. Clover's order creation is merchant-scoped under api.clover.com. Square posts to /v2/orders on connect.squareup.com with an idempotency key. Toast uses a partner client-credentials flow and posts to its orders endpoint on ws-api.toasttab.com. NCR Aloha Cloud exposes a different order injection path with location-scoped routing. Revel's Management Console API uses django-style resource URLs with token auth. Auth, base URL, idempotency semantics, modifier model, and per-merchant rate limits all differ. A thin abstraction hides them at your peril.

Respecting five different rate limits while 20 calls come in simultaneously for the same merchant. Clover publishes around 16 requests per second per merchant. Toast publishes tiered per-partner quotas. Square publishes a per-application cap measured per second. NCR Aloha Cloud and Revel tier by plan. A voice agent that takes orders for a single merchant can saturate any of these with 20 concurrent calls plus catalog refresh plus modifier lookup plus order status polling. The integration work is as much about queue shaping as it is about endpoint wiring.

It can for a proof of concept. In production every integration partner introduces its own latency, its own outage profile, and its own pass-through pricing. Going direct to each POS API is what lets PieLine post an order within seconds of the caller hanging up, publish a predictable flat price ($350 per month for up to 1,000 calls), and add POS-specific behavior (Toast check splitting, Square fulfillment endpoints, Clover printer grouping) that a lowest-common-denominator integrator cannot expose.

Each POS gives a menu item a different kind of ID. Square uses a 26-character CatalogObject identifier. Toast uses GUIDs on MenuItem and on every nested option group. Clover uses a merchant-scoped item ID distinct from its inventory ID. NCR Aloha uses numeric item numbers scoped per location. Revel uses integer primary keys per merchant. A voice utterance like 'chicken burrito' has to resolve to a specific ID in the specific namespace of the specific POS of the specific merchant of this call. Stale mappings are the single biggest source of order rejections in production, above auth and schema failures combined.

Both, depending on the POS. Square and Toast emit order lifecycle webhooks. Clover emits events over its v3 webhook channel. NCR Aloha Cloud supports notifications on some tenants but many partners still poll. Revel's Management Console does not push; partners poll on a cadence. For a voice agent, the relevant status is 'kitchen has seen this ticket,' which on most POS systems is inferred from an order state transition rather than a dedicated event. PieLine treats order confirmation as a user-visible step of the call only when the POS supports a deterministic acknowledgement.

For a POS PieLine already supports, most restaurants go live the same day. The integration itself is not the bottleneck; menu mapping is. The PieLine onboarding team scrapes the restaurant's online menu, maps items to the right POS item IDs, and configures rules (delivery zones, minimum orders, hours, specials). For a new POS platform PieLine has not integrated yet, the work is measured in weeks, not days, because the auth handshake, catalog pull, order post, and modifier model all have to be learned on a vendor-by-vendor basis.

Ask whether the order posts directly to the POS, or lands on a separate tablet that a staff member has to watch. Ask which specific POS systems are live (Clover, Square, Toast, NCR Aloha, Revel are table stakes; many vendors only claim one). Ask what happens on a POS rate limit 429 during a rush. Ask how the modifier model maps: does a voice utterance of 'no onions, extra guac' map to the exact option group IDs the POS expects, or does the integration just append a free-text comment. The last one decides whether the kitchen loves the system or hates it.