orderbird POS

How a sale is rung up and what it runs on: a fast till on tablet, phone or dedicated terminal, articles, modifiers and discounts, split bills and tips, receipts printed or sent digitally (QR code, email, a digital Bon), returns and cancellations, a customer display, which hardware is supported or sold (receipt printers, cash drawers, scanners, scales), and whether the till keeps selling when the internet is down.

0 — Not a till; sales cannot be rung up or receipts issued in the product.

3 — Sales rung up on one device with a printed receipt; digital receipts, supported hardware and offline operation are basic or not described.

5 — A till app on named devices (iPad, Android or Windows) with articles, modifiers, discounts and split payments, receipts printed or sent digitally, returns and cancellations, a list of supported printers, drawers and scanners, and an offline mode stated.

8 — Several device types and own or third-party hardware with a published compatibility list, offline mode with its limits stated (how long, which payments, how sync resolves), digital receipts meeting the receipt obligation, customer display, scales and barcode labels supported, and hardware rentable or bought with the terms stated.

10 — A till that never stops a sale: offline operation documented including card payments and fiscal signing, hardware open to standard devices rather than locked to the vendor, receipt layouts that meet the legal minimum content in each named country, and a stated uptime or a status page with incident history.

How the till takes card and mobile payments and what that costs: an integrated terminal and the acquirer behind it named, girocard, credit cards, Apple Pay and Google Pay, tap to pay on a phone, the fee per transaction by card type, monthly terminal fees, payout timing, and whether the merchant may use a terminal or acquirer of their own choice instead. A "free" till paid for by card fees counts here.

0 — No card payment of any kind can be recorded at the till.

3 — Card payments recorded at the till, by an integrated terminal or by typing the amount into a separate one; the acquirer, the fees and the choice of terminal are basic or not described.

5 — An integrated card terminal with the payment provider named, girocard, credit cards and mobile wallets accepted, the transaction fee published for the main card types, payouts with their timing stated, and the amount passed to the terminal without retyping.

