One SOP for six countries is how you lose money

Somebody always wants the one-pager. One SOP. Six countries. Same pack, same label, same escalation, same definition of delivered. It looks like management. It feels like scale. It is how you leak money into seams you refused to see.

I know the temptation. I founded an asset-light company that exists to make six APAC markets feel like they can be held in one head. Holding them in one head is not the same as running them as one process. The first is a coordination trick. The second is a delusion with a document attached.

One SOP for six countries is how you lose money. Not all at once. In the exceptions you called "local issues" until they became the P&L.

Copy-paste is not expansion

Singapore habits die in Indonesia. Indonesia habits confuse Vietnam. Vietnam's last mile is not Thailand's, and the Philippines will punish an address format you thought was universal. None of this is new. It just gets ignored every time someone is in a hurry to say they're regional.

A copied SOP fails in small ways first. A field that isn't required in one market is fatal in another. A handover window that works in a dense city is fantasy in a market where the depot closes earlier than your origin team thinks. A returns flow that assumes a convenient drop-off point meets a country where the drop-off point is a person, not a shop.

Each small way has a cost. Re-label. Storage. A second delivery. A destroyed COD attempt. A customer refund you eat because arguing takes longer than the margin. You can hide those in "ops costs" for a while. Then you notice a market that was supposed to be cheap is where the exceptions live, and the exceptions are the market.

The seam is the product

Cross-border money is made or lost between processes, not inside them. Origin can be excellent. Destination can be excellent. The thing that sits between them, the document, the scan, the definition of whose problem a hold is, that's where you either have a company or you have two vendors who don't speak.

One SOP pretends the seam is identical. It isn't. Customs personalities differ. What a carrier will scan differs. What "delivered" means differs. If you force one language onto that, you don't get consistency. You get a report that looks consistent while the ground does whatever it was going to do.

I would rather maintain six ugly, true SOPs than one beautiful lie. The ugly ones can be improved. The lie can only be defended, and defending it is a full-time job that doesn't move cartons.

What I actually standardise

Not the steps. The questions. What is the last scan we trust. Who owns a missed scan. What does a failed delivery do to COD. Who can kill a bad address before it flies. Those questions are the same in every market. The answers are not. Standardising the questions is management. Standardising the answers is laziness dressed up as a playbook.

We also standardise how we talk to customers about differences. "It's the same as Singapore" is a sentence I don't allow. It makes you sound big. It makes the first exception feel like a betrayal. Better to say: this market does this, here's what that means for your buyer, here's how we'll handle the ugly version. Adults can hear that. Adults cannot hear "regional SOP" and then a doorway story from Manila that was never in the document.

Asset-light makes this sharper. We don't get to walk the floor in every city. The SOP is sometimes the only object we have that resembles control. If that object is a photocopy, we have photocopied our ignorance.

Scale the questions. Localise the answers. If you reverse that, you're just spreading a mistake.

Money hides in the thing you called an edge case

The one-SOP people always have a line about edge cases. We'll handle those as they come. They come every day. In a six-market operation, the edge case is the volume. Rain. COD. A public holiday you didn't put in the calendar because it isn't your public holiday. A document format that was fine last month.

I'm not interested in looking regional. I'm interested in not paying for the same surprise twice. That means a process per market, written, owned, boring. It means saying no to a launch when the SOP is still a Singapore file with the header changed. It means arguing with people who want the map more than the work.

If your six-country operation is losing money and you can't see where, stop looking at the rate card. Look at the SOP you copied. That's usually the hole. It was neat. Neat is not the same as true, and untrue processes are a subscription you pay in exceptions.