Skip to content
OrderAgentOrderAgent
All plans

One connected workflow, not a dozen integrations

This isn't a hub wiring together a dozen separate apps. It's one system, where WhatsApp, AI, payments, invoicing and your web catalog all follow the same customer and the same order through every step — here's exactly what that connects to, and what it doesn't.

The one channel your customers already use

Every message, in and out, runs through Meta's own official WhatsApp Business Cloud API — never an unofficial client, which is how shops that automate WhatsApp any other way risk losing their number. Your business's own WhatsApp number and Business Account are what get connected, and a webhook is what delivers every incoming message, media file and button tap to OrderAgent the moment it arrives.

  • Every business on the platform maps to its own number and its own customers — nothing is shared between tenants.

Bring your own QR — no new payment gateway

The QR code and bank account you already use for payments is what gets presented to customers. There's no new merchant account to open and no payment gateway to integrate — OrderAgent sends the same QR you already have.

Understood by AI, decided by fixed rules

Natural-language messages and payment receipts are both read by AI — to identify products, quantities and intent in a message, or the amount, date and reference on a receipt. The AI only ever labels what it sees; every decision after that runs through the same deterministic checks, whoever's message it was.

One workflow, start to finish

A customer can start on your web catalog, send their cart into WhatsApp, confirm, pay, submit a receipt and receive an invoice — and OrderAgent follows the same customer and the same order through every one of those steps. Nothing is re-entered, and nothing needs reconciling between separate systems afterwards.

  • Approving a payment is what triggers the invoice, automatically, from the order's own frozen prices.
  • A broadcast campaign reaches customers built from the same tags and order history everything else already uses.

Where your data actually lives

Every order, customer, payment, receipt, invoice and message is stored in a PostgreSQL database, on Supabase's managed infrastructure. Files split the same way the data does: product photos and your payment QR are public, because WhatsApp has to be able to fetch them directly — payment receipts and invoices are stored privately, reachable only through a signed link issued per view, which expires.

Every business kept apart

Your WhatsApp number, customers, products, orders and payment details are resolved to your business alone. Nothing about how another business on the platform is configured, or who their customers are, is ever visible from yours.

Access, by role

Customers, your own staff, and the platform's own administrators each reach different things through different doors — a staff member marking a delivery can't approve a payment, and a platform admin's session can't read your dashboard as if they were you.

Built and deployed properly

The application runs on Vercel, with scheduled jobs handling reminders, expiries and campaigns in the background. Every change goes through GitHub, with automated type-checking, a full build and a test suite gating it before it's deployed.

What isn't built yet

There's no accounting, point-of-sale or courier integration today. If one of those matters to how you run your shop, that's worth telling us before you sign up, not after.

See integrations on your own shop

Onboarding is hands-on — a number provisioned for you, your catalogue loaded, your payment details set up with you on the call.