Why your website says in stock and the shelf says otherwise

One of the questions I am often asked is why customers keep running into problems that nobody inside the business can see. Inventory visibility is a good example, few customer frustrations are as avoidable as discovering that a product shown as available online is not available when it matters. Whether the customer is visiting a store, ordering online, reserving for collection or speaking to customer support, they expect the stock information in front of them to be accurate. When it is not, the problem extends well beyond operational inconvenience. Customers begin to question the reliability of the whole business.

How the gap appears

It is easy to assume that inventory problems start with a single system failure. In my experience, they rarely do, they emerge gradually from a collection of disconnected processes and technologies. A growing company may have an eCommerce platform, an ERP system, a warehouse management solution, a point of sale environment, marketplace integrations and store level stock systems, each updates stock information at its own interval. At low transaction volumes, this is a manageable technical compromise. As volumes grow, the compromise becomes a customer experience problem.

A stock adjustment in one system may take minutes, hours or longer to appear in another. During that window, customers make decisions using information that may already be wrong. The result is a gap between what the business believes is happening and what customers are actually experiencing. Looking back over four decades in technology, including the large scale banking infrastructures I worked on in the 1980s and 1990s, the principle has not changed. When systems hold different versions of the same fact, someone eventually pays for the reconciliation. Increasingly, that someone is the customer.

Inventory accuracy is a customer experience measure

Inventory accuracy is usually treated as an operational metric. I think it is better understood as a customer experience metric. Customers do not see databases, integrations, warehouses or allocation rules. They see a simple promise: available or unavailable. Every time that promise proves inaccurate, confidence erodes, it is also worth noting that businesses that handle this best are rarely those with the most systems, they are typically those with the most connected systems.

Key considerations

Customers treat stock information as a commitment

When a website indicates that a product is available, customers generally read it as confirmation rather than an estimate. They may travel to a store, place an order, reserve an item or build plans around it. If the information proves wrong, the frustration is out of proportion to the transaction itself, because the issue is no longer availability. It is the perceived reliability of the business.

Latency creates hidden revenue loss

Many organisations focus on overselling as the primary risk, and it is a genuine one. The opposite problem can be just as damaging, and is far harder to spot.

If stock levels update slowly, a product may appear unavailable online while units sit on a shelf or in another location. Customers abandon purchases that could have been fulfilled, and nobody records a lost sale that never became an order. The commercial impact is often larger than businesses realise precisely because it is invisible in most reporting.

Omnichannel depends on shared visibility

Click and collect, ship from store, endless aisle, marketplace selling and in-store ordering all rest on the same foundation: trusted inventory data. The more channels a business operates, the greater the consequences of inaccurate stock information. Omnichannel retail cannot work properly if every system operates from a different version of reality.

Customer service cannot fix a data problem

Support teams are frequently left managing frustration caused by inventory inaccuracies. Excellent service can recover individual situations, but it does not address the root cause. Resolving stock visibility problems through customer service is usually the most expensive and least scalable approach available.

Real time visibility requires architectural thinking

Accurate inventory rarely comes from a single software purchase. It requires clear ownership of inventory data, well designed integrations, near real time synchronisation, robust exception handling and a defined source of truth. Architecture ultimately determines whether stock data can move quickly enough to meet modern customer expectations.

What I have seen in practice

Two projects from my own experience illustrate the point, although neither was framed as an inventory project at the outset. The first was a school wear and book bag manufacturer whose outdated systems were holding back growth. We built a fully integrated eCommerce and back office system, and the result was an 80% increase in operational output alongside a much better customer experience. The gain came less from the website than from the website and the back office finally working from the same information.

The second was a launch management & gift card provider, which for years processed gift card orders manually, adapting to the different formats of each processor. Moving to a centralised ordering platform with unified API services removed that intervention and gave the business a single, dependable view of its orders. Different sectors, different products, but the same lesson: when systems share a source of truth, a good deal of day-to-day friction disappears.

Business implications

When inventory data cannot be trusted, companies tend to see:

• more order cancellations
• higher customer service workloads
• lost sales opportunities
• reduced customer confidence and lower repeat purchase rates
• greater operational complexity
• increased reputational risk

Conversely, businesses that achieve accurate stock visibility benefit from smoother customer journeys, better fulfilment performance, higher conversion rates and stronger loyalty. Whilst there are clear benefits, they depend on treating the work as more than a technical exercise.

Practical considerations

For founders and leadership teams wondering where they stand, a few questions are a sensible starting point:

• Where does inventory data originate, and which system is the primary source of truth?
• How is stock information currently synchronised across channels?
• What is the delay between an inventory change and the customer facing update?
• How many cancellations and support contacts are caused by stock discrepancies?
• Can the current architecture support real time or near real time synchronisation as the business grows?

It is also worth deciding who owns the answer. Inventory visibility sits across operations, technology and customer experience and projects that belong to everyone often belong to no one.

Final reflection

Inventory accuracy directly influences customer trust. Disconnected systems create customer facing problems long before internal teams recognise them, and revenue can be lost through underselling as much as overselling. The quality of your inventory architecture increasingly determines the quality of your customer experience. Ultimately, technology should support broader business goals, and in this case the goal is simple: when a customer is told something is available, it should be. Hopefully these reflections help you consider where your own business stands.