Skip to content
NG WMS
ERP integration

Your ERP and the warehouse, on the same numbers.

The link with the ERP runs through the API, webhooks and an outbox. Every API client has its own key with an expiry date, every message leaves a trace in the log, and a message that was not delivered waits in the outbox and can be sent again, with the same ID.

  • API with OAuth2 tokens
  • Webhooks
  • Outbox with retries
  • Two-way message log
Book a demoAll features
Interface illustration with sample data
Capabilities

Integration you can see and control

Everything passing between the WMS and other systems has an owner, a status and a history — and a way to fix it when something gets stuck.

  • API clients and keys

    Each connecting system gets its own API client: a key with a prefix, a label and an expiry date, in the Active, Expired or Revoked state. A key can be revoked before it expires.

  • The secret is shown once

    The key secret is shown only when it is created, and only its fingerprint is stored. A token is issued through the OAuth2 client credentials flow; an inactive client gets no token.

  • Call statistics

    Per client: requests, successful, rejected and failed calls, average response time, by day and by endpoint, with the latest errors.

  • Webhooks

    A URL and a subscription to events from the catalogue. Authentication: none, Bearer, Basic, OAuth2 password or OAuth2 client credentials. A test message and delivery counters.

  • Outbox

    Outgoing messages are Pending, Sent or Undeliverable, with the number of attempts, the time of the next attempt and the last HTTP status.

  • Retry with the same ID

    An undelivered message is resent manually with the same message ID, so the receiving side can recognise the repeat and not process it twice.

  • Message log in both directions

    Incoming and outgoing messages in the Processing, Done, Failed or Under review state, with a correlation ID and contract version. Messages under review are resolved manually.

  • Developer documentation

    An OpenAPI description of the API, opened through Swagger UI, and a Postman collection for test calls.

How it flows

What one connection looks like

The same pattern for every system that talks to the warehouse.

  1. 01

    Connect

    Create an API client, collect the secret once, and the system obtains a token through the OAuth2 client credentials flow.

  2. 02

    Exchange

    Incoming messages arrive through the API, and catalogue events leave by webhook, via the outbox.

  3. 03

    Monitor

    The log, statistics and latest errors show the state, and undelivered messages are sent again.

What changes in practice

Documents that know about the ERP

A count has “Sent to ERP” and “ERP confirmed” states, and an order in picking preparation can carry an “ERP stop” flag with a reason. Exchange with the ERP is part of the flow, not a side job.

Errors visible before anyone reports them

Per-client statistics, the latest errors and undeliverable messages in the outbox show where the link is failing, before it turns into a stock discrepancy.

Mapping by agreement

The mechanism is the same for every system: API, webhooks and the outbox. Which fields and events are exchanged with your ERP is agreed for the specific project.

Frequently asked questions

Which ERP does NG WMS work with?

With yours. The link runs through the API, webhooks and the outbox, so NG WMS works with NG One as well as other ERP systems; which fields and events are exchanged is configured for your system.

How does another system authenticate to the WMS?

Through an API client: it receives a key and a secret, then a token via the OAuth2 client credentials flow. The key has an expiry date and can be revoked; an inactive client gets no token.

What if the ERP is unavailable when the WMS sends an event?

The message stays in the outbox with its number of attempts and the time of the next attempt. A message that remains undeliverable is resent manually, with the same message ID.

Is there API documentation?

Yes: an OpenAPI description through Swagger UI and a Postman collection for test calls.

How can I see what arrived from the ERP?

The message log records incoming and outgoing messages with their state, correlation ID and contract version. Messages that need checking stay “Under review” until someone resolves them.

Related

  • WMS basics6 min read

    What is a WMS, and when does a warehouse need more than an ERP?

    A WMS runs stock by location, task and scan; the ERP keeps the books. What a warehouse management system actually does, how it differs from an ERP inventory module, and the signs that you have outgrown spreadsheets.

Want to see how this would look in your warehouse?

In a demo we walk through your receiving, picking and dispatch in NG WMS and show how NG Copilot supports your warehouse team.

Book a demo