8 — Fees per card type and terminal cost published, tap to pay on a phone, tips and split payments on the terminal, several integrated acquirers or terminals to choose from (not only the vendor's own), the regulated payment institution named, and card payments reconciled to the daily closing.

10 — Payments without lock-in: the till works with any of several named acquirers on equal terms, fees for every card type, currency and chargeback published, the merchant's contract with the acquirer separable from the POS licence, and a change of acquirer documented without changing the till.

Whether the till survives a cash audit: for Germany a certified technical security device (TSE) with its provider and BSI certificate named, hardware or cloud, the DSFinV-K export for the Kassennachschau and the tax audit, the receipt obligation (Belegausgabepflicht), the Kassenbuch and daily closing (Z-Bericht), GoBD-compliant storage for ten years, and help with the § 146a AO registration; for Austria the RKSV signature and FinanzOnline registration; for other countries their named fiscal rules (NF525, Fiskaltrust and similar).

0 — No fiscal function at all; the product is not a cash register in the legal sense, or states that it does not meet the fiscal rules of the markets it sells into.

3 — The till is called compliant ("finanzamtkonform", "KassenSichV-ready") without naming the TSE, the export formats or the closing; the details are basic or not described.

5 — A TSE included or offered with its provider named (hardware or cloud), the DSFinV-K export available, receipts carrying the TSE signature, a daily closing and cash book, and the receipt obligation met on paper or digitally.

8 — TSE provider and BSI certification named with what happens when the TSE fails, DSFinV-K and the GoBD archive for ten years stated, the § 146a AO registration supported, a procedure documentation (Verfahrensdokumentation) template offered, and the fiscal rules of at least one further country (Austrian RKSV or another) named and met.

10 — Audit-proof across markets: fiscal compliance documented per named country with certificates published, the procedure documentation maintained by the vendor, the fiscal journal exportable after the contract ends, and the vendor's handling of a Kassennachschau (what the auditor gets, from whom, how fast) described.

What the till runs beside the sale: stock and articles with variants, suppliers and purchase orders, recipes or ingredients for hospitality, tables, courses and a kitchen display or kitchen printer, self-order and QR ordering, staff logins with roles and rights, cash differences per employee, reports by product, staff and hour, and several branches or sites managed from one back office.

0 — No articles, stock, staff or reporting beyond the single sale.

3 — An article list and a sales report; stock, staff rights, tables and several locations are basic or not described.

5 — Article and stock management with variants or modifiers, staff logins with roles, reports by product, employee and period, and for hospitality tables and kitchen printing or a kitchen display; several locations or tills under one account.

8 — Stock with suppliers, purchase orders and inventory counts or recipes, a kitchen display and QR or self-order, granular staff rights and a log of cancellations and voids per employee, central articles and prices pushed to several branches, and cross-site reporting.

10 — Multi-site operations run through the product: stock transfers between branches, central menu and price management with local overrides, franchise or group structures, forecasting from sales history, and every change to an article, price or void attributed and exportable.

What reaches the books and what leaves with the merchant: an export to DATEV (DATEV format, DATEV Kassenarchiv online, DATEV Unternehmen online) and to named accounting tools, booking with revenue accounts and tax rates, card payouts and fees reconciled, an API and webhooks, integrations with shop, booking or staff tools, and a complete export of articles, customers, sales and fiscal journals when the contract ends.

0 — No export of any kind; the day's figures have to be retyped.

3 — A CSV or PDF report of sales; booking data, named integrations and a full export are basic or not described.

5 — A DATEV export or another named accounting export with revenue accounts and tax rates, several integrations listed, a documented API, and sales and articles exportable.

8 — DATEV Kassenarchiv online or DATEV Unternehmen online named, card payouts and fees booked separately for reconciliation, a public API with webhooks and a developer portal, integrations with named shop, booking and staff-scheduling tools, and a full export of articles, customers and sales stated.

10 — Nothing stays behind: a complete export of all records including the fiscal journal and receipts in documented formats, access to past data after cancellation for the retention period stated, a migration path from and to other named systems, and the API covering every object the back office shows.

Who the contracting entity and the parent company are, where sales, customer and employee data are hosted, and who the subprocessors are (hosting, cloud TSE, payment processing, receipt delivery, email, analytics). Independently sourced by the sovereignty pipeline; POS data is financial and fiscal at once, holds staff logins and customer cards, and has to stay readable for the tax office for ten years, so the whole chain counts, not only the database.

0 — Non-EU vendor and contracting entity, hosting unstated, subprocessors unnamed, and no data processing agreement offered.

3 — A privacy policy and a data processing agreement exist, but hosting location is unstated or non-EU and the subprocessors are not listed.

5 — EU hosting available and an EU contracting entity or EU representative, but parts of the chain (cloud TSE, payment processing, email, analytics, support) run through non-EU providers without a stated safeguard.

8 — EU hosting on named infrastructure, EU contracting entity, TSE provider and payment institution, subprocessors listed with their locations, a data processing agreement published, and security certifications (ISO 27001, SOC 2) stated.

10 — Sovereign end to end and evidenced: European ownership, entity, TSE, payment institution, hosting and every subprocessor, data export and deletion documented, and certifications published with their scope rather than implied.

Whether a buyer can compute the real annual cost from public pages alone: licence per till or per location, which modules (tables, kitchen display, stock, extra tills, DATEV export) cost extra, the TSE and its yearly fee, hardware to buy or rent, card terminal fees and transaction fees, setup and installation, support plans, minimum term and notice period.

0 — No public prices at all; every customer is a sales call or a dealer quote.

3 — A starting price or a free tier exists, but how cost scales with tills, locations, modules or hardware is unclear.

5 — Plans are public with their price per till or location and main inclusions, but at least one commonly needed piece (the TSE, extra tills, hardware, card fees, setup) is unpriced or "on request".

8 — Every plan priced publicly with its scaling rule, the TSE, hardware and add-ons priced, card fees and terminal costs listed, setup and support priced, minimum term and VAT treatment stated.

10 — Complete price computability: annual cost derivable for a given number of tills, locations, modules and card volume, with every add-on, hardware, TSE, setup, support and payment fee and the cancellation and data-return terms published.