A restaurant order confirmation message should tell the guest that the order was accepted, identify the items and total, show the payment status, and explain when and where pickup or delivery is expected. It should also give the guest an order reference and a working way to contact the right person if something is wrong.
The key is accuracy. A message that says “paid” when payment is still pending, or gives a pickup time the kitchen has not accepted, can create more work than it saves. Start with the information your staff can stand behind, then check how it reaches the guest.
Separate acceptance, payment and preparation
An order can pass through several stages after a guest submits it. A submission receipt means the request arrived. An acceptance message means the restaurant has agreed to fulfill it. Payment and preparation are separate facts.
Use wording that matches the stage. If the restaurant must review an order first, “We received your order and will confirm it shortly” is clearer than “Your order is confirmed.” Once accepted, the message can say “Your order has been accepted.” Avoid saying food is being prepared unless that status is actually available and current.
Payment needs its own line. “Paid online,” “Payment pending,” and “Pay at pickup” tell the guest different things. The payment provider or ordering system supplies the payment status; the restaurant should establish which status triggers each message. A payment authorization, if used, should not automatically be described as a completed charge. Ask the provider how its payment statuses map to the words guests see.
Assign an owner for each piece of information. The guest supplies the items, fulfillment choice and contact details. The restaurant supplies availability, acceptance and the expected preparation time. The payment service supplies payment status. For delivery, the person or service arranging the delivery should supply any delivery estimate and contact route. Your ordering setup brings those inputs into the message; ask what happens if an input is missing or changes.
For a broader look at how these choices fit into a purchase, see the online ordering buying guide. For confirmation messages specifically, ask a vendor whether the message is sent on submission or acceptance, and whether you can change that trigger.
Show the order, total and fulfillment details
Guests need enough detail to spot a mistake before the food is handed over. List each item with its quantity, selected options and any special instructions the restaurant received. Include an order reference that staff can search for when the guest calls.
Show the total as a breakdown rather than a single unexplained number. Separate the item subtotal, any delivery or service charge, tip and applicable tax when those amounts are part of the order. Clearly state whether the amount has been paid or remains due. Do not combine a tip with a delivery charge or present a payment status as a price.
The following is a hypothetical pickup order. The times, items and amounts are assumptions, not a quote or an example of a particular provider's message. The total includes the listed food, tip and assumed tax; there is no delivery or service charge in this example.
| Message field | Sample data | What the guest needs to know |
|---|---|---|
| Status and reference | Accepted; order 482 | The restaurant accepted this order; use 482 when calling. |
| Items | 2 veggie wraps at $10 each; 1 soup at $6; no onions on either wrap | Quantities and the received instruction match the request. |
| Amount | Food $26; tip $3; assumed tax $2; total $31 | The guest can see how the $31 total was calculated. |
| Payment | Paid online: $31 | No payment is expected at pickup for this order. |
| Pickup | Expected at 6:30 p.m.; 12 Oak Street; collect at the front counter | The time is an estimate and the pickup point is specific. |
| Contact | Call the restaurant at 555-0102; mention order 482 | There is a direct route for a correction. |
A concise message using that data could read: “Order 482 accepted. Pickup is expected at 6:30 p.m. at 12 Oak Street, front counter. Your order: 2 veggie wraps, no onions; 1 soup. Food $26, tip $3, tax $2; total $31, paid online. Questions or corrections? Call 555-0102 and mention order 482.”
For delivery, replace the pickup instructions with the delivery address and an estimated arrival time or window. Include an apartment or access detail only as needed to complete the handoff, and check that the guest can recognize the address. If a delivery provider handles the order, make clear which number the guest should use for a food mistake and which contact handles a delivery issue.
Keep the main message short enough to scan. If item details or the full charge breakdown appear on a separate order page, make that destination easy to reach and ask whether it remains accessible to the guest. Do not hide the acceptance status, fulfillment details or contact path behind a long block of promotional text.
Give guests a contact path that works
Put the restaurant name and contact information in the confirmation itself. A phone number is useful only if someone can answer it during the hours orders are being fulfilled. If a guest replies to an email or text, know where that reply goes. A message sent from an unmonitored address should point to a monitored alternative.
Decide who can handle common requests before choosing the wording. The front counter may be able to correct an item before preparation starts, while a delivery provider may need to handle a driver-location question. Give staff a way to find the order by reference and a clear process for deciding whether a requested change is still possible.
Do not promise that every change or cancellation can be accommodated. A practical line is: “Call us as soon as possible about changes; we will let you know what we can do.” If the restaurant cannot edit an accepted order in its system, agree on a staff procedure for recording the request and communicating the outcome.
Check the contact details wherever guests encounter them. The number on your restaurant website and the one in your confirmation should lead to the intended location. If you operate several locations, make sure the message uses the location fulfilling the order, not just a head office number.
Plan for changes, delays and exceptions
The first confirmation is a snapshot. After it is sent, an item may become unavailable, preparation may take longer, or the guest may ask to change an order. Agree on which events require a follow-up and who is responsible for sending it. Ask the ordering provider whether updates can be sent through the system, and what staff must handle separately.
For the hypothetical order above, suppose the soup becomes unavailable after acceptance. A useful follow-up identifies order 482, explains that the soup is unavailable and asks the guest to call to discuss the available options. Staff should not describe a replacement, revised total or refund as complete until the relevant action has actually happened. Record the decision where the team can find it.
For a delay, give a revised estimate only when someone has checked it. “Your pickup is now expected at 6:45 p.m.” is useful if that is the current estimate; “ready soon” gives the guest little to plan around. If no reliable time is available, say the order is delayed and provide the contact path rather than inventing a precise time.
Also decide what happens when a message cannot be delivered. Staff need a way to notice the issue and determine whether another contact method is appropriate. Ask vendors what delivery or failure information staff can see, and whether message costs or channel limits apply. A sent notice is not the same as proof that a guest read it.
Use a checklist before changing your setup
Review the confirmation against a recent order record without exposing guest details unnecessarily. Then use a simulated order to check the wording and staff workflow. Configure the simulation so it cannot make a real card payment, send a guest message or dispatch a courier. If your provider cannot offer that separation, review a sample message and walk through the steps with staff instead.
- Trigger: Does the message distinguish receipt from restaurant acceptance?
- Order: Do reference, location, quantities, options and received instructions match the order record?
- Money: Do the line items add to the total, and does the payment wording match the actual status?
- Fulfillment: Are the pickup point or delivery address and estimated time clear?
- Contact: Does the listed route reach the person responsible, and can staff find the order?
- Exceptions: Can the team communicate a delay, unavailable item or agreed change without implying it has already been resolved?
A simulation checks the content and workflow without involving a guest. If you later run a live service pilot, plan it separately with staff, explain the live conditions and monitor actual orders and messages. Do not treat a simulation as proof that every live notification or handoff will work.
Use the checklist to review your current setup, then ask Fleksa about its restaurant online ordering, including current US availability and how its confirmation and update options would fit your workflow.
Frequently asked questions
Is an order receipt the same as an acceptance?
No. A receipt can acknowledge that a request arrived; acceptance means the restaurant has agreed to fulfill it. Use distinct wording if staff review orders before accepting them.
Should a confirmation include the payment status?
Yes. Show whether the order is paid, payment is pending or the guest should pay at pickup, according to the actual payment status. Keep that status separate from the total and its breakdown.
What should a delay message say?
Identify the order, explain that it is delayed, give a revised estimate if one is available, and provide a working contact path. Avoid presenting an unverified time as a promise.
