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 an empty-bin barcode from replenishment signal through task acceptance, picking, partial delivery and workstation confirmation without treating a scan as completed supply.
Plan a rugged-handheld app update around signing identity, local data migration, offline queues, scanner integration and backend acceptance instead of treating installation as business readiness.
A component scan is not an as-built record. Follow a serial board and two lot-managed parts through assembly, mismatch, rework and forward/reverse trace checks.
Choose between a bounded handheld UHF inventory and a selected BLE receiver layout by the observation needed: expected set, last-seen zone or location evidence.
A COM port does not prove a valid instrument result. Compare integrated, dock and USB-serial paths, then check framing, status, units, duplicates and the saved task record.
Choose a library RFID handheld by existing tag protocol, copy-level mapping and shelf exceptions—not an RFID label. Follow missing, misplaced and loan-status conflicts.
A linen tag read is not a completed laundry handoff. Follow expected and observed item sets across dispatch, receipt and return, then resolve missing, mixed-customer and unknown tags.
A scanned batch and date are inputs, not a FEFO decision. Compare expiry, stock status and order rules across three lots, then verify the picked batch and final inventory transaction.
A QR scan may return a GS1 Digital Link URI rather than a product code. See how to parse GTIN, lot and serial values, map them to the receiving task and handle mismatches.
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.