Sales, stock, purchasing, VAT returns and e-invoicing in one program running on the office computer. It works without the internet, and the data stays with you — encrypted, on your own disk.
Stanio is desktop software. Download it on a laptop or on the office computer.
The demo is an ordinary program: install it, run it, log in with anything. No account, and nothing to tell us.
This is not a website. The whole database sits on the computer in the shop, so an internet outage does not stop selling. A second till syncs over the local network, and a branch across town through our relay once the link is back.
The database is one file on your disk, encrypted whole. A stolen laptop gives up nothing: without the key the file does not even look like a database. You can carry a backup out on a USB stick and restore it on a new machine.
Eight modules to choose from. A builders’ merchant needs stock and sales; a workshop with a rental counter needs the rental module. Your installer does not contain the code of modules you have not bought, and adding one later is an update, not a fresh deployment.
Eight modules read like a table of contents. Here is how it looks from behind the counter — from seven in the morning until closing time.
6:50
You switch the computer on and the program opens on yesterday’s figures — and says, right at the top, what is waiting today: two invoices past their due date, cement below its threshold, the van’s policy expiring on Thursday. Nothing is pulled from a cloud and nobody asks for an account: the database spent the night on that disk.
7:20
A customer off the street, a receipt, done. The till does not make you open a record for someone who came by once, and does not ask for invoice details nobody needs.
9:05
You scan the barcodes straight into the goods-in document. Stock goes up, the purchase price lands on the product record, and what you owe the supplier is booked along the way.
10:15
You tap your card and the screen goes dark — together with the price list and the customer records. The unfinished receipt stays open: you come back a quarter of an hour later, tap the card again and carry on in the very same document.
11:30
Someone cut through a cable two streets away. Selling carries on, because it was never a website — and the till out on the yard keeps talking to the one at the counter over the local network.
13:10
You add items from the files, apply a discount and print a quote with an expiry date. When the customer comes back a week later, the same list turns into an order with one click — no retyping forty lines.
15:40
The delivery note from the reservation turns into an invoice in one move. The customer record shows straight away how much is still owed, and for how many days.
18:00
A daily report by product and by customer, a backup onto a memory stick, and you close up. This month’s JPK return will be built from what you have just done.
Each module does one thing and talks to the rest. A sales invoice takes goods off the shelf, a supplier invoice puts them back, and accounting sees both.
A till for walk-in customers and invoices for companies, in one place.
Quantity and value kept current, not worked out once a quarter.
The other half of the picture: supplier invoices and payables.
File JPK_V7 from the program, or hand a CSV package to your accountant.
Invoices in the FA(3) structure and a sending queue with states.
Due dates, refuelling and consumption — without a separate spreadsheet.
Equipment by the hour and by the day, with a calendar and handover notes.
Clock in and out with the same card that unlocks the till.
The demo is the same program a customer gets, with a sample builders’ merchant inside. Log in with any username and password, issue an invoice and watch the stock go down. Nothing is written to disk: closing the program erases everything you did in it.
Stanio is desktop software. Download it on a laptop or on the office computer.
Rather not install anything? The same demo runs in your browser. https://demo.stanio.pl
No matter which modules you buy. Product records are used by both stock and sales, and a backup has nothing to do with the scope of your licence.
One product card for the whole program: net and gross price, unit, minimum stock, barcode. A customer’s tax number is checked against its control digit as you type, because otherwise the mistake surfaces at e-invoicing — a month after the sale.
Two thousand items load from a CSV file, not by hand. A preview first — what the program understood and which rows were rejected — then the save. Customer lists come in the same way, and everything can be exported back out the same way.
Everyone works under their own account: the cashier with a PIN, the manager with a password. Permissions are granted directly or through groups, with values attached — a maximum discount, a credit-note limit.
A backup on start, on shutdown and on demand. A package carried out on a USB stick comes back even on a new computer: it carries the key wrapped in the recovery code, so after a disk failure the program becomes the same installation it was before.
Two tills in one shop find each other on the local network and exchange changes in the background. A branch outside that network goes through our relay. Every till holds the full data set, so every one keeps working when the line drops.
Counter and weighbridge scales with their drivers, a scanner caught on every screen, a weighbridge ticket built from two weighings. The scale puts the mass straight into a receipt line, the display shows the customer the same price the cashier sees, and the drawer opens when a sale is paid in cash. A shelf label with name, price and barcode prints straight from the product card.
An MT940 file from online banking goes in as a whole: customer payments are matched to invoices, your own transfers to supplier invoices. Nothing is posted on its own — only payments where the customer wrote the invoice number are ticked in advance, and an unrecognised entry is never guessed at.
The dashboard collects what the modules report: invoices past their due date, orders due today, stock below its threshold, a policy expiring next week, an employee’s day left without a clock-out. Each of those normally sits on a different screen, waiting for someone to look. A matter disappears when its cause does — you cannot dismiss one, because a dismissed matter is exactly the one that gets forgotten.
One tap of a card instead of a login and a PIN; the next tap covers the screen when you step away from the counter — and it does not log you out, so an open receipt waits for your return. Everyone assigns their own cards, and a lost one is withdrawn with a single click. The program never stores the card number: the database holds only its fingerprint.
Yes. The whole database sits on the computer in the shop, so selling, stock and printing an invoice all work with the line down. The internet is needed to activate the licence, to send e-invoices and to sync with a branch elsewhere.
Yes. Every till holds the full data set and works on its own, and changes are exchanged in the background over the local network — the tills find each other without anyone configuring addresses. A branch outside that network connects through our relay. The number of workstations is part of the licence.
No. Product records load from a CSV file, which is what you already keep in a spreadsheet. You see a preview first — what the program understood and which rows were rejected — and only then save. Customer lists load the same way, and the next import corrects existing cards instead of creating duplicates.
Yes, if you file them yourself: the JPK_V7M and JPK_V7K declaration together with the ledger, GTU markings and quarterly settlement. If you use an accountant, you can send them a CSV package with documents and the VAT ledger instead.
Invoices are produced in the FA(3) structure the Polish e-invoicing system requires. The sending queue is visible on every till, the KSeF number and confirmation are stored with the document, and the certificate is set up on a screen of its own. How it works out for your firm is best walked through when we quote.
On your disk, in one encrypted file. We have no access to it and we do not keep a copy. Only the licence passes through our servers and — if you have branches — an encrypted envelope of changes that we cannot open.
It depends on the number of workstations and the modules you choose, so we quote after a short conversation rather than guess. Tell us what you sell and how many computers you work on, and we will reply with a price.
Two sentences are enough: what you sell and how many workstations you need. We will reply with a price and a timeline — no half-hour forms.
Write to us