Why the same few gaps
keep coming back

A new vendor file usually moves through more than one internal
reviewer at a contract catering business: someone confirming the vendor
is a real, contractable entity, someone checking product specification
and compliance documentation, someone who has to sign off on a physical
sample, and someone finalising commercial and service terms. Each of
those reviewers needs a specific document, and each is blocked if the
document in front of them does not match the one the previous reviewer
already approved.

The pattern that causes a stall is rarely a missing document
category. It is usually a mismatch: the entity name on the tax
registration does not exactly match the name on the certificate, the
specification sheet describes a format that is not the one the sample
represents, or the certificate attached has no visible status or date,
so the reviewer has to chase confirmation before they can sign off.
Fixing this is mostly a matter of sequencing and consistency, not volume
of paperwork.

The
submission sequence that avoids a stalled file

Stage one: entity and registration documents. Submit
the vendor’s legal entity registration, tax identification, and export
registration where relevant, such as an Importer Exporter Code for a
cross-border vendor, before anything else. Every other document in the
file gets filed against this entity, so getting the name and
registration details right first avoids a reconciliation problem
later.

Stage two: product specification and compliance
certificates. Submit the specification sheet for the exact
format being proposed, alongside current management system certificates.
The specification needs to name the product precisely, for the 12 inch
traditional plate line, that means the full product name rather than a
shortened description, since a mismatched name between the specification
and later documents is one of the more common causes of a reviewer
sending a file back.

Stage three: sample approval record. Request a trial
sample against the specification submitted in stage two, and get the
internal sign off documented, not just the sample delivered. A sample
that was received but never formally approved in writing is a gap that
surfaces later when someone asks whether the format was actually signed
off, and it is far easier to close at the time than to reconstruct
afterward.

Stage four: commercial and service terms. With
entity, specification and sample confirmed, finalise the terms that
govern ongoing supply: minimum order per format, lead time, and how
volume and destination determine a quotation. This is the stage to
confirm operational expectations like dispatch timing rather than the
stage to introduce them for the first time.

Stage five: reference and escalation contact. Close
the file with a named contact for quality or compliance escalation on
the vendor side. This is a small addition that saves time later, because
it means an issue raised after onboarding has a direct route rather than
starting again at a general enquiries contact.

The documents
most likely to cause a hold, and why

An expired or undated certificate is the most common hold point, not
because the vendor lacks certification, but because the copy on file
does not show a clear current status. Ask for a certificate that states
its issue reference and status plainly, and ask the vendor directly if a
copy on file looks dated.

A specification sheet without a clear product name or version
reference causes confusion when it is compared against a sample or a
later commercial document. This is worth checking before submission, not
after a reviewer flags it.

A sample sent without a documented internal approval is a gap that
does not show up until someone asks for proof the format was signed off.
Build the approval step into the process at the time the sample is
received, rather than assuming it happened because the sample sits on a
shelf somewhere.

An entity name mismatch, where the name on a tax document differs
even slightly from the name on a certificate or invoice, is a small
thing that causes a disproportionate amount of back and forth, because
it looks like a discrepancy that needs explaining even when it has an
innocent cause, such as a trading name versus a registered name.

Multi-format
vendors need one file per format group, not one file for everything

An institutional buyer replacing a range across plates, bowls and
trays is often better served by treating each product line as its own
specification and sample line inside a single vendor file, rather than
one blended specification covering the whole range. This keeps the
sample approval record clean, since a reviewer signing off a plate
format is not being asked to also vouch for a bowl format they have not
separately evaluated.

If the
file is going to a committee rather than a buyer

The sequence on this page assumes an internal approval run by a
category manager or procurement lead who can move a file forward as
documents arrive. A purchase or tender committee works differently,
because it reviews in scheduled stages and a file that misses a cutoff
waits for the next meeting regardless of how fast the gap is closed.
That timing problem is dealt with in building an audit ready
supplier file.

What this means for your
enquiry

Submitting a vendor enquiry that already carries the product formats,
the volume per format, and the destination lets a quotation and the
relevant compliance documents move together, rather than the compliance
file trailing behind a commercial conversation that has already
started.

Frequently asked questions

Related reading

• how
  institutional and contract catering supply is structured
• the certifications and registrations
  your file will need
• the
  compliance file checklist behind these documents
• building an
  audit ready supplier file

References