Shanghai or Long Beach shippingVolume pricing availableCompatibility review
PRODUCT / 02
PTID-DI-8045UHF RFID Dry Inlay
CONFIRMED PRODUCT INFORMATION
Specifications at a glance
Use these supplier-provided specifications to shortlist the product, then validate the exact workflow with samples in your own environment.
Product form
Dry inlay — no pressure-sensitive adhesive backing
Finished size
80 × 45 mm
Nominal frequency
900 MHz
Protocol
UHF EPC G2 / ISO 18000-6C
Supported programming
EPC and TID; exact writable range confirmed by sample test
Indicative read/write range
0.1–10 m according to reader power; no distance guarantee
Power requirement
Higher than conventional fixed-TID tags; high-power reader recommended
Supplier comparison
Reported 40–50% improvement over Generation 1 and more than 50% over the long-strip format
Compatible IC
Compatible UHF RFID IC
Lead time
Within 30 days after order confirmation
Shipping origin
Shanghai, China, or Long Beach, California, USA, depending on inventory and quotation
* Technical and comparison claims are supplier-provided. Range, compatibility, memory behavior, locking and regulatory fit must be verified by the buyer; the stated 0.1–10 m range is not guaranteed.
ENGINEERING WORKFLOW
What this product is designed to do
01
Supported TID programming
Use the special-purpose experimental IC in a supported, authorized TID workflow; confirm the exact writable range and commands with a sample.
02
EPC read and write
Provision and update EPC data using compatible EPC Gen2 / ISO 18000-6C reader commands and software.
03
Application-level validation
Test performance with the actual reader, antenna, surface, orientation, power setting, and RF environment before deployment.
BEFORE YOU ORDER
Five details that make a quotation faster
Including these details helps avoid the most common compatibility and delivery assumptions.
01
Confirm the permitted UHF band, reader power, and local spectrum rules in the destination market.
02
Validate the exact TID and EPC write, password, and lock workflow with your own reader and software.
03
Test read range on the real mounting material and in the intended tag orientation.
04
Confirm sample quantity, production quantity, delivery destination, and required lead time.
05
Describe the authorized engineering, migration, research, or OEM use case so compatibility can be reviewed.
COMPLETE THE WORKFLOW
Need a matching EPC / TID reader-writer?
Use the companion UHF RFID reader/writer with supported Windows and Android workflows.
Understand, test and select changeable-TID hardware
Start with the standard memory model, then examine special behavior, prove it on your reader and check whether a standard memory bank would be the better design.
PRODUCT FAQ
Questions buyers ask before sampling
Is this a dry or wet RFID inlay?+
It is supplied as a dry inlay. It does not include the pressure-sensitive adhesive backing normally associated with a wet inlay.
Can the TID be changed?+
This special-purpose experimental tag is offered for supported TID programming. Confirm the exact writable range, commands, passwords and locking behavior with a sample and the intended reader.
Is a 10 meter read range guaranteed?+
No. The 0.1–10 m figure is only an indicative supplier-test range. Actual distance can be short and varies with reader power, antenna, orientation, surface, interference and settings.
Can I order samples?+
Sample availability and quantity are confirmed by email. Include the destination country, reader model, software environment, and expected production volume.
What is the lead time?+
The listed lead time is within 30 days after order confirmation, subject to quantity, destination, and final commercial confirmation.
◇
For authorized testing, research, migration, and OEM integration only. Not offered for impersonation, unauthorized duplication, access-control bypass, counterfeiting, or toll and parking evasion. Buyers must confirm applicable law, spectrum rules, standards, and third-party rights.
REQUEST A SAMPLE OR QUOTE
Tell us about your application
Share the quantity, destination, reader or host system, and relevant technical requirements. Company and authorized use case remain optional.
