Beyond the storefront: what commerce infrastructure looks like at scale

If someone on your team has ever said “let’s just add an online store” like it’s a weekend project, and you’re the one who has to explain why that’s never really “just” anything, this one’s for you.

I’ve now built or rebuilt commerce infrastructure for a few different businesses, and the pattern repeats itself almost exactly. The storefront, the part customers actually see, is the easy piece. The other, larger piece is the plumbing nobody outside engineering thinks about: inventory that has to agree with itself across three channels, payments that need to reconcile against orders without someone doing it by hand every Friday afternoon, and a B2B customer who expects the same price and stock level online that your sales rep would quote them on a phone call.

Where it actually breaks

It’s rarely the storefront that breaks. It’s the seams between systems that were never designed to talk to each other. A warehouse system from 2015. A point-of-sale system from a different vendor entirely. An accounting package everyone’s a little afraid to touch. Each one has its own idea of what “in stock” means, and the business usually finds out they disagree the moment a customer orders something that isn’t actually there.

I’ve watched teams try to paper over this with process instead of engineering: someone updates a spreadsheet every morning, someone else copies numbers between two admin panels by hand. It works, for a while, at a scale where “for a while” is measured in months. Then the business grows, or the one person who understood the whole workaround goes on leave, and the entire thing just stops working.

The real work of commerce infrastructure isn’t the storefront. It’s making sure every system that touches an order agrees on what actually happened.

What actually holds up

The businesses that don’t hit this wall tend to do a few unglamorous things early. They pick one system to be the source of truth for stock, instead of letting three systems each believe they’re right. They build, or buy, an integration layer, instead of quietly making their staff the integration layer. And they treat B2B ordering as a real product surface with its own requirements, not an afterthought bolted onto the consumer storefront because someone assumed the same page would do.

None of that is exciting to put in a pitch deck. It’s also the difference between a commerce platform that scales calmly through a busy season and one that needs a war room every time there’s a sale.

If you’re looking at your own setup and recognising a few of these seams, I’d be glad to talk it through.

— Ali