Asquarete

Count a room in minutes instead of a shift.

Stock counts are done by hand, so they happen quarterly instead of weekly, and the number in the system drifts from the number on the shelf. Everyone knows the figure is wrong; nobody can afford the hours to fix it.

Get a feasibility read

What we build

  • A handheld app that sweeps a whole area and deduplicates the reads on-device
  • Reconciliation against expected stock, with found, missing and unexpected split out
  • Adjustments posted back to your system of record, not exported to a spreadsheet
  • An offline queue, so a count in a dead zone isn't lost

Hardware it runs on

Chainway C72
Handheld UHF reader for bulk sweeps
Chainway C5
Rugged terminal for mixed barcode and RFID
Zebra RFD40
Bluetooth sled paired to a Zebra terminal

Every device listed here is one we have written about or shipped against. If yours isn't on the list, the feasibility read covers whether it can be.

How it reaches your system of record

Reads are deduplicated on the device, resolved to products, and written into Odoo in batches over JSON-RPC. Odoo 18 and 19 do support UHF RFID natively, but only inside a narrow envelope — a Zebra RFD40, SGTIN-96 encoding, numeric-only serials and GS1-registered barcodes. This path exists for everyone outside it, and works the same way against a custom backend.

What you get

  • Android application, source included
  • Backend module or bridge service
  • EPC-to-product resolution scheme, documented
  • Handover notes covering the reader lifecycle

What it costs

A fixed fee, scoped after the feasibility read. You see the number before any work starts, and it doesn't move.

How an engagement runs

The work behind it

We publish the engineering, not just the sales page.

Case study · Chainway C72

Inventory counts from 4 hours to 11 minutes — Chainway C72 + Odoo, 8,000-SKU warehouse

A distribution warehouse ran cycle counts by hand against 8,000 SKUs. A Chainway C72 bulk-read pipeline with server-side dedup cut a 4-hour count to 11 minutes and posted adjustments straight into Odoo.

Guide · Chainway C72

Chainway C72 Android SDK Integration in Kotlin

Chainway's C72 sample code targets RFIDWithUHF, a class the SDK itself marks obsolete. Production integrations must use RFIDWithUHFUART, handle the trigger key event directly, and explicitly release the reader in onPause to avoid UART lock errors on the next launch.

Guide · Generic UHF handheld

Integrating UHF RFID Scan Data into Odoo

Odoo 18 and 19 support UHF RFID natively, but only with a Zebra RFD40 paired to a TCX-series device or Android phone, only SGTIN-96 encoding with numeric-only serials, and only GS1-registered GTIN-14 barcodes. Outside those three constraints — Chainway hardware, alphanumeric serials, non-GS1 products — RFID reaches Odoo through a dedup buffer and batched JSON-RPC against stock.quant.

Send us the device and the error

Model, SDK version, and what's failing. A written read within 24 hours, and nothing owed if it's a no-go.

Get a feasibility read