ISO 18000-6C / ISO 18000-63 UHF RFID Buyer's Guide

ISO 18000-6C / ISO 18000-63 — governance, lineage and why the name changed

Few RFID standards have collected as many aliases as this one. The same UHF air interface shows up under different names on different datasheets, and procurement teams routinely lose an afternoon deciding whether a tag quoted under a given name will even talk to a reader quoted under a different one. It will — and knowing why is worth the afternoon. Buyers frequently encounter three names for what is substantively the same standard: ISO 18000-6C, EPC Gen2, and ISO/IEC 18000-63. Understanding the lineage and the ISO governance structure behind these documents clarifies why datasheets and procurement specifications use different references, and why conformance to one implies conformance to the others.

• ISO/IEC JTC 1/SC 31 governance — the standard is developed and maintained by ISO/IEC Joint Technical Committee 1, Subcommittee 31 (Automatic identification and data capture techniques), working group WG 4 (RFID for item management). SC 31 operates under joint ISO and IEC rules and produces standards recognized worldwide, including the ISO/IEC 18000 family of RFID air-interface specifications across the frequency bands.
• The 18000 family covers multiple frequencies — 18000-2 (125-134 kHz LF), 18000-3 (13.56 MHz HF, referenced by ISO/IEC 15693 and 14443), 18000-4 (2.45 GHz microwave), 18000-6 (860-960 MHz UHF, subdivided into 6A/6B/6C) and 18000-63 (the successor to 6C after the 2013 restructuring). UHF buyers encounter 6C and 63 interchangeably.
• 6A and 6B legacy subsets. ISO 18000-6A and 6B were earlier UHF RFID protocols with different air interfaces, different anti-collision algorithms and incompatible hardware implementations. They saw limited commercial deployment and are effectively obsolete today; any new UHF deployment should assume 6C/63 compatibility.
• 6C to 63 restructuring — in 2013 ISO restructured the UHF family, elevating what had been the 18000-6C annex to its own standalone document ISO/IEC 18000-63 for the Gen2 air interface, with companion documents 18000-64 (alternative UHF tags in the same band) and 18000-61/62 (for other air-interface variants). The first edition was 18000-63:2013, replaced by the second edition 18000-63:2015, and the current third edition 18000-63:2021 (the version most chip and reader datasheets reference today). Current buyer practice treats 18000-6C and 18000-63 as interchangeable references to the Gen2 protocol.
• GS1 EPCglobal alignment: the ISO documents are developed in coordination with GS1 EPCglobal, the industry body that authored the original Gen2 specification. GS1 maintains the EPC Gen2v2 document (updated periodically since 2013) as the authoritative air-interface specification, with ISO publishing the formally balloted international version. Conformance to one is effectively conformance to the other; minor editorial differences exist but the air-interface operation is identical.
• How to read a datasheet reference. A tag datasheet stating 'ISO 18000-6C compliant', 'ISO/IEC 18000-63 compliant' or 'EPC Gen2v2 compliant' refers to the same underlying protocol. Newer datasheets increasingly cite ISO/IEC 18000-63 as the primary reference, with EPC Gen2v2 and the legacy 18000-6C cited for backward compatibility. All three references indicate the same operational protocol.

Tag performance classes — chip sensitivity, memory tier and the buyer's mental model

