Track the pallet, its current load or both with a defined identity and movement history. Plan read points, load changes and reconciliation so the stock system records the physical pallet lifecycle correctly.
Speak directly with Oxford Traceability about RFID identification of pallet movements.
Define whether the identifier belongs to the pallet, its load or both, and map the movements to record. Trial the proposed tag positions with real goods, wrap and neighbouring pallets. Agree direction, grouping and duplicate-read rules, plus the process for handling a changed load or incomplete read.
An RFID tag can identify a pallet or a tagged load, but the tracking system must know what that identity means. Define how goods become associated with a pallet, how that association changes and which movements need a confirmed record.
Decide whether the identifier represents a reusable pallet, the current unit load or individual tagged goods. A pallet reused for another shipment should not inherit the previous load unintentionally. Document the point at which a new association is created and the old one is closed.
List receiving, production, storage, picking and dispatch events that need evidence. State what each read point can establish. If tags are only observed at selected gateways, describe the result as movement history at those points rather than continuous location everywhere in the warehouse.
Test the tag and mounting position with actual goods, wrapping and pallet materials. Include the normal orientation and movement method. Compare reads around neighbouring pallets as well as in an isolated trial, because the system must separate the intended load from surrounding stock.
Describe partial picking, damaged goods removal, added cases and repalletising. Define who or what updates the load association and how an uncertain change is held for review. A successful read of the pallet tag does not confirm the current contents unless those associations remain controlled.
For reusable pallets, define return status, inspection and removal from service. Decide how a damaged or replaced tag retains the correct asset history. Keep asset maintenance records and the current shipment relationship distinct so one can change without corrupting the other.
Agree how missed movements and unexpected identities are investigated. Include a practical fallback identification route and a controlled correction record. Validate the path from tag observation through the stock-system update, rather than assessing the reader only by how many tags it reports.
Use the selection guide to organise the comparison, then send the application details for review.
The right choice changes with identifier and data rules for RFID identification of pallet movements, substrate, label or tag behaviour, your line layout and required results.
A reusable pallet and the goods currently on it have different lifecycles. Define when a load association is created, changed and closed, then test picking, rebuilding and return. Reading the pallet identifier only confirms the intended contents when that association is still valid.
Keep the reusable pallet identity distinct from the current shipment or unit-load identity where both are needed. Decide whether individual case identities are captured or quantities are associated at a defined packing event. Make that level of evidence explicit in downstream reports.
When cases are picked, damaged, added or moved to another pallet, specify the event that updates the association. Include authorised manual changes where automatic identification is unavailable. A record that only captures full-pallet arrival and departure may miss those intermediate content changes.
Use representative contents, wrap and tag positions at the proposed read points. Include a nearby pallet and reverse movement. Compare the accepted event with the load record current at that moment, rather than assuming that a repeat pallet read means the same contents as the previous trip.
When a pallet is emptied or returned, define how the previous load is closed and how the next association is released. Preserve the earlier movement history for traceability. Reusing an asset identifier must not overwrite previous shipments or attach their contents to a new dispatch.
In a hypothetical exercise, pallet P starts with cases A, B and C. B is removed and D is added before dispatch. The dispatch record should resolve to A, C and D using the approved association process. After P is emptied and reused, a query for the first dispatch must still return that historical set.
For the next step, discuss this application using the examples and unresolved decisions above.
Your final solution for RFID identification of pallet movements must reflect the law, current standards and site-specific risks that apply to your installation.