Platform
mPorts is an AI commerce operations platform: the AI operating layer that works across the marketplaces, retailers, ERP, warehouses, 3PLs and carriers a business already runs on. Two products run inside it: mPorts OMS for commerce operations and order management, and mPorts Distribution for operating your own B2B distribution marketplace. Each external system is connected once, and every mPorts application uses that same connection; AI operations, and the permissions, approvals and verification that govern them, are capabilities of the platform, delivered today inside mPorts OMS.
One platform, two products, and the platform’s own capabilities. Everything below this section explains how it works; this is what it is.
The mPorts Platform
What a customer adopts, and what runs inside it
Platform capabilities
Two products run inside the platform. They are separable, and most companies start with one.
Product · commerce operations
Commerce operations for product launch, orders, inventory, fulfillment and shipping across the channels you sell on — with analytics that show what the operation costs and earns, and AI that can investigate and act.
Product · B2B distribution
B2B distribution and marketplace operations: build and run your own marketplace on your own domain, where your suppliers list, your business buyers order, and you run what happens in between.
Four capabilities of the platform itself. They are not standalone products, and they are not sold separately: they are delivered today inside mPorts OMS.
Connect marketplaces, retailers, ERP, warehouses, 3PLs, carriers and the other systems that run your commerce — each once — so everything mPorts does shares one connection.
Direction
The business context, live state, history, relationships, decisions and outcomes AI needs to understand an ongoing operation. mPorts records all of it today; reasoning from that record when the next decision comes up is the direction it is building toward.
Ask questions in business language, investigate exceptions across the connected records, get the cause and a recommendation, and have permitted work performed after a person confirms.
Permissions, approval boundaries, audit trails, and verification of what actually changed in the external system — the same rules for AI as for people.
Read top to bottom: the systems you already run, connected once; the record of the operation AI works from; AI that asks, investigates, recommends and performs permitted work; the permissions, approvals and audit that govern it; and confirmation, from the external system’s own record, of what actually changed.
Today mPorts records every change, run, decision, confirmation and verification. Reasoning from that record when the next decision comes up is the stated direction, marked as such wherever it appears.
The same path whether a person raises the question or the system does. Five stages ship today; the sixth is where mPorts is going.
Marketplaces, retailers, ERP and WMS, 3PLs, carriers, EDI and spreadsheets — connected once, so orders, products, inventory, shipments and costs flow through one connection.
One operating picture: what each product, order, warehouse and policy is, how they relate, what is happening now and what needs attention.
The cause named and the next step recommended — by the team, or by AI reading the same records — with the reasoning shown.
The change runs through the same governed workflow a person’s would, in the connected system, after a person confirms where your rules require it.
mPorts checks the external system’s own record that the change took. Every record shows verified, stale or unknown; unknown is never shown as success.
Every run, decision and change is recorded today. Using that accumulated experience to shape the next decision is the direction mPorts is building toward.
The difference is how much of the operation mPorts owns. Most evaluations land between these two, and moving from the right column to the left later is a normal path rather than a migration.
The systems you already run connect to mPorts once. From them mPorts builds one operating picture of products, listings, orders, inventory, fulfillment, shipments and cost. The work runs in mPorts OMS, or in mPorts Distribution where you operate your own B2B channel. AI operations read the same records, recommend, and act through governed workflows after a person confirms, and mPorts verifies the resulting state in the external system.
Wherever the manual checking is. If orders already arrive and running them across channels, warehouses and cost is the constraint, start with mPorts OMS. If the constraint is running the marketplace between your suppliers and your business buyers, start with mPorts Distribution.
Alongside it. mPorts connects to the systems you already run and keeps them in place; the ERP stays the system of record for finance and the ledger, and mPorts runs the commerce operation across it and the channels, warehouses and carriers around it.
No. They are capabilities of the mPorts Platform, delivered today inside mPorts OMS. Each system connects to mPorts once and everything built on the platform shares that connection; AI operations and the controls around it work on the same products, orders, inventory and warehouse billing the products run on. The products you buy are mPorts OMS and mPorts Distribution.
Today it records: every run, decision, confirmation and change is kept, with what was looked at and what changed. Using that accumulated experience to shape the next decision is the direction mPorts is building toward, and the site labels it as direction wherever it appears.
Which systems, which channels, and where someone checks by hand today. We will show you which layer mPorts would run for you — and say so if it is the wrong fit.