Before ordering UHF RFID handhelds for more than one country, match each destination to the exact hardware variant, supported radio configuration and applicable compliance documents. A common model name or a country option in an application is not enough to establish that every delivered unit is suitable for every site.
Consider an integrator preparing otherwise similar inventory workflows for a UK site and an Australian site. The same application screens and tag identifiers might be used at both locations, but the equipment and deployment conditions still need separate confirmation. This is an editorial purchasing scenario, not a customer case, a regulatory approval or an AIDC GO test result.
Put the deployment country next to the order line
“International project” is not a usable radio configuration. Name the country where each unit will transmit, the proposed site and whether devices may later move between countries. Keep the quantity for each destination separate, even when the sales model name is identical.
Ask the supplier to identify the full orderable part number and hardware regional variant, not just the family name on the quotation. Then request the documents and permitted configuration corresponding to that variant and destination. A description such as “UHF RFID” identifies a technology family; it does not establish the applicable operating conditions for a particular shipment.
For integrated equipment, begin with RFID mobile computers. If the project will retain an existing host, use the RFID sled category and identify both the reader and host. The host's operating system or cellular region is not evidence for the RFID transmitter's regulatory configuration.
Read the local rule as a set of conditions
Country comparisons should not reduce a regulator's requirements to one frequency label. The applicable entry may distinguish device use, transmit-power basis, channel conditions and other restrictions. Retain the relevant entry and its document date, rather than copying a number from an unversioned worldwide chart.
For the UK example, Ofcom's IR 2030, published 7 April 2026 and checked for this article on 11 September 2026, includes separate RFID entries and columns for frequency, maximum transmit power and channel conditions. The purchasing lesson is to identify the applicable entry as a whole; this article does not select an operating band or power setting for a proposed handheld. Source: Ofcom IR 2030
For the Australian example, ACMA lists RFID among devices covered by its low-interference-potential-devices guidance. A class licence does not require an individual application or fee, but its rules still apply; additional equipment, electromagnetic-energy and labelling rules can also apply. “Licence exempt” therefore does not mean “no conditions.” Source: ACMA LIPD class licence guidance
These examples are not a complete compliance assessment for either country. Before supply or use, the responsible supplier or local compliance adviser should confirm the current requirements for the actual equipment and intended use. Requirements and documents can change after the dates recorded here.
Reconcile hardware, software and documents
Treat the quotation, delivered label, configuration screen and supporting documents as four views of the same proposed system. If their identifiers do not line up, ask for the explanation before accepting the shipment or changing a setting.
| Item to reconcile | Evidence for the proposed shipment | What it does not establish by itself |
|---|---|---|
| Hardware variant | Full part number, model and regional designation on the quotation and delivered unit. | A family name does not establish that another regional variant is interchangeable. |
| Software configuration | Supported region settings and the documented method for checking the selected configuration on that variant. | A visible country menu does not establish permission to switch an unqualified unit. |
| Applicable documents | Model and variant references, document revision, destination and conditions covered. | A report for a different model or accessory arrangement does not establish coverage of this shipment. |
| Site acceptance record | Delivered identity, selected configuration, agreed operating conditions and application observations. | A successful tag read does not establish regulatory compliance or complete business acceptance. |
A missing configuration can also affect operation. Zebra's RFD40 Product Reference Guide, MN-004189-04EN Rev. A, lists an unset RF region as one possible reason the sled does not read tags. That is a specific manufacturer's troubleshooting example, not evidence that AIDC GO RX or SX models use the same tool, allow the same settings or can be changed freely between regions. Source: Zebra RFD40 Product Reference Guide
Do not resolve a mismatch by trying country settings until tags respond. Obtain the documented configuration for the supplied hardware and destination first. If the supplier says that one variant covers several countries, ask which countries, under which settings and documents, and who controls any permitted change.
Plan for shipment changes and replacement units
Return to the two-site example. A replacement reader urgently sent from another warehouse might have the same family name but a different part number. The receiving team should compare the replacement identity with the approved site configuration before putting it into service. A working application login would not resolve a radio-variant mismatch.
Keep the configuration record with the site equipment record, not only in the original buyer's email. Record the delivered unit identity, firmware and configuration-tool versions where relevant, the selected region and the document references supporting the decision. These are recommended project records, not a claim that AIDC GO provides an automatic compliance inventory.
If an antenna, accessory or software revision changes, ask whether the existing documentation and setup instructions still apply. Do not infer that every modification changes an approval, or that none do. The relevant question is whether the actual modified configuration remains within the documented scope.
Supply responsibilities also matter. ACMA's guidance separates radiocommunications technical standards, electromagnetic-energy requirements and labelling obligations in the General Equipment Rules. Buying a unit and configuring it are not substitutes for checking the applicable supplier obligations. Source: ACMA, check the rules to follow
Test the inventory task after the configuration is established
Once the equipment and regional setup are confirmed, evaluate the intended task using representative tags and the agreed working area. Retain the hardware identity, software settings, tag type, placement and application result. This makes a later comparison meaningful without turning a field trial into a regulatory certification exercise.
Reading one test tag only shows that a read occurred under those conditions. The inventory and asset-tracking solution helps connect the hardware direction to the application task. Use the UHF RFID read-range guide for working-area and tag observations rather than treating country configuration as a promise of distance or completeness.
Send AIDC GO the deployment-country list, quantities by site, intended task, tag information and proposed integrated-reader or sled direction. Include any required document references and plans to transfer or replace equipment across borders. Use Integration Support for the exact model, interface and version questions, then contact AIDC GO to confirm the proposed supply configuration.
The useful procurement outcome is a traceable match between destination, delivered hardware, supported settings and applicable documents. No statement in this guide establishes global AIDC GO approval, an unrestricted region-switching capability or a certification that has not been supplied for the specific model.