> Documentation index: https://stilldeeppos.com/llms.txt # Features of the StillDeep point of sale > Sales, taxes, offline mode, ticketing, retail, rentals, appointments, reservations, receipts and printing: what the StillDeep engine does for every register. Source: https://stilldeeppos.com/features Every feature lives in the engine, not in the screen. A kiosk, a touch register and a web shop share the same rules, the same taxes and the same receipts. ## Selling - One sales engine for every register: cart, discounts, fees, payments, refunds and shift closing follow the same path whether the screen runs in the same process or over gRPC. - The server checks every sale again: prices, taxes and totals sent by a screen are never trusted as is. - Split payments, even shares, quick cash amounts, gift receipts, duplicates of past invoices. - Shifts with pauses, transfer to another register, blind cash counts and closing from any register with the right permission. - Canadian sales taxes (GST, QST, HST) computed per invoice with the official rounding rules. Canadian cash rounding is available as an extension. - Money is always stored as integer cents, never as floating point numbers: no penny lost to rounding. ## Offline by design - Each register keeps a local SQLite copy of the catalog, taxes and members, and an outbox of sales. - When the server cannot be reached, sales continue from the local copy; the outbox is drained first when the server comes back, before any update. - Printed numbers (receipts, tickets, reservations) never collide between registers, even offline. - Receipts and tickets carry a signed QR code that a register can verify without the Internet. ## Trades and modules ### Ticketing Scheduled events, seats and capacities held while the cart is open, tickets printed with their seat and code. ### Retail Inventory ledger, retail and case barcodes, scale labels, prices by kilogram or pound, lots and expiry dates, shelf labels. ### Rentals and locations Rental agreements with return dates and deposits, rented locations that carry their customer. ### Services by appointment Agenda, services that require a qualified staff group, appointments taken with a deposit. ### Reservations A sale put aside under an RV number, resumed by scan or from the customer file, paid in several steps. ### Cards and loyalty Customer cards, coupons issued and sealed by the server, badges for employees and customers. Restaurant and bar modules are planned. Modules are activated per business today; activation per register, sold as a license, is planned. ## Receipts and printing - Thermal printers (ESC/POS over network, USB or serial) and regular printers through the system driver. - A drag-and-drop designer in the Admin for receipts, tickets, cards (CR80) and employee badges, with conditions and loops. - PDF and image output, barcodes and QR codes, French and English templates chosen from the customer's language. - Print destinations declared in the Admin, actual printer chosen at each register. ## Scanning Barcode readers as keyboard (HID) or serial port, several per register. Each screen declares what it accepts: products, customers, employees, receipts, coupons. Codes that cannot come from a reader are refused. ## Administration and reports - Admin web app on the local network: catalog, taxes, employees and roles, registers, payment methods, printers, receipt layouts, extensions. - Report web app for the numbers, reachable from the local network and, if you choose, from the Internet. - French and English everywhere, with the language of each customer remembered. ## Extensions .NET extensions add steps before and after every sale action, sections in Admin forms and their own pages. The host validates everything an extension writes. Read [the extensions guide](/docs/extensions).