Sources: where stock physically sits
Each source is a warehouse, shop, distribution center or drop-shipper, with its own address and its own quantity per product. A store with one location runs on the Default Source that Magento creates.
The product grid shows 20 under Quantity per Source and 14 under Salable Quantity, and a customer has just been told an item is out of stock while it's sitting on the shelf. Most of the time that gap is Magento's Multi-Source Inventory (MSI), built in since 2.3, doing its job: unshipped orders hold stock as reservations, and the out-of-stock threshold comes off the top. When the gap stays after orders ship, or the shelf count lives in another system entirely, something else needs fixing.
Salable quantity is what a website's stock can still sell. It's worked out across every source assigned to that stock.
| Warehouse source, quantity | 12 |
|---|---|
| Retail store source, quantity | 8 |
| Out-of-stock threshold (Held back so the store stops selling before it hits zero) | −2 |
| Reservations from four placed, unshipped orders (Created the moment each order is placed) | −4 |
| Salable quantity on the website | 14 |
When those four orders ship, Magento adds compensating reservations and deducts the units from whichever source shipped them. Source quantity falls to 16 in total, the reservations net to zero, and salable quantity stays at 14. A cancellation or refund adds a compensation the other way and gives the units back.
Each source is a warehouse, shop, distribution center or drop-shipper, with its own address and its own quantity per product. A store with one location runs on the Default Source that Magento creates.
A stock groups sources in priority order and links them to sales channels, which today means websites. One stock can serve several websites, but each website belongs to exactly one stock.
Instead of decrementing source quantity when an order is placed, Magento writes a reservation that lowers salable quantity right away. It's how checkout stays fast under load without overselling. Every reservation for an order should net to zero once it's complete, canceled or closed.
When an order ships, the source selection algorithm suggests where it comes from. Priority uses the order of sources in the stock. Distance Priority uses the shipping address, worked out through Google Maps (which needs an API key and may cost money) or offline from imported geocode data.
How you'll know: Salable quantity is lower than it should be long after the orders behind it were shipped or canceled.
Fix: Run bin/magento inventory:reservation:list-inconsistencies to list the mismatches, and pipe its raw output (-r) into bin/magento inventory:reservation:create-compensations to fix them. Run the list again to confirm it reports no inconsistencies, then look for the order flow, import or extension that skipped the compensation.
How you'll know: Someone imports a quantity file every night, and overselling happens in the hours between imports.
Fix: Have the warehouse system's changes reach Magento's source quantities as they happen, through the inventory API, instead of on a timer. The Magento API page covers how integrations authenticate.
How you'll know: An item shows available on the Magento store after its last units sold on Amazon, eBay or Walmart Marketplace.
Fix: MSI only knows about Magento orders. One system has to own the count and every channel has to sell from it, through a marketplace connector or a custom sync that adjusts the same source quantity.
How you'll know: Stock updates 'succeed', but the storefront doesn't change, or every update lands on the default source.
Fix: Adobe's guidance is to write per-source quantities as source items and read the aggregated stock item for availability. Updating the wrong one, or ignoring source codes, leaves salable quantity where it was.
It's the inventory system built into Magento since version 2.3, in both Open Source and Adobe Commerce. It tracks quantity per physical location (sources), groups locations into stocks that each website sells from, holds stock for open orders with reservations, and suggests which location ships each order through a source selection algorithm.
The amount a website can still sell: the quantities of every source in its stock, less the out-of-stock threshold, less reservations for orders that haven't shipped. That's why it's often lower than Quantity per Source in the product grid, and why it doesn't change again when those orders ship.
No. MSI only sees orders placed in Magento. A sale on Amazon, eBay or another channel leaves Magento's quantities untouched unless a marketplace integration or a custom connection writes the change back in.
A source is a physical place with its own quantity per product. A stock is a set of sources, in priority order, linked to one or more websites. Shoppers see the stock's salable quantity; warehouse staff ship from a source.
There's no built-in WMS connector, but Magento's inventory API lets an outside system read stock and write per-source quantities, which is what any WMS integration relies on.
n-frames does, as an integration we build and look after. We write warehouse receipts and adjustments to the right Magento source as they happen, feed marketplace sales back into the same count, and report any SKU the two systems disagree on to a person instead of overwriting it.