Part of mPorts OMS
Keep the systems you already use.
Connectivity is the part of mPorts OMS that talks to everything outside it: the marketplaces and retailers orders arrive from, the warehouses and third-party logistics providers that ship them, the carriers that carry them, and your own applications. Every one of those conversations runs through one integration engine, so a system is added in one place and checked in one place.
OMS connectivity
Why one engine instead of many separate connections
The obvious way to connect systems is the direct way: whichever application needs a marketplace talks to that marketplace itself. It is the fastest route to your first connection and the slowest route to your twentieth.
Separate connections multiply. Each application ends up holding its own logins, its own retry behaviour, its own idea of what a failed request means. When something breaks, "where does this talk to them?" has as many answers as you have applications.
What sits where
- Marketplaces & channels
- Warehouse & 3PL
- Carriers & tracking
- Application APIs
- OMS connectivity
- mPorts OMS
- mPorts Distribution
- AI operations
These are kinds of system, not a partner list. An adapter existing in code is not the same as a live certified integration, a commercial relationship, or permission to use a company’s name — so no partner names or logos appear on this page.
What this buys you day to day
One place to add a system. One place to look when a system misbehaves. One set of logins to keep safe, rather than several sets kept in several places.
It also keeps the rest of the software simpler: mPorts OMS asks for what it needs in its own terms, and the engine is the part that knows how a particular outside system expects to be spoken to.
- Marketplaces and commerce channels
- Warehouse and third-party logistics systems
- Carriers and tracking providers
- Application APIs
What we are not claiming
No integration count appears on this page. Counting adapter folders would produce a number, but it would not be a number about live, certified, in-production integrations — and that is the number a buyer is actually asking for.
ERP connectivity is not listed as an available capability. It is named in older internal material; we did not find an implementation, so it is not claimed here.
Questions buyers ask
- Is our system supported?
- Ask us and we will check rather than guess. Supported means a live connection, not the existence of an adapter folder, and we would rather answer the real question.
- Is connectivity a separate product we have to buy?
- No. It is part of mPorts OMS. mPorts sells exactly two products — mPorts OMS and mPorts Distribution — and connectivity is one of the things the OMS does.
- Do you support EDI?
- Yes. mPorts connects to retailers over EDI — purchase orders, acknowledgments, shipment notices and invoices — and the orders those documents create are operated alongside every other channel. Which retailers, and in which format, is a scoping conversation: large retailers each specify their own.
- Where do the logins live?
- With the integration engine, rather than scattered across each application. That is one of the main day-to-day reasons for keeping the connection in one place.