Skip to content
capability · catalogue & sync

One list, every machine.

The item list is the quiet centre of a weighing business — names, codes, prices, tares, limits. Advanzio makes it one list, managed once, delivered to every machine that needs it, with delivery you can see.
Today

One catalogue, centrally kept

Items with their codes, prices, units, tares, packing settings, and images, managed in the console — singly, or in bulk from the spreadsheets a business already has. Bulk upload reads the sheet, shows what it understood, lets you fix rows in place, and only then commits: the catalogue never absorbs a silent error. Even item photos arrive in bulk — drop a folder, and images match themselves to items by name.

web console · catalogue
The web console's item catalogue: a grid of items with photos, low and high limits, and tare

Custom fields, without a developer

Every weighing business tracks something the standard columns don’t hold. Advanzio’s catalogue extends by configuration: define a field once and it appears through the forms, the tables, the uploads — and travels to the machine wire, encoded the way the scale expects. New requirement, no software project.

Sync to fleet — with proof of delivery

One action sends the catalogue to every active machine in scope. What makes it different is the reporting: each item on each machine advances saved → committing → synced, and synced means the machine confirmed it — on supported scales, the scale itself acknowledges each line it stored. The console shows the fleet’s delivery state per item and per machine, with retry exactly where it is needed. The platform does not resend what a machine already holds — an unchanged catalogue honestly reports nothing to push.

web console · item detail
An item's detail view in the web console, with its code and per-capability tabs

Codes kept straight

The customer’s own item code rides on every weighment, so records always know what they were; the operator’s PLU stays the quick key it has always been. Two identities, never confused, both preserved.

operator app · items
The operator app's item list, with an expanded card showing the item code

Branch scope

Catalogues and their delivery respect the customer’s structure — a branch sees and receives its own world.

Arriving
  • Catalogue lifecycle operations — replace-and-clear flows so a machine’s stored list can be rebuilt from zero, not only updated forward.
  • Deeper per-machine reporting — the delivery ledger surfaced with more history: what landed when, on which firmware, confirmed how.
Direction
  • The catalogue as the business’s product spine — the same central list feeding surfaces beyond weighing: labels, listings, and the further verticals the platform grows into, so a product is defined once and known everywhere.