Every system you run, one tile each.
Your supply chain is already a mosaic. A store here, a warehouse system there, an ERP nobody wants to touch, and a carrier portal per country. We replace none of them. Each one becomes a tile that reads and writes against the same item identity, which is the only thing they have ever had in common.
Nothing matches that name. Tell us what you run and we will tell you what it takes: contact the team.
Where you sell
14 connectionsStore platforms and marketplaces. Three connect natively today with two-way sync, so orders flow in and statuses flow back out under your name. The rest are built per account; timing depends on the platform's API.
ShopifyWhere else you sell
14 connectionsMarketplaces, and the channel managers that feed them. Orders arrive in the same queue as your own store, with each channel's tracking and returns rules applied per channel.
Who carries it
6 connectionsDirectly contracted partners for the last mile, plus every carrier account you already hold. Negotiated rates are live in France and the United Kingdom. Everywhere else you connect your own accounts and keep your own rates, with the same labels, tracking, returns and invoice audit.





Where it is stored and picked
17 connectionsWarehouse management systems and fulfilment operators. We do not replace the system your warehouse team already knows. We read it through the item identity, so inbound, putaway, allocation and dispatch line up with the purchase order and the outbound label.
What runs the business
13 connectionsThe system of record. ERP connectors are scoped with your team under the enterprise offer, because no two implementations of the same ERP are alike.
What decides where an order is served from
13 connectionsOrder management and distributed order management. Where you run one, we read it. Where you do not, the console covers a single-warehouse operation on its own.
Where the product data lives
6 connectionsProduct information systems. The passport draws composition, origin and care data from here, so the PIM is read rather than re-keyed.
What the customer looks at
12 connectionsTracking aggregators and visibility platforms. If you already run one and your customers know it, we feed it rather than replace it. If you do not, consolidated tracking on your own domain is already included.
Everyone owns a tile. We assemble the picture.
None of these vendors will adopt another one's data model, so we do not ask them to. One identity per item, minted as early in the chain as we can reach, and every tile read through it.
From wiring to first shipment.
Between signing and your first real label.
We look at what you run
A call where you show us the systems and we tell you which are a connector, which are an API build, and which are a file drop.
The live ones connect themselves
Store connectors are an OAuth screen and a few minutes.
The rest get scoped properly
ERP, WMS and anything with EDI gets a written scope with your team before a line is built, so no field mapping is assumed.
First real order
The first label is generated from a real order, and tracking and the passport are checked against it before volume moves over.
Not on the list?
This page shows the systems we are asked about most, not a limit. If yours has an API, a file drop or EDI, it can be read. Tell us what it is and we will tell you what it takes.
Questions we get asked.
Which e-commerce platforms connect natively today?
Shopify, WooCommerce and PrestaShop have native two-way connectors you can install yourself. Orders flow in continuously and tracking flows back into the store under your own branding. Other platforms and marketplaces, including eBay and TikTok Shop, are built per account.
Do you replace my ERP, WMS or OMS?
No. Next Horizon reads and synchronises with them and never replaces them. Replacing a system of record is a multi-year programme that frequently fails, and a visibility problem does not require one.
How are ERP connectors scoped?
With your team, in writing, before anything is built. No two implementations of the same ERP are alike, and every expensive failure in this category starts with an assumed field mapping. SAP, Microsoft Dynamics 365 and NetSuite are the most common starting points.
My system is not on this page. Can you still connect it?
Usually. If it exposes an API, a file drop or EDI, it can be read. Tell us what it is and you get a clear answer on effort and timing.
Can I keep my own carrier accounts?
Yes, and many customers do. Your negotiated rates stay exactly as they are and the labels count against your plan allowance. The console, tracking, returns, invoice audit and the Digital Product Passport all work identically whether the rate is yours or ours.
Do I need a tracking aggregator as well?
No. Consolidated multi-carrier tracking on your own domain is already included. If you already run an aggregator your customers recognise, we feed it rather than ask you to drop it.
How long does a typical integration take?
A native store connector is minutes to install and a few business days to a first real label, with the variable being how many carriers and countries are in scope. An ERP or WMS connector is a scoped project and the timeline comes out of that scope, not out of a price list.