OrderEase now supports linked inventory, allowing multiple SKUs to draw from a single shared physical stock pool. This is configured at the SKU level within your existing catalog and inventory settings, and applies across all order channels like rep app, portal, EDI, and integrated platforms.For trade businesses selling products across multiple pack sizes, inventory accuracy has always required manual intervention. A single bulk sale could pull from three separate SKU balances simultaneously -- and without someone reconciling them by hand, overselling was a matter of when, not if.
Linked inventory removes that exposure entirely. Every SKU tied to the same physical stock updates the moment a sale is recorded, on any channel, in any format. The math stays correct without anyone doing it manually.The problem is structural, not operational. B2B suppliers routinely manage one physical product; a bulk hopper of grass seed, a roll of material, a pallet of components that gets sold under multiple SKUs, depending on how the buyer orders. A lawn and garden distributor might carry that grass seed in 1kg, 5 kg, and 25 kg bags, or in a 25kg case. Three catalog entries. One physical stock pool.
Every OMS and ERP on the market treats those SKUs as independent entities, not because it reflects reality, but because relational inventory logic at the SKU level has historically been expensive to implement and rare to find outside enterprise platforms.
The result is a workaround economy. Weekly inventory audits. Spreadsheets that map SKUs back to their physical source. Trust that no one placed an order between the last manual count and the next one. For teams running automated order intake at scale, it is a reliability problem with real financial consequences -- oversells, fulfillment delays, and the kind of backorder notice that erodes a buyer relationship faster than almost anything else.
OrderEase now treats linked SKUs the way operations teams actually think about them: as representations of the same physical thing. That is not a small change in how the software works. It is a shift in the underlying model -- from a system that tracks catalog entries to one that tracks physical reality.
Within inventory settings, a supplier designates one SKU as the physical stock source and links other SKUs to it. Each linked SKU has a defined conversion factor: a 5kg bag draws 5 units from the source, a 25kg case draws 25. When an order comes in through any channel, the deduction occurs at the source level and propagates instantly to all linked SKUs. No batch syncs, no scheduled reconciliation jobs, no manual steps required.The reconciliation work disappears. The manual inventory reconciliation that ops teams run after every bulk order cycle -- the spreadsheet cross-reference, the SKU-by-SKU count, the 'did anyone place an order since the last sync' check -- goes away. Not reduced. Gone. At scale, it is a meaningful reduction in operational overhead that compounds with every additional SKU and every additional channel.
Overselling a SKU because a linked pack size depleted the underlying stock is one of the most common fulfillment errors in wholesale -- and one of the most preventable. Linked inventory makes that class of error structurally impossible. The stock count is accurate because it is derived from a single source of truth, not reconstructed from multiple independent counts kept in sync by hand.The system becomes the record. Inventory counts are trustworthy in real time, across the full catalog. Suppliers can act on what the system shows without verifying it manually first. For operations teams managing a large catalog with multiple pack sizes per product, stock level trends are now meaningful at the source level -- not fragmented across linked SKUs that each tell a partial version of the story.
Buyers see accurate availability when placing orders. Not approximate availability. Not last night's availability. The real number, at the moment of order submission, reflects every sale that has come in through every channel up to that point. Fewer order adjustments. Fewer backorder notices. Fewer support calls.Multi-pack inventory is a solved problem for DTC and retail brands. Shopify handles product variants natively. Warehouse management systems built for consumer fulfillment track physical stock at the unit level and map it to every SKU representation, so the operator doesn't have to think about it. The tooling works because the product model is relatively simple.B2B wholesale runs on a fundamentally different inventory model. The same physical product is often sold by weight, by unit, by case, and by pallet -- across different buyer segments, under separate SKUs, sometimes with different pricing, minimum order quantities, and lead times attached to each format. Most OMS and ERP systems were built on the assumption that a SKU is a discrete physical entity. That assumption works for most use cases and breaks for this one. The workaround has been accepted as the cost of operating at this level of complexity. It does not have to be permanent.
Customer feedback consistently flagged multi-pack inventory as a top source of fulfillment errors, particularly in lawn and garden, building materials, and food distribution. The issue became more acute as more customers moved to automated order intake, when orders are processed automatically, inventory discrepancies become fulfillment errors before anyone sees them.
Most B2B ordering tools treat inventory as a flat count per SKU. Linked inventory introduces relational logic at the SKU level that reflects how physical supply chains actually operate. The gap between 'tracks inventory per SKU' and 'tracks physical stock across linked SKUs' is not visible in a feature checklist. It is very visible in a fulfillment error report.