Staff can sell a legitimate variable-price item without leaving an untraceable entry if the POS records what was sold, the amount, who entered it, and any required approval. The buying question is whether those controls work together during service—not simply whether a screen has an open-price button.
Before choosing a system or changing your setup, decide who can enter an amount, what limits apply, what the guest sees, and how a manager will review the sale. Then ask each vendor to demonstrate that exact workflow on the devices and staff roles you expect to use.
Define the item and the decision point
An open-price item is deliberately set up for an amount entered at the time of sale. For example, a restaurant might sell a special item whose price changes with the day's supplier cost. That is different from changing the price of a regular menu item to correct a mistake or give a discount. Those actions may have separate permissions and records.
Start with a specific service scenario. A cashier needs to ring up a market-price seafood special while the line is moving. The cashier must know the item name and price, enter the amount, and see whether the system accepts it. If the amount exceeds the restaurant's limit, the cashier needs a clear next step rather than a vague error or a workaround.
Write down the rules before the demo:
- Item naming: Should the button have a specific name, such as “Market-price special,” or can staff enter a description? What must appear on the guest receipt?
- Amount entry: Who supplies the current price, and can staff see the amount before adding it to the check?
- Limits: What minimum and maximum amount can a staff member enter? Is a manager required outside that range?
- Review: Which report or transaction detail should show the item, amount, employee, and any approval?
- Fallback: If the control is unavailable or unclear, who takes over and how is the sale recorded?
Decide which requirements are essential and which are preferences. A receipt that names the item may be essential; a particular report layout may not be, provided the manager can find the same information reliably.
Compare the workflow, not the feature label
Ask each vendor to demonstrate the complete path: create or select the item, enter an amount, add it to a check, inspect the receipt, and find the transaction afterward. Use a cashier role first, then repeat the steps with a manager role. A demo under an administrator account alone does not show what ordinary staff can do.
Toast lists restaurant POS, hardware, online ordering, payments, kitchen display systems, and integrations. Square offers restaurant point of sale and related payment and order tools. Fleksa offers restaurant POS alongside direct ordering, reservations, and related tools. For each, use the same requirements sheet rather than assuming that an open-price label means the controls are identical.
Ask the demonstrator to show what happens when the amount is blank, zero, below the minimum, or above the maximum. Can the cashier change the amount after adding the item? If so, where does the original entry or change appear? Does approval happen before the sale proceeds, and can the manager later identify who approved it?
Check the guest-facing result too. A generic line such as “Miscellaneous” may make a legitimate sale hard to recognize later. Ask whether the receipt can show a useful item name and whether staff-entered descriptions, if available, also appear in transaction details. Check printed and digital receipts if you intend to use both.
Run the same questions on every relevant device and order channel. A counter terminal, handheld, and manager reporting screen may present different controls. If the restaurant wants to use the item for phone orders entered at the POS as well as counter sales, include both workflows. Do not assume a setting on one screen applies everywhere.
Record any unavailable function and the consequence. If a cashier cannot be limited to a maximum amount, can a manager review every open-price sale before the end of a shift? If that review is too slow or easy to skip, the gap may rule out the setup. Ask whether a feature requires a particular plan, processor, device, or configuration, and have the vendor include those dependencies in its written quote.
For hardware questions, compare the actual devices and peripherals you plan to buy, not just the software screen. The POS hardware page is a starting point for a device discussion. For broader costs, use the guide to no-monthly-fee POS costs to build a consistent quote comparison.
Use an open-price control and receipt worksheet
The following is a hypothetical simulation for a counter sale. The restaurant has chosen a cashier limit of $40 per open-price item and requires a manager to handle any higher amount. These are operating rules for the example, not claims about a particular POS.
The guest orders a market-price special for $18.50 and a side for $7.25. The item subtotal is $25.75. This worksheet excludes tax, tips, payment processing fees, fixed software and hardware costs, and exception costs; it is a transaction check, not an all-in operating-cost comparison. An actual receipt must reflect the restaurant's configured charges and applicable requirements.
The table shows the expected control or record at each step. Use its last column to decide what to ask the vendor to demonstrate; replace the expected result with an actual result only after an authorized test.
| Step | Example entry | Expected result | What to verify |
|---|---|---|---|
| Item and amount | Cashier selects “Market-price special” and enters $18.50 | Screen identifies the item and shows $18.50 before the check proceeds | Can the cashier enter and confirm the amount without broader price-edit rights? |
| Limit | Cashier attempts $45.00 on the same item | Cashier cannot complete that entry without the restaurant's manager process | Is the entry blocked, and what exactly must the manager do next? |
| Receipt | Special $18.50; side $7.25 | Both item names and amounts appear; item subtotal is $25.75 | Does the receipt identify the special clearly rather than only as a generic charge? |
| Manager review | Find the $18.50 open-price sale | Transaction detail identifies the item, amount, and entering employee | Where are changes and approvals shown, if they occurred, and can the manager retrieve them? |
The $45 attempt is a separate exception check; it is not part of the $25.75 subtotal. If the product cannot enforce the $40 limit, mark that requirement as unmet. Do not treat a manager's ability to view the sale afterward as proof that the cashier was blocked beforehand.
For the simulation, use a vendor-provided demonstration or practice environment that cannot create a real card payment, guest message, or courier dispatch. Ask the vendor to show a sample receipt and transaction record there. If a practice environment cannot show a required state, record it as unresolved rather than guessing.
A live service pilot is different. If you choose one, authorize it separately, assign a manager to monitor real transactions, and agree on a fallback before opening the workflow to staff. Do not use real customer payments or notifications as practice steps.
Choose the operating rule and handle exceptions
Give one person ownership of the setup and another clear responsibility for shift review. For example, the owner or general manager might approve the item name and limit; the shift manager checks open-price transactions against the day's authorized specials. Decide where the current price comes from and how staff learn when it changes.
Set acceptance criteria that a busy manager can apply. In the example, the cashier must be able to enter $18.50 under the named item, see it on the check, and produce a receipt with that name and amount. The $45 entry must be stopped for the cashier. The manager must be able to find the completed $18.50 sale and identify the entering employee. If an approval or change occurs, its record must also be available for review.
If any essential criterion fails, do not quietly substitute a generic button or share a manager login. Keep the item out of that workflow until the vendor provides an acceptable configuration, or have the authorized manager handle the sale using a documented alternative. Train staff on that alternative and tell them whom to call when the system gives an unexpected result.
Before signing, compare written quote totals over the same period. Separate fixed software and hardware charges from variable payment processing charges and any quoted exception costs, such as additional devices or support. A quoted processing rate alone is not the full operating cost. Ask about contract term, cancellation charges, processor requirements, and what happens to transaction records if you leave. For contract, legal, or tax treatment questions, consult a qualified adviser.
Fleksa's plans page, checked in November 2026, is the place to review its published pricing; confirm the current quote and configuration for your restaurant. Also ask how the open-price record fits into the reports your managers use in their restaurant management software.
Bring the worksheet to a demo and request the cashier, manager, receipt, and review steps in order. Request a restaurant POS system demo using your scenario and acceptance criteria, then compare the demonstrated results with the other quotes.
Frequently asked questions
Is an open-price item the same as a price override?
No. An open-price item is intended to receive an amount during the sale. A price override changes an existing item's price. Ask how the POS controls and records each action separately.
What should appear on an open-price receipt?
At minimum, decide whether the guest needs a recognizable item name and the entered amount. Check the actual receipt format and any other charges required for your restaurant with the appropriate adviser.
Can a manager review replace an entry limit?
It may be an alternative control, but it does not stop an excessive amount before the sale. Decide whether your restaurant can reliably review every relevant transaction and handle mistakes promptly.
