Getting started

OrderLoop runs at orderloop.app. Each person in a workspace signs in with their own email and password and has a role: a viewer reads, an approver also decides approvals, and an operator also starts and cancels orders, edits and publishes flows, and manages the team. See Team and roles.

An operator adds you on the Team page and sends you a temporary password. Sign in with your email and that password, then choose a password of your own. If your workspace requires two-factor sign-in for your role, you set it up next.

Run a scenario

In workspaces with the demo data loaded, the dashboard lists one-click scenarios, each a real order on a built-in flow: a guest checkout, a B2B purchase order read from an email, an order over its credit limit, an out-of-stock order that rolls back, a purchase request, a stock review, two subscriptions (one with a failing card), a marketplace order with two sellers, buy online and pick up in store, a ship-from-store order with an e-book, a shipment split between the warehouse and a store, a till sale with a gift card, a retail order that is returned and one priced in euros.

Without the demo data the panel is hidden; start an order from New order instead. Either way (operators only), the order page opens. The flow graph colours each node as it runs, waits and finishes, and the timeline records every step. Below the queues, the dashboard’s Last 30 days section shows, in USD, completion rate by model, revenue per day, refund rate and the slowest steps by p95 duration.

Some orders stop at an approval or wait for an event. Decide approvals from the order page or the Approvals inbox; deliver events (for example payment.received) from the order page, the REST API or a signed webhook.

Start an order over the API

Other systems call the REST API with an API token. An operator creates one on the Team page with a name, a role and an expiry; it is shown once.

curl -s https://orderloop.app/api/v1/orders \
  -H 'authorization: Bearer ol_live_…' \
  -H 'content-type: application/json' \
  -H 'Idempotency-Key: demo-1' \
  -d '{
    "flowId": "tpl-storefront-order",
    "input": {
      "model": "b2c",
      "channel": "web",
      "customerId": "cus_ada",
      "lines": [{ "sku": "MON-27", "qty": 1 }]
    }
  }'
# → 201 { "orderId": "ord_…" }   (a repeat with the same key: 200, same orderId)

Then read its live state with GET /api/v1/orders/:id, or subscribe to outbound webhooks to hear when it is paid, shipped or finished.

Connect other systems

Inbound orders: a storefront, marketplace or till posts signed orders.
Channel adapters: Shopify order webhooks and EDI X12 850 purchase orders.
Email intake: customers email orders and purchase orders.
MCP server and A2A endpoint: AI clients and other agents.

Concepts: flows, versions, orders, waits and rollback.
Building flows: the editor and the rules a flow must follow.

Sign in

Run a scenario

Start an order over the API

Connect other systems

Next