Because protocol conformance is essentially universal among modern UHF tags, the differentiating characteristics that buyers evaluate are grouped under the informal concept of 'tag performance class.' This mental model organizes the datasheet comparison across chip families, sensitivity bins and memory tiers, and maps cleanly onto how tag catalogues (including Proud Tek's) are structured for procurement.

• Read-sensitivity bin as the primary performance axis. Read sensitivity is the minimum reader-generated RF power (expressed in dBm, more negative = more sensitive) at which a tag reliably responds. Modern tags span roughly -18 dBm (entry-level, short range) through -22 dBm (mainstream retail) to -24 to -27 dBm (premium/high-performance inlays). Each additional 2-3 dB of sensitivity approximately doubles the free-space read range.
• Write-sensitivity delta: write operations (committing new EPC or user-memory data to the tag) require higher RF power than read operations, typically 3-5 dB more. A tag rated -22 dBm read may have -17 to -19 dBm write sensitivity. This matters for field-encoding workflows where tags are written in situ on conveyors or in write-and-verify stations; short write range forces closer reader proximity or repeated retries.
• Memory tier classification: Gen2 tags are bought in memory tiers: minimum (96-bit EPC only, no user memory, lowest cost, highest volume), standard (128-bit EPC plus 32-512 bits of user memory, mainstream retail apparel), extended (256-bit EPC plus 1-4 kbit user memory, pharma and industrial), and large (512-bit EPC plus 8 kbit or more user memory, embedded sensor or maintenance-record applications). Chip price increases roughly 1.5-3x per tier jump.
• Chip family shorthand: buyers and integrators use chip family shorthand (Impinj M730/M770/M750, Impinj M800 series, NXP UCODE 9/9xe/9xm, Alien Higgs-9/EC, STMicroelectronics ST25RU3993 receivers) as a proxy for performance class because chip-family documentation specifies the sensitivity bin, memory layout and feature set. A tag spec that references the chip family implicitly references a well-known set of performance characteristics.
• Feature-set differentiation: beyond core sensitivity and memory, newer chips differentiate on advanced features: encoded TID and authentication (brand-protection), NXP UCODE DNA crypto authentication, integrated BLE (Bluetooth) bridges for IoT bridging, temperature sensing (RFMicron Magnus, Farsens sensor chips), tamper detection and battery-assisted passive (BAP) operation. These features occupy their own performance sub-classes at premium price points.
• Performance class as procurement language. When a retail buyer specifies 'standard apparel inlay, M730-equivalent or better', they are using performance-class shorthand that a supplier can answer with a catalogue mapping. Proud Tek's catalogue maps each UHF tag model to a (chip family, sensitivity bin, memory tier, form factor, recommended substrate) tuple so this shorthand resolves to concrete model numbers during sampling and quotation.

Read-sensitivity and write-sensitivity specifications in depth

A datasheet sensitivity figure is a promise made in an anechoic chamber; the loading dock is where it gets renegotiated. Because read and write sensitivity drive the realized performance of a UHF deployment, a deeper look at how these are measured, reported and affected by real-world conditions helps buyers interpret datasheet numbers and avoid surprises in pilot testing. Laboratory sensitivity specifications are a ceiling; real-world performance is almost always worse, and the gap between the two is dominated by antenna tuning, substrate effects and reader-side link budget.

• Laboratory sensitivity measurement: read sensitivity is typically measured in an anechoic chamber at a fixed frequency (often 915 MHz in North American measurements, 866 MHz in European measurements) with the tag antenna oriented for peak gain. The reported number is the minimum reader EIRP at which the tag returns a valid EPC within a standardized number of inventory rounds. Measurement conditions are documented in the chip datasheet.
• Frequency dependence: chip sensitivity and antenna impedance match vary with frequency. A tag optimized for 902-928 MHz North American operation may show 3-5 dB worse sensitivity at European 865-868 MHz and vice versa. Global tags (designed to operate across the full 860-960 MHz band) accept a modest sensitivity penalty (typically 1-2 dB) in exchange for worldwide operability, and this tradeoff is explicit on global-tag datasheets.
• Substrate detuning: antenna impedance is designed against a specific dielectric-constant environment. Mounting a tag designed for cardboard packaging onto glass, plastic or low-moisture substrates (tyres, apparel with metallic yarn) detunes the antenna and can shift resonance by 5-10 MHz, with 3-8 dB sensitivity loss. Substrate-matched antenna designs (on-glass tags, anti-metal tags, on-tyre tags) restore the sensitivity budget for their target material.
• Orientation sensitivity: most dipole-style UHF antennas have a figure-8 radiation pattern with deep nulls perpendicular to the dipole axis. Orientation misalignment between tag and reader antenna easily introduces 10 dB or more of apparent sensitivity loss. Dual-polarization reader antennas and near-circular-polarization tag designs mitigate this but do not eliminate it, and deployment design should account for worst-case tag orientation.
• Write sensitivity as a separate budget. Because writes require more RF energy, the effective write range of a tag is smaller than its read range, often by a factor of 2-3x. Deployments that depend on in-field encoding (source-tagging printers, write-and-verify gates) need to size reader power, antenna gain and mounting distance against the write-sensitivity specification rather than read sensitivity. Specifying only read sensitivity in procurement is a common pitfall.
• Reader link budget: the complete link budget includes reader transmit power (regulated to 4 W EIRP in North America under FCC Part 15.247, 2 W ERP in Europe under EN 302 208), reader antenna gain, free-space path loss, tag antenna gain, chip sensitivity, and return-link margin for backscatter reception. A realistic read-range model combines all these; tag sensitivity alone does not predict deployment performance.

Form-factor and substrate selection — matching the tag to its physical application

Tag form factor and substrate compatibility are typically the dominant procurement decision once performance class has been chosen. This section maps the common UHF form factors buyers see on a catalogue like Proud Tek's to their intended applications, substrate constraints and deployment contexts, so that procurement specifications align with the physical reality of the tagged item.

• Standard paper label / inlay. The highest-volume form factor, used for apparel, consumer packaged goods and general logistics. Typical dimensions 50-100 mm antenna length, adhesive paper or PET face stock, priced at the lowest cost per tag. Performance is optimized for cardboard, plastic, and fabric substrates; performance on metal or high-moisture substrates is severely degraded and should not be attempted.
• Small-format labels and die-cut inlays. For jewelry, cosmetics, small electronics and other small-item applications, chip manufacturers offer miniaturized antenna designs (often 30-50 mm). These accept 2-5 dB sensitivity loss versus full-size inlays in exchange for fitting into small packaging. Small-format tags should be evaluated in the actual deployment environment because substrate effects dominate their short antennas.
• On-metal and anti-metal tags. For steel, aluminum and other conductive substrates, specialized anti-metal tags use either a ferrite-backed antenna design, a microstrip/patch antenna, or a foam-spacer separation layer to maintain antenna performance. These tags are 3-8x the cost of standard labels but are the only practical option for metal-mounted applications; substituting a standard label will produce near-zero read range.
• Hard tags for industrial asset tracking. Plastic- or ceramic-encased hard tags survive industrial environments (vibration, chemical exposure, temperature extremes, impact). Typical ratings include IP67/IP68 water ingress, -40 °C to +125 °C operating temperature, and mechanical-shock ratings appropriate for industrial applications. Hard tags are the dominant form factor for returnable transport items, tool tracking, vehicle tracking and manufacturing-in-process identification.
• Embedded and on-glass tags. For high-end retail (wine, spirits, luxury goods), automotive windshields (electronic tolling), and pharmaceutical primary packaging, specialized on-glass and embeddable tag designs account for the dielectric properties of glass and container contents. These often use specialized NXP UCODE on-glass chips or Impinj on-glass antenna designs tuned for the application.
• Retail-market standard sizes. For apparel retail, the de facto standard is a paper label matching one of a small number of standard sizes documented by Auburn University RFID Lab and the RAIN Alliance retail-tagging working group. Buyers purchasing apparel tags should specify tag size matching their retailer's receiving guidelines to avoid supply-chain rejection at distribution centres.

Compliance and conformance-testing methodology

ISO 18000-63 compliance is typically tested at the chip and tag level through a combination of independent laboratory testing, industry-association conformance programmes and supplier quality-control testing. Buyer confidence in the compliance claim relies on understanding how conformance is established and how a buyer can independently verify it.

• Chip-level pre-conformance testing. Chip manufacturers (Impinj, NXP, Alien) run extensive pre-conformance testing of their Gen2 chips against the GS1 and ISO reference test specifications before releasing a chip to market. Public chip datasheets typically cite the specific EPC Gen2v2 and ISO 18000-63 versions and any optional feature support. A tag built on a certified chip inherits the chip's air-interface conformance.
• Tag-level interoperability testing. Beyond chip-level conformance, the RAIN Alliance operates a tag and reader interoperability programme at accredited testing laboratories (including ETS-Lindgren, Auburn University RFID Lab and MET Labs). Tags that pass interoperability testing are listed on the RAIN Certified Products Database with a Certification ID; buyers can look up vendor product-model numbers to verify the certification status.
• Field-performance testing: for retail mandate qualification (Walmart ARC programme via Auburn University, Target tag qualification, European retailer programmes), tags undergo additional field-performance testing in mock distribution-centre and store environments. Passing these tests is a prerequisite for supplying tags to the retailer's source-tagged-goods programme; performance-class certification at the retailer-specific level is distinct from ISO conformance.
• Supplier QC and lot-level reporting. Beyond certification, buyers should expect lot-level quality-control reporting from their tag supplier: percentage of tags meeting the rated read-sensitivity bin, encoding-yield percentage on source-tagged labels, and defect tracking across production lots. Proud Tek supplies lot-level QC reports as part of standard order delivery for UHF RFID products.
• Regional regulatory compliance is separate. ISO 18000-63 governs the air-interface protocol and is not a regulatory compliance standard. Regional regulatory approvals (FCC Part 15.247 in North America, EN 302 208 in Europe, MIC Article 18 in Japan) govern the reader hardware and are separate from tag conformance. Tags do not require separate regulatory type approval because they are passive devices that backscatter the reader's signal.
• Buyer procurement checklist: for a UHF tag purchase, confirm: ISO/IEC 18000-63 or EPC Gen2v2 conformance (usually present for all modern tags); chip family and sensitivity bin matching the performance-class specification; RAIN Alliance certification ID if cross-vendor certification matters; lot-level QC reporting and defect-tracking commitments; and for retail supply, retailer-specific tag-qualification status (Walmart ARC, Target, etc.).

Protocol evolution, backward compatibility and extension features

The ISO 18000-63 / EPC Gen2v2 standard has evolved since the original Gen2 release in 2004, with significant additions in 2013 (Gen2v2, which introduced cryptographic and authentication extensions) and subsequent amendments. Buyers encountering these extensions on premium chips should understand which features are optional and which are baseline, so that procurement decisions reflect actual application requirements rather than speculative future use.

• Baseline Gen2 (2004): the original specification defined the core air interface, the four memory banks (Reserved, EPC, TID, User), the Select/Query/ACK/Read/Write command set, inventory rounds with Q-algorithm anti-collision, sessions S0-S3, kill and access passwords, and basic lock-state control. Every modern tag supports the Gen2 baseline; applications that don't need premium features run natively on any Gen2 tag.
• Gen2v2 cryptographic extensions (2013). Gen2v2 added optional crypto-suite support (AES-128, PRESENT-80), secure-access commands (Authenticate, Challenge, Untraceable), and the file-management subsystem for user memory with per-file access control. Chips that implement Gen2v2 crypto (NXP UCODE DNA, Impinj M700 with integrated authentication, Alien Higgs EC) are the basis of brand-protection and anti-counterfeit applications.
• Untraceable command: the Untraceable command allows a tag to be hidden from subsequent inventory operations (by reducing its response to short form or hiding TID and user memory). This is a privacy-oriented feature relevant to consumer-facing retail tags that must be silenceable at point of sale under the EU GDPR-era retail privacy expectations; not all chips support it and not all applications require it.
• Extended TID and encoded TID. The TID (Tag Identifier) memory bank holds a unique chip serial number assigned by the chip manufacturer. Newer chips include 'encoded TID' with manufacturer and chip-model identification, and some premium chips include signed TID for authentication purposes. Buyers concerned with brand protection or anti-counterfeit should specifically require encoded-TID support on the procurement specification.
• Battery-assisted passive (BAP) tags. BAP tags incorporate a small battery to power the chip while retaining the backscatter-based Gen2 communication. This extends read range dramatically (to 30-100 m in some designs) and supports integrated sensing. BAP tags are a distinct product category with different unit economics and battery-life considerations; they are Gen2-compliant but price per tag is an order of magnitude higher than passive tags.
• Backward compatibility commitment: the ISO and GS1 standards committees have maintained strict backward compatibility since the original 2004 specification: a Gen2 reader can read any Gen2v2 tag (receiving whatever the tag chooses to expose), and a Gen2v2 reader can read older Gen2 tags. Premium features degrade gracefully to baseline inventory on older-reader infrastructure. This commitment protects buyer investment in installed reader infrastructure across multi-year tag-technology refresh cycles.
• Gen2v3 (January 2025) — the next-generation extension. GS1 published Gen2v3 in January 2025 as the first major UHF EPC protocol revision in over a decade. Three new capabilities matter for buyers: Query X / Query Y selection commands enable filtering by EPC scheme, header value or feature flag (an interrogator can target only baggage-scheme tags and ignore unrelated item-level tags inside the bag, for example); modulated-power inventory lets the reader briefly drop transmit power so only on-target tags wake up, suppressing fringe-tag responses; the Read-Var command lets the reader request exactly the slice of User or TID memory it needs (lot, batch, expiry) rather than fixed-width reads. Gen2v3 is fully backward compatible — Gen2v2 chips work on Gen2v3 readers and vice versa — and reader vendors add Gen2v3 support through firmware updates only. Tag-chip silicon implementing Gen2v3 sampled through 2025 with production rollout in 2026-2027 across the major chip vendors (Impinj, NXP, EM Microelectronic, Shanghai Quanray).

Command reference — Select, Query, ACK, Read, Write, Lock, Kill and authenticated extensions

The ISO 18000-63 / EPC Gen2v2 protocol defines a concrete set of commands that readers issue and tags respond to. Procurement teams rarely need to operate at command level, but integrators writing middleware, validating read behaviour, or diagnosing field-performance issues need to understand the command set in enough detail to interpret reader logs and reference the specification correctly. This section summarizes the core and extended command set with the parameters that matter in practice.

• Select command: identifies the subset of the tag population that should participate in the next inventory round. Parameters include the target memory bank (EPC, TID or User), the pointer and length of the bit mask to match, and the action to take on matching versus non-matching tags (assert/deassert SL flag, set inventoried flag to A or B). Select is how middleware filters inventory to specific GTINs, retailer subsets or application-specific serial ranges without reading the full tag population.
• Query command: initiates an inventory round with parameters including the session (S0-S3), target flag state (A or B), Q value (log2 of the initial slot count), DR (divide ratio for link frequency), M (modulation type, including FM0 and Miller subcarriers), Sel flag treatment and TRext (extended preamble). Q-algorithm tuning is the most common field-performance lever: underestimating Q causes collisions, overestimating Q wastes slots.
• ACK command: acknowledges a singulated tag's RN16 response and instructs it to backscatter its EPC. The ACK+EPC round trip is the high-throughput inner loop of inventory; each successful ACK represents one unique-tag read. Collision rates at this stage are visible in reader-log noise and indicate Q-algorithm mis-tuning.
• Read command: retrieves data from a specified memory bank (Reserved, EPC, TID, User) at a specified word pointer and word count. Reading TID during inventory provides encoded manufacturer and chip-model identification; reading User memory enables retrieval of lot numbers, maintenance records or extended serial data. Read requires the tag to be in the Open or Secured access state, obtained via Req_RN and Access commands for password-protected memory.
• Write command: commits new data to a memory bank. Writes are word-wise (16 bits per write) and are verified through readback. Write requires the tag to be in the Secured state after Access password verification if the memory bank is password-locked. Power budget for writes is 3-5 dB higher than reads, so write-range-limited applications must account for this in reader placement.
• Lock command: sets the permanent or temporary lock state for each memory bank, controlling whether the bank can be written, whether a password is required to unlock, and whether the lock itself can be undone. Lock states are the mechanism for tamper-resistant source tagging: retailers require specific lock configurations to prevent tag cloning after source-tagging.
• Kill command: permanently disables a tag when issued with the correct 32-bit kill password. After a successful Kill, the tag will not respond to any subsequent commands. Kill is used for consumer-privacy-at-checkout in retail, for end-of-life decommissioning of returnable assets, and for controlled removal of tags from circulation in DPP and serialization programmes.
• Authenticated Gen2v2 commands — Authenticate, Challenge, SecureComm, KeyUpdate and Untraceable are the crypto-enabled commands introduced with Gen2v2. Authenticate verifies the tag against a reader-presented challenge using AES-128 or PRESENT-80; Challenge initiates mutual authentication; SecureComm tunnels encrypted read/write. These are implemented on UCODE DNA, NTAG 424 DNA (NFC side), Impinj M7xx/M8xx with integrated authentication and similar premium chips; baseline Gen2 chips return a protocol error when asked for authenticated commands.

Deployment case-study patterns — how performance-class selection plays out in production

The abstract performance-class model becomes concrete when applied to specific deployment types. The following case-study patterns are composites of common production deployments Proud Tek has supported, showing how buyers move from a performance-class specification to an actual chip selection, and what read-rate and operational characteristics they should expect.

• Retail apparel DC receiving. Walmart-style source-tagged goods flowing into a regional DC with dock-door portals. Chip selection: Impinj M730 or NXP UCODE 9 on 97x27 mm paper inlay, read-sensitivity bin -22 to -24 dBm, 96-bit EPC only. Typical performance: 99.5%+ pallet read rates with 4-antenna portal, 1000-3000 tags per second at peak loading. Common issue: orientation-sensitivity on hanging apparel resolved with dual-polarization antennas and near-circular tag dipole designs.
• Jewelry and small-item anti-theft. Small-format 30x15 mm die-cut inlays applied to hang-tags on jewelry worth $100-5000 per item. Chip: NXP UCODE 9 in high-sensitivity bin, 96-bit EPC plus kill password, encoded TID for brand authentication. Typical performance: 95-98% read rate at 1-2 meter range in open-tray staging, 99%+ in closed-box sealed trays. Common issue: metal bezels and settings absorb UHF energy; case-level tagging plus per-item barcode backup is the mitigation.
• Returnable transport items (RTI). Plastic totes and crates circulating between manufacturer, DC and retailer with embedded hard tags expected to last 5-10 years. Chip: Alien Higgs-9 or Impinj M730 in IP67-rated ABS/polycarbonate housing, extended-memory variant (512 bits user memory) for RTI history logging. Typical performance: sub-second read-through at conveyor speed (1.5 m/s), 99.9%+ read rate after commissioning. Common issue: tag mechanical failure from handling impact; hard-tag housing selection is the long-term wear determinant.
• Pharmaceutical case-level serialization. DSCSA compliance requires unit-level serialization with aggregation to case and pallet. Chip: NXP UCODE 9xm (up to 496-bit EPC + 752-bit user memory configurable) or Impinj M781 (128-bit EPC + 512-bit user memory) for GS1 element string encoding — M770 (128-bit EPC + 64-bit user memory) is too small for full aggregation payloads. Typical performance: 99.9%+ read rate at DC portal, 98%+ at warehouse cycle count. Common issue: medication case materials (foil-lined blister packs, multi-layer cardboard) cause substrate detuning; pharma-certified inlays with liquid/foil-friendly antenna designs are the standard remedy.
• Anti-metal industrial assets. Tool cribs, returnable metal containers, valve bodies and industrial equipment that must be tagged directly on metal surfaces. Chip: Alien Higgs-9 or Impinj M730 in an on-metal hard-tag housing with ferrite backing or microstrip patch antenna, 1-3 mm standoff from metal surface. Typical performance: 3-8 m read range with linear polarization, 99%+ read rate in commissioning-tested geometries. Common issue: untested mounting positions produce substantially reduced range; installation-time read-rate validation per tag is recommended for mission-critical applications.
• Healthcare surgical instrument trays. Autoclave-rated tags surviving 134 °C steam sterilization cycles repeatedly over 500-1000 cycles. Chip: NXP UCODE 9 or specialized autoclave-qualified chip in PEEK or silicone housing. Typical performance: 99%+ read rate at handheld range (50 cm), 5-8 year functional life across sterilization cycles. Common issue: adhesion of housing to instrument surface degrades faster than the chip; laser-welded or mechanically clipped attachment is preferred over adhesive mounting.
• Airline baggage: IATA Resolution 753 tags surviving a single travel journey under airport baggage handling conditions. Chip: NXP UCODE 9 or Impinj M730 on printable-substrate label meeting IATA RP 1740c specification. Typical performance: 99%+ read rate at airport portal and sortation conveyor, consistent with published industry data (Delta, Lufthansa, Air France-KLM). Common issue: moisture absorption on substrate under long-dwell transit; moisture-resistant label constructions are standard for premium airline programmes.
• Sensor-integrated cold-chain. Temperature-logging passive tags on pharmaceutical or food cold-chain shipments. Chip: Farsens Rocky 100 with integrated temperature sensor or Asygn sensor chip on custom inlay. Typical performance: per-minute temperature logging for 30-90 day shipment durations, read-on-demand at dock-door portals. Common issue: sensor calibration drift over time; periodic sensor recalibration or supplier-certified calibration commitments are the operational requirement.

Proud Tek's catalogue organization and buyer engagement — from specification to sample

To make the standards and performance-class concepts above actionable for a procurement team, Proud Tek organizes the UHF tag catalogue explicitly around the buyer's mental model: chip family, sensitivity bin, memory tier, form factor and recommended substrate. This final section describes how buyers engage with the catalogue, the typical sampling and pilot process, and how Proud Tek supports retailer-mandate compliance and large-account procurement. Conformance guarantees that any compliant tag will talk to any compliant reader; it says nothing about which tag survives your loading dock, your autoclave or your metal shelving. Picking the one that does is procurement's real job — and it is the job this catalogue exists to make routine.

• Catalogue axes: each UHF tag product page lists the chip family (Impinj M730/M770/M730 Ice, Impinj M800 series, NXP UCODE 9/9xe, Alien Higgs-9/EC), read-sensitivity bin in dBm at 915 MHz and 866 MHz, write-sensitivity, memory layout (EPC size, user memory size, password protection), form factor (label, inlay, hard tag, on-metal, on-glass), recommended substrate list and ISO/IEC 18000-63 conformance reference.
• Retailer-mandate alignment: for buyers supplying to Walmart, Target, Amazon or European retailer programmes, the catalogue cross-references each tag model against the retailer's published qualification list (Walmart ARC Certification, Target tag qualification, Macy's tag specifications, European retailer requirements where applicable) so that procurement teams can select models that are pre-qualified for their target receiving facility.
• Sampling workflow: buyers engage via the contact form or sales team to request samples. Standard sample packs include 25-100 tags per selected model, shipped within 5-7 business days. For buyers evaluating multiple chip families or form factors in parallel, multi-model sample packs coordinate same-day shipment so pilot testing can compare like-for-like across the shortlist.
• Pilot-phase technical support. Proud Tek's application-engineering team supports pilot deployment with free tag-placement recommendations, reader-configuration guidance (antenna polarization, transmit power, session selection for the application class), and read-rate troubleshooting. Typical pilot durations run 2-6 weeks depending on application complexity.
• Scaling to production: once a pilot validates the performance-class selection, production orders move to standard lead times (typically 2-4 weeks for stock models, 4-8 weeks for custom-printed or custom-antenna designs). Lot-level QC reports accompany each shipment with sensitivity-bin distribution, encoding yield and defect counts matching the quality commitments in the quote.
• Long-term account relationships. For enterprise accounts with multi-year tag programmes (retail apparel, automotive returnable containers, healthcare asset tracking), Proud Tek maintains a dedicated account engineer who tracks chip-generation evolution, coordinates transition testing when Impinj, NXP or Alien release new chip generations, and ensures continuity of performance-class specifications across supply-chain tag-family refreshes.

FAQ