Make the hardware decision from the workflow outward.
Selection guides, technical foundations and deployment checklists for software companies, system integrators, AIDC solution providers and IoT project teams.
Follow a two-unit warehouse return from authorization and parcel receipt to item inspection and approved disposition without confusing a successful scan with sellable stock.
Trace receiver coordinates, map and layer reference systems, orthometric and ellipsoidal heights, and the exported GIS record through a bounded field-data example.
Trace an NFC tag identifier from the device to the correct asset record, avoid truncated-ID collisions, and control tag replacement without treating a UID as authentication.
Calculate whether a barcode or QR symbol and its quiet zone fit the effective print area, then verify paper output, decoded data and project quality separately.
Verify the source location, item, tracking identity, quantity and destination tote in one warehouse picking task, including mismatch and short-pick exceptions.
Evaluate how a field tablet keeps project drawings available offline while preserving sheet identity, revision status, annotations and post-sync decisions.
Use a barcode handheld to identify each pallet by SSCC, match it to the expected shipment record and route duplicates, unexpected units and content differences correctly.
Connect RFID tool reads to authorised check-out, return and missing-tool decisions without confusing a tag count with asset identity or custody status.
Separate scanner repeat controls from application transaction rules so rapid barcode scanning suppresses accidental duplicates without losing intentional repeats.
FACT-LIMITED GUIDANCE
What these guides use—and what they do not assume.
The library uses AIDC GO’s approved product catalogue, 140-field public specification library, current technical-reference PDFs and published workflow content.
It does not invent performance, certifications, SDK/API or MDM support, warranty, MOQ, lead time, customer results or commercial commitments. Project suitability remains subject to configuration, region, application and validation.
NEXT STEP
Turn the research into a project brief.
Bring the workflow, physical inputs, application boundary and open questions.