Your ERP Owns Your CX

Website says the product is available.

The warehouse has twelve.

Four are damaged, three are reserved for another channel, two are sitting in a stocktake discrepancy and the remaining three cannot be delivered to this customer.

The customer does not experience an inventory architecture.

They experience a lie.

Ecommerce teams are usually asked to fix the visible part.

“Change the stock message.” “Add an estimated delivery date.” “Improve the account page.” “Put a friendly apology in the email.”

In a simple store, Shopify can hold the product, price, inventory and order, but even this breaks down quickly as soon as more than one location is added, or more than 100 SKU’s.

In a complex B2B, wholesale or omnichannel business, the storefront is presenting decisions made across ERP, warehouse, finance, product, transport and customer-service systems. It can display those decisions. It cannot make the warehouse and finance agree just because the page needs one answer.

So then, you end up with your ERP quietly owning more of the customer experience than the customer experience team does.

B2B price is often a small database of commercial history.

If two teams can change the price, the integration needs a winner. If nobody owns the rule, the customer eventually finds it at checkout, on the invoice or when an account manager explains why the website was technically correct and their invoice may be wrong.

A redesigned product page cannot repair unclear price authority.

Stock availability creates the same problem.

Someone in the business has to decide who gets the stock, how fresh the check must be and what happens when two customers want the last three.

B2B buyers can fill a cart, submit an order and still fail a decision they never saw.

An account may be over its credit limit. An invoice may be disputed. The delivery address may belong to a branch that is not authorised to buy the item. A customer may be allowed to order only against a purchase order or within a monthly limit.

The damaging part is often the handoff. The website says “order confirmed”. ERP says “order on hold”. Customer service finds out when the buyer asks why nothing shipped.

Both systems behaved as configured. The customer still received the wrong promise.

Nobody puts “clean branch calendars and delivery routes” on a re platform mood board.

Customers notice them more quickly than the new typography or the flash agency design you deliberated over, while rushing through operations at the tail end of a project.

An integration can move the field.

It cannot decide what the field means.

ERP may be the wrong home for rich product content, search ranking, behavioural personalisation, web experimentation or customer-facing workflow.

A warehouse system may own fulfilment truth. An order-management system may orchestrate stock across channels.

A commerce platform may legitimately own B2B catalogues and checkout rules. A CRM may hold the sales relationship more accurately than the customer master.

Customers do not care which system owns the field. They care that the price survives the invoice, the product arrives and “confirmed” means “confirmed”.