RFID Smart Cabinets & Smart Storage

What is an RFID smart cabinet, and when is it the right tool?

An RFID smart cabinet is a lockable cabinet with UHF RFID antennas built into it. Because the antennas are inside the body and the body is shielded, the reader can count the tagged contents of the cabinet on demand — no opening drawers, no scanning barcodes one at a time. The cabinet answers three questions that a lock and a paper log cannot: what is in here right now, who had each item last, and what is missing.

It is the right tool when an item is issued to a person and has to come back, when the manual count is slow enough that it stops happening, or when a missing item turns into a safety, quality or billing question. Three tests decide it:

Pick by what you store

Fifteen models, grouped by the job they do. Every model page carries the manufacturer’s specification for that cabinet; where the manufacturer does not publish a value it is left out rather than estimated.

How does it connect to my ERP, WMS or HIS?

The cabinet keeps its own record of every issue, return and count against a user and an item, and exposes those events. Your system keeps the item master, the cost centre and the reorder rule. Drawing that boundary correctly is most of the integration work.

Networking on the cabinet side is TCP/IP as standard, with Wi-Fi or 4G optional on several models; the key cabinets use RJ45. If the link drops, the cabinet keeps authenticating and buffering locally and synchronises when it comes back — it does not become a locked door.

How do I pilot it without risk?

A pilot is not a smaller purchase; it is a measurement. Scope it around one cabinet, one location and one item group, and agree what a pass looks like before the unit ships.

1. Pick one item group — The group with the worst reconciliation history or the highest value per item. Not the whole tool room.
2. Write the pass criteria down first — Read rate on the real items, exceptions per shift, how often the cabinet is actually used, hours saved per count.
3. Tag and register the group — Choose the tag against the item material, then place it the same way on every item.
4. Run one full cycle — A real shift pattern, including the day the network drops and the day someone returns the wrong item.
5. Decide on the numbers — If the four criteria are met, the next cabinet is a repeat order. If they are not, we change the tag, the layout or the software rule — not the cabinet.

The four pass criteria — read rate on the real items, exceptions per shift, how often staff actually use the cabinet, and count hours removed — are the same four we ask about when a customer tells us the first cabinet worked.

Common questions

• What is an RFID smart cabinet?

  A cabinet with fixed UHF RFID antennas inside it and a reader that counts the tagged contents on demand. Instead of opening drawers and reading serial numbers, the cabinet reports what is inside, who signed it out and when. The cabinet is the reader; the location of the tag is what makes the count possible.

• How is it different from a lockable cabinet and a paper log?

  A lockable cabinet and a paper log record intent. A smart cabinet records state. The difference shows up at the end of a shift: a log tells you what someone wrote down, a smart cabinet tells you what is physically in the cabinet now, and names the user whose session the item left on.

• What actually decides whether the count is accurate?

  Four things, in this order: the cabinet (shielded body, antenna layout, power), the tag and where it sits on the item, the item itself, and the software rules that define what a valid count is. Get the tag and the antenna layout wrong and no amount of software will fix the count. We size these together with you rather than quoting a percentage.

• Can it read tools and parts made of metal, or items containing liquid?

  Yes, with the right tag. Plain label tags detuned against metal read poorly, which is why on-metal tags exist: they carry a spacer so the antenna keeps its impedance against a conductive surface. Liquids behave in the opposite way and need their own tag choice. Both are tag-selection problems, not cabinet problems, and they should be settled before the cabinet is specified.

• What happens if the network or the server is down?

  The cabinet keeps working. It authenticates locally and buffers the transaction, then synchronises when the link recovers. The cabinet is not a thin client that stops at the doorway, which is why a cabinet can be installed in a workshop or a basement before the network reaches it.

• How do the transactions get into our ERP, WMS or HIS?

  The cabinet writes to its own database and exposes the events; your system consumes them. The cabinet side usually delivers issue, return and count events against a user and an item; your side owns the item master, the cost centre and the reorder rule. We will map the boundary with you, and we will say plainly when something needs to be built rather than configured.

• How long does a pilot take, and what counts as a pass?

  A pilot should be scoped around one cabinet, one location and one item group, with the pass criteria written down before it starts. The four that matter are read rate on the real items, the number of unexplained exceptions per shift, how often staff actually use the cabinet instead of the old routine, and the hours the count no longer takes. If those four are met, the second cabinet is a repeat order rather than a decision.

• What has to be tagged, and who applies the tags?

  Tag only what the cabinet manages. Tagging every item on site is the fastest way to make a pilot expensive and slow. For a first cabinet, the item group is usually the one with the highest value or the worst reconciliation history. Tags are applied on site or by the supplier depending on the item, and the placement has to be consistent, because the count depends on it.