/Help Center
Adminpos

How to set up a new POS Point from scratch

Verified May 2, 20263 min read

A POS Point is the configuration record for a single sales location. The bar gets one, the restaurant gets one, the poolside kiosk gets one. Each carries its own warehouses, cash desk, payment methods, printer mappings, and behavior flags. This guide walks the full setup so a fresh POS Point is ready for staff to log in and ring up an order.

Before you start

Make sure these exist already (create them in their own modules first):

  • At least one warehouse (Inventory → Warehouses) — the POS will deduct stock from it.
  • A cash desk with a TCR code (Accounting → Cash Desks) if you fiscalize. Without it, fiscal receipts will fail.
  • Active payment methods (Payments → Payment Methods) — Cash, Card, etc., each with isActive on.
  • QZ Tray installed on the device that will print, if you want silent printing — see the printer setup article.

Step 1 — create the POS Point

  1. Go to POS → POS Points and click Create.
  2. Name it after the physical location ("Restaurant", "Pool Bar", "Lobby Coffee"). The name appears on receipts and in reports.
  3. Set isActive on. An inactive POS Point is hidden from staff.

Step 2 — connect warehouse, cash desk, currency

  • Warehouses: pick one or more. The POS deducts stock from the first warehouse that has the product (or all, depending on your stock setup).
  • Cash desk (TCR): the fiscal device this POS Point reports to. Required for Albanian fiscalization (NIVF/NSLF/IIC).
  • Default currency + default payment account: what new orders default to. Staff can change at the order if needed.

Step 3 — pick active payment methods

Tick the methods this POS Point accepts. Typical: Cash, Card, Room Charge. Methods that aren't on the list won't appear on the payment screen even if they exist globally. Less is more — fewer choices means fewer mis-taps at busy hours.

Step 4 — configure printing

Three independent print routes — fiscal, non-fiscal, and waiter report — each with a printingOption (default = browser dialog, silent = QZ default printer, silent_to_printer = QZ to a specific named printer) and an optional printer name. Set fiscal to silent_to_printer + your fiscal thermal, and waiterReport to silent_to_printer + the kitchen printer. See the QZ Tray article for the full setup.

Step 5 — workflow flags

  • hasTables: enable for sit-down service. Staff see a table grid; takeaway/bar use turn this off.
  • tableReservationsEnabled: shows the Reservations tab on the table grid. See the table reservations article.
  • tablesMoveEnabled: lets staff transfer an open order between tables. See the order transfer article.
  • courseManagement: groups items into starter/main/dessert and prints each course separately.
  • liveOrderPrintingEnabled: emits each order to the subscribe-and-print page (a dedicated mini-PC in the kitchen).
  • alwaysFinalize: forces every save to also fiscalize/finalize. Use only if your workflow never has "hold and add later".
  • serviceFeeEnabled + serviceFeeType (percentage|fixed) + serviceFeeValue: auto-applies a service charge to every order. See the tip & service charge article.
  • waiterLogout: logs the waiter out after each finalize. Use on shared tablets.
  • differentUserOrder: lets multiple waiters share one open table. Off = one waiter "owns" the table.

Step 6 — save options & finalize behavior

saveOptions controls which buttons show on the order screen: save, finalize, print, sendToKitchen. Trim the list to match the workflow — a takeaway counter doesn't need sendToKitchen if it's not using the kitchen ticket flow.

Step 7 — verify with a test order

  1. Save the POS Point and log in to the POS app on the target device.
  2. Open a test table or start a takeaway, add one product, finalize on Cash for a small amount.
  3. Confirm: the receipt prints to the right printer, the fiscal QR/IIC appears (if fiscalized), and the order shows in Reports → Sales for today.
  4. Void or refund the test order so it doesn't pollute end-of-day numbers.

Frequently asked questions

Related articles