mPorts

Platform

How mPorts fits together

mPorts sells exactly two products. mPorts Distribution is where business buyers find and buy your products. mPorts OMS is where your team runs everything that happens after an order exists — orders, inventory, fulfillment and shipments across every channel, with connectivity, AI and analytics built into it. The two are separable, and most companies start with one.

Two products, and what sits inside them

Read down. The two products are the top two rows; everything below is part of mPorts OMS rather than something sold separately.

Sell & distribute
  • mPorts Distribution
Operate
  • mPorts OMS
Inside the OMS — connect
  • Connectivity
Inside the OMS — understand
  • Cost and margin reporting
Inside the OMS — work with AI
  • AI operations

A commercial operating model, not a systems architecture diagram. Connectivity, analytics and AI are things mPorts OMS does; none of them is a separate product, and nothing on this site will sell them to you as one.

The two products

  • mPorts Distribution

    A B2B commerce and distribution platform for manufacturers, brands, distributors and business buyers. Where business buyers find your products, ask for a quote, and order.

    mPorts Distribution
  • mPorts OMS

    The commerce operations system for orders, inventory, fulfillment and shipments across sales channels. Where your team runs what happens after the order.

    mPorts OMS

What mPorts OMS includes

These are capabilities of mPorts OMS. Each has its own page because each is worth understanding on its own, not because each is a separate thing to buy.

  • Orders

    One queue across every connected channel, with a control tower over it.

    Orders
  • Inventory

    Position across locations, with policy set per channel.

    Inventory
  • Fulfillment

    Where an order ships from, and what happens when that plan fails.

    Fulfillment
  • Shipping

    Shipment creation, carrier labels and tracking against what was promised.

    Shipping
  • Exceptions

    The orders that are not behaving, each with a cause and a next step.

    Exceptions
  • EDI

    Connect to retailers the way they require.

    EDI
  • Connectivity

    How the OMS connects to the systems you already run on.

    Connectivity
  • AI operations

    Ask an operational question and get an answer from the information the OMS already holds.

    AI operations
  • Analytics

    Inventory health, per-SKU cost, fulfillment cost and order performance.

    Analytics

Why analytics is not sold as a separate product

Cost and margin reporting — per-SKU cost, days in inventory, order profit and loss, shipping rate and warehouse cost analysis — lives inside mPorts OMS, because those are operational questions and they are best answered where the work happens.

Older internal material named a standalone analytics product. We found no shipping implementation of one, so it is not presented as a product here.

  • Per-SKU cost and days in inventory
  • Order profit and loss
  • Shipping rate and warehouse cost analysis

You do not have to adopt both

The two products are separable, and which one matters depends on where the work currently hurts. A company that needs a route to business buyers has a different starting point from one whose orders already arrive and whose difficulty is operating them.

Questions buyers ask

Where should we start?
Wherever the manual work is. If reaching business buyers is the constraint, start with mPorts Distribution. If orders already arrive and serving them is the constraint, start with mPorts OMS.
Does mPorts replace our ERP?
No. mPorts is designed to run alongside the systems you already have, connecting to them rather than replacing them.

Start where the work hurts.