mPorts

Part of mPorts OMS

Know exactly where every order stands.

Every order from every connected retailer and marketplace, in one queue, with a control tower over it that shows what is new, what is late and what is stuck. Orders in mPorts OMS covers how orders come in, what state each one is in, the control tower view, and the record of what changed and who changed it.

A channel does not just send you an order. It sends you its own idea of what an order is — its own statuses, its own cancellation rules, its own definition of late. Managing five channels by hand means holding five of those models in your head at once.

The point of one queue is not tidiness. It is that a question like “which orders are at risk today?” has one answer, instead of five partial ones someone has to piece together before anyone can act.

What this looks like in the product

The mPorts OMS Orders screen: tabs for order state, summary cards, filters, and a table of orders showing date, channel, warehouse and status.
The Orders queue: every order from every connected channel, with its state, channel and warehouse, and the ones that need attention first. Customer-sensitive information has been redacted from product screenshots.

Can I see one order end to end?

An order open in mPorts OMS: status, channel, warehouse, the line items and their status, and the warehouse allocation across locations.

An order detail in mPorts OMS: order info with status, channel, order date and warehouse; an LTL carrier section; line items with status; and a warehouse allocation table showing available units per location.
An order in mPorts OMS: status, channel, order date and warehouse; the LTL carrier; line items; and available units per location. Customer-sensitive information has been redacted from product screenshots.

One order, worked end to end

Worked example

A retailer order was accepted two days ago and has not moved since.

  1. Signal

    The order sits at the same stage while everything around it ships.

  2. What mPorts shows

    The stage it stopped at, submitted to the warehouse and never received, with the timestamps on both sides.

  3. Investigation

    The warehouse submission and the missing acknowledgment side by side, plus whether the stock is still where the plan assumed.

  4. Recommendation

    Resubmit to the warehouse, or replan if the stock has moved. mPorts names the blocker and the fix that matches it.

  5. Approval

    A person confirms the resubmission wherever your rules require one. Nothing that writes runs on its own.

  6. Action

    The resubmission runs through the same steps a person would use.

  7. Record

    Who did what, when, and what the order looked like before and after, kept on the order.

  • Order capture

    Orders arrive from connected channels into one queue, in one shape.

  • Order state

    A named state at every point, so an order is never merely “in progress”.

  • Control tower

    Attention on the orders that need it rather than the ones that do not.

  • Audit record

    Material changes record actor, entity, action, and before and after state.

Questions buyers ask

Does this replace the channel's own order screen?

No. Each marketplace still keeps its own record of its own sales. mPorts OMS holds one picture across all of them, which is the thing no single marketplace can give you.

What counts as an order being “at risk”?

That depends on the commitments attached to it — the promised date, the channel's rules, the inventory behind it. The value is that those live in one place rather than being reassembled by hand.

Operate every channel from one place.