Choose your integration path
Each Alderstone app connects to your ERP through one of two transports: a built-in native connector or REST middleware you host. Use this guide to choose a transport for each app.
The short version
- Your ERP has a built-in native connector (visible in Settings → Integrations)? Use it. Configure credentials and connect in Settings.
- Your ERP has no native connector, or you need custom translation, orchestration, or multi-system logic between Alderstone and the ERP? Implement the REST contract on middleware you control.
When REST is the right choice
Choose REST middleware when any of these apply:
| Situation | Why REST fits |
|---|---|
| Your ERP (SAP, NetSuite, custom, legacy) has no native Alderstone connector | The REST contract works with any system your middleware can reach |
| You already run an iPaaS (Workato, Make, n8n) | Implement the contract as recipes/scenarios/workflows; see the Quickstart |
| You need custom mapping, filtering, or enrichment between Alderstone and the ERP | Your middleware owns the translation layer |
| Data must come from more than one system (e.g. pricing from one, catalogue from another) | Middleware can aggregate before responding |
| Security policy forbids third parties holding ERP credentials | ERP credentials stay inside your middleware; Alderstone only holds its own API key |
What each app needs from the transport
Both transports expose the same capabilities to the app. With native connectors Alderstone calls the ERP APIs; with REST your middleware does.
OrderBridge uses the connection for catalogue search, pricing validation, credit checks, allocation usage, and draft sales order creation during the PO workflow. If your ERP is the system of record for products, customers, and sales orders, the connection must reach it.
Nudge uses the connection to sync debtors, invoices, and payments inbound, and to push dispatched invoices and approved payments outbound. See Sync & push flows. If your GL/AR system is the system of record for debtors and invoices, the connection must reach it.
Mixing transports
Transports are configured per app, per company, and each app stores its integration credentials independently. Common combinations:
- REST for both apps, pointing at the same middleware host with different route groups.
- Native for OrderBridge (supported ERP) and REST for Nudge (different GL system), or the reverse.
- REST during a migration, switching to native once a built-in connector becomes available for your ERP.
Next steps
- Going with REST? Follow the Quickstart to get a health check passing, then implement the OrderBridge or Nudge contract.
- Going native? Open Settings → Integrations in the relevant app and follow the in-app connect flow; no developer work needed.