Written by: JJ Tan, Founder, Jelly
Key Takeaways
- Restaurant stock control complaints usually come from a gap between recorded stock and what is actually on hand.
- A repeatable five-stage process, listen, investigate, correct, communicate, prevent, resolves complaints faster and reduces recurrence.
- Every investigation relies on the same evidence set: supplier invoices, delivery notes, stocktake records, POS sales data and recipe costings.
- Structured complaint handling protects GP margins by catching price variances, short deliveries and waste before they erode profit.
- Jelly automates invoice scanning, Price Alerts, live dish costing and POS integrations so the evidence is always ready when a complaint lands.
Before You Begin: Evidence To Have Ready
Every stock control complaint investigation draws on the same set of records. Confirm these are accessible and current before the process starts.
- Recent supplier invoices, including every line item, quantity and price
- Signed delivery notes and goods-received records
- Stocktake records from the most recent count
- POS sales data for the period in question
- Recipe and dish costings, including batch sizes and wastage percentages
- A named owner for the complaint, accountable for seeing it through to resolution
This is a recurring process, and the same evidence sources feed every complaint type. Keeping them current forms the foundation. For a deeper look at stocktake methodology, see Advanced Restaurant Stocktake Techniques That Cut Waste.
See How Jelly Keeps Your Evidence Ready
Why A Structured Complaint Process Matters
A structured approach to restaurant stock control complaints produces measurable operational outcomes.
- Faster resolution, because complaints are closed with evidence, not guesswork
- Fewer repeat complaints, because corrective actions address root causes, not symptoms
- Defensible supplier conversations, because invoice line items and delivery records replace informal accounts
- Protected GP, because price variances and short deliveries are caught and credited before they erode margin
- Consistency across sites, because one process scales from a single restaurant to a multi-site group
What Are The 5 Stages Of Complaint Handling In A Restaurant?
Effective stock control complaint handling in a restaurant follows five stages: listen, investigate, correct, communicate, prevent. Each stage connects the complaint back to the stock control record that caused it. Together they resolve the immediate issue with evidence and close the loop with a logged corrective action, so the same failure does not recur.
- Listen: Capture The Complaint Without Defensiveness
The first job is to record the complaint accurately before anyone responds. Acknowledge it, note the time, the dish or item affected, and who raised it. Avoid speculating about the cause at this stage, because early guesses anchor the investigation before the evidence is in. For a guest told a dish is 86’d, example wording is: “I am sorry, we have sold out of that dish this evening. Let me tell you what we have available that I think you would enjoy.” Log the 86’d item immediately so it feeds the investigation. The complaint is then captured in full, the guest or team member feels heard, and no commitment about cause has been made.
- Investigate: Check The Evidence Before Drawing Conclusions
The next step is to establish what the stock control record shows versus what actually happened. Pull the relevant invoice line items, delivery notes, stocktake records and POS sales data. Jelly surfaces all of this in one place, as invoice scanning captures every SKU and price, live dish costing shows what the recipe requires, and Sales Mix shows what was sold. Cross-reference the three to identify where the gap entered, whether at delivery, in storage, at prep, or at the pass. The gap is then located and quantified with documentary evidence.
- Correct: Fix The Immediate Issue
The third stage focuses on removing the problem from service and protecting the guest or the business. Substitute the 86’d dish with an available alternative and update the POS immediately. For a short or damaged delivery, quarantine the affected stock. For a stocktake variance, recount the affected category before service continues. Raise a supplier credit note where a short or damaged delivery is confirmed. The immediate risk is contained and the guest or operation is no longer exposed to the failure.
- Communicate: Close The Loop With The Guest Or Supplier
The fourth stage confirms the resolution in writing or in person. For a guest, return to the table to confirm the alternative and, where appropriate, offer a goodwill gesture proportionate to the inconvenience. For a supplier short delivery, use wording such as: “We received [quantity] of [item] on [date] against an order of [quantity]. Please confirm the credit note reference and expected delivery of the balance.” Keep the communication factual and reference the invoice or delivery note number. The guest or supplier then receives a clear, evidence-based response and the complaint is formally closed.
- Prevent: Log The Corrective Action And Change The System
The final stage aims to stop the same complaint recurring. Log the complaint, the evidence, the corrective action taken, the owner and the date. Identify the system change required, such as a reorder point adjustment, a supplier SLA, a recipe update or a POS menu change. Jelly’s Price Alert flags every subsequent price movement from the same supplier, and live dish costing updates automatically when new invoices are scanned. Prevention then sits inside the workflow rather than relying on manual checks. The corrective action is documented, owned and verifiable at the next review.
Handling Customer Complaints About Stock Outs And 86’d Items
The five stages apply to every complaint, and guest complaints about 86’d dishes follow a clear pattern. When a guest complains that a dish is unavailable, the complaint signals that demand forecasting, ordering or stock rotation failed upstream. The immediate response, offering an alternative, forms only the first step in handling this category of restaurant stock control complaints.
Validate the 86’d item against the stocktake record and POS sales data. If the item sold out faster than expected, check whether the order quantity was based on accurate sales history. If stock was received but depleted before service, investigate whether portion sizes, prep waste or unrecorded spoilage account for the gap. Update the POS and any online menus immediately, because a dish that stays orderable online after selling out in the walk-in is a separate failure that stock software alone does not fix. Log the shortage so it feeds the next ordering cycle and the corrective-action record.
Handling Internal And Supplier Stock Control Complaints
Internal stock control complaints, such as a variance between the stocktake count and the system record, and supplier complaints share the same investigation structure. Start with a physical recount of the affected category before attributing the variance to any cause. Then trace the gap across the four most common entry points: receiving, storage, prep and loss.
Designating a named member of staff to check every delivery against the order and sign off only what has been received in the correct quantity and condition is a basic control. This control frequently breaks down under service pressure. For supplier delivery discrepancies, raise the dispute in writing, referencing the delivery note and the invoice line item. Request a credit note and confirm the reference number before the next order is placed. For a fuller treatment of stock management fundamentals, see Restaurant Stock Management: The Ultimate UK Guide.
Complaint-Type Resolution Matrix
The five-stage process applies to every complaint type, but each one needs specific evidence and a tailored corrective action. Use this matrix-style list to match the complaint in front of you to the records it needs and the fix it should trigger.
- Missing stock (variance): Check the stocktake record, delivery notes, POS sales and waste log. Recount, identify the entry point, update the reorder level and log the corrective action.
- Short delivery: Check the delivery note against the invoice line item and order confirmation. Raise a credit note with the supplier, adjust the stock record and update the next order.
- Damaged goods: Check the delivery note for condition at receipt, the invoice and any photos. Reject or quarantine stock, raise a credit note and notify the supplier in writing.
- Expired stock: Check use-by records, FIFO rotation logs and delivery dates. Remove stock from service, log waste, then review rotation procedures and storage layout.
- Inaccurate records: Compare the stocktake sheet with the system count and invoice with goods received. Recount the affected category, reconcile invoices and retrain on the receiving procedure.
- Excess waste: Review the waste log, recipe portion sizes and prep records. Identify the waste category, such as spoilage, prep or portion, then update the recipe or ordering.
- Staff error (portion, prep): Check the recipe card, dish costing and POS sales against stock depletion. Retrain on the recipe standard, update the recipe card and monitor variance for 30 days.
What Not To Do When Handling Stock Control Complaints
Most complaints that drag on or recur fail at one of the five stages. These are the mistakes that break the process.
- Do not blame staff or suppliers until you have checked the documentary evidence. Review the invoice, delivery note and stocktake record first, because blame without evidence closes the investigation in the wrong place.
- Do not leave a complaint unresolved because it seems minor. Small unresolved complaints recur and compound, which turns a one-off short delivery into a supplier performance problem.
- Do not forget to update the POS or printed menus after an 86’d item. Missing updates generate a second complaint from the next guest who orders it.
- Do not resolve a supplier discrepancy verbally without a written credit note reference. Written references create a clear trail for future reviews.
- Do not log the resolution without logging the corrective action. Recording only the symptom fix guarantees the same cause will appear again.
- Do not investigate without separating facts from assumptions. A belief that “the team did not check the delivery” remains an assumption until the delivery record confirms it.
The Corrective-Action Log And Measuring Success
Every resolved stock control complaint should generate a corrective-action record with five fields. Capture the complaint, the evidence that confirmed the cause, the action taken, the owner and the review date when the fix will be verified.
The indicators to review at each cycle act as directional guides rather than fixed benchmarks.
- Stock variance, asking whether the gap between theoretical and actual stock is narrowing
- Waste, checking whether the waste log shows the same categories week on week
- Supplier complaint frequency, tracking whether the same suppliers generate repeated discrepancies
- Resolution time, measuring whether complaints are being closed faster as the process matures
- Repeat complaints, checking whether the same complaint type appears again after a corrective action was logged
A persistent unexplained variance on the same ingredient after a corrective action has been logged signals that the action addressed the symptom rather than the cause. In that case, return to the investigation stage.
UK Regulatory Grounding For Stock Control Complaints
The corrective-action log is more than good practice, because it creates the record-keeping that regulation expects. GOV.UK guidance provides the regulatory foundation for this process in England, Northern Ireland and Wales.
The FSA’s food traceability guidance requires food businesses to operate a “one step back, one step forward” system, identifying the immediate supplier of every ingredient received and the business to which food was supplied. Traceability records should identify supplier and customer details, the food product involved, quantities supplied or received, dates of delivery or dispatch, and batch, lot or consignment codes where available, with batch codes described as best practice unless sector-specific rules require them. These records must be accurate and available promptly when requested by an authorised officer. In a supplier dispute, Jelly’s automated invoice scanning provides the line-item evidence that satisfies this requirement without manual retrieval.
The GOV.UK General Food Law guidance grounds these obligations in Article 18 of assimilated Regulation 178/2002, which requires food business operators to keep supplier and customer records and make them available to competent authorities on demand. Article 19 requires withdrawal or recall of food that does not comply with food safety requirements and has left the operator’s control, with immediate notification to the FSA and local authority. Section 14 of the Food Safety Act 1990 makes it an offence to sell food not of the nature, substance or quality demanded by the purchaser. That is why a quality complaint is a legal matter as well as a service one. Section 20 provides that where an offence is due to the act or default of another person, that other person is guilty. This point is directly relevant when a supplier’s short or damaged delivery causes a food incident.
The GOV.UK food incidents and recalls guidance requires businesses to first gather information and trace suppliers before taking further action, to withdraw unsafe food immediately, and to document what they do with affected stock. The FSA’s incident reporting structure, which defines the incident, describes the investigation, contains the risk with traceability records, summarises actions taken and records root cause analysis and prevention measures, maps directly onto the five-stage process above.
Frequently Asked Questions
Who Should Own The Complaint-Handling Process In A Restaurant?
Ownership depends on the complaint type. Guest-facing complaints about 86’d dishes or dish quality are typically owned by the front-of-house manager or head chef, who has the authority to update the POS and communicate with the guest. Supplier discrepancies and stocktake variances are owned by the head chef or operations manager, who has access to the invoice records and the supplier relationship. In a multi-site operation, the operations manager holds overall accountability for the corrective-action log across sites. The critical requirement is that every complaint has a named owner before the investigation begins, because complaints without an owner are the ones that recur.
How Often Should The Corrective-Action Log Be Reviewed?
A weekly CAPA review (30–45 minutes) is the core closure-focused layer of a four-layer corrective action cadence, sitting between daily triage and a monthly effectiveness and repeat-issue review. The review should check whether the action has been implemented, whether the relevant indicator, such as variance, waste or supplier complaint frequency, has moved in the right direction, and whether any action is overdue. For multi-site operations, a monthly effectiveness and repeat-issue review is the recommended cadence for checking whether the same complaint or issue type is recurring, including across more than one location, which signals a systemic issue rather than a site-specific one. Corrective actions should remain open until the indicator confirms the cause has been addressed, not just that the action was completed.
How Should A Repeat Supplier Discrepancy Be Handled?
A single short delivery is a discrepancy, while a pattern of short deliveries from the same supplier is a supplier performance issue that requires a formal conversation backed by data. Pull the invoice history for the supplier, identify the frequency and value of discrepancies, and present the evidence in writing before the next order is placed. Request a credit note for each confirmed shortfall and set a threshold that triggers a supplier review, such as a defined number of confirmed discrepancies within a rolling period, agreed in advance with the supplier. If the pattern continues, benchmark the supplier against alternatives using the same invoice data. Jelly’s Price Alert feature flags every price movement from every supplier, giving operators the data to hold that conversation with specifics rather than impressions.
How Should Stock Control Complaints Be Managed Across Multiple Sites?
Each site should run the same five-stage process with its own corrective-action log, and the operations manager or finance manager needs visibility across all sites in one place. A complaint that appears at one site and is resolved locally may be appearing at a second site under a different description, such as the same supplier short delivery, the same recipe variance or the same 86’d item. Centralising invoice data, dish costings and variance records across sites makes cross-site patterns visible. Jelly’s flat rate of £129 per month per location means the same evidence infrastructure scales to each new site without variable cost surprises.
Conclusion
Guest complaints and supplier or internal complaints usually reflect the same stock control failure viewed from different angles. The five-stage process set out above resolves restaurant stock control complaints faster, protects GP and reduces the chance of the same failure recurring. The process only works when the evidence is ready, with the same sources listed at the start available in one place without manual retrieval. Jelly supplies that evidence automatically, from the moment an invoice is scanned to the moment a dish margin turns red on the dashboard. The corrective-action log closes the loop, while the regulatory framework, including FSA traceability, General Food Law Article 18 and the Food Safety Act 1990, provides the legal grounding. The process provides the discipline.
Talk To Jelly About Your Stock Complaints
