"The freezer near the bakery" may work in conversation but fails in a service history. A supermarket can have several similar glass-door cabinets, multiple island modules, open chillers, and service counters. Product names alone also create risk: a deli showcase may be straight glass or curved glass, and a glass-door upright cabinet is not an open multideck.
A stable asset code connects the physical cabinet with the correct drawing, model, installation type, service record, and spare-part request.
Separate Stable Identity From Changing Information
Design the asset code from fields that rarely change, such as site, store zone, equipment category, structure, and sequence. Keep model, serial number, status, and service contractor in the asset register, where they can be updated without renaming every historical record.
For example, a code may represent Site 01, Frozen Zone, Island Freezer, Combined Sliding-Lid Structure, Position 03. The project team chooses abbreviations and publishes a key.
Avoid embedding a supplier name or current store department if either may change while the physical asset remains.
Preserve Product Category and Structure
XCCOLD projects can include multideck open chillers, glass-door upright chillers or freezers, commercial island freezers, fresh-meat showcase counters, and deli food showcase counters. Asset records should distinguish both category and visible structure.
| Category | Structure Field Example | Application Field Example |
|---|---|---|
| Deli showcase counter | Straight glass or curved glass | Deli or prepared food |
| Fresh meat showcase | Straight glass service counter | Fresh meat |
| Island freezer | Sliding glass lid; combined island | Frozen food |
| Multideck chiller | Open type; upright wall case | Chilled packaged goods |
| Upright chiller | Glass-door type; door count | Beverage or chilled products |
These are record fields, not permission to substitute images or parts across structures.
Build a Location Hierarchy
Use site, floor where relevant, store zone, aisle or wall, run, and position. Draw the viewing direction so left-to-right numbering remains consistent.
Avoid codes based on "front" or "back" without a plan reference. Store staff, installers, and service technicians may face the run from different sides.
Put asset IDs on the equipment schedule and marked floor plan in the supermarket refrigeration project checklist.
Handle Multi-Module Runs
A long island freezer or open-chiller line may include several modules. Give the overall run a parent code and each module a child code. Record end sections and joining positions.
Service records can then state whether an issue belongs to the whole run, module B, a specific door, or one joint. Door positions should use a defined direction.
Keep the manufacturer's model and serial number at module level where applicable. Never create serial values from the project asset code.
Link Manufacturer Data Without Replacing It
The asset register should store product title, category, structure, application, installation type, model, serial, supplier order, production or delivery reference, and commissioning record where available.
The internal asset code helps the store locate equipment. Manufacturer model and serial data support technical identification. Both are needed.
Photograph labels in place and transcribe carefully. Where a field is unreadable, mark it for follow-up rather than guessing.
Place Physical Labels Thoughtfully
Choose a visible, durable location that does not cover manufacturer labels, controls, ventilation, service panels, glass, cleaning areas, or customer product information. Confirm label material and adhesive compatibility with the equipment finish.
Place a secondary label at the service side when the customer-facing label would be intrusive. The asset register can record label position.
Avoid putting structure or application text on a cabinet until the project confirms it. A mislabeled fresh-meat counter can create downstream service confusion.
Use QR Codes as Links, Not Identity
A QR code can open the asset record, manuals, or service form, but printed human-readable identity should remain. Codes can fail because of damage, access permissions, network availability, or changed URLs.
Control the destination and user permissions. Avoid exposing confidential project documents through a public link.
Test every code after printing and during handover.
Connect Service and Cleaning Records
Every service request should include asset code, model, serial, exact location, structure, symptom, time, and photographs. The service access planning article shows why location and access need to travel together.
Cleaning and inspection logs can use the same asset code. This prevents a report for one case from being filed under a similar neighbor.
Where one event affects a run, list all child codes rather than using only the parent.
Control Moves and Store Remodels
When a cabinet moves, preserve the asset identity and add a location-history entry. Update floor plans, label position, utilities, installation type, and service access records.
If the move changes the equipment's application, ask the responsible technical and food-safety teams to review suitability. A location change alone does not prove a cabinet can serve a new product category.
Record old and new fixed references and the date of change.
Manage Replacements
A replacement cabinet should receive a new asset identity or a clearly controlled successor relationship, depending on the organization's policy. Avoid overwriting old model and serial data in a way that makes historical service appear to belong to the new unit.
Link the retired asset, replacement asset, removal date, installation date, and migrated documents. Preserve open warranty or claim files separately.
Temporary rental or loan equipment also needs a temporary code and return status.
Govern the Code List
Assign ownership for creating codes, preventing duplicates, correcting labels, and archiving retired assets. Publish abbreviation definitions and reserve codes before labels are printed.
Audit the physical equipment against the register at project handover and after major remodels. Record missing labels and unregistered cabinets.
The code system should remain simple enough for store staff to read during a phone call.
Related Reading
- Supermarket Refrigeration Project Checklist provides the project intake fields around the asset register.
- Commercial Refrigeration Service Access links equipment identity with technician access.
Common Questions
Can the serial number serve as the store asset code?
Serial numbers identify manufacturer units but may be hard to read and cannot express store location. Preserve both fields.
What happens when a cabinet moves?
Keep the identity, update location history, and revise drawings and site records.
Should each door have its own code?
Use a parent cabinet or module code plus defined door positions when door-level service records matter.
Can similar deli counters share one category code?
They can share a category field, while the structure field keeps curved and straight glass distinct.
Share the Asset Schedule
Use the XCCOLD contact page to share the site zones, real product categories, structure tags, installation types, module layout, and service-record needs. A clean asset schedule helps project, store, and service teams refer to the same cabinet.