Now viewingIntegrations

Integrations

POS paths where they are available. Kitchen Mode fallback where they are not.

Aharo is designed around approved pickup orders first, then POS or reservation handoff when the restaurant's systems and access level support it.

Live call

Demo Restaurant

In progress
Caller
Pickup order
Agent
Asha, warm tone
Captured
Items, spice, notes
ETA
25 minutes

Pending approval

CA$38.37

Chicken Lababdar - mild
Garlic Naan x2
Mango Lassi
Square
Public API path to build first
Toast
Partner-gated path
Manual
Kitchen Mode fallback
Review
Staff approval before handoff

Adapter model

What the integration layer needs before orders can flow

The most important step is menu and modifier mapping. Without POS item IDs, order injection can mismatch price, tax, spice, or kitchen routing.

Location and provider

Store provider, account, merchant, and location identifiers during restaurant setup.

Menu mapping

Match Aharo menu items, modifiers, spice levels, and prices to POS catalog/menu objects.

Order handoff

Push only approved orders, capture the external POS order ID, and keep a fallback if handoff fails.