One workspace, many retailer clients

An LSP or 4PL does not have one supply chain. It has a book of them, one per retailer client, and each client expects to be treated as if it were the only one. That is the operational reality the software has to fit: many clients, one team, hard boundaries between them.

Why a shared workspace fails without scoping

The naive answer is one workspace with a client filter. It works until someone forgets the filter, and then one client sees another client's POs, prices or suppliers. In a regulated, competitive relationship that is not a bug, it is a breach. Scoping has to be enforced by the platform, not by a habit, because habits are exactly what fail when a team is busy.

Managed accounts

A managed account is a broad grant with delegated authority. The LSP operates a retailer's POs, packs and checks against the retailer's guide, and sees exactly what the retailer chose to delegate. It is one primitive, expressed as a grant, that says what the operator may do on the client's behalf and nothing more. Add a client and you add a grant, not an instance.

Per-client branding and partitions

Clients expect to see themselves. A header client switcher, per-client data partitions and per-client branding let an LSP present each retailer's world as that retailer's world, while the underlying record stays one canonical model underneath. The label on a surface is a display setting. The data boundary is not, and the two should never be confused.

Graduation without a migration

Clients grow up. When a managed client wants to stand alone, the grant flips from managed to peer. The relationships, the carton history and the compliance record stay exactly where they are. No export, no re-import, no two-week migration project, and no window in which the client's data is in two places and neither is authoritative.

Branding is a surface, scoping is a boundary

It is worth being precise about the difference. Branding changes what a client sees: the logo, the colours, the labels on the navigation. Scoping changes what a client can reach at all. A client can be shown a surface that looks entirely their own while the platform still guarantees they cannot read a row that was never granted to them. One is cosmetic, the other is a control, and the control is the one that matters when two clients are competitors.

One supplier, many retail relationships

A supplier that ships to several of your clients should not be onboarded several times. The supplier entity is resolved once, and the routing guide and validation rules attach to the trading relationship, not to the tenant. One supplier, many retailers, each with its own rules, and one login for the supplier to keep.

What the operator is billed on

It helps that the commercial model matches the operating model. Usage is metered per container and per operating seat, so an LSP's cost tracks the work it actually does rather than the number of clients it holds. Add a client and the cost is the containers that client moves, not another licence, which is what makes a book of small retailers viable on the same platform as one large one.

What scales, and what does not

What scales is the platform: one workspace, N clients, the supplier and CFS portals free for every client so the network grows with the work rather than with a sales cycle. What does not scale is a bespoke instance per client, because every instance is its own release, its own support load and its own upgrade path. The grant model is what lets an LSP add a retailer without adding a system, which is the difference between a platform business and a managed service that happens to use software.