mPorts
简体中文

Part of mPorts OMS

Catch the orders going wrong before a customer does.

Exceptions in mPorts OMS is the capability that surfaces the orders which are not behaving and gives each one a reason. It covers exception detection across the order lifecycle, the workbench where they are worked, and the recorded resolution.

Talk to mPorts Back to mPorts OMS

Most orders are fine. The operational job is almost entirely about the ones that are not, and the cost of a bad system is that finding them takes longer than fixing them.

An exception is only useful if it names a cause. “Order 4471 is late” is a symptom; “Order 4471 is late because the allocated location is short two lines” is something a person can act on in one step rather than four.

Shipments that stopped moving, surfaced with the reason

A real example: labels were created and then nothing happened. Each row has been idle for more than seventy days, and the product says so in plain words rather than leaving it to be discovered.

The mPorts OMS shipment tracking screen, listing shipments with a status of Label Created, a days-idle count and the note “Not picked up yet”.
A screenshot of mPorts OMS. Tracking numbers and order numbers are obscured — a carrier tracking number can be looked up on the carrier’s own website, so it is not ours to publish. The idle counts and statuses are real and unaltered: this is the product surfacing shipments that never moved.

What this looks like in the product

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

Exceptions

Exception workbench

What is wrong, why, and what to do next

  • Inventory shortfalllines short · location
  • SLA at riskpromised date
  • Shipment problemcarrier
  • Fulfillment failurerecovery
The exception workbench: each exception carries its cause and the next step, rather than only a symptom.

  • Detection

    Exceptions raised across the lifecycle rather than noticed by a person.

  • Cause, not symptom

    Each exception carries why, so the next step is obvious.

  • Workbench

    One place to work them, instead of several screens per case.

  • Recorded resolution

    What was done is part of the order's record.

Questions buyers ask

Does the AI resolve exceptions automatically?
AI can explain what went wrong and suggest what to do, and it acts through the same workflow a person uses, with approval wherever your rules require it. What runs without a person watching depends on the rules you set — it is something you configure, not a default.
What counts as an exception?
Anything that means an order will not do what was promised: inventory shortfalls, missed SLAs, shipment problems, fulfillment failures.

Related reading

Operate every channel from one place.

Talk to mPorts Back to mPorts OMS