Choose an online ordering system by working backward from service. List the orders you need to accept, the way they must reach staff and the full cost of fulfilling them. Then ask vendors to demonstrate those requirements with your menu before you sign.
A low subscription price is not enough if staff must re-enter every ticket or guests cannot order during the hours you serve. Use the scorecard below to compare the same requirements and order volumes across vendors, then run a safe simulation before opening the new channel to guests.
Understand what you are buying
A restaurant online ordering system takes a guest from a menu to an order your team can prepare. The details vary, but the buying decision usually covers five jobs:
- Menu: Show items, prices, choices and availability accurately.
- Checkout: Collect the order type, timing, contact information and payment where applicable.
- Handoff: Put a readable ticket in front of the people who accept and prepare it.
- Fulfillment: Support the pickup or delivery process you intend to offer.
- Records: Give staff enough order and payment information to resolve questions and reconcile activity.
Ask vendors to show each step rather than assuming that a feature name describes the whole workflow. For example, a delivery option on a menu does not tell you who supplies the courier, how dispatch works or what happens when no driver is available.
Direct ordering gives guests a way to order from your restaurant through a channel you direct them to, such as your website. A marketplace lists restaurants where guests can browse and discover places to order. They serve different purposes, and a restaurant can use both. Compare their contributions and workloads instead of assuming an order on one channel would otherwise have appeared on the other. This guide to comparing direct and marketplace orders can help with that separate calculation.
Direct systems also differ in how guests reach checkout. Some work through a page supplied by the vendor; others may be connected to a restaurant's existing site or POS. Ask where the guest goes after selecting Order, whose branding appears and who controls the domain. If you need a new site as well, consider the work involved in maintaining a restaurant website, not just the checkout screen. A clean ordering page cannot fix a phone number, menu or hours that are wrong elsewhere.
Finally, clarify what happens to customer and order records if you leave. Ask which fields you can export, in what format, whether there is a charge and how long records remain available. Access to data and permission to use it for a particular purpose are separate questions; ask a qualified adviser about contract or legal questions when needed.
Match requirements to the way you serve
Start with a typical shift, then describe the awkward cases: a sold-out item, a guest who chooses the wrong time and a driver who is late. The following is a hypothetical example, not a description of a particular product.
Imagine a neighborhood restaurant that offers pickup throughout its service hours and delivery only in the evening. Its lunch menu ends before dinner starts. Guests can choose a side with a main dish, and some sides cost extra. The restaurant has one kitchen printer and wants staff to review incoming orders at the counter.
For this restaurant, a system that displays a menu but cannot handle the required time windows or paid choices would create manual work or incorrect orders. Before comparing extras, the owner should ask vendors to demonstrate the following scorecard. Mark a requirement as passed only when the vendor shows the actual workflow or supplies a clear written commitment.
| Requirement | What to ask or demonstrate | Decision standard |
|---|---|---|
| Pickup and delivery | Show pickup throughout service and delivery only in the evening; explain delivery-area rules. | Guests cannot select a service outside its configured hours or area. |
| Menu and modifiers | Show the lunch-to-dinner change and a main with a paid side. | The right menu appears at the intended time, and the side and its price reach the ticket. |
| Staff handoff | Show acceptance at the counter and the route to the existing printer. | Staff can identify and prepare the order without retyping it; confirm printer compatibility. |
| Exceptions | Show how staff mark an item unavailable and handle a delayed or failed delivery. | A named staff member has a clear action for each case, including how to contact the guest if needed. |
The scorecard separates a feature label from the result the restaurant needs. If a vendor cannot meet a standard, record the workaround and who will perform it. For example, a second tablet may be workable, but only if someone is responsible for watching it during a rush. If the existing printer is not supported, get the cost and setup requirements for an alternative before treating the handoff as solved.
Also ask how soon orders can be placed, whether guests can schedule ahead and how preparation times are set. Can staff pause new orders without closing the entire restaurant? Can they change an item without changing the printed menu? Decide which controls are essential for your service and which would merely be convenient.
For delivery, draw your intended service area and ask how boundaries, minimums and delivery charges are configured. Identify who accepts an order, requests a courier and handles a failed dispatch. Fleksa supplies restaurant software, not a courier fleet, so ask how your proposed delivery arrangement would be set up and billed.
Compare complete vendor quotes, not headline fees
Give every vendor the same assumptions: location count, pickup and delivery order volumes, expected payment mix, required hardware and delivery arrangement. Request an itemized written quote and a worked monthly total. A percentage alone does not tell you the cost if one vendor also charges for setup, devices or dispatch.
Separate these lines when comparing offers:
- Fixed charges: Monthly subscription, location fees, equipment rental and required add-ons. Show one-time setup or hardware purchases separately.
- Variable charges: Provider commission, payment processing and any per-order software or delivery charges. Ask what amount each percentage applies to.
- Guest charges: Delivery or service fees shown to the customer. Identify who receives each charge and whether it offsets an expense on the restaurant's statement.
- Exception costs: Possible charges for refunds, canceled orders, failed deliveries or support. Ask how each is billed and who bears it.
Payment processing fees are only one part of operating cost. Deposits are money transferred to your account, not a fee or necessarily the same measure as sales. Ask for a sample statement showing order totals, guest charges, tips, deductions and deposits, and how refunds appear. That makes it easier for whoever closes the books to match an order to the money received.
As of November 2026, the Fleksa plans page lists Fix at $199 per month per location with 0% Fleksa commission on direct online orders. Payment processing, delivery or dispatch, hardware and add-ons, and applicable sales tax are extra. Confirm current availability and terms in a written quote.
Here is a separate hypothetical cost example for that plan: assume one location has 300 direct delivery orders in a month and pays an illustrative $6 delivery charge for each. Delivery spend is 300 × $6, or $1,800. Adding the $199 fixed subscription gives $1,999, and the subscription allocation is about $0.66 per order. The $6 charge is an assumption, not a delivery quote.
That $1,999 includes the fixed subscription and assumed variable delivery charges. It excludes payment processing, hardware, add-ons, applicable tax and exception costs such as failed deliveries or refunds. If guests pay a delivery charge that the restaurant receives, calculate that offset separately; it remains a cost to the guest. The total is not a full operating cost or a prediction of sales, and it is not directly comparable with a marketplace offer without the same assumptions.
Check the commitment as well as the monthly figure. Ask about setup timing, renewal, price changes, cancellation notice, equipment ownership and data export after termination. Compare one-time charges separately from recurring charges so a cheap first month does not hide a larger commitment. Bring contract or tax questions to a qualified adviser.
Test the journey and plan the launch
A demonstration is useful, but your acceptance test should follow an order from the guest's phone to the person preparing it. Agree on the pass criteria and the person responsible for each check before launch. Use a sandbox or other simulated setup arranged with the vendor: the practice scenario must not trigger a real card payment, guest message or courier dispatch.
- Place a simulated mobile order. Find the menu on a phone, choose pickup at an allowed time and select a main with the paid side. Pass if the item, choice, price and order time are correct before submission. Repeat with an unavailable item and an out-of-hours delivery choice; neither should be selectable under the restaurant's rules.
- Check the simulated confirmation. Pass if the test confirmation displays the order type, items, total and promised time clearly. Inspect the confirmation in the test environment without sending a real guest message. Ask what staff and guests would see if acceptance is delayed.
- Follow the staff handoff. Pass if the designated staff member can identify the simulated order, accept it using the intended workflow and see a complete preparation ticket on the agreed device. If a printer is involved, confirm the test setup can safely demonstrate the print path.
- Rehearse an exception. Simulate an unavailable item and a failed delivery assignment. Pass if staff know who takes the next action, where the order status is recorded and how a real guest would be contacted, without actually contacting anyone or dispatching a courier.
Record failures with the screen or step involved, the owner of the fix and a retest date. A verbal promise is not a pass. If the vendor cannot provide a safe simulation for a step, agree on another non-live demonstration before relying on that workflow.
Once the simulated checks pass, plan a limited live service pilot during a manageable shift. Unlike a simulation, a live pilot involves actual orders, so brief staff on monitoring, guest support and any real fulfillment. Decide who watches incoming orders, who can pause ordering and how staff will handle an outage or a ticket that does not appear. Keep a manual fallback, including how to record an order and reconcile it later.
If you are replacing an existing system, agree on the cutover time and check each link that sends guests to ordering: your website, business profiles, social pages and printed materials. Keep the old and new workflows clearly labeled while both are in use, so staff know which screen to watch. A careful cutover reduces confusion but cannot guarantee uninterrupted service or that every order will be captured.
After the pilot, compare the results with the scorecard. Fix failed handoffs and unclear charges before expanding hours or delivery coverage. Review the Fleksa restaurant ordering system page and, if it fits your needs, ask for a demonstration using your menu, service hours and handoff requirements.
Frequently asked questions
Should a restaurant use direct ordering or a marketplace?
Direct ordering serves guests who reach your restaurant's own ordering channel; a marketplace also offers a place for guests to discover restaurants. You can use both. Compare their full costs and operational workload without assuming they generate the same orders.
What should an online ordering quote include?
Ask for subscription and setup charges, commissions, payment processing, hardware, add-ons, delivery or dispatch charges, guest fees and possible exception costs. Use the same order assumptions for every quote and separate one-time costs from recurring ones.
How can I test ordering without affecting real guests?
Ask for a sandbox or another simulated demonstration that does not process a real card payment, send a guest message or dispatch a courier. Check the menu, confirmation, staff handoff and an exception before planning a limited live service pilot.
