What a Contract Caterer Should Require of a Produce Supplier

A contract catering procurement lead rarely starts with the question of which produce supplier to appoint. The question that comes first is narrower: what does the operation have to require of a produce supplier, and what has to be checked before that supplier joins the approved list.

Approval is a decision about risk before it is one about price. Once a supplier is on the list, a unit manager at a site nobody visited this month can order from them without asking anyone, and whatever that supplier does next arrives on a plate the client is paying for. Due diligence sits before the commercial conversation, not inside it.

What the approved supplier list is actually for

An approved supplier list is a control, not a directory. It records who the operation has decided it is safe to buy from, and it is what a client asks to see when they want to know how the caterer knows where the food came from. Unit ordering, mobilising a contract, answering a withdrawal notice: all of it rests on checks made before a name went on the list.

Which is why the list should be shorter than the buying history. A name that got on because a chef used it at a previous site, or because a unit needed something in a hurry, is a supplier nobody assessed. Your own purchase ledger tells you how many of those you carry: pull the produce spend by supplier for the last quarter and count the names that are not on the list. That count is the gap between the control and the practice.

Start with what your own contract already promises

The requirements are not invented from scratch. Most flow down from the contract the caterer has already signed. A client contract that promises allergen information, provenance on the menu, or evidence of how the food was handled commits the caterer to a supply chain that can produce it. A tender asking for a food safety management system in the operation implies one in the businesses supplying it.

So the first document to read in a supplier due diligence is not the supplier's. It is your own contract, and the tender you won it with. Everything you owe the client, you have to be able to require of a supplier. Requirements copied from a template questionnaire produce a folder of certificates nobody can map back to an obligation.

The evidence to ask for, and why each item exists

Ask for the document, not the assurance. A supplier saying they are compliant is a sentence; paperwork is a check somebody else has already done, dated. What to ask any produce supplier for:

• Registration with the local authority as a food business. The base fact of trading legally, and it names the authority that inspects them.
• A food safety management system based on HACCP principles, and the records it produces. The plan matters less than the records behind it: a plan with no completed logs is a document, not a system.
• Third-party certification to whichever scheme your client contract names. Schemes differ, and the one that counts is the one your contract or the client's own policy specifies.
• Product and public liability cover at the level your contract requires. Check the level and the renewal date, not just that a policy exists.
• Traceability, one step back and one step forward. The supplier should be able to say where a line came from and where it went while you are on the phone, not by the end of the week.
• A written withdrawal procedure, with the named contact and the escalation route on it. A withdrawal is worked from a document under pressure, so the document has to name who is called and in what order.
• Cold chain evidence. Temperature control from source to the door is where produce condition is kept or lost, and a supplier who logs it can show you the log.
• Specification and allergen data per line. For produce the specification is what the line has to be — the product, the count, the grade and the source — and the allergen position on anything packed or prepared is a separate answer, in writing.

None of these is a formality. Each is there because the caterer carries the consequence when it is missing.

What the certificates do not tell you

A supplier can hold every document above and still be wrong for a catering operation, because those documents describe safety rather than service. The operational questions decide whether a mobilisation works, and they belong in the same due diligence. The order cut-off and the delivery window, in writing. What happens when a line is short, and whose decision the substitution is. Who holds the specification, and whether it is written down or carried in somebody's head. Whether an invoice can be matched to its order without a separate reconciliation.

Ask those of every candidate: they are what the mobilisation runs on, and none of them appears on a certificate. Produce Network answers them as method rather than as a promise, and the shape that takes for an events operation — volume planned by the event week, one contracted 02:00 to 06:00 delivery window per event rather than a nightly run, and one consolidated monthly statement — is set out on the produce supplier page for catering operations.

Work the volume from your own contracts, not a benchmark

The temptation, when a tender asks you to justify the shape of the supply base, is to reach for an industry figure. There is none worth borrowing: the arithmetic is specific to the contracts you hold, and it is already in your own systems.

Say the operation runs 6 contracts, each ordering produce from 3 suppliers: that is 18 supplier relationships to assess, re-approve and keep current. Say each of those suppliers carries 4 documents with a renewal date, and you are tracking 72 dates. Nothing in that is a claim about anybody's business — it is a multiplication you can run against your own contract register in an afternoon.

The same method sizes the delivery side. Say the operation runs 9 events in a week and each takes one produce delivery: that is 9 slots somebody has to be on site to receive. Your own order history gives the real figures, and those are the numbers to write into a tender.

Test the answers rather than filing them

Due diligence fails in one of two directions: a questionnaire everyone passes, or a folder nobody opens again after mobilisation. Ask every supplier the same questions in writing so the answers are comparable — a conversation is remembered differently by the two people who had it. Then test the written answer against a live order: a supplier who says traceability is same-day can be asked, mid-trial, where a specific box came from, and a supplier who commits to a window can be measured against your own door log rather than their report.

The trial is the part a tender timetable has least room for, and it is the only stage at which a buyer finds out whether the documents describe the business. Run the new supply beside the incumbent for a cycle, on your own orders, and prove it before anything is cancelled.

What approval should mean after the tender closes

Approval is a date, not a state. A supplier approved during a mobilisation two years ago may have renewed its insurance, changed certification and changed people since. Without a review date against each supplier, the list records a decision nobody has revisited.

Set the review cadence to the shortest renewal on file, keep the evidence against the supplier record rather than in an inbox, and re-run the operational questions alongside the documents. The commercial review is the straightforward half. The approval is the half that carries the risk.

If you are assembling the produce requirements for a contract catering tender, or re-approving supply you already run, book a call and we will walk through what your contract asks for and how an account is built against it.