Agree acceptance checks, sampling, evidence for reported problems, and handling scope during purchasing. Counting boxes does not replace checks of printing, closures, and device reading. This article covers consumable procurement records; the project team defines its own use workflow.

Collect final approved records before counting

Prepare the order, specifications, artwork or print template, sample records, and packing list. Check versions and approval scope to avoid using an early enquiry image or an outdated file. Resolve unconfirmed parameters during order approval rather than inferring them after delivery.

For customized bands, check ticket wording, number ranges, and group quantities. For RFID, prepare encoding rules and data files. For writable or printable bands, record writing tools, printers, and reading methods.

Separate appearance checks from operating checks

Check products, selection references, versions, group codes, and quantities against the packing list, and verify agreed batch marks. Compare dimensions, print orientation, missing characters, color variation, and closures with the approved sample. Photograph unusual packaging and record box or pack numbers.

Sample printing, scanning, or chip reading as agreed, using the same equipment and settings as the sample stage. Retain original passed and failed results. One readable band does not establish that the entire batch conforms; define sampling scope and criteria in the order.

Make problem reports traceable to a batch

Report material and construction versions, batch, quantity, equipment, and reproduction conditions with de-identified photos or read/write records. Describe print, device-setting, and data-file issues separately to help identify responsibility. Continued use, returns, or retests follow the purchase agreement and the using organization’s procedures.

Avoid reporting only “cannot read.” Explain whether reading failed, returned data differed, or the system displayed the wrong identity, and retain the sample-to-file comparison. Record the resolution and update affected documents once the issue is closed.

Check changes before reusing reorder records

Specify materials, colors, sizes, templates, and encoding rules to retain, alongside new quantities, packaging, and arrival requirements. Confirm whether the prior version is being continued. Reassess affected items when materials, construction, chips, devices, or systems change. Record actual use, spare stock, and voided quantities to plan the next order; confirm storage conditions and periods against the specific instructions.

  • Batch file: approved documents, lists, and sampling results.
  • Exception file: reproduction conditions, resolution, and updated documents.
  • Reorder list: retained requirements, changes, and delivery needs.