Modules

A licence covers three things at once: the type (subscription or perpetual), the number of workstations and the modules. Modules are chosen to match what the company actually does — and adding one later is a program update, not a fresh deployment.

Sales

A till for walk-in customers and invoices for companies, in one place.

A merchant sells two ways at once: cash over the counter, and on credit to a company collecting on Thursday. The module handles both without making anyone choose at the start of the day.

Till: receipts, line discounts, parking a sale and coming back to it, returns
A quote with an expiry date, and once the customer agrees — an order from the same list
Invoices, delivery notes and credit notes; a delivery note becomes an invoice in one move
Customer orders with stock reserved and released in instalments
Receivables: who owes what and for how long, with payments, balances and reminders
Period reports: by product, by customer, by day, plus the VAT ledger

Stock

Quantity and value kept current, not worked out once a quarter.

Stock levels sit beside the history rather than replacing it: every movement is recorded, and the current quantity and value are ready to read. With ten million movements the stock valuation report takes three milliseconds instead of eleven seconds.

Goods received with purchase price and supplier, issues, adjustments
Shortages: what fell below its threshold and by how much
Stock value, and purchase price carried onto the product card
Stocktake: a sheet to print, a count, and closing adjustments
Scanning a barcode opens a goods-received note with the product already on it

Purchasing

The other half of the picture: supplier invoices and payables.

Without purchasing there is neither a real cost price nor complete VAT. A supplier invoice puts goods into stock through an event — the stock module does not even need to know purchasing exists.

Supplier invoices with net prices and goods received into stock
Purchase credit notes with goods returned to the supplier
Purchase orders with delivery in instalments
Payables and payments — how much you owe and to whom
Fixed-asset purchases marked the way the VAT return requires

Accounting

File JPK_V7 from the program, or hand a CSV package to your accountant.

Two routes, because customers split into two groups: some file themselves, others send everything to an accounting office. The program supports both and does not make you choose once and for all.

JPK_V7M and JPK_V7K with the ledger, quarterly settlement and carried-forward surplus
GTU and related-party markings and fixed-asset boxes taken from the records
Period summary by VAT rate from both the sales and purchase ledgers
CSV package for the accountant: documents, VAT ledger and line items
A submission log visible on every till — so everyone knows what has already gone

KSeF

Invoices in the FA(3) structure and a sending queue with states.

Poland’s National e-Invoicing System is becoming mandatory, so an invoice has to be able to leave in its format. The module builds FA(3) from sales documents, keeps the queue and records the KSeF number along with the confirmation.

Invoice in the FA(3) structure, with boxes chosen by VAT rate code
Exempt sales with the legal basis in the annotations
A sending queue visible on every till — you see what is waiting, and where
KSeF number and confirmation stored with the document
Certificate settings on a screen of their own

Fleet

Due dates, refuelling and consumption — without a separate spreadsheet.

A merchant with two tippers and a crane truck either tracks inspections in a calendar or does not track them at all. Fleet is its own module because it belongs to the company, not to rental or to sales.

Vehicle records with insurance and inspection due dates
Refuelling with consumption worked out from the odometer
Costs assigned to a vehicle
Odometer raised by an event — including from another module

Rental

Equipment by the hour and by the day, with a calendar and handover notes.

A plate compactor, scaffolding, a table saw — equipment hired by the day is a different kind of money from goods sold. It still settles as an invoice, because rental asks the sales module for one.

Equipment records with hourly and daily rates
Bookings that cannot overlap
Handovers and returns with a note to print
An availability calendar — you can see what is free and when
Settlement by invoice through the sales module

Working time

Clock in and out with the same card that unlocks the till.

Time and attendance with no separate reader at the door and no separate subscription: the card a cashier locks the workstation with records their day as well. The program invents no hours — a day with no clock-out stays open and waits to be corrected, because these numbers turn into wages.

Arrival is recorded by itself when you enter the program with a card
A board of who is in today, including those who have already left
A break mid-day is a second stretch, not a day started afresh
A correction keeps its reason and the hour from before it
A monthly summary and a CSV package for the payroll office

In every edition, whatever the modules

These belong to the program itself. Product records are used by both stock and sales; two tills have to agree with each other even when the customer bought one module.

Product and customer records

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.

Loading a price list from a spreadsheet

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.

Accounts and permissions

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.

Backups

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.

Data exchange between tills

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.

Workstation hardware

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.

Bank statements instead of retyping

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.

What needs attention today

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.

Contactless card and workstation lock

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.