A restaurant POS should apply your service charge only to the checks you intend, show the amount clearly to staff and guests, and report it in a way your manager can reconcile. The buying decision is whether the system can do all three under your actual service rules—not just add a fee to one demonstration check.
Before signing or changing a setup, write down the rule, ask the vendor to demonstrate it, and compare each result with an expected screen, receipt, and report. Include checks that should not receive the charge and situations where an authorized employee needs to remove it.
Define the charge before you see a demo
Start with the service situation. Does the charge apply to dine-in checks, particular order types, or parties meeting a stated size? Is it a fixed amount or a percentage? If it is a percentage, specify the amount it is calculated on. Decide whether it applies once per check or under some other rule.
Write down who needs to see the result and when. A server may need to confirm the charge before presenting a check. A guest needs to understand the line on the receipt. A manager needs to see the charge and any removal in reporting. A rule that looks right on a setup screen is not enough if staff cannot verify it during service.
Also decide which checks are ineligible. For example, if a policy applies to parties of six or more, a party of five should not receive it. A party is a group of guests, not a count of physical tables: a six-person party may occupy two tables, while two separate parties may sit at adjacent tables. Ask how staff enter and change party size, especially when checks are split or tables are combined.
Document how the charge should appear to the guest and what information belongs in the report. Decide who can remove it, what reason they must record, and what staff should do if the POS applies it incorrectly. Service charges, tips, deposits, and sales are different measures; do not assume the POS will classify or report them in the same way.
Tax treatment and the wording of a policy can depend on the circumstances. Ask a qualified tax or legal adviser what treatment and disclosures apply to your restaurant, then give the vendor those requirements to configure and demonstrate. The POS demonstration is a check of system behavior, not a substitute for that advice.
Compare the workflow, not just the feature name
Give each vendor the same requirements sheet. 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 connected with direct ordering, reservations, and related tools. Those descriptions do not establish how any particular service-charge rule works; ask each vendor to demonstrate yours.
For the restaurant POS system you are considering, walk through an eligible check and an ineligible check. If you are deciding between a fixed charge and a percentage, ask to see each as a separate configuration. Check the amount before payment, on the guest-facing receipt, and in the manager's report.
Then change the circumstances. Add a guest, remove a guest, split a check, combine checks, and adjust an item where those actions matter to your policy. Ask the vendor to show when the charge is recalculated and whether an employee sees a warning. If a charge must be removed, have the vendor demonstrate the permitted role, the reason entry if available, and the resulting receipt and report.
Use the devices and roles that would be involved in your operation. A manager reviewing a report may not use the same screen as a server presenting a check. If you use handhelds, counters, or other POS hardware, ask which parts of the workflow work on each device. If orders arrive through more than one channel, ask which channels can apply the rule and how staff handle those that cannot.
Record the configuration, plan, payment processor, hardware, and integrations required for each demonstrated result. Ask for unavailable functions and manual steps to be stated in writing. Obtain a current quote for the required setup and ask about contract duration, cancellation fees, and processor requirements. Fleksa's plans page is a starting point for its pricing; pricing details were checked in November 2026. Confirm the current quote and the service-charge setup before making a decision.
Use an eligibility and receipt matrix
The following is a hypothetical restaurant policy used to prepare a test. A dine-in party of six or more is eligible; a party of five or fewer is not. The restaurant is comparing two alternative rules: a fixed $9 charge per eligible check, or a 10% charge on the food-and-drink subtotal. The two charges are not combined.
For this arithmetic example, the subtotal is $80 and no tax is included. The expected totals include the subtotal and the selected service charge only; they exclude tax, tips, processing fees, and other charges. They are check totals, not a calculation of operating cost. Test tax separately using the treatment your adviser has specified.
| Scenario | Fixed rule | Percentage rule | Expected receipt or report |
|---|---|---|---|
| Six guests, $80 subtotal | $9 charge; $89 total | $8 charge; $88 total | Show the charge as a distinct line; report the amount under the agreed category. |
| Five guests, $80 subtotal | No charge; $80 total | No charge; $80 total | No service-charge line or amount, according to the agreed display. |
| Eligible check; authorized removal | Remove $9; $80 total | Remove $8; $80 total | Receipt reflects removal; manager can verify the removal and reason if required. |
| Eligible party becomes ineligible before payment | No charge; $80 total | No charge; $80 total | Screen and receipt match the updated eligibility; report matches the final check. |
Read each row as an acceptance check, not as proof that a product supports the rule. For the first row, the percentage calculation is $80 × 10% = $8; the fixed alternative is $9 regardless of that calculation. In the removal row, the expected final total returns to $80 under either alternative. A vendor must show how its system records the change, not merely show the final total.
Add rows for your own exceptions. If your policy covers split checks, state whether eligibility follows the original party or each resulting check, and specify the expected charge on each receipt. For a combined check, state how staff should identify the party and how many charges should appear. Do not assume the system will make the same distinction your policy does.
Run these checks in an authorized test or demo environment with simulated transactions. Confirm in advance that the simulation cannot create a real card payment, guest message, or courier dispatch. A sample receipt and test report should be clearly identifiable as test output. Record the actual result only after the authorized test, alongside the device, role, configuration, and date.
Set acceptance criteria and an exception plan
Assign a manager to own the matrix and approve the operating rule. Each row should have a clear pass condition: the right amount on the right check, the agreed receipt display, and a report the manager can reconcile. For removal, include the authorized role and the evidence the manager expects to see. A verbal assurance is useful for discussion, but the demonstrated workflow is what staff will need to follow.
Mark a row as unresolved if the vendor cannot demonstrate it, the result differs from the policy, or a needed role or device is unavailable. Ask whether a different configuration, plan, or integration is required and what that adds to the quote. For a manual workaround, name the employee responsible, describe the steps, and decide whether the extra work is acceptable during a busy shift.
Set a fallback before launch. For example, if staff cannot determine whether a split check is eligible, they might pause the charge and ask the manager to review the policy and check. The correct fallback for your restaurant depends on your policy and the advice you receive; train staff on the approved version rather than letting each server improvise.
A simulation prepares staff without involving guests or money. If you later run a live service pilot, authorize it separately, train the participating team, and monitor actual receipts and reports under your approved policy. Review exceptions with the manager and correct the setup or procedure before expanding its use. Related restaurant management software can be part of the reporting discussion, but ask exactly where service-charge totals and removals appear.
Ready to compare your rule with a real workflow? Request a POS demo and bring your completed scenarios, expected receipts, report requirements, and acceptance criteria.
Frequently asked questions
Should a service charge appear separately on the receipt?
Write your required guest-facing wording and display into the test, then ask the vendor to show it on the actual receipt format you use. Consult a qualified adviser about any applicable disclosure requirements.
Can a POS automatically remove a charge when party size changes?
That depends on the product and configuration. Ask the vendor to demonstrate the change on the relevant device and show the updated check, receipt, and report.
Is a service charge the same as a tip?
Do not treat them as interchangeable in your test or reports. Define the categories your restaurant needs and consult a qualified adviser about their treatment.
