Part of mPorts OMS
Keep every shipment and every channel updated.
Shipping in mPorts OMS is the capability that turns a fulfillment decision into a shipment and follows it. It covers shipment creation, carrier labels, tracking workflows, and the shipping rate analysis attached to them.
A tracking number is not the same as knowing where something is. The useful state is whether the shipment is doing what was promised, and that only exists if the promise and the movement are held in the same record.
Shipping sits inside the order lifecycle rather than beside it for the same reason returns does: the moment it becomes a separate system, someone has to reconcile two versions of the same event.
What this looks like in the product
An interface diagram using the product’s real navigation and field names — no customer data.
Shipments
Created, labelled, and tracked against the promise
- Ready to shipcarrier · service
- Label createdtracking
- In transitagainst promised date
- Exceptioncause
-
Shipment creation
Turning a fulfillment plan into a shipment.
-
Carrier labels
Label generation across carriers, in the same flow.
-
Tracking workflows
Following a shipment against what was promised, not just where it is.
-
Shipping rate analysis
What lanes actually cost, next to the operation.
Questions buyers ask
- Which carriers are supported?
- Connecting to carriers is part of what mPorts OMS does. Whether a specific carrier is already connected depends on whether that connection has been built, which we confirm rather than assume.
- Does it handle international shipments?
- What a shipment requires varies by lane and by channel. The honest answer for a specific route is a scoping conversation, not a yes.