Store, web and ledger on one stock position
Retail carries a problem others do not: the law touches every single receipt, and there are a thousand receipts a day. NG One keeps those flows in one core: one stock position for store and web, costing and price changes as documents that post, a statutory sales ledger that arises from turnover, and the fiscal channel as an integration with its own lifecycle. Since April 2026 the law requires you to know which fiscal receipt belongs to which outgoing document — in NG One that link exists as data, not as after-the-fact matching from a till report.
- POS with statutory sales ledger
- Retail and wholesale costing
- Price change as a document
- One stock for store and web
- Fiscal channel and ESIR
- Fiscal receipt ↔ SEF (April 2026)
What suffocates retail today
All of it follows from one cause: the till, the warehouse, the web and accounting are four systems that meet once a day, at best.
The POS does its thing, the ERP does its own, the ledger catches up later
The till knows turnover, the warehouse knows stock, and the statutory sales ledger is topped up whenever someone gets round to it — usually when we remember an inspection is possible. The daily take is retyped, card turnover is matched by hand only once the statement arrives, and the gap between what the till reported and what the ledger recorded is explained with “it will be sorted at month end”.
Price changes are written by hand and the shelf lags behind
The purchase price moves, a new retail price is needed — and the manual work begins: a calculation in a spreadsheet, a price-change record on paper, a new label printed on another device, and the entry into the system two days later. Meanwhile the old price is charged, the difference flows into a price variance nobody tracks, and stocktaking discovers it six months on.
The web shop and the store fight over the same goods
The site has its own stock synced overnight; the store has its own in real time. The last unit sells twice — once online, once at the till — and someone calls a customer to cancel. The price is different in a third place because the promotion did not reach every channel, and an item bought online but returned to the store has no document that can receive it.
The fiscal receipt and SEF are two separate worlds
Fiscalisation is one chain and the VAT record another, and since April 2026 you must know which fiscal receipt belongs to which outgoing document and how it enters the record. When those are two systems that do not know each other, the link is made by hand — from a till report and from memory — and it is accurate exactly as far as someone had time that month.
Stocktaking closes the store and shortages are posted “somehow”
The count is done on paper, the store closes for a day, and differences are typed into a list that is then reconciled with accounting for a week. A shortage above the allowance is not only a cost but a tax obligation requiring an internal calculation and a record — and that is usually discovered once it has already been posted incorrectly.
How NG One answers
One core where the till, the stock, the ledger and the tax are the same data — and the fiscal channel is a separate adapter, because fiscalisation has its own rhythm of regulatory change and must not impose it on the rest of the system.
POS and retail outlets with the statutory sales ledger
Till, outlet, shift, daily take and payment methods live in the same system as the stock and the ledger — the statutory sales ledger arises from turnover rather than from later transcription. The daily settlement per outlet posts automatically and posts to dimensions: outlet, item group, shift. Card turnover matches against the statement, and a discrepancy shows the same day rather than waiting for month end to appear.
The fiscal channel, ESIR and NG eFiscal
Fiscalisation runs through LPFR and VPFR, and the ESIR layer does what the law asks of it. NG eFiscal is a separate Konis product for the fiscal channel and it stays that way: NG One orchestrates it rather than duplicating it. The split is architectural, not commercial — fiscalisation carries its own certification and its own rhythm of regulatory change, so it stands as an adapter with its own lifecycle and its own monitoring, not as a branch in the same code.
Retail and wholesale costing, price change as a document
A price change is a document in inventory: it changes the price, produces the record, posts the price variance and leaves a trace of who changed it and when. Retail and wholesale costing computes the purchase price with landed costs, margin, VAT and the selling price — so the price on the shelf is a result, not an estimate. Labels and shelf tags print through ZPL from the same reporting layer, at the moment the price becomes effective.
Omnichannel with NG Commerce
NG Commerce is the family's online sales platform and it stays that way — NG One does not replace it but gives it one source of truth: one stock position, one price list, one partner, one document. The last unit does not exist twice, because the reservation is made against the same position the till sees. Exchange rests on the API-first layer with REST and OpenAPI over every resource; the scope of fields and events is defined per project, because the catalogue and the promotion rules differ from retailer to retailer.
Fiscal receipt ↔ SEF
The state joined invoicing, VAT, delivery notes and the invoice registry into one ecosystem. NG One connects those flows in the domain — one graph that knows which fiscal receipt belongs to which outgoing document and how it enters the EEO and EPP records — while keeping them as SEPARATE integration adapters with their own lifecycles. The link is a structural advantage without a dangerous coupling: when one service changes, the whole chain does not fall. Statutory parameters are time-versioned, so a change of rate or form does not require a new version of the system.
Automation on the daily work
Card and bank statement matching by payment reference, amount and partner; automatic rules in the event → condition → action shape; an AI daily brief on My Work that tells the store manager what deviates today. Suggestions arrive as drafts a human confirms, the copilot answers with evidence and a drill-down to the source document, works under your permissions inside your tenant, and everything enters the AI audit trail. The automation KPI measures “what the system did on its own” with a number from your tenant.
The flow retail runs
From goods receipt to VAT record — with the fiscal channel as a separate adapter rather than a branch in the same code.
- Step 1
Receiving and costing
Goods enter the outlet at a cost that already includes every dependent charge. The retail price is the result of a calculation, not an estimate.
- Goods receipt with lot, expiry and UoM conversion
- Landed costs and customs in the cost of imported goods
- Retail and wholesale costing: margin, VAT, selling price
- Price variance as a posting, not as a stocktaking difference
- Step 2
Price, promotion and price change
A price change is a document with its record and its posting — across every channel at once, because there is one price list.
- Price list and promotion with validity dates
- Price change with record and variance posting
- Labels and shelf tags through ZPL printing
- The same price at the till, on the site and on a quotation
- Step 3
Selling in store
The till works against the same stock as the warehouse, and the statutory sales ledger arises from turnover instead of being topped up later.
- POS: shift, daily take, payment methods
- Statutory sales ledger from turnover, not transcription
- Fiscal receipt through LPFR/VPFR and ESIR
- Returns and complaints as documents linked to the receipt
- Step 4
Selling online
The web channel does not get its own copy of stock; it reserves from the same one. Click-and-collect and in-store returns are the same flow, not an exception.
- One stock position, one price list, one partner
- Reservation from a web order against available quantity
- Collection in store and shipping from store
- Bought online, returned in store — one document
- Step 5
Daily settlement
The day closes itself, and what is left for a person is what genuinely needs a decision.
- Daily turnover per outlet and its posting
- Card turnover matched against the statement
- Shift shortage and overage as a record with an explanation
- Automation KPI: what the system did on its own
- Step 6
VAT, stocktaking and the law
A tax obligation arises from a line rather than from a month-end total — including when the line is a fiscal receipt.
- VAT records in the EEO and EPP structure, POPDV and PP PDV
- Fiscal receipt ↔ SEF as data, not as after-the-fact matching
- Outlet stocktaking and posting of differences to dimensions
- Shortage above allowance → internal calculation and record
The spaces that carry this solution
A solution is neither a separate product nor a separate licence. It is the same system seen from one angle, and these business spaces carry most of the work this page describes.
Sales and customers
From opportunity to cash, in one chain with nothing retyped.
30 capabilitiesInventory and logistics
Stock on hand, goods in motion and value on the ledger — one record, reconciled at all times.
30 capabilitiesFinance and compliance
Serbian statutory accounting, dimensions and VAT — in the core, not bolted on.
30 capabilities
Questions about this solution
Scope, boundaries, and the rules this entry point works by.
Does NG One have its own fiscal module or does it use NG eFiscal?
NG eFiscal is a separate Konis product for the fiscal channel and it stays that way — NG One orchestrates it rather than duplicating it. That is not a licensing split but an architectural one: fiscalisation has its own lifecycle, its own certification and its own rhythm of regulatory change. When the adapter is separate, a change to fiscalisation rules touches the adapter and not your posting, your stock and your VAT record. From NG One's point of view it is one channel among channels: SEF has its own, fiscalisation has its own, the bank has its own — each with its own failure behaviour and its own monitoring, instead of one chain that falls as a whole.
What does the fiscal receipt and SEF link from April 2026 mean?
The state has joined invoicing, VAT records, delivery notes and the invoice registry into one ecosystem, so you must know which fiscal receipt belongs to which outgoing document and how it enters the VAT record. NG One solves that at two levels, and we consider the distinction a structural advantage: in the domain the flows are connected — one graph where the link exists as data rather than as later matching from a till report — while at the integration level they are SEPARATE adapters with their own lifecycles. When one service changes or fails, the whole chain does not fall. The EEO and EPP records, POPDV and PP PDV arise from the same lines that produce the fiscal receipt, so reconciliation is a consequence of posting rather than a month-end job.
How is the statutory sales ledger kept, and what about price changes?
The statutory sales ledger arises from turnover inside the same system that holds the stock, rather than by transcribing a till report — that is the point of POS and ERP not being two products. A price change is a document in the inventory and logistics space: it changes the price, produces the record, posts the price variance and leaves a trace of who changed it and when. Retail and wholesale costing sits in the retail module — a price change is a goods document and belongs to inventory, while retail price costing is retail's job. That split is not a formality: it is the reason a price change no longer means opening a spreadsheet, printing a label on a third device and remembering to key it in on Monday.
We run a web shop on NG Commerce. How does it connect?
NG Commerce remains the online sales platform — NG One does not replace it but gives it one source of truth. The point is not synchronisation but unity: one stock position that both the till and the site reserve against, one price list with validity dates, one partner and one document. The last unit therefore does not exist twice, because there are not two positions to reconcile. Exchange rests on the API-first layer with REST and OpenAPI over every resource, plus an MCP layer for agents. The exact scope of fields and events is defined per project — catalogue, channels and promotion rules differ from retailer to retailer, and that is work for analysis, not for assumption.
How does stocktaking work and what about shortages above the allowance?
Stocktaking is a document in the inventory and logistics space, captured on a handheld rather than on paper, with differences posted to dimensions — so you know which outlet, which item group and which shift carry the deviation. A shortage above the permitted allowance is not only a cost but a tax obligation requiring an internal calculation and an entry in the records; that is an item we keep explicitly on the list of easily-missed obligations, because it is the most common place to go wrong quietly. So in NG One it is a posting with a document behind it, not a manual stock correction nobody can explain six months later.
What does early enrolment bring for a retail chain?
Enrolling by 1 September 2026 carries a 40% discount on the price of the solution, against a 10% reservation advance — the only amount paid at enrolment. The price is not read off a list but established by analysis: we walk your outlets, your till flow, the way you run price changes and costing, the relationship between store and web, and the systems NG One exchanges data with, until the scope is written down. For retail the benefit is concrete: the configuration — dimensions, price lists, document types, permissions — is set around your business, instead of your business being bent into someone else's template later.
Related solutions
Test NG One against your own outlet and your own web channel
Book a working review for retail. We walk your flow from costing to fiscal receipt — price changes, the statutory sales ledger, stocktaking, daily settlement and the link to online sales — on your items, your prices and your outlets.