The pricing unit determines which part of your POS bill grows when your restaurant does. A per-device charge usually rises when you add a billable terminal. A per-location charge usually rises when you open another restaurant, even if that restaurant starts with only one terminal. Some quotes include both.
Before comparing monthly totals, ask each provider to show what is included at your current size and what changes when you add a device or a location. Then add the one-time setup and hardware charges. A low starting quote can look quite different after either change.
Identify every pricing unit in the quote
Start with a count of physical locations, devices and staff accounts. These are separate units. A restaurant with one location, three terminals and 15 staff members should not assume its quote covers all three counts without an additional charge.
Ask the provider to label each recurring line by its billing unit:
- Per device: Does the fee apply to each terminal, tablet, handheld or other device that accesses the POS? Is one device included in the base price?
- Per location: What counts as a location, and how many devices or services are included there?
- Per user: Is the charge based on named staff accounts, active users or another count? Do managers and seasonal staff count?
- Per feature or service: Which tools are included, and which are charged separately for each device, location or account?
Also ask whether a minimum fee, device tier or package changes the calculation. For example, a quote might include two devices in a location fee and charge for the third. Another might charge for every device from the first. The monthly totals could match today but diverge when you expand.
Define a terminal in the quote rather than assuming every screen is billed the same way. A counter register, a handheld used for orders and a kitchen screen may have different roles. Ask which ones count toward each fee and whether a spare device counts while it is not in use.
Review the restaurant POS requirements alongside the pricing sheet. A terminal that needs an extra paid module to do its job is not fully priced by its device fee alone. Similarly, a staff account fee may matter more than the terminal fee if a new site brings a large team.
Model an extra terminal and a second location
The following numbers are hypothetical, not Fleksa prices or a vendor quote. Assume the existing restaurant pays $100 per month for its location and $30 per month for its one terminal. The provider charges the same rates for additions, with no included extra devices. All additions begin at the start of the period and run for 12 months.
The table compares two separate changes to that starting setup. It shows the additional cost of each change, not the full bill for the existing restaurant.
| Change | Added monthly fees | One-time fees | Added first-year total |
|---|---|---|---|
| One extra terminal at the existing location | $30 device fee | $120 hardware + $50 setup = $170 | 12 × $30 + $170 = $530 |
| Second location with one terminal | $100 location + $30 device + $20 shared service = $150 | $120 hardware + $300 implementation = $420 | 12 × $150 + $420 = $2,220 |
For the extra terminal, the recurring portion is $360 over the year. Adding $170 in one-time hardware and setup makes the incremental total $530. For the second restaurant, $1,800 in recurring charges plus $420 in one-time charges makes $2,220. The $20 shared-service charge is included only because this hypothetical quote specifies it as an added monthly fee for the second site.
These totals include the stated recurring location, device and service fees, plus the stated one-time charges. They exclude payment processing, delivery, taxes, extra users, other feature charges and exception costs such as repairs or early termination. They are not all-in operating costs. Obtain those amounts separately if they apply to your decision.
The recommendation follows from the setup: if you need only another ordering point inside the existing restaurant, compare the $530 incremental terminal scenario with equivalent terminal quotes, not with the cost of opening a site. If you plan a second restaurant, use the location scenario and ask for every site-specific charge in writing. Do not assume a second location costs only another device fee.
Ask what changes at the second restaurant
A second location can add more than a base subscription. Send providers the same short description: one new address, the planned opening date, the number and type of terminals, expected staff accounts and the functions needed on opening day. Request a first-year quote and a recurring monthly amount after setup.
Ask whether implementation is charged once per location, per device or by the work required. Have the quote distinguish software configuration from hardware, installation, menu setup and training. If a shared service appears on the quote, ask what it covers and whether the charge rises again at a third location. Do not add a shared-service fee merely because a provider offers central management.
Also check whether the new site needs its own subscriptions for tools used by the first restaurant. If you want a shared view across sites, ask what access is included and whether each location can still have its own menu, prices and staff permissions. The answer affects both the operational setup and the relevant pricing unit.
For a like-for-like shortlist, Toast lists restaurant POS, hardware, online ordering, payments, kitchen display and integrations. Square offers restaurant point of sale and related payment and ordering tools. Fleksa offers restaurant POS connected with direct ordering, reservations and related tools. Give each provider the same requirements sheet and ask for written charges rather than assuming the packages are equivalent.
Check Fleksa's plans for its published pricing, checked in November 2026, and request a current quote for your device and location counts. For broader questions about connected operations, review the restaurant management software details and ask which functions and setup are available for your locations.
Check inactive, spare and replacement devices
A device count can change without a restaurant adding a new register. You might keep a spare for busy weekends, replace a broken tablet or close a patio station for the season. Ask when a device starts and stops being billable: on activation, assignment to a location, actual use or another event.
Get the answer for each situation that matters to you:
- Dormant device: Can you deactivate it, and when does the recurring charge stop?
- Replacement: Can a license be transferred to the new device, and can both devices be billed during the swap?
- Seasonal return: Is there a reactivation fee or minimum billing period?
- Spare: Does keeping a configured backup make it billable before it is needed?
Ask how to make each change and who is authorized to do it. A manager may need to remove a device before the next billing date; a contract may set a different process. Request the applicable terms, including cancellation and contract duration, in writing. For contract or tax treatment, consult a qualified adviser as needed.
Separate the license question from the equipment question. A replacement device might require a new purchase even if the software license transfers. Check the provider's requirements for restaurant POS hardware, including support for the specific equipment you plan to use. Ask what setup, shipping or repair charges could apply rather than treating a monthly software fee as the full cost.
Make the quotes comparable before signing
Put each quote on the same timeline. List the current setup, the added terminal and the second location as separate scenarios. For each, show one-time charges, monthly charges, included quantities and the first-year total. Keep processing fees separate from the software subtotal: a quoted processing rate is not the restaurant's all-in POS operating cost.
For a new location, confirm the menu and permissions before service. Use a restaurant-approved reference menu to check categories, modifiers, quantities, availability and totals. Run practice checks in a simulation that cannot trigger a real card payment, guest message or courier dispatch. If you later run a live service pilot, plan it separately with the provider and staff; do not treat a simulation as proof of live-service performance.
Take your device count, location plan and two expansion scenarios to a Fleksa POS discussion. Ask for an itemized quote showing what changes when you add a terminal, open a second site or deactivate a device.
Frequently asked questions
Does per-location pricing include every terminal?
Not necessarily. A location fee may include a set number of devices, or devices may be billed separately. Ask for the included count and the charge for each additional device.
Is an inactive POS terminal still billable?
That depends on the agreement and how the provider defines an active device. Ask how to deactivate it, when billing stops and whether restarting it carries a fee.
How should I compare a second location with an extra terminal?
Price them as separate changes from the same starting setup. Include the recurring fees and one-time costs specified for each, then list excluded costs so you can request them before deciding.
