There is a version of supply chain visibility that looks convincing until something goes wrong.
A dashboard shows shipment statuses. A report shows carrier performance. A spreadsheet tracks purchase orders. Each of these things exists. None of them talk to each other. When a deviation happens — a late shipment, a supplier confirmation that does not match the original order, a customs hold — the team still moves between systems, reconciles data by hand, and pieces together what is actually happening.
That is the integration problem. Not missing data, but data that cannot reach the people who need it, when they need it.
The problem with data that does not talk to each other
When the systems involved in a supply chain operation are not connected, the people working in that operation become the connectors. Someone copies a booking from the ERP into the transport system. Someone emails the carrier for a status update. Someone checks the customs broker's portal separately. Someone exports data from three places and rebuilds it in a spreadsheet before the weekly review.
None of this is unusual. Most logistics and procurement teams operate this way. But the total time it takes adds up, and none of it is time spent on actual decisions.
When a platform connects those systems properly, that category of work disappears. The booking flows from the ERP automatically. The carrier sends updates directly into the platform. The exception surfaces without anyone having to look for it. The analytics update without anyone exporting a file.
That is what integration changes. Not speed, exactly. The removal of a type of work that was never the point in the first place.
How the Connectivity Hub handles the technical work
Every piece of data entering or leaving the vchain ONE platform passes through a layer called the Connectivity Hub. Its job is to handle the technical complexity of connecting systems that speak different languages.
Here is a concrete example of how it works. A manufacturer's ERP sends a booking request. The Hub receives it, checks that the data is formatted correctly, translates it into the platform's internal structure, sends it to the right carrier, and returns the booking confirmation. The operations team sees a confirmed shipment. They did not touch the translation step — the Hub did.
The same applies in reverse. When DHL sends a scan event with its own internal status code, the Hub translates that code into a standardized status that ONE understands, and passes it to the rules engine that decides whether an exception should be raised. Every carrier uses different codes for the same events. The Hub normalizes all of them into one consistent format.
Every request and response that passes through the Hub is logged. If a data issue occurs, the logs show exactly what came in, what went out, and where the problem started. Failed messages can be replayed. Nothing disappears silently.
What the platform connects to
The ONE platform connects to six categories of external systems. Each connection has a specific operational purpose.
ERP systems. The connection between a manufacturer's ERP and the platform runs in both directions. Booking requests originate in the ERP and arrive in the platform automatically. Confirmations, shipping labels, and status updates return to the ERP through the same connection. Teams stop re-entering data that already exists somewhere else.
Carriers. Six carrier integrations are live today: Unifaun/NShift (Apport), DHL, UPS, Schenker, Agility, and Searates. Each connects through its own protocol. Some use REST APIs for real-time event streaming. Unifaun/NShift uses a scheduled XML file feed. Inside the platform, all of them produce the same standardized output. New carriers can be added through the Hub without touching the core platform.
Emissions calculation. The platform connects to Proxio, an emissions calculation engine, to produce CO2 and environmental data per shipment. This feeds directly into the analytics layer. Sustainability reporting does not require a separate tool or a manual export.
Customs brokers. Declaration status and document imports from customs broker feeds arrive in the platform automatically. Teams see clearance milestones without calling or emailing the broker for updates.
Tariff and pricing engines. Rate retrieval and cost allocation happen inside the platform through connected pricing sources. Carrier comparison does not require switching to a separate rate card or spreadsheet.
Analytics. Power BI dashboards are embedded directly inside the ONE platform interface through a secure Microsoft connection. Procurement and logistics managers access performance reports, carrier comparisons, supplier data, and exception analytics without leaving the operational environment, and without needing a separate Power BI license.
What this means specifically for procurement
For teams managing purchase orders and supplier relationships, the most useful integration is the one between the ERP and ONE Purchase, vchain's procurement module.
Purchase orders flow from the ERP into the platform automatically. Suppliers receive them, confirm delivery dates and quantities, and send their responses back through the same channel. If a supplier's confirmation does not match the original order at the line or SKU level, the platform flags it immediately.
The procurement team sees the original order, the supplier's response, and any discrepancy in one place. They do not need to check the ERP, read through email threads, or ask someone to pull a report. The data is already there, already compared, already flagged if something is off.
This is the difference between a system that stores procurement data and one that actively supports procurement decisions.
Without platform integration | With vchain ONE connected |
|---|---|
Bookings entered manually in multiple systems | ERP triggers booking automatically |
Carrier updates checked system by system | All carrier events in one normalized feed |
Exceptions discovered through manual checking | Raised automatically by the rules engine |
Customs status requested from broker by email | Declaration milestones visible in the platform |
Emissions calculated in a separate tool | Per-shipment emissions data embedded |
Analytics exported and rebuilt in spreadsheets | Power BI reports embedded in the platform |
Supplier confirmations tracked in email or ERP | PO exchange managed through connected workflow |
Each row is a recurring task. When recurring tasks require manual steps, that is where operational time goes. When the connections are in place, those steps stop existing.
Why the connections matter more than the dashboard
A supply chain platform is only as useful as the data it can access. A dashboard with incomplete or delayed data does not help a team make faster decisions. It gives them one more place to check.
The Connectivity Hub is what makes the platform's other capabilities work. Real-time tracking works because carrier events arrive automatically. Exception detection works because the platform sees everything as it happens. Analytics are accurate because the data comes from connected sources, not manual exports.
Getting the integrations right is not a technical detail to sort out after go-live. It is what determines whether the platform changes how the team works or just adds another screen to look at.
If your team is still moving data between systems manually, that is the problem the ONE platform is built to solve.
Frequently asked questions
What is the vchain Connectivity Hub?
The Connectivity Hub is the integration layer at the center of the vchain ONE platform. It handles protocol translation, data transformation, error handling, and logging for every data flow between the platform and external systems — including ERPs, carriers, customs brokers, and analytics tools.
Which carriers does vchain integrate with?
The ONE platform currently integrates with six carriers: DHL, UPS, Schenker, Agility, Searates, and Unifaun/NShift (Apport). Each connects through its own protocol — REST API for real-time event feeds, FTP XML for batch processing — but all produce a standardized output inside the platform.
How does vchain integrate with an ERP system?
The connection is bi-directional. Booking requests originate in the ERP and arrive in the platform automatically. Confirmations, shipping labels, and status updates return to the ERP through the same connection — eliminating manual re-entry and the errors it introduces.
