Choose RFID inventory equipment around a defined reading task: which tagged items should be detected, inside what physical zone and during which stock operation. Compare the expected item list with observed reads in a controlled trial. Specify how missed, repeated and unexpected reads will be investigated before accepting any automatic stock update.
Which tag technology fits the task?
Begin with the item and the movement. Write down whether the proposed tag identifies a reusable asset, an individual saleable unit or a container. Then describe where it should be read: at a receiving point, within a counting area or during a transfer. Give each proposed task its own acceptance row and owner.
GS1 explains that active RFID tags have a radio transmitter and usually their own power source. Documentation. Ask the equipment supplier to identify the proposed tag type explicitly. Record the exact tag and reader models beside the intended task. Keep the supplier’s stated operating conditions with that proposal so the practical trial can use the same equipment and configuration rather than a loosely similar sample.
Passive RFID tags communicate by backscattering a reader’s radio signal. Documentation. Passive tags can draw operating power directly from the reader. Documentation. Use these documented characteristics to frame questions about your proposed installation. Ask how the reader and tag will be arranged for the actual movement and what needs to be confirmed on site. Request a demonstration using the intended tagged item and its proposed tag position.
Battery-assisted passive tags still communicate through backscatter even when a battery supports their circuitry or sensors. Documentation. Do not use “battery-powered” as the only technology description in the equipment schedule. Ask whether the proposed tag transmits actively or uses backscatter, and what the battery does in that particular model. Give the person maintaining the equipment a clear model-specific reference and a written responsibility for checking its condition.
Keep the business identity separate from the physical tag choice in your worksheet. Record the stock or asset reference, the intended tag identifier and the person approving that association. Include a replacement-tag exercise so the team has to explain how the record will remain understandable when the physical label changes.
How will you define the read zone?
GS1 identifies operating frequency as one factor affecting passive-tag read range. Documentation. Rather than adopting a headline distance as an acceptance threshold, draw the proposed zone and name the task being performed inside it. Mark where an item should be detected and where a nearby item should remain outside the task. Record the reader configuration used for each trial.
The reader’s antenna characteristics help determine the volume in which tags can be read. Documentation. Ask the installer to show the proposed antenna location and direction on your drawing. Include adjacent storage and the route taken by staff carrying goods. During the trial, keep a written expected list so you can compare the intended population with the reads returned at each arrangement.
GS1 also identifies electromagnetic wave polarisation and tag orientation as factors affecting that read volume. Documentation. Include more than one orientation in the proposed trial. Turn the same tagged item as it would be handled during the real movement, then record the observations against the configuration used. Ask the installer which adjustments they propose and repeat the affected test after any change. Keep earlier results available for comparison.
Set the business boundary as carefully as the physical boundary. A receiving exercise should identify the receipt or delivery reference, the expected items and the person deciding when the exercise is complete. A stock-count exercise should identify the location and the point at which the expected list was prepared. These are acceptance requirements to agree with your team.
Include an adjacent item deliberately outside the intended movement. Ask the operator to show how they identify and investigate an unexpected read before proposing a stock change. Record the disposition separately from the raw observation so the reviewer can see what was detected and what the business decided to do about it.
Decide what belongs on the tag
GS1 says tag storage capacity depends on the chip, application and type of tag. Documentation. Start your data brief with the fields required by the reading task. Ask the supplier to explain which values are encoded on the proposed tag and which are retrieved from the associated system. Keep an example decoded identifier with the relevant catalogue or asset record for the demonstration.
GS1 describes simple licence-plate tags carrying a 96-bit or 128-bit unique identifier. Documentation. A proposed identifier-led design should therefore include a clear record lookup exercise. Ask a colleague to trace the sample tag value to the intended item and explain what happens when the value has no recognised record. Write down who can create or change an association and how that decision will be checked.
GS1 describes serialised identifiers as usually stored in the EPC memory bank. Documentation. Ask the supplier to identify the memory area and encoding used for the proposed identifier. Preserve that answer with the model and configuration notes. If additional data is proposed, require a reason for each field and an example showing how the intended application will read and interpret it.
Keep descriptive information in a form the operations team can inspect during acceptance. For each sample, put the business reference, decoded tag value and expected location on the same sheet. Have someone who did not prepare the labels trace the association. Any uncertainty about whether a tag represents a unit or a container should be resolved before the stock movement exercise.
An exception reconciliation worksheet
Use this original worksheet as a proposed test protocol. Enter the expected population first. For every run, record the equipment configuration, the physical arrangement and the observed identifiers. Leave the outcome open until the responsible person has explained any difference and repeated the affected scenario.
| Proposed scenario | Expected population | Difference to investigate | Acceptance evidence |
|---|---|---|---|
| Receiving-zone pass | Items on one selected receipt | Expected tag missing | Receipt reference, read list and investigation |
| Repeat pass | Same selected items | Same identifier observed again | Observation list and proposed duplicate handling |
| Adjacent stock present | Selected receipt only | Identifier outside the receipt | Zone drawing and disposition |
| Item orientation changed | Same business reference | Detection differs by arrangement | Position and reader configuration |
| Replacement tag fitted | One authorised item association | Old and new identifiers overlap | Replacement decision and record check |
For a hypothetical equipment store, prepare a trial involving a small set of tagged tools moving from receiving to an allocated shelf. Keep one additional tagged tool beside the route but outside the selected transfer. Ask the operator to reconcile the expected list, the observed list and the proposed stock movement without treating every observation as an authorised transfer.
Run the exercise again with one expected tool held back. The person reconciling should explain the discrepancy and choose the next investigation step from the written procedure. Then repeat the same selected movement to assess the proposed handling of repeat observations. These are acceptance exercises to perform, with results recorded only after the trial.
Assign ownership for unresolved differences. A missing read may need an equipment check, an identity check or a physical recount; ask the investigator to document what they checked and what remains uncertain. Require a specific resolution before including that item in an accepted movement. Review the exception sheet alongside the final proposed stock record.
Use the inventory control guide for wider stock processes and the POS inventory integration guide for checkout reconciliation. If a portal needs inventory data, include its handover in web development. Bring the zone drawing and trial worksheet to get started to discuss the proposed integration.
By Spout Team. AI-assisted drafting by Codex using the linked primary documentation.