Skip to content
Resources
Supplier management

Tapas bar supplier management: control formats, yields, cold chain, and substitutions

Build a tapas-specific supplier record for gross and drained weights, fillet and slice counts, cured formats, prepared pieces, cold-chain evidence, and approved substitutions.

Tapas purchasing is unusually sensitive to format because one case can feed several plates and one plate can use a defined count rather than a broad weight. Gross weight may include liquid or packing medium; drained or usable weight may be the operator’s relevant portion basis; fillet or slice count can determine whether a board, pintxo, or shared dish can be plated as intended. These fields should be visible before the supplier is compared. The public Torg category page shows the kind of B2B language buyers may encounter, including wholesale, private label, product categories, certificates, and minimum-order statements. It is marketplace content, not proof that a listed supplier has a particular capability or that a claim applies to the bar. Ask for current item-level evidence.

Build a format and yield ledger for small plates

Start with the exact supplier description, item code, pack, lot, label, storage, date or code, and invoice basis. Add internal fields for plate family, portion tool, drained or gross basis, usable preparation, expected piece type, count method, waste, and menu description. For olives, peppers, conservas, or marinated vegetables, distinguish liquid-inclusive weight from drained or usable observation. For anchovies or other seafood, record fillet count, size or presentation when supplied, oil or packing medium, and the portion method. For cured meats and cheeses, preserve whole, bone-in, boneless, block, log, pre-sliced, hand-sliced, or portioned format and note whether a slicing or trimming step is performed in house. For croquettes or other prepared pieces, capture piece count, frozen or chilled state, cooking method, breakage, and portion definition. Do not treat a marketing phrase such as restaurant grade or premium as a completed specification.

  • Store gross, net, drained, usable, and invoiced bases as separate fields and state which one drives the local portion observation.
  • Record piece counts using a named sample and method and distinguish a supplier-declared count from an operator count.
  • Capture cured-product format, cure or origin wording, slice thickness or presentation when supplied, pack, storage, opening, and service use.
  • Link prepared products to cooking, thawing, holding, breakage, and waste observations without claiming that one batch represents every pack.
  • Keep source documents, lot, label, photos, receiving record, menu wording, and approval scope available for later reconstruction.

Connect cold chain, receiving, and substitution approval

Cold-chain review should be specific to the product, packaging, route, local plan, and supplier document. Record delivery date and time, product state, packaging or seal, visible leakage or damage, required local temperature or condition check, receiver, photograph, storage move, and final status. Do not publish a universal temperature threshold from a different jurisdiction or product category. If a delivery is warmer, later, damaged, short, or in an unapproved format, preserve the evidence and hold the item according to local procedure. A substitute may look attractive because it has the same culinary role, but the bar still needs to compare drained or usable basis, piece count, cure or preparation, texture, recipe, menu wording, allergen information where relevant, pack, lot, storage, and cost basis. Approval belongs to the role defined by the operator and should be limited to the item, site, channel, and date scope reviewed.

Clearly labelled illustrative scenario: conservas, cured meat, and prepared pieces

Illustrative tapas supplier evidence ledger

Illustrative operator-entered scenario only. The products, formats, weights, counts, prices, dates, cold-chain observations, calculations, supplier claims, menu effects, and decisions below are invented values for testing a local ledger. They are not supplier facts, certifications, reviews, market prices, savings, universal thresholds, or customer proof. Replace every value with current labels, documents, receipt evidence, local procedure, and responsible approval.

Drained basisIllustrative operator-entered: a conservas tin is recorded with 1.2 kg gross label basis and 0.8 kg drained observation for one received packIllustrative weights; verify label and local method
Fillet countIllustrative operator-entered: an anchovy pack is opened under a named sample method and the receiver records 24 fillets, retaining the supplier-declared basis separatelyIllustrative count; not a universal pack promise
Cured formatIllustrative operator-entered: a cured ham arrives boneless and pre-sliced instead of the approved block format; label, lot, storage and photograph are held for reviewIllustrative format discrepancy; no origin conclusion
Prepared piecesIllustrative calculation: a 3 kg croquette case yields 42 intact service pieces and 2 damaged pieces in one operator observationIllustrative local count and loss; not guaranteed yield
Substitution decisionIllustrative operator-entered: an alternative olive remains unapproved until drained basis, piece size, taste test, menu wording, allergen evidence where relevant, and lot linkage are reviewedIllustrative approval status; no supplier claim

The ledger keeps liquid, fillet count, cured format, prepared pieces, and approval evidence distinct. Its illustrative weights and counts support a local question; they do not prove a supplier specification or universal yield.

The bar should design trials around the plate rather than around the catalogue. Name the plate or board, portion tool, drained or usable basis, fillet or slice count, cooking or warming method, holding time, presentation, evaluator, and lot. Note whether a substitute changes the number of pieces, the visible size, the amount of liquid, the texture after opening, the slicing labor, the finished plate, or the menu statement. If the cold-chain record is incomplete, the question is not solved by a good tasting note. Keep the product on hold or route it according to the local procedure and record who may release it. A credit request should link the source line, evidence, supplier response, and confirmed document; a pending request is not a saving.

  1. 1Define the plate-facing item. State product identity, form, gross or drained basis, piece type, pack, lot, storage, intended plate, portion method, and menu scope.
  2. 2Verify the source. Save label, supplier document, item code, origin or classification wording, certificate evidence when supplied, invoice, and lot without treating marketing copy as proof.
  3. 3Receive and inspect. Record delivery time, product state, package and seal, required local checks, gross or labelled basis, photographs, receiver, storage move, and status.
  4. 4Measure the local portion. Count fillets, slices, prepared pieces or usable weight under a named method and record sample, preparation, waste, evaluator, and limitation.
  5. 5Review a substitution. Compare format, weight basis, count, cure or preparation, recipe, plate, menu, allergen evidence where relevant, storage, pack, lot, and approval scope.
  6. 6Close the evidence. Record accept, hold, reject, return, release, supplier response, credit or correction, affected menu records, and the next review trigger.

FAQ

Is drained weight always the correct basis for a tapas portion?
Not always. The relevant basis depends on the product, recipe, packing medium, preparation, invoice, and local method. Preserve gross, labelled, invoiced, drained, and usable fields where relevant and state which one the operator uses for the defined comparison.
Can a supplier-declared fillet or slice count be treated as guaranteed?
No. Keep the supplier statement with its scope and record the operator’s own sample and method separately. A count can vary with product, pack, preparation, and sampling, so do not turn one observation into a universal promise.
Does a cured-product origin or classification in marketing copy prove the menu claim?
No. Marketplace and supplier-marketing language can identify questions, but the bar needs current item-level documents and local review before using origin, classification, curing, or premium wording on a menu.
What cold-chain temperature should every tapas bar accept?
There is no single threshold to copy across products and jurisdictions. Use the current local plan, product requirements, supplier evidence, and competent advice. Record the actual check and decision rather than publishing a borrowed number.
Can a similar olive or croquette be substituted at service?
Only if the restaurant’s policy gives the role authority and the comparison is complete for format, usable basis, count, texture, recipe, menu, allergen evidence where relevant, storage, lot, and traceability. Similar culinary use is not proof of equivalence.
When does a cold-chain or format dispute become a credit?
After the evidence is linked to the source line and the supplier provides a confirmed credit document or decision, subject to the restaurant’s finance process. Keep a request, a pending response, and a posted credit distinct; none is automatically a saving.

Keep reading

Want to review your purchasing?

Submit the details and we will confirm which invoices are useful.

Review 3 invoices free