Skip to content

Solution — Inventory

What the site promises has to be what the warehouse can do.

Inventory problems are experienced by customers as broken promises: an item that was in stock at checkout and cancelled a day later, a delivery estimate nobody could honor, a back-in-stock email for something still not back in stock.

Underneath, the cause is usually definitional. Nobody has decided precisely what "available" means — across locations, channels, pre-orders, allocations and in-flight transfers — so each system computes its own answer.

  • Availability
  • Allocation
  • Channel sync
  • Fulfillment

Symptoms

The cost shows up in support

Support ticket volume is often the most honest inventory report a business has. When cancellations and "where is my order" tickets climb together, the problem is usually upstream of the storefront.

Signals

  • Oversells on fast-moving items
  • Cancellations after the order confirms
  • Availability lagging behind reality
  • Counts differing by sales channel
  • Pre-orders and back-orders handled manually
  • Bundles and kits with unreliable stock
  • Fulfillment status arriving late or not at all
  • Support absorbing the difference

Availability is a business rule, not a number a system happens to hold.

Likely causes

Where accuracy gets lost

  1. 01

    No single definition of available-to-sell

    On-hand, committed, allocated, in transit and safety stock are combined differently by each system that touches them.

  2. 02

    Sync timing mismatched to velocity

    An hourly sync is fine for slow SKUs and disastrous for the ones that sell out in twenty minutes.

  3. 03

    Multi-location logic left implicit

    Which locations are sellable, in what priority, and what happens when one runs dry.

  4. 04

    Bundles, kits and pre-orders as exceptions

    Handled manually because the model never accounted for them, then forgotten under load.

  5. 05

    Fulfillment events not flowing back

    Shipments, partial shipments and tracking that never reach the storefront or the customer.

  6. 06

    Returns and restocks unmodeled

    Physical stock returns to the shelf but availability doesn't, or does twice.

What we'd examine

Trace one SKU end to end

The fastest diagnostic is to follow a single fast-moving product through every system that claims to know its quantity — receiving, ERP or inventory system, 3PL, storefront, marketplace — and record where the numbers diverge and why.

From there the fix is usually part definition, part integration, part merchandising: sell what you can deliver, and say so clearly on the page.

When the ERP is the other half of the problem

The audit

  • Available-to-sell definition and formula
  • Location and channel allocation rules
  • Safety stock and buffer policy
  • Sync frequency by SKU velocity
  • Pre-order and back-order handling
  • Bundle and kit stock logic
  • Order routing and split shipments
  • 3PL data exchange and latency
  • Fulfillment and tracking write-back
  • Return, restock and refund flow
  • Cancellation and oversell reporting
  • Customer-facing availability messaging

Proof

Constraints that can't be faked

Wulf's Fish

Five years of extensive custom development for a business selling perishable product, where availability, cut-offs and fulfillment logic have to reflect operational reality rather than a generic commerce model.

Read the Wulf's Fish case study

  • Custom development
  • Store management

ROAM Adventure Co.

Direct-to-consumer and wholesale demand drawing on the same physical inventory — the case where allocation rules stop being theoretical.

Read the ROAM case study

  • Wholesale portal
  • Store management

Selling things you can't ship?

Tell us which SKUs cause the most cancellations. That's usually where the definition broke.