The pallet, the movement and the charge in one system

A real WMS in the core. Inventory operations are complete without any add-on — receiving, put-away, internal transfers, reservations, picking, packing, dispatch, returns, stocktaking and handheld tasks all run on standard warehouse documents. Above them an optimisation layer switches on per warehouse: bin locations and zones with capacities, directed put-away and optimised picking paths, wave and batch picking, replenishment, cross-docking, cycle counting and SSCC packing. Because that layer is configuration per warehouse rather than a second system, a large distribution centre gains it while a small site stays simple, and in neither direction is there a data migration.

Consignment is a first-class part of the stock position: each pallet is recorded with its owner, held and moved on their behalf, and separated from your own stock. Movements — receipt, put-away, transfer, pick, dispatch, return — carry the owner, so at any moment you can say how much of whose goods sits where. That ownership record is also what makes the reconciliation with a client honest: the balance you report to the goods owner comes from the same movements the warehouse ran, not from a separate tally kept for their benefit.

From the movements themselves. Every receipt, day held, pick, return and special handling is already a record, so the basis for a service invoice exists without reassembling it in a spreadsheet. You define service items — storage per pallet-day, handling per movement, value-added work — and a versioned contract or price list per client with valid-from and valid-to dates, and the invoice is produced from the measured events over the period. The line records which rate produced which charge, so when a client disputes a figure the answer is the movements behind it, not a spreadsheet only one person understands. What NG One does not do is invent a rate you did not agree — the billing is only as good as the contract you configured, and that is the honest boundary.

Yes. Lot, serial number and expiry belong to the stock movement line, together with FEFO issuing and unit-of-measure conversions across pallet, case and unit. Traceability runs both ways: from a batch you get every order and owner that received it; from a complaint you reach the goods receipt and the supplier. When a client issues a recall, the affected pallets and shipments are a query answered in minutes — a difference measured in hours on the day it happens, and the reason FEFO is enforced as a rule rather than left to the discipline of whoever is on shift.

The delivery note arises from the dispatch that already exists in the inventory flow, carrying carrier, vehicle and receipt confirmation, with a distinct flow for excise goods; the Serbian e-delivery note goes to SEF from that same document rather than as a separate task. The data a transport document needs — consignor, consignee, goods, vehicle — is populated from the shipment rather than typed a second time, so the paper that leaves with the truck matches the goods it describes. On the import side, customs and forwarding charges enter the cost through landed costs and the customs declaration. We are honest about the edge: NG One drives these from the goods flow, and where a specific international form is required it is fed from that data rather than kept in a separate file.

The SEF channel sends and receives invoices in UBL 2.1 and tracks their status; the e-delivery note via SEF is derived from the dispatch that already exists in the inventory flow, with carrier, vehicle and receipt confirmation and a distinct flow for excise goods. VAT records are populated in the EEO and EPP structure from posted documents, and the POPDV and PP PDV XML come out of those same records; the goods ledger (KEP) is kept from stock movements. If you run a retail counter alongside the warehouse, e-fiscalisation through an ESIR with an LPFR or VPFR is there, and public-sector invoices go through the CRF. Underneath all of it is the decision that cannot be added later: every rate, threshold and mapping is a record with a validity period, so correcting a March document in December follows March's rules.