mPorts

Part of mPorts OMS

See margin on every order.

Analytics in mPorts OMS is the capability that reports on the operation from inside it. It covers inventory health, per-SKU cost, days in inventory, order profit and loss, fulfillment and shipping rate analysis, and saved reports that can be run again.

Reporting assembled after the fact answers last month's question. The reason this sits inside the operation is that the questions worth asking — what is sitting too long, which lane is quietly expensive, what did this order actually earn — are operational questions whose answers change what you do today.

These are the same records the operation runs on, not a copy of them moved somewhere else and reconciled on a schedule.

What this looks like in the product

An interface diagram using the product’s real navigation and field names — no customer data.

Analytics

Reports

Run, save, and run again

  • Inventory healthwhat is sitting, how long
  • Per-SKU costcost · days in inventory
  • Fulfillment costwarehouse · shipping rate
  • Order performanceprofit and loss
Reports: operational reporting on inventory health, per-SKU cost, fulfillment cost and order performance.
  • Inventory health

    What is sitting, how long, and what that is costing.

  • Per-SKU cost

    What a SKU costs you, and how long it has been sitting.

  • Fulfillment and shipping cost

    Warehouse cost and shipping rate analysis.

  • Order performance

    Order profit and loss, against what was promised.

  • Saved reports

    Reports that can be run again rather than rebuilt.

Questions buyers ask

Is this a separate analytics product?
No. Analytics is a capability of mPorts OMS. There is no standalone analytics application and it is not sold separately.
Can we export to our own BI tool?
Reporting lives next to the live record, and getting data out into another tool is a scoping question we would work through rather than assume.

Operate every channel from one place.