Restaurant Supplier Dependencies: Look Beyond Spend Share

Why spend share hides dependence

Spend share tells you where money goes. It does not tell you which items a service needs, how many routes actually exist behind each supplier name, or which outlets would be affected together. A large account can be easy to replace, while a small one can sit on a single source with no ready alternative.

Keep two questions apart. Dependence asks what relies on what. Possible impact asks which activities would stop or change if a dependency were unavailable. Neither is the same as how likely a disruption is, and this exercise does not estimate likelihood.

Map each item from use back to source

Give each dependency a stable ID. Start from the use: the item and its approved specification, the activity that needs it and the outlet IDs where it is used. Then record the direct supplier, and what is known further back, such as the producer, plant, packer, transport hub, utility or region the route relies on.

For every upstream claim, record its source, the date it was stated and how confident you are, described in words. A supplier's email last month is different evidence from a site document checked this week. Write unknowns down as unknown.

Worked example: one coffee, two distributors

In this fictional example, outlets O1, O2 and O3 buy the same approved coffee. O1 and O2 order through distributor D-A and O3 through D-B, which looks like two independent supply routes. Supplier evidence shows that both distributors currently source that specified coffee from producer P-X. The group records this as DEP-01, a shared dependency that covers all three outlets.

Two distributor names do not establish two independent production routes. If P-X could not supply the specified coffee, both distributors could be affected at once. Retain the date and source of that evidence, because sourcing arrangements can change; a producer name alone may still leave the actual plant or logistics route unknown.

Small items can stop a whole service

DEP-02 is a lid supplied by D-C. Its cost is minor, yet the specified takeaway drinks at O1 and O2 need the approved cup-and-lid pairing. A proposed backup cup does not fit the approved lid, so it cannot be described as ready. Record that known mismatch separately from unanswered sourcing questions.

Outlets appear in more than one row. O1 and O2 sit under both DEP-01 and DEP-02, so adding the outlet lists together would claim five exposed outlets when there are three. Count unique outlet IDs directly if you need that figure.

Unknown is not independent

When a supplier cannot say where an item comes from, the honest entry is unknown. Treating a gap as proof of independence makes the map look safer than the evidence allows.

Even different producers may share a packing site, port, transport hub, utility or growing region. State exactly which dependencies were checked, what evidence supports separation and what remains unknown. A claim of no identified shared dependency within that scope is more limited than a guarantee that the routes are independent.

Check an alternative before calling it ready

In the example a coffee from producer P-Y is proposed. It stays recorded as ALT-01, separate from DEP-01 and marked unverified, until the producer and site identity, the match to the approved specification, the capacity available in the relevant window, the logistics route and the authorisation to use it have each been checked.

Readiness is a recorded set of conditions with evidence, not a count of supplier names. Purchasing, receiving and food or menu approval controls still apply to any alternative.

Run one bounded disruption exercise

Choose one dependency and one window, for example DEP-01 unavailable for a stated period. List the activities affected at each outlet, the stock and arrivals confirmed by evidence, and the constraints that apply. Do not calculate days of cover unless the scope, safe usable stock and demand have each been established separately.

Record the authorised fallback. It may be a restricted service, such as a shorter beverage menu, rather than an unapproved substitute. Name the owner, the decision taken and the date to recheck. The exercise shows where the map is thin; it does not certify continuity, remove risk or recommend stockpiling.

What the supply-chain guidance supports

Business Queensland's guidance on managing risk in supply chains describes identifying the parties in a chain, including producers, packaging and logistics, separating what is within your control, assessing how disruptions would affect key activities and preparing alternative sources in advance. This guide uses only those general principles. Australian legal guidance and the linked template are not applied.