Questions worth answering before you ask them.

They're different radio frequencies, and each trades off range against reliability near metal and liquid. LF (125–134 kHz) is short-range and very tolerant of tough environments — think implantable livestock tags. HF/NFC (13.56 MHz) is the tap-and-scan range used in access cards and small labels. UHF (860–960 MHz) reads from several meters away and is what most warehouse, retail, and laundry deployments use.

No — everything we sell is passive. The tag draws its power from the reader's radio signal itself, so there's no battery to replace and effectively no shelf-life limit on the electronics.

Yes, for most non-metal, non-liquid materials — that's one of RFID's main advantages over barcodes. Metal and water-heavy contents (produce, liquids, some fabrics when wet) attenuate the signal, which is why we build specific on-metal and wash-rated variants rather than a single universal tag.

A barcode needs direct line of sight to one code at a time. RFID reads through most materials, doesn't need to be visible, and a single reader can capture dozens to hundreds of tags per second — which is what makes cart-level or dock-door scanning possible.

In most cases, yes. Our UHF tags follow the EPC Class 1 Gen 2 / ISO 18000-6C standard used by the large majority of commercial readers on the market. Tell us your existing reader model and we'll confirm compatibility before you order anything.

Start with what the tag has to survive, not what it's tracking: mounting surface (metal, plastic, fabric), temperature range, exposure to washing or chemicals, and the read range you need. Send us those four details and we'll point you to a catalog fit or scope a custom one.

Yes — tags can ship pre-encoded and sequentially numbered to your spec, or blank if you'd rather encode them on-site with our desktop printer/encoder.

Both. Our middleware sits between the raw tag reads and your inventory, WMS, or ERP system — filtering duplicate reads and pushing clean, actionable events wherever they need to go. See the Middleware & Software Platform listing for specifics.

Yes — a sample kit is the standard first step for a new application. Request one through the contact page and a named engineer will follow up with the right tag and reader combination for a test.

Catalog tags usually ship within 1–3 weeks depending on quantity and encoding requirements. Custom builds — new form factors, materials, or ratings — run longer, and we'll give you a firm date once the spec is locked.

Sample kits have no minimum. Production orders typically start in the low thousands per SKU, though this varies by tag type — ask your account engineer for the specific minimum on the product you need.

Yes, we ship internationally and support the deployment remotely — documentation, configuration files, and a named engineer on the account, the same as a local customer would get.

You get a named engineer, not a support ticket queue. If a tag isn't reading the way its datasheet says it should in your environment, that's on us to diagnose and fix — including a design change if that's what it takes.

Usually, yes — most of what we ship started as a variant of an existing design rather than a clean-sheet build. Frequency, memory, form factor, material, and environmental rating are all configurable; tell us the application and we'll scope it honestly.

Yes — our middleware includes common WMS/ERP connectors and a REST API/MQTT interface for custom integrations, and our team works directly with your IT or operations staff during setup.