Integrations

It talks to what you already use.

Accounting first, because that is where the re-keying lives. Then commerce, routing and carriers. Every integration is listed with its status, specified or in build, rather than as a logo wall.

Public APIPrototype
POST /v1/orders
Authorization: Bearer bx_live_••••
{
  "customer": "cust_8f21",
  "deliverOn": "2026-09-10",
  "lines": [
    { "sku": "KS-WHT", "qty": 60 },
    { "sku": "BT-STD", "qty": 120 }
  ]
}

201 Created
{ "id": "ord_2041", "status": "Confirmed",
  "delivery": { "id": "dlv_7719", "run": null } }
AccountingRelease 1

Xero

Invoices, credit notes and payments sync. Customers map once.

Spec 7.5

AccountingRelease 2+

MYOB

The same invoice, credit and payment sync for MYOB Business and AccountRight.

Spec 19.6

CommerceRelease 2+

Shopify

Web orders enter through the same order path as everything else.

Spec 19.7

CommerceRelease 2+

WooCommerce

Orders in, fulfilment and tracking status back.

Spec 19.7

RoutingRelease 2+

Routing providers

Planned distance, duration and ETA from a routing provider; optimisation behind the sequencer.

Spec 19.1 · 19.2

CarriersRelease 2+

External carriers

Hand a delivery to a carrier when your own fleet cannot take it, and keep the tracking.

Spec 19.5

PlatformRelease 1

Public API

Orders, deliveries, customers and proof over a documented REST API with scoped keys.

Spec 9.3 · 1.7

PlatformRelease 1

Webhooks

Delivery events pushed to your systems as they happen.

Spec 9.4

"Release 1" means specified and in the first build. "Release 2+" means specified and scheduled after it. Nothing here is live yet, and nothing here is a promise made by a logo.

The demo

Send us yesterday's order email and a run sheet.
We'll show you that day in boXe.

Your orders, your customers and your runs, walked through end to end on a call.