TL;DR
Inventory software for ecommerce prevents stock confusion when it keeps one SKU record by location, separates sellable inventory from committed and held units, and records each fulfilment and return event. Test those states with two sales channels, a partial shipment, a cancellation, and a damaged return before choosing a system.
Use a five-event demo to choose inventory software for ecommerce: two channel sales, a fulfilment handoff, a cancellation, and a return. Buy the system only if it shows sellable stock separately from committed, unavailable, and incoming units throughout the test.
For this checklist, sellable stock means stock a customer can buy now. Shopify’s inventory model separates available, committed, unavailable, incoming, and on-hand quantities. That separation gives ecommerce teams the ledger they need to prevent stock confusion.
The system needs six capabilities: canonical SKU mapping, inventory commitment, channel allocation, location rules, fulfilment handoffs, and return disposition.
What Ecommerce Inventory Software Must Solve
One SKU sold in two places is one inventory problem. Your storefront, marketplace, warehouse, and sales team must work from the same SKU, variant, and location record.
A buyer should see one answer to four questions:
- How many units are physically on hand?
- How many units are already promised to open orders?
- How many units are held for quality control, damage, or safety stock?
- How many units can each channel sell now?
Committed inventory is stock set aside for unfulfilled orders, draft orders, or ready-to-ship transfers. Unavailable inventory is physical stock held from sale for reasons such as damage, quality control, or safety stock.
A polished dashboard is not enough. The software must show why a number changed, who changed it, and which order, transfer, receipt, or return caused the change.
How Overselling Happens Across Sales Channels
Overselling starts when one channel publishes physical stock while another channel has already claimed part of it. The warehouse may hold the right number, but the storefront shows the wrong number.
A common failure sequence looks like this:
- Your DTC store accepts the last three units.
- Those units sit in an open order but do not reduce marketplace availability.
- A marketplace sells the same three units.
- The warehouse finds only one physical set of stock to ship.
Inventory commitment prevents that mistake. When an order arrives, the system should move the quantity from sellable stock to committed stock before another channel can offer it.
Channel allocation adds a second control. An allocation rule reserves part of shared stock for a channel, customer group, warehouse, or priority order. Ask the vendor to show what happens when a wholesale order, a marketplace order, and a DTC order all request the same last units.
For confirmed sales orders, use clear inventory reservation rules before running a promotion. A team should not decide which order wins after the orders arrive.
Sellable Stock vs. Committed Inventory
Sellable stock is not the same as on-hand stock. On-hand stock includes units that may already be promised or unavailable for sale.
Start the demo with 20 units on hand, 2 units in quality control, 0 committed units, and 5 incoming units. Your sellable quantity is 18:
20 on hand − 2 unavailable − 0 committed = 18 sellable.
The 5 incoming units stay outside that calculation until receiving confirms them. Shopify also treats incoming inventory as unavailable for sale until receipt.
Run the following script with one real SKU, one warehouse, and two sales channels. The state names can differ, but the numbers and audit trail must hold.
-
Starting inventory: Show on hand 20, unavailable 2, committed 0, incoming 5, and sellable 18. Request the SKU, location, and channel mapping.
-
DTC order for 3: Show on hand 20, unavailable 2, committed 3, incoming 5, and sellable 15. Request the order ID and event log.
-
Marketplace order for 15: Show on hand 20, unavailable 2, committed 18, incoming 5, and sellable 0. Request both channel quantities.
-
Fulfil 3 and cancel 2: Show on hand 17, unavailable 2, committed 13, incoming 5, and sellable 2. Request the pick and cancellation records.
-
Receive a damaged return: Show on hand 18, unavailable 3, committed 13, incoming 5, and sellable 2. Request the return condition and disposition.
-
Release the return after inspection: Show on hand 18, unavailable 2, committed 13, incoming 5, and sellable 3. Request the approval and audit trail.
These numbers show the decision you need to make. If a vendor cannot explain each unit after these events, the system will force your team back into spreadsheets.
Run This Ecommerce Inventory Demo
Create the DTC order for 3 units first. Then create the marketplace order for 15 units immediately after it.
The marketplace must display 0 sellable units after both orders. Add one more unit to a cart or test order. The vendor should show the configured response, such as preventing purchase or creating a backorder.
Next, send the DTC order to fulfilment. Ask the vendor to show the pick ticket, warehouse bin, packing slip, partial shipment status, and tracking update. A partial shipment must not release the unshipped unit back to sale.
Then cancel 2 unfulfilled marketplace units. The system should release those 2 units from committed stock and return them to sellable stock when the cancellation uses a restock rule. Shopify’s order cancellation flow selects restocking by default.
Finally, receive one shipped unit as a damaged return. The unit should enter an unavailable or quality-control state. Only an inspection decision should move it back to sellable stock.
Check Workflows After Channel Sync
Channel sync matters, but it is only the first handoff. The next workflows determine whether the number remains trustworthy.
Allocation and Location Rules
Ask where the system commits inventory. A useful answer names the warehouse, bin, order, sales channel, and timestamp.
Ask whether a store can sell stock held in another location. The system should show the eligible fulfilment location before it shows a customer an available quantity.
If your team manages multiple sites, readers can compare methods for live multi-warehouse reporting. Your demo should include one transfer between locations and show when the destination can sell the transferred stock.
Warehouse and Fulfilment Handoffs
A warehouse handoff starts when an order becomes pickable. The warehouse needs the correct SKU, quantity, bin, lot where relevant, and shipment status.
Require the vendor to show receiving, picking, packing, and partial shipment actions. A picker should not need to guess which unit belongs to which order.
Teams improving warehouse execution can use this warehouse management guide alongside the demo. The guide helps you map the physical work before configuring software around it.
Returns, Lots, and Reporting
A returned unit has at least two possible outcomes: sell it again or hold it from sale. The system should record the condition decision before it changes channel availability.
Lot and serial tracking matter when you must identify the exact batch or individual unit returned. Use lot and serial tracking software when expiry dates, recalls, warranties, or high-value products make that record necessary.
Your final reporting test is simple: open the SKU and ask why the sellable quantity is 2, 0, or 18. The system should show every contributing event without manual reconciliation.
When Free Ecommerce Inventory Software Is Enough
Our rule of thumb: free ecommerce inventory software is enough when one person manages one stock location, one simple catalogue, and can pass the five-event test without a manual export.
Move to a fuller system when you need any of these controls:
- Shared stock across a storefront and marketplace
- Channel-specific allocation rules
- Multiple warehouses or fulfilment partners
- Partial shipments and backorders
- Returns that need inspection before resale
- Lot, serial, or expiry tracking
- A visible audit trail for stock adjustments
A free plan can track quantities. It becomes risky when your team must decide which order receives the last unit or whether a return can be sold again.
Ecommerce Inventory Software Buyer Checklist
Use this checklist after every vendor demo:
- Map one real SKU and variant across every selling channel.
- Show on-hand, sellable, committed, unavailable, and incoming quantities.
- Create two orders that consume the last sellable units.
- Show the rule for an additional order after sellable stock reaches 0.
- Demonstrate location and channel allocation.
- Generate a pick task and complete a partial shipment.
- Cancel an unfulfilled quantity and show the restock result.
- Receive a damaged return without making it sellable.
- Release the return after inspection and show the audit record.
- Export or report the full stock history for that SKU.
A vendor that passes all 10 checks has shown more than inventory sync. The vendor has shown that its inventory record can survive normal ecommerce operations.
FAQs
Does a Shipping App Replace Inventory Software?
No. A shipping app creates labels and sends tracking, while inventory software controls whether stock is available before fulfilment begins. Keep the inventory system as the stock ledger, then send approved fulfilment work to shipping tools or warehouse teams.
What Should a Bundle Do to Component Stock?
A bundle should commit its components when the bundle order commits. A three-item kit needs three component-level inventory movements, even when the customer sees one product. Test one real bundle if your catalogue sells kits, packs, or multipacks.
What Should a Failed Inventory Sync Trigger?
A failed sync should create a visible exception with the SKU, channel, timestamp, and failed event. Your team needs a defined owner and a safe response, such as pausing the affected listing or reducing sellable stock until the event is resolved.
Can a 3PL Be the Inventory Source of Truth?
Yes, if the 3PL sends timely order, receipt, adjustment, shipment, and return events into the same inventory ledger. Run the five-event script with the 3PL connection, not only with the software’s demo data.
At Arka, we help Salesforce teams commit, allocate, and reallocate inventory while keeping warehouse operations and inventory visibility in Salesforce. Our Basic plan is $199 per month, paid yearly, and includes multiple warehouses, purchase orders and transfers, barcoding and packing slips, and inventory alerts.
