Running a multi-tenant control tower without losing your mind
How 3PLs onboard merchant sub-tenants in days, not quarters — and keep every tenant's world cleanly separated.
The promise of running a 3PL is leverage: one operation, many clients. The trap is that most software makes every new client a rebuild. You clone a dashboard, fork some config, and six months later you are maintaining fourteen slightly different versions of the same thing.
Tenancy is a data-model problem
If tenancy is bolted on at the UI layer, it leaks. The only version that holds up is tenancy enforced at the data layer, so a merchant sub-tenant literally cannot address another tenant's shipments — not by policy, but by construction.
“We onboarded three merchant sub-tenants in a week. Each one sees only their own world, and we never touched the underlying stack.”
— Sofia Brandt, COO, Northwind Fulfilment
Once separation is structural, onboarding becomes configuration instead of engineering. That is the whole game.
Fifteen years running last-mile operations across the Benelux. Writes about the unglamorous mechanics of getting parcels to doors on time.