Product we built · Ongoing
TAGeX is an asset capture application that turns photographs of commercial equipment taken on site into clean, reviewed inventory records in NetSuite, and then tracks where each item physically ends up.
Overview
Asset capture for commercial liquidations and relocations. Someone walks a restaurant or hotel with a phone and photographs every asset; TAGeX turns that raw capture into clean inventory data, writes it to NetSuite as a real inventory record, and tracks where each item physically lands on a warehouse shelf.
Capabilities
Gallery
How we delivered it
Liquidation and relocation capture happens on site, on a phone, by whoever is walking the floor — not by a data-entry specialist. The raw output is photographs, while NetSuite needs clean, structured inventory records, and the two have to end up agreeing.
We made item status the spine of the product. Every item moves through documenting, in review, data scrubbing, submitted and edited, and the status decides which fields are editable, who may edit them, and whether the item exists in NetSuite yet.
Mobile capture in the field, a staged review and scrubbing pipeline, role-aware field permissions, and a NetSuite integration that treats NetSuite as authoritative the moment an item is submitted.
A submitted item's bin move goes to NetSuite first and only lands locally if NetSuite accepts it, so the app and the system of record cannot silently disagree about where an item is.
TAGeX carries commercial equipment from a customer's site to a warehouse shelf. When a restaurant or hotel is liquidated or relocated, someone walks the site photographing every asset. TAGeX turns that raw capture into structured inventory data, pushes it to NetSuite, and tracks the item's physical location.
Items move through five stages: documenting, in review, data scrubbing, submitted, and edited. The status is the spine of the product — it decides which fields are editable, who is allowed to edit them, and whether the item exists in NetSuite yet.
Status drives real behaviour rather than just labelling a row. Once an item is submitted it exists in NetSuite, so a bin move goes to NetSuite first and only lands in the local record if NetSuite accepts it. The two systems cannot silently disagree about where an item is.
Writing locally first and syncing later would let a warehouse move succeed on the floor and fail in the system of record. Making NetSuite authoritative for submitted items removes that class of drift entirely.
Liquidators, asset recovery firms and relocation specialists who move commercial equipment at volume and need it reconciled against NetSuite. It suits operations where the capture happens in the field, on a phone, by someone who is not a data-entry specialist.
FAQs
The local record does not change. For a submitted item the move is sent to NetSuite first and only applied locally once NetSuite accepts it, so the app never shows a location NetSuite disagrees with.
No. Item status determines which fields are editable and which roles may edit them, so data that has already been scrubbed and submitted cannot be quietly altered.
No. The capture step is designed for someone walking the site with a phone. The structuring and review work happens afterwards in the data scrubbing and review stages.
Tell us what you want to build and we will help you scope it, plan it and ship it.
