VK Orbit · Definition

S2O

Strategy‑to‑Order

The stretch between a category strategy being agreed and an order being raised against it.

Source‑to‑Pay describes what procurement does. Procure‑to‑Pay describes what the business does. S2O names the part in between, which neither of them owns: the translation of a decision into something a system can execute and a requester can actually use.

Why the gap needs a name

Unnamed gaps do not get funded. Every organisation has a process for setting category strategy and a process for raising orders. Very few have one for turning the first into the second. The reason is not negligence. The work has names in places. One government procurement lifecycle gives it a stage of its own and leaves the owner blank. A major ERP splits it across two seeded administrator roles, neither of them the category manager. What it does not have anywhere is an owner in the business, so it has never appeared in a budget, an objective or a target operating model.

The academic map stops short of it too. The most complete review of purchasing strategy traces five levels, from firm strategy down to how a category manager will work with each individual supplier, and ends there. There is no rung for the buying channel, the catalogue or the transaction.

Where it jams

Five owned inputs. Four readers downstream who each need it differently. One person in the middle.

Contract lifecycle sets the price, the terms and the obligations. Supplier lifecycle sets qualification, preferred and qualified lists, and risk. Sourcing contributes the awards, master data the taxonomy and item detail, and policy the thresholds and approvals. All five are owned, governed and audited.

Downstream, four readers need that same strategy expressed differently.

Sourcing needs the sourcing strategy, the route to market and the preferred list that falls out of both.
Order management needs it at contract and supplier level: which supplier transacts on which channel, at what price basis, against which threshold.
The requester needs to find the thing, at a price that matches, and to know it is allowed.
Accounts payable needs none of it until something is wrong, and then all of it at once.

Those translations are rarely written, because writing them is nobody’s deliverable. So the work does not stop. It reroutes. Every gap becomes a question, and every question arrives at the one person who owns the strategy and already has a full week. That is the jam, and it is why the operable content degrades quietly instead of failing loudly.

What S2O is not

Not a replacement for S2PIt sits inside it. S2P is the whole cycle; S2O is the join that is usually missing from the middle of it.

Not a systemNo product covers it. Parts of it live in the ERP, parts in CLM, parts in supplier management, parts in a spreadsheet.

Not Source‑to‑OrderThe S is strategy, not source. Sourcing is one of the five inputs, not the starting point.

Not a maintenance jobIt is a design job. Settle the downstream requirements when the strategy is written, and they arrive operable.

The principle

You touch it, you own it. Procurement applies that to contracts, to suppliers, to spend and to risk. It has never applied it to the operable content where all four are consumed.