Plan RFID portals for receiving and dispatch around the movement you need to confirm. Test real loads, neighbouring stock, direction and incomplete passages before connecting reader observations to warehouse records.
Speak directly with Oxford Traceability about dock-door RFID movement capture.
Define the doorway event, direction of travel and the loads that should be associated with it. Trial tagged goods moving through the portal while other tagged stock remains nearby. Agree the sensing and business rules for direction, repeated reads and incomplete loads, with an exception route before dispatch or receipt is confirmed.
A portal observes tags in a read area. The warehouse needs a defensible movement event linked to a door, direction and expected load. Define that distinction before choosing reader positions or connecting the portal to stock records.
Decide whether the process records arrival, loading, dispatch or a movement between internal zones. Define when that event is complete and which business record should change. A tag appearing near the doorway is an observation that may need more context before it becomes a confirmed movement.
Include staged pallets, adjacent doors and vehicles passing across the face of the portal. Trial the expected tags, goods and wrapping in their normal orientations. Record unwanted reads as well as missed tags so the read zone is judged against the actual warehouse layout.
Describe how the system distinguishes entry, exit and a load that approaches and reverses. Agree the sensing and event logic for pauses in the doorway. Retain incomplete movements as exceptions until the defined conditions for a valid event have been satisfied.
Identify the shipment or receipt data available to the portal. Define how missing, additional or unexpected identifiers are presented to the operator. Avoid treating an apparently busy read as proof that all required goods have crossed the boundary.
A load can remain in range or pass the door more than once. Specify which observations are combined, which are a separate movement and how cancelled loading is reconciled. Keep enough context to explain an exception without silently creating duplicate receipts or dispatches.
Define the approved response if the reader, network or warehouse system is unavailable. Include operator notification, any local event retention and controlled reconciliation after recovery. Test the procedure before relying on automated movement confirmation during a live shipping window.
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 dock-door RFID movement capture, substrate, label or tag behaviour, your line layout and required results.
A dock portal should distinguish a completed receiving or dispatch event from staging, reversing and activity at an adjacent door. Build acceptance around a known physical movement sequence and compare the business records with it, including the movements that should create no transaction.
Agree what opens a movement episode and what confirms its completion. Include a load that approaches the door, pauses and returns to the staging area. Tags detected during that episode may provide useful observations without proving that the shipment left the building.
Place known tagged loads in normal waiting positions and operate neighbouring doors during the trial. Check which reads are associated with which doorway and shipment. Record an unexpected tag separately from a missing required tag; both can produce incorrect inventory records through different routes.
Define the expected identifiers and what happens when a load is short, extra or assigned to another order. Keep shipment amendments controlled while loading is under way. A read of the pallet identity should not silently confirm the contents unless their association has been established and remains valid.
Specify the response when the same load crosses twice or unloading reverses an earlier action. Distinguish a repeat observation from a genuine new movement. If the warehouse system is unavailable, show the unresolved event to the operator and test its later acknowledgement without creating duplicate dispatches.
A hypothetical acceptance run stages pallet A near the door, sends B through, returns B before departure and then loads C. Compare the recorded state of all three with the agreed business rules. A must not be dispatched merely because it was visible to the reader, and B’s return must be explained rather than hidden by a final count.
For the next step, discuss this application using the examples and unresolved decisions above.
Your final solution for dock-door RFID movement capture must reflect the law, current standards and site-specific risks that apply to your installation.