Part of mPorts OMS
Know what you can sell, what’s running low, and what it costs to hold.
Inventory in mPorts OMS shows the stock at every warehouse, lets you decide how much each channel may sell, and sends those numbers out so channels stop disagreeing with the warehouse. The same records answer the next questions — what is running low, what has stopped moving, how old it is and what it costs to hold — and the system notifies the team when stock at a warehouse falls below its floor.
The questions inventory should answer without a spreadsheet
Each is answered from a screen or a notification in mPorts OMS today — the warehouse counts, the channel limits and the warehouse’s own bill.
What can we sell, and where?
Actual stock, reserved and available per SKU per warehouse, with what each channel is allowed to sell from it — and incoming units on open purchase orders.
What is running low?
When stock at a warehouse falls below its floor, the team is notified once, and the notification opens the SKU. Low-stock listings are flagged on the product itself.
What has stopped moving?
Days in inventory shows each SKU’s on-hand lots by age band, the units past ninety days and the oldest lot on shelf.
What is it costing us to hold?
Storage allocated to each SKU from the warehouse’s own bill — labelled as allocated, because the warehouse bills per warehouse, not per SKU.
Do the channel and the warehouse agree?
The count at every warehouse next to what each channel is allowed to sell from it, so a channel selling stock the warehouse no longer holds is visible before the order fails.
What deserves a decision?
Two screens read together: Days in inventory for a warehouse, and Cost Explorer’s storage line for the same warehouse — so the decision about slow stock is made on purpose rather than discovered in next month’s bill.
Stock by warehouse, and what each channel may sell
The Inventory screen: stock by warehouse, with the available figure each channel’s limit draws from.
Why one number for every channel oversells
Publishing one global availability number to every channel is the simplest thing to build and the most expensive thing to operate. The number was true when it was sent and false by the time it was used.
You set a limit per channel because channels are not equal. One deserves a safety buffer, another gets everything you have, a third is held back while a big order is outstanding. That is a business decision, and you make it as one.
One discrepancy, worked end to end
One retailer shows zero available for a SKU that your other channels are still selling.
-
Notice
A retailer shows zero stock for a SKU while the warehouse still has units.
-
What mPorts shows
The warehouse count for the SKU, and how much each channel is allowed to sell from it.
-
Investigate
The update that sent zero to that retailer, and the limit or buffer that produced it.
-
Recommend
Correct the limit or the source of the count. mPorts shows the options and the number each would send; the operator decides.
-
Decide
The change is made by a person with the right to make it.
-
Act
The corrected availability goes out on the next inventory feed to that channel.
-
Record
The change and the update are recorded, so the next person can see why the number changed.
-
Inventory visibility
Actual, reserved, available and incoming per SKU per warehouse, as one picture.
-
How much each channel may sell
What each channel sees, decided per channel rather than globally.
-
Inventory feeds
Publishing availability and prices outward to connected channels, with an error queue when a feed is rejected.
-
Low-stock notification
One notification when stock at a warehouse falls below its floor, opening the SKU.
-
Days in inventory
How long stock has been sitting, by SKU and warehouse, with the oldest lot on shelf.
-
Cost to hold
Storage and fulfillment allocated to each SKU from the warehouse’s bill, labelled as allocated.
Questions buyers ask
How does mPorts prevent overselling?
By keeping one stock count and letting each channel’s limit decide what it is told. Whether that eliminates overselling on a given channel depends on how that channel is connected and how quickly it picks up updates.
How does mPorts tell us when stock is running low?
When stock at a warehouse falls below its floor, mPorts OMS sends one notification to the team and marks the listing as low stock; the notification opens the SKU. It fires once per episode, so nobody is notified about the same shortage every hour.
How does mPorts work with our warehouse management system?
Your WMS runs the building — bins, picks, putaway. mPorts OMS connects to it, keeps the stock count and the per-channel limits above it, and sends orders to it to ship.
Can I see how old the stock is and what it costs to hold?
Yes. Stock age by SKU and warehouse, and the storage and fulfillment cost allocated to each SKU, are part of Business analytics in mPorts OMS and read from the same inventory and billing records. Allocated cost is labelled as allocated.