Before your website promises fast delivery or a wide service area, check whether the whole operation can deliver on that promise: the kitchen, the ordering system and whoever handles the trip. Use recent service records for the relevant hours and locations, not a best-case estimate or a single successful order.
Give every public claim an owner, a source and a review date. If you cannot support the wording for the guests who will see it, add a clear limit or remove it. A delivery estimate shown at checkout is a separate decision; the focus here is what your marketing pages promise before a guest starts an order.
Find every delivery promise on your website
Start with the obvious phrases: “delivery in 30 minutes,” “we deliver across town” and “delivery available every day.” Then look for less direct promises. A map, a delivery icon beside business hours, or a headline saying “order from anywhere in town” can set expectations just as strongly as a sentence.
Check the home page, menu pages, location pages, banners, footers and mobile views. Follow buttons into the ordering flow and note where the marketing message changes. A claim may appear accurate on one page but conflict with a different location’s hours or delivery area elsewhere.
Copy each statement into a delivery claim evidence ledger. Record the exact wording and page, rather than a summary such as “fast delivery.” Add the location and hours it appears to cover. If the claim has no visible limits, treat it as a broad promise when deciding what evidence it needs.
Different people may hold different pieces of the answer. The kitchen manager can explain preparation times and rush-hour constraints. The person managing online ordering can check configured hours and address rules. A delivery partner or dispatcher can explain its current service area, availability and trip charges. The person who edits the website needs to know which version to publish.
Also inventory cost language. “No commission” does not tell a guest what delivery costs, and it does not tell an owner the full cost of fulfilling an order. Keep claims about the restaurant’s software costs separate from any fee presented to the guest.
Compare claims with current service evidence
For a speed claim, define the clock first. Does it start when the guest submits the order, when the restaurant accepts it, or when a courier picks it up? Does it end at arrival or handoff? A pickup-to-arrival figure alone cannot support a promise about the full wait after ordering.
Look at completed deliveries across the hours, locations and distances covered by the wording. Include busy periods and delayed orders, not just smooth trips. Check whether the records include preparation, courier assignment and travel. If they do not, ask the people responsible for those stages what records they can provide. A limited sample may help you spot a problem, but it cannot establish a reliable promise for every future order.
For a coverage claim, compare the advertised map or place names with the actual address eligibility rules and current delivery partner coverage. A circle on a map may include addresses the ordering system cannot accept. Coverage can also differ by location, time or courier availability. Ask who updates each boundary and how quickly a change reaches the website.
The following ledger is a hypothetical example. Its assumptions are not service results or claims about Fleksa. It shows how an owner might turn three website statements into decisions.
| Public claim | Evidence to compare | Decision | Owner and trigger |
|---|---|---|---|
| “Delivery in 30 minutes” | Assume records show varied total waits, including longer Friday orders. | Remove the fixed promise; describe delivery without a time guarantee. | Kitchen manager reviews after a schedule change. |
| “We deliver throughout Oak Hill” | Assume the configured boundary excludes some Oak Hill addresses. | Remove the neighborhood-wide claim; ask guests to check their address when ordering. | Ordering manager reviews after a boundary change. |
| “Delivery available every evening” | Assume Sunday delivery ends before the restaurant closes. | Publish the actual delivery hours by location. | Shift lead reviews after an hours change. |
The point of the ledger is not to find a favorable number for each claim. It is to identify the gap between what guests reasonably expect and what the operation can support. In the example, the Friday delays matter because the original speed wording has no day or time limit. The excluded addresses matter because “throughout” leaves no room for exceptions.
Add useful limits or remove the claim
Good qualification is specific and easy to find. If delivery is offered only during certain hours, put those hours next to the claim or link directly to the relevant location information. If eligibility depends on the address, say so before the guest invests time building an order. Do not hide a major restriction in a distant footer while the headline promises universal coverage.
Choose language that matches the evidence. “Check delivery availability for your address” is more useful than a town-wide promise when the boundary has exceptions. “Delivery hours vary by location” can introduce a location list, but it should not replace the actual hours where those hours can be shown. Avoid turning an unsupported guarantee into a vague “usually fast” claim unless you can explain what that means.
Check fee wording with the same care. Fleksa’s plans, checked in November 2026, list Fix at $199 per month per location and 0% Fleksa commission on direct online orders. Payment processing, delivery or dispatch, hardware and add-ons, and applicable sales tax are extra. The commission figure is not an all-in operating cost, and delivery availability varies by location. Ask for a current quote and how trip charges apply before using any cost comparison in your marketing.
Before publishing revised wording, run a simulated review. Read the page as a guest at an eligible address and then as one just outside the delivery boundary. Follow the relevant links without placing an order. Confirm that the wording points both readers to the right next step and that the displayed hours agree across pages. This check must not create a real payment, guest message or courier dispatch.
A simulation checks the presentation and logic; it does not prove real-world delivery speed or courier availability. If you later conduct a live service pilot, plan it separately with the people responsible for orders and dispatch, and use its actual records alongside other relevant service evidence. Do not treat a practice click-through as a completed delivery.
Keep the ledger current after changes
Assign one person to maintain the ledger, even when several teams supply evidence. For each row, keep the exact claim, its page, the location and hours covered, the evidence source, the decision, the owner and the next review date. A link to an internal report or a dated note about a partner’s coverage is more useful than “operations confirmed.”
Review the claims on a regular schedule and whenever something material changes: delivery boundaries, opening hours, kitchen capacity, ordering rules, dispatch arrangements or fees. A new delivery partner may have different coverage. A menu change may affect preparation time. A location that stays open later does not necessarily offer delivery for those extra hours.
When a change happens, update the public page and the underlying ordering settings together where applicable. Then check the mobile page and any other locations where the old wording appeared. If the operational change is temporary but its end date is uncertain, remove or qualify the claim until you can verify it again. Keep the old ledger entry with the date and reason for the change so the next reviewer understands the decision.
Use the ledger to review one high-visibility claim today. If you are considering a new setup, explore Fleksa’s restaurant website and ask Fleksa about verified availability in your US location, including how delivery coverage and charges would be confirmed.
Frequently asked questions
Can I advertise a delivery time based on my fastest orders?
No. Fastest orders do not represent the full guest wait across the hours and areas your claim covers. Define the start and end of the wait, review relevant completed orders including delays, and remove a fixed promise you cannot support.
Should the website show a delivery map?
A map can help if it reflects current address eligibility and makes any limits clear. Check it against the ordering rules and delivery partner coverage, and give guests a way to check their own address.
Does zero commission mean delivery has no cost?
No. A commission figure describes one charge, not the whole delivery operation. Check processing and per-trip dispatch charges, any guest-facing fee, and other applicable costs separately.
