When your order count changes from month to month, compare ordering plans against a full year of expected volume—not just an average month. Apply each written quote to the same monthly counts, add fixed and one-time charges, and check both the annual total and the largest monthly bill.
The cheapest plan over a year may still be difficult to budget for in a busy month. The right choice also depends on which orders count toward each pricing tier, what happens when you cross a limit, and whether the contract lets you adjust your plan as volume changes.
Gather monthly order counts or credible ranges
Start with the orders that would run through the system you are buying. Pull monthly totals from your current ordering dashboard, POS reports or bookkeeping records. If different people manage those systems, ask each for the same date range and reconcile any differences before requesting quotes.
Count orders, not individual items or guests. An order containing four meals is generally one order for a volume model, but the provider's definition controls its quote. Ask whether the count includes pickup, delivery, scheduled orders, canceled orders, refunds and test orders. Also ask whether an order placed through another channel but entered into the POS counts toward the limit.
Keep marketplace orders separate from direct website orders unless the proposed contract charges for both. A delivery order and a pickup order may also carry different costs. If the quote uses a percentage of sales rather than an order count, collect the corresponding sales amounts as a separate input. A count alone cannot calculate a percentage-based charge.
Use at least 12 months of history if you have it. Mark unusual periods, such as a closure, a large catering event or a menu change, rather than silently treating them as normal. For a new location, build a range from opening plans, expected service days and capacity. For example, estimate orders per open day and multiply by the number of days you expect to operate. Treat the result as a planning assumption, not a forecast the vendor has validated.
Write down three useful views: a slow month, a typical month and a busy month. Then map all 12 months, even if several use the same estimate. That preserves the shape of your year. Two restaurants with the same annual count can face different tier charges if one has steady volume and the other has a few very busy months.
Before comparing prices, make sure each quote covers the workflow you need. The online ordering buying guide can help you identify requirements to include. A low quote is less useful if a necessary function is priced separately.
Apply each quote to the same monthly volumes
Ask vendors for written pricing at your slow, typical and busy counts, plus the rules between those points. Some plans use a flat subscription; others may change price when a monthly threshold is crossed. Ask whether crossing a threshold changes the price for the whole month, triggers a charge only on extra orders, or moves you into a different plan for a longer period.
The following is a hypothetical comparison, not a quote from Fleksa or another provider. The restaurant expects four months at 100 orders, four at 300 and four at 600. Plan A costs $180 per month at each volume. Plan B costs $60 for up to 200 orders, $150 for 201–400 and $300 for 401–700. Each plan has a 12-month commitment. Plan A has a $240 one-time setup charge; Plan B has a $120 one-time setup charge.
| Annual volume pattern | Plan A | Plan B | Comparison |
|---|---|---|---|
| 4 slow months, 100 orders each | 4 × $180 = $720 | 4 × $60 = $240 | B is $480 less |
| 4 typical months, 300 orders each | 4 × $180 = $720 | 4 × $150 = $600 | B is $120 less |
| 4 busy months, 600 orders each | 4 × $180 = $720 | 4 × $300 = $1,200 | A is $480 less |
| First year, including setup | $2,160 + $240 = $2,400 | $2,040 + $120 = $2,160 | B is $240 less |
The table includes the assumed fixed subscriptions, volume-tier charges and setup fees. It assumes no exception charges. It excludes payment processing, delivery or dispatch, hardware, add-ons and applicable taxes. Those costs would need to be added from actual quotes before choosing a provider.
On these assumptions, Plan B costs less over the first year, but its busy-month subscription is $120 higher than Plan A's. Plan A may be easier to budget for if cash is tight during peak months. Plan B is the lower quoted software cost if the annual savings matter more and the restaurant can absorb the higher busy-month bills.
Do not assume the result holds if the mix of months changes. Replace one slow month with a busy month and recalculate both plans. Also ask what Plan B would charge above 700 orders; the example does not define that price. Check the exact threshold, too: an order count of 401 is priced differently from 400 under the assumed tiers.
Include fixed costs, minimums and exceptions
A monthly subscription is only one line on a quote. Request a breakdown for setup, menu entry, training, a restaurant website, integrations, additional locations, hardware and optional services. Ask whether each charge is one-time, monthly, annual or dependent on use. If a feature is bundled, confirm that it is included at the location and volume you are pricing.
Review minimums alongside the tier schedule. A plan may advertise a low starting rate but require a higher monthly minimum, a prepaid term or a charge when you leave early. Ask whether the minimum applies during a closure or a month with no orders. A pause option is useful only if the contract explains what it costs and how long it lasts.
Look for charges that appear when something goes wrong or changes: refunds, canceled orders, chargebacks, menu updates, extra support or a move to a higher tier. Not every provider charges for these. Ask for the applicable amounts and conditions, then include the ones that reasonably fit your operation. If an amount cannot be estimated, list it separately rather than treating it as free.
Payment fees deserve their own line. A quoted processing rate is not the all-in cost of operating online ordering. Request the percentage, any per-transaction amount and other applicable processing charges, then apply them to your expected paid transactions and sales. Compare the same payment assumptions across quotes, or use each provider's written terms if processing differs.
Delivery costs are separate again. Ask who arranges dispatch, what the restaurant is charged, and what the guest pays. A guest delivery charge can offset a restaurant expense, but it remains a cost to the customer. Do not count the charge as a software discount or assume a direct-order plan includes a free courier.
For a current reference point, Fleksa's plans page, checked November 2026, lists Fix at $199 per month per location and 0% Fleksa commission on direct online orders. Payment processing, delivery or dispatch, hardware or add-ons, and applicable sales tax are extra. Confirm current terms and US availability in a written quote. The hypothetical plans above do not represent Fleksa pricing.
Compare annual totals and monthly cash flow
Build one row for each month and one column for each quote. Enter the expected count, apply the correct subscription or tier charge, and add the other quoted costs that occur that month. Add setup and any prepaid amount when they are due. Then total the year and identify the highest bill. A plan with a lower annual sum can still create a cash squeeze if a large prepayment lands before a busy season.
Run a second version with a different seasonal pattern. Keep the annual count plausible, but move some orders from quiet months into busy months. That shows whether concentration—not just total volume—pushes the plan into higher tiers. If a quote includes a sales percentage or payment fees, also vary order value; more orders and larger tickets affect those charges differently.
For each version, record the assumptions beside the result: included channels, expected open days, monthly counts, average paid order value where needed, and any charges left out. If you expect additional locations, model them separately unless the quote explicitly combines their volume. A per-location subscription should not be treated as one shared bill without confirmation.
Compare contract terms before deciding whether a small price difference is meaningful. Ask how much notice is needed to change tiers, whether unused capacity carries over, and what happens at renewal. If a provider offers a promotional rate, calculate the first year using the actual promotional period and show the later rate separately. Ask a qualified adviser about contract, legal or tax treatment when needed.
Finally, consider the value of predictable billing against the cost of unused capacity. A higher flat amount may be acceptable if it covers the service you need and makes a peak bill manageable. A tiered plan may fit better when slow months are genuinely slow and changing tiers does not create unwanted commitments. Neither structure wins without the restaurant's own monthly pattern and complete quote.
Check the ordering workflow before you sign
Price the same scope on each quote. Write down whether you need pickup, direct delivery, scheduled orders, menu changes and a restaurant website. Ask which functions are included, which require an add-on, and who handles setup. Check how staff receive an order and what happens when an item is unavailable.
Ask for a demonstration using simulated orders. Have the team walk through a normal order, a cancellation and a busy-period change without making a real card payment, sending a guest message or dispatching a courier. A simulated check can reveal workflow questions; it does not prove how the system will perform during live service. If you later arrange a live pilot, agree on its scope, costs and staff responsibilities with the provider first.
Use your completed monthly worksheet to review your current setup, then ask Fleksa about restaurant online ordering, a written quote and verified US availability for your location.
Frequently asked questions
Should I compare plans using average monthly orders?
Use the average as a reference, but price each month separately. An average can hide busy months that cross a tier and slow months when a minimum still applies.
What if my monthly order estimates are uncertain?
Build low and high seasonal scenarios and apply both to every quote. Ask the vendor what happens if you exceed the highest tier or need to change plans.
Does a zero-commission plan cover payment and delivery costs?
Not necessarily. Ask for processing, delivery or dispatch, hardware, add-ons and applicable taxes separately, and include the charges that apply to your operation.
