Item file setup
The item file is the system
Every number a POS produces comes from the item file: what rings at the till, what reports say, what a count compares against. Building it properly is the least glamorous part of an implementation and the one that decides whether the rest works.
Built or cleaned before go-live, never during it.
What is involved in setting up a POS item file?
Deciding the structure, then filling it. Departments and categories decide what every report can ever tell you, so they are chosen first and deliberately. After that it is descriptions that read well on a receipt, barcodes that scan, pricing, cost where it is known, and the flags that drive behavior at the register — age restrictions, weighed items, and other item-level controls.
Structure is the part worth slowing down for. Pricing can be corrected in an afternoon; a department scheme that nobody can report against is lived with for years.
- Structure before contentDepartments decide what every future report can say.
- Descriptions are customer-facingThey print on the receipt and show on the screen.
- Flags drive register behaviorAge restrictions and weighed items are item-file settings.
- Cost is what makes margin reporting realWithout it you get sales reporting and nothing else.
We cannot invent data the store does not have. Where cost or barcodes are missing, the file is built without them and the reporting that depends on them is limited until they exist — which is worth knowing in advance rather than discovering in a report.
What a file is made of
The decisions, in the order they matter
The first two are structural. The rest are filling in.
Departments and categories
ReportingThe reporting structure. Chosen first because everything else inherits it.
Item-level flags
Age-restricted itemsAge restriction, weighed items, anything that changes what the register does.
Barcodes and labels
Label printingEverything that reaches a lane has to scan, and what does not needs a label.
Cost and suppliers
Purchase ordersWhat makes margin reporting and receiving work rather than just sales totals.
By trade
How the item file differs by trade
The decisions are the same everywhere. Which ones carry the most weight depends on what the store sells.
Grocery
Grocery POSDepartments that match how fresh is managed and reported, weighed items flagged, and prices that change often enough that batch changes and labels matter.
Convenience
Convenience POSA long file of fast movers where barcodes and descriptions have to be right at speed, and every age-restricted product configured with the required item-level restrictions.
Liquor
Liquor POSMany similar products that differ by size or supplier, so descriptions have to tell them apart, cost is kept per item for margin per line, and age-restricted products are flagged.
Specialty retail
Specialty retail POSSlower-moving lines where categories and suppliers decide what reporting can say, and descriptions that let staff find one item among many similar ones.
What a bad item file costs
-
Departments were never really decided
Reporting can never answer the question being asked of it.
Structure is agreed before the file is filled.
Reporting -
Descriptions were typed for whoever typed them
Receipts and screens read badly, and staff cannot find items.
Descriptions are written to be read at a till.
-
No cost field in the file
Margin reporting is impossible and nobody notices until it is asked for.
Cost is captured where it exists, and its absence is stated where it does not.
-
Items arrive without barcodes
Every one is a manual lookup at the lane.
Labeling is part of setup rather than a later discovery.
Barcode scanning and labels
Item file questions
Can you build the file from my supplier lists?
Often yes, where the lists carry enough. What they do not carry has to come from somewhere, and we say which is which rather than filling gaps invisibly.
How long does it take?
It depends on how many lines there are and how good the starting data is. That is why we look at what exists before quoting rather than after.
Can I change departments later?
You can, but historic reporting does not move with it, which is why the structure is worth deciding properly at the start.
What if I do not have cost data?
The file is built without it and margin reporting waits. That is a real limitation and you should hear it now rather than from a report later.
Tell us what the file looks like today
How many lines, where they live, and whether cost and barcodes are in there. That is enough to scope the setup.