Alderstone

OrderBridge: integration overview

OrderBridge turns inbound purchase orders (uploaded PDFs or emails) into draft sales orders in your ERP. The integration is how it knows your catalogue, your prices, and where to create the order.

What the integration does

During the PO workflow, OrderBridge calls your ERP connection at four points:

  1. Match: searches your ERP's customers and products so operators can link PO lines to real catalogue entries.
  2. Price check: resolves the system unit price for each matched line and flags mismatches against the PO price.
  3. Allocation (optional): sums historical ordered quantity when SKU allocation caps are configured.
  4. Submit: creates a draft sales order in your ERP once the PO is confirmed.

The PO workflow page shows the exact call sequence with request and response expectations for each stage.

Choosing a transport

Configure one active transport per company in Settings → Integrations:

  • Native: a built-in direct connection to a supported ERP. No development work needed.
  • REST: Alderstone calls your middleware, which implements the OrderBridge REST API. Works with any ERP.

Not sure which fits? See Choose your integration path.

Setting up a REST connection

  1. Implement at least POST /health and POST /sale-draft on your middleware. These are exercised by the connection test on save.
  2. In Settings → Integrations, select REST, enter your middleware's base URL (no trailing slash), and click Generate API key.
  3. Store the ask_… key in your middleware and validate it on every request. See Authentication.
  4. Save. Alderstone runs the connection test; the connection shows connected once both calls succeed.

The Quickstart walks through this end to end, including platform recipes for Workato, Make, and n8n, and a go-live checklist.

Next steps

Was this page helpful?