Manual tax setup gives control. It also demands proof.

Tax setup is one of those POS decisions that looks small until the first receipt is wrong. A restaurant may need inclusive tax, exclusive tax, item-level rates, service charges, exemptions, delivery differences, rounding rules, and receipt wording that varies by market.

This is not tax advice. It is an operating checklist for configuring and testing a POS. A local accountant, tax advisor, or regulatory specialist should confirm the rules before live billing.

Start with the selling price

The first question is whether displayed prices include tax. In an inclusive model, the menu price already contains tax and the receipt breaks out the tax portion. In an exclusive model, tax is added at checkout. Staff, customers, menus, and reports must all tell the same story.

Do not mix these casually. If dine-in prices are inclusive but delivery marketplace prices are exclusive, name that difference and test each path separately.

Map tax by item and context

Some restaurants have one tax rate for every sale. Many do not. Food, alcohol, packaged goods, service charges, catering, delivery, discounts, and exemptions may behave differently. The POS should let you represent the actual operating rule, but the restaurant must still decide who can change it and how changes are documented.

For multi-location operators, avoid copying settings blindly from one country or region to another. A configuration that is correct in one location can be wrong in the next.

Build a test-order matrix

Keep expected results in writing. If the POS total does not match the expected answer, resolve the rule before service. “Close enough” is not a finance policy.

Rounding and receipts

Rounding should be predictable at item, order, and report level. Small differences can grow when the restaurant compares receipts, daily reports, accounting exports, and tax filings. Decide whether rounding happens per item or per invoice, then test both tiny and large baskets.

Receipts should show the information customers and local rules expect: business details, tax numbers where required, taxable amount, tax amount, inclusive or exclusive presentation, discounts, service charges, payment mode, and invoice identifiers. Requirements vary. Verify them locally.

Control changes

Tax settings should not be casual front-counter edits. Name the people who can change them, record why a change was made, and keep before-and-after screenshots or exports. When tax rules change by date, schedule a test before the effective date and another test after the change goes live.

FloCafe and manual tax configuration

FloPOS is used across many markets, and FloCafe supports manual tax options for restaurant workflows. That flexibility is useful because restaurant rules vary widely. It should also make operators more careful: the software can provide configuration room, but it cannot certify that a local rule was chosen correctly.

If you are evaluating FloCafe for a new country, region, or concept, configure taxes with your actual menu and have the receipts reviewed before live service. Include cash and external-terminal payments in the test so the close-out report matches the tax report.

Configuration worksheet

1. List every revenue category: food, beverage, alcohol, delivery, catering, retail, fees, and discounts.
2. Mark whether prices are inclusive or exclusive for each service channel.
3. Assign the expected tax rate or exemption with local review.
4. Define rounding behavior and receipt wording.
5. Run the test-order matrix and attach expected totals.
6. Lock down who can change settings and how changes are reviewed.

Manual tax setup is powerful because it does not force every restaurant into one jurisdiction’s assumptions. The same power can create mistakes if nobody owns validation. Treat tax setup like a launch-critical workflow, because it is one.