Integrations

Connect your ERP and WMS to your transport operations.

Orders, milestones, documents and costs: define the data exchanged with OneChain and your partners, based on your systems and workflows.

In practice

One order, several systems.

The order is in the ERP, the booking with the forwarder, and receipt in the WMS. A shared reference connects this information.

OneChain scopes interfaces with your teams. The project defines the data, its direction, and who can view or change it.

Into the shipment file

  • ERP

    Order · PO-1048

    Purchasing team
  • Forwarder

    Booking · documents

    Transport partner
OneChain

Shipment file · PO-1048

Transport team · shared references

To the receiving teams

  • WMS

    Reference · expected date

    Warehouse team
  • ERP / reporting

    Selected statuses · costs

    Finance team
Illustrative flow to scope. Fields, direction and frequency defined for each interface.

Define what comes in and what goes back.

Orders and references can feed OneChain; bookings, dates and documents come from partners. The scope determines which information is exchanged with the warehouse.

Data returned to the ERP or reporting can include statuses, dates or costs. Each field has an agreed source of truth.

Choose the channel around the flow.

API, structured import or SFTP file: the choice depends on your systems, formats and required update frequency.

An intermediary system can handle field mappings. Email and document exchanges with a partner also need a defined scope.

Assign an owner for errors.

A reference is missing, a format changes, or a transmission fails. Define who detects the issue, who corrects the data and who resumes the exchange.

Business teams validate the data; IT, OneChain and partners agree technical responsibilities. Test this process with an initial flow.

Prepare your implementation

Details to work through using your flows and organization.

Can my ERP or WMS be connected?

Feasibility is assessed by system, version, data and exchange direction. The project confirms the required channel, mappings and access.

Can we start with a file?

A structured file may suit an initial flow. Define its fields, format, frequency and checks before considering an API.

How should we prepare a high-volume import or export?

Specify whether data must be created, updated or extracted. Validate formats, permissions, batch sizes, limits, error reports and any costs. Excel support depends on the agreed scope.

Does the TMS replace the ERP for master data?

No. The ERP usually remains the reference for orders, items and addresses; the TMS uses the information transport needs. Issues found during operations are fixed at the source, in the ERP. The project assigns a reference source to each field.

How it works at a glance

Explore your flows, partners and permissions.

These diagrams detail three parts of the project. The exchanges shown depend on the scope defined with your systems and partners.

Your systems

  • ERP

    Orders and references

  • WMS

    Sites and receipts

  • Business files

    Structured imports

OneChain

One shared reference

Order · Shipment · Delivery

Data flows back to

  • ERP

    Shipment statuses and costs

  • WMS

    Appointments and deliveries

  • BI

    Costs, lead times and performance

Less re-entry, from order to delivery.API · EDI / SFTP · Imports

How it works at a glance

Bring provider information together.

Documents, statuses and partner information feed the same shipment files.

Your transport ecosystem

  • Forwarders

    Bookings and documents

  • Carriers

    Pickups and deliveries

  • Data partners

    Positions and ETAs

OneChain

One shared shipment file

Milestones · Dates · Documents

Useful information for every team

  • Transport team

    Follow milestones and exceptions

  • Warehouse

    Prepare the receipt

  • Authorized partners

    Access shipment documents

Partner information brought together in the right place.API · Portals · Emails and documents

How it works at a glance

The right information for each role.

Teams and partners contribute according to their role and scope.

Who connects

  • Application

    Application identity

  • User

    Role within your team

  • Partner

    Authorized scope

OneChain

Controlled access

Identity · Role · Scope

What you control

  • Data

    Access within the client scope

  • Actions

    Permissions enforced

  • Traceability

    Tracked exchanges and decisions

The right information, for the right people.
Integrations

Map your first transport data flow.

Bring a systems diagram and a sample file. Identify the data to exchange and who owns each step.

Map my data flow