INTEGRATION · POS · AS OF NOVEMBER 2026

Analyse OktoPOS with Kiosa: every receipt, every location, one view.

Kiosa reads the receipts from your OktoPOS system every 15 minutes and turns them into revenue per location, day and daypart, plus item, discount and void analyses. Built for restaurants and groups with several locations that want to compare all sites on the same basis.

Kiosa is independent software and not a product of OktoPOS. The connection runs through the OktoPOS API, read-only. Your POS stays as it is.

01 // DATA FROM OKTOPOS

Which data Kiosa takes from OktoPOS.

OktoPOS delivers every receipt individually, with line items, payment methods and cashier. That depth is why Kiosa can analyse OktoPOS data down to the single receipt.

Data typeWhat exactlyWhat it is used for in Kiosa
ReceiptsReceipt number, business day, time and POS terminalDaily revenue, receipt count, average receipt and revenue by daypart per location in One View
Line itemsItem, quantity, price, external referenceItem analysis, best and worst sellers, items bought together in the basket
DiscountsDiscount amount per line itemDiscount rate per location, item and cashier, alert on unusual values
VoidsNegative receipts and negative line itemsVoid overview per location and cashier
CashiersCashier per receiptRevenue and average receipt per employee, discounts per cashier
Payment methodsCash, debit card, credit card, online, voucher, otherPayment method mix per location and day
TaxesTax rates and gross amounts per receiptNet revenue as the default in all analyses
Product groups (optional)From the OktoPOS item report, which you upload once as a CSVAnalysis by food, beverages and product groups; without the report, Kiosa assigns the items itself

Tips, table and guest counts are not available through the OktoPOS interface, so Kiosa does not show these values for OktoPOS.

02 // CADENCE

New every 15 minutes, re-checked every night.

A POS export from the previous day is not enough when you want to know at 2 pm how lunch went. That is why Kiosa reads continuously and re-checks at night.

Every 15 minutes

New receipts since the last run. One View shows the current day per location, and the comparison with plan and prior year updates along with it.

Every night

Kiosa reads the last two days again in full. That way later voids and corrections made at the POS are included in the numbers.

Early in the morning

The daily totals in Kiosa are reconciled with the values from OktoPOS. After that the Morning Briefing is created with whatever stands out from the previous day.

03 // CONNECTION

How the connection works.

You create an API access in OktoPOS and enter it in Kiosa. We take care of mapping, history and verification.

Step 1 · You, in the OktoPOS Manager

Create API access

Under System → API access, create a new access, select the restaurants and choose "BI" as the external reference. Grant permission to read item master data, customer data and receipts.

Step 2 · You, in Kiosa onboarding

Enter the key

Enter the API key and API base URL of your OktoPOS Manager in the "POS access" step. Kiosa stores the key encrypted.

Step 3 · Kiosa

Map POS terminals, load history

We map each POS terminal to its location and, on request, load past periods so that prior year and forecast have a basis.

Step 4 · Together

Cross-check the numbers

You compare one period in Kiosa with your OktoPOS report. If the daily revenues match, the connection keeps running on its cycle.

What you need: access to the OktoPOS Manager with the right to create API accesses. Optionally the OktoPOS item report as a CSV, ideally covering the last twelve months, for a clean product group mapping. How long onboarding takes depends on access and data quality, which is why we do not quote a flat timeline.

04 // USE CASES

Three questions OktoPOS data answers in Kiosa.

Kiosa was created at Mama Trattoria, ten restaurants in Hamburg that use OktoPOS. These questions come up there every week.

Which location falls behind, and when?

The location comparison puts the revenue of all sites side by side per daypart, against plan and prior year. You see whether a location is weak at lunch or in the evening, instead of only knowing a daily total.

In the AI Partner you ask directly: "Which location was furthest below prior year yesterday between 12 and 3 pm?"

Where do discounts and voids get out of hand?

Because OktoPOS delivers discounts per line item and the cashier per receipt, Kiosa calculates the discount rate per location, item and employee. Voids appear as their own overview. If a value moves well away from normal, an alert appears before it becomes a habit.

What does the team upsell?

With real individual receipts, Kiosa analyses the basket: average receipt per location and employee, how often a drink or dessert is added to a main course, which items are bought together. The best-and-worst-seller analysis shows which items carry the menu.

05 // POS + STAFFING

OktoPOS plus staffing system: now you can steer.

Revenue alone does not tell you whether a day was good. Kiosa connects the OktoPOS revenue with the working hours and labor costs from gastromatic, e2n or ordio.

Labor cost ratio per day

Labor costs from the staffing system divided by net revenue from OktoPOS, per location and day, instead of once a month from the monthly financial statement (BWA). How the metric is built is explained in the article Labor cost ratio in restaurants.

Revenue per labor hour

Revenue per daypart against the hours actually clocked shows whether the team is scheduled at the right times, location by location.

Forecast for planning

From the OktoPOS history, Kiosa calculates a revenue forecast per location. If you book the Scheduling module, you plan staffing directly against this forecast.

06 // CONTEXT

What the OktoPOS Manager shows and what Kiosa adds.

In the OktoPOS Manager

OktoPOS comes with its own reports, including operating result and gross profit per location, a margin report and a labor cost analysis, plus exports to Excel and an MCP interface for AI agents (OktoPOS Management).

In Kiosa

Kiosa puts the POS data together with staffing, plan, prior year and, on request, cost of goods in one view, calculates deviations itself and reports them. For analysing POS data beyond a single report, see the guide Restaurant POS data analysis.

07 // FREQUENTLY ASKED QUESTIONS

Frequently asked questions about OktoPOS and Kiosa

No. Kiosa is independent software and does not belong to OktoPOS. Kiosa uses the OktoPOS API with a key that you create yourself in the OktoPOS Manager, and only reads. Besides OktoPOS, Kiosa also connects Hypersoft as a POS and gastromatic, e2n and ordio as staffing systems; the overview is under Integrations.

No. The OktoPOS connector makes read requests only. Items, prices and receipts stay in OktoPOS as they are, and you keep ringing up sales as usual.

New receipts arrive every 15 minutes. Every night Kiosa reads the last two days again so that later corrections and voids are included, and in the early morning it reconciles the daily totals with OktoPOS.

The connection costs nothing extra. It is included in One View: €99 per location per month, net, no setup fee, 12-month minimum term. You book further modules such as Inventory only if you need them; all prices under Pricing.

Yes. After setup, Kiosa loads past periods on request so that the prior-year comparison and revenue forecast have a basis from the start. How far back it goes depends on which receipts exist in your OktoPOS.

Kiosa connects OktoPOS and Hypersoft as POS systems, and both end up in the same analyses. For another POS system, talk to us in the demo call and we will clarify whether and how the data can be connected. We do not make blanket promises.

Connect OktoPOS and see all locations at a glance?

In the demo call we show you One View and the AI Partner with real numbers and walk through connecting your OktoPOS systems step by step.

Book a demo call