To investigate a disputed direct order, retain enough information to connect the order to its payment, track what happened during fulfillment, and understand any contact with the guest. Start with the order number and payment reference. Then collect only the records that address the specific dispute, such as a pickup confirmation or a delivery status.
Keep a consistent process rather than relying on a manager to remember where everything lives. A useful evidence packet has a named owner, a deadline, a short timeline, and copies or secure references to relevant records. Have your retention and handling rules reviewed by qualified legal counsel.
Identify the order and payment references
A guest may give you a name and an approximate time, while a payment provider may give you a transaction reference. Neither is necessarily enough on its own. Your first job is to match the payment to the correct order without exposing more customer information than the investigation needs.
Record the order number, order date and time, total charged, ordering channel, and fulfillment method. Add the payment transaction reference and payment status from the payment provider. If the guest reports an unfamiliar charge, note how the charge appears to the guest when that information is available.
Do not assume the payment reference is the same as the order number. Confirm the match using more than one field, such as the amount and timestamp. If the amounts or times differ, note the discrepancy and investigate before submitting a response. A tip, an adjustment, or a different time zone could affect the comparison; the records need to establish what happened in the particular order.
Ask your ordering and payment providers where these references appear, who can access them, and whether they remain available after an order is completed. Also ask whether staff can export a record or share a secure link with an authorized reviewer. A screenshot may be useful, but it should show enough context to identify the order and the time of the event.
For a broader review of how orders enter your operation, the online ordering buying guide can help you map the ordering channel. The dispute process starts with a narrower question: can an authorized person find the right order and its matching payment quickly?
Collect records that answer the dispute
Different complaints call for different evidence. A guest who says an order never arrived raises a different question from a guest who says the wrong item was supplied. Gather the order details in both cases, then add only the operational records that help establish the relevant facts.
The worksheet below connects common questions to useful records and their limits. It is a starting point, not a promise that every system captures every event.
| Dispute question | Records to look for | What to check | Limit |
|---|---|---|---|
| Was this the right order and payment? | Order confirmation, itemized total, payment reference and status | Amount, time, order ID and any adjustments | A payment record alone does not prove fulfillment. |
| Was the order prepared as requested? | Order details, kitchen ticket or preparation notes, if retained | Items, modifications and recorded changes | A ticket shows what was sent to the kitchen, not necessarily what reached the guest. |
| Was it picked up or delivered? | Pickup status or delivery provider event history | Event times, handoff details and any reported exception | A status update may not establish who received the food. |
| Was the issue addressed? | Relevant guest messages, staff notes and adjustment records | What was reported, when, and what action was recorded | A staff note is an account of an event, not independent proof of every detail. |
For pickup, ask whether your process records a handoff and, if so, what the record actually means. A staff member marking an order complete may indicate that food left the counter; it does not automatically identify the person who took it. For delivery, request the relevant event history from the party that handled dispatch. Ask what each status means and whether failed delivery attempts or exceptions are included.
Keep the original order and subsequent changes distinguishable. If a guest calls to remove an item, for example, record who made the change, when it was made, and whether the payment or order total was adjusted. A later order view without a change history may not explain the sequence.
Guest communications can clarify what was reported and what the restaurant did next. Save the relevant exchange and staff notes, not an unrelated conversation history. Avoid storing full card numbers or sensitive authentication information in a dispute folder. Use provider references and approved secure tools instead; ask the payment provider what information it needs and how it should be submitted.
When evaluating restaurant online ordering, ask which order events are recorded, how corrections appear, and how long authorized staff can retrieve them. Make the same inquiry about payment and delivery tools. A direct ordering channel and the services that process payment or handle delivery may each hold different parts of the record.
Check deadlines and set retention rules
As soon as a dispute arrives, find the response deadline in the provider's notice or portal. Record the date, time, time zone if given, and the required response method. Check whether the provider requests particular fields or document formats. Do not assume a deadline from a previous case applies to the next one.
Work backward from the deadline. Allow time to request records from a delivery provider, resolve mismatched references, and have a second person review the packet. Set an earlier internal target so a missing attachment does not become a last-minute problem. If a record cannot be obtained in time, document what was requested and what is available; do not fill the gap with an assumption.
Retention needs a separate decision. Ask each provider how long records remain accessible, whether access changes if you close an account, and what happens to exports. Then have qualified counsel review a written retention schedule for the restaurant's circumstances, including applicable requirements, privacy considerations, and secure disposal. Keep access limited to people with a business reason to investigate or respond.
Hypothetical example: A guest disputes a $36 direct delivery order, saying it did not arrive. The order record shows $30 in food and a $6 delivery charge, for a $36 total. The payment reference matches that amount and the order time. The delivery history shows a driver marked the order delivered, but contains no recipient name. A guest message sent afterward reports that the food was missing.
The packet should include the order and matching payment reference, the relevant delivery events, the guest's message, and any documented restaurant response. Its timeline should say that delivery was marked complete and that the guest reported nonreceipt; it should not say the guest received the food. The $36 is the order total, not a processing fee or an operating-cost calculation. This example does not establish how a payment provider would decide the dispute.
Before relying on a record, check its timestamp and source. A saved screen showing a status without an order identifier may be hard to connect to the case. A concise note explaining where the record came from can make review easier without turning staff guesses into facts.
Assign one response owner and use a checklist
Choose one person to own each case, with a backup for absences. The owner does not have to gather every document personally. The kitchen lead may find a ticket, the delivery contact may request dispatch history, and an authorized payment administrator may retrieve the transaction reference. One owner keeps the deadline, the timeline, and the final submission from falling between roles.
Use this checklist for every disputed direct order, adapting it to the provider's request and the retention rules reviewed for your business:
- Log the notice: record the dispute reason, amount, provider reference, response method, and deadline.
- Match the order: connect the order ID, date, total, fulfillment method, and payment transaction reference. Flag mismatches.
- Build a timeline: list the order, payment, preparation, handoff or delivery, guest contact, and any recorded adjustment in time order where records exist.
- Collect relevant support: attach or securely reference the records that address the complaint. Identify their source and distinguish an event from a later staff account.
- Review the packet: check that it answers the provider's request, does not claim more than the records show, and excludes unnecessary customer information.
- Submit and close: use the provider's required channel, save confirmation of submission and the outcome when available, and retain or dispose of the packet under the reviewed schedule.
Practice the workflow with a fictional order and a simulated dispute notice. Use dummy identifiers and a test folder; do not trigger a real payment, guest message, or courier dispatch. Time how long staff need to locate each type of record and note which questions require a provider's help. This is a process rehearsal, not proof that a live dispute will produce the same records or outcome.
Separately, during normal service, a manager can review a completed order's existing records with appropriate access to see whether the documented workflow is usable. That review should not create a dispute or contact the guest. Follow up on gaps by asking providers about access, exports, event definitions, and account closure before changing your procedure.
Start with one recent process review: map where your order, payment, and fulfillment records live, then run the fictional checklist with your response owner. If you are reviewing your ordering setup, explore Fleksa's restaurant website and ordering options, and ask Fleksa about verified US availability and the records available for your setup.
Frequently asked questions
Is an order confirmation enough to resolve a dispute?
Not always. It can establish what was ordered, but a fulfillment complaint may also require pickup or delivery records and relevant guest communications. Respond to the specific issue and the provider's request.
How long should a restaurant keep dispute evidence?
There is no single period to apply blindly. Check provider access periods and have qualified counsel review a retention schedule for your circumstances, including how records are secured and disposed of.
Who should submit the response?
Assign one authorized owner and a backup. Other staff or service providers can supply records, but the owner should check the deadline, review the packet, and save confirmation of submission.
