Your systems stay. Clarity agrees with them.
Clarity is not a replacement for your ERP, WMS, or order system. It reconciles what the tags actually say against what those systems believe, and hands the corrected picture back. Nothing gets switched off to make room for it.
Reader and hardware interoperability is covered separately on Partners.
Eight conversations, both directions.
An integration is not one pipe. It is a set of exchanges, each with its own shape and cadence, and the scoping conversation is mostly about which of these you need and how often.
What your systems tell us, so the record has something to reconcile against.
- Product catalog styles, SKUs, sizes, images, and prices, as a delta feed or a periodic full sync
- Stock ledger what your ERP believes is in each location, which is the number accuracy is measured against
- Expected shipments ASNs and carton manifests, so receiving has something to check against
- Markdowns and promotions price changes pushed through to the handheld in real time
What the tags actually say, returned to the systems that need to act on it.
- Count results the corrected item-level position after a cycle count, with adjustments per location
- Receipts and discrepancies what arrived against what was expected, ready for the claim or the DC conversation
- Transfers stock moved between sites, with the receiving location's ASN generated automatically
- Status changes faulty, wasted, reserved, or picked items excluded from stock before the next count runs
Each exchange runs at the speed the process actually needs.
- Real time reads, markdowns, order status, and anything a colleague is standing waiting for
- Scheduled catalog deltas, ledger syncs, and sales feeds on the timetable your systems can support
- Event driven a webhook when a carton is audited or a count completes, rather than a poll that mostly finds nothing
- Batch weekly or monthly full syncs where a delta feed is not available
Four transports, and you pick the one your IT team already supports.
The fastest integration is the one that uses a mechanism your team has run before. We would rather meet an older system on its own terms than make a modernization project a precondition of an RFID rollout.
REST
Documented endpoints across Store, Supply Chain, and Edge. The default where your systems can call out, and the only option that supports genuinely real-time exchanges.
Flat file
CSV and XML over SFTP, inbound and outbound, on a schedule. Unglamorous, universally supported, and still how a great deal of retail data actually moves.
Cloud storage
Drop files into blob storage and we collect them, or the reverse. Useful where your systems already publish to cloud storage and adding an endpoint is the harder path.
Webhooks
We push the event to you when it happens. Best where your side wants to react to a completed count or an audited carton rather than ask repeatedly whether one has happened.
The systems already running your business.
Clarity has been integrated to all of these in live retail environments. The category matters more than the brand, because the exchange is defined by what the system holds rather than by whose logo is on it.
Where the item is sold.
- ERP the system of record for product and stock, including SAP S/4
- OMS order management, for click-and-collect and ship-from-store fulfillment
- POS sales feeds, so sold items leave the expected position
- Pricing and promotions markdown files and promotion lists pushed to the floor
Where the item travels.
- WMS warehouse management, for expected shipments and receipts
- WCS and warehouse automation conveyor and sortation control systems, including Swisslog and SYNQ
- Third-party logistics where a 3PL runs the DC and the data has to cross an organizational boundary as well as a technical one
- Supplier systems for source tagging programs and inbound carton manifests
Specific customer architectures are covered under NDA in scoping, not on this page. If you want to know whether we have integrated to your exact stack before, ask and we will tell you plainly.
Some retailers get their own plugin.
Most integrations use the standard interfaces. Some do not, because a legacy system speaks a file format nobody else uses, or a business rule exists in one retailer and nowhere else.
For those, Clarity supports customer-specific plugins: handlers written against your data and deployed alongside the platform, rather than a fork of it. You get the behavior you need and still receive every release.
SFTP · CSV · delta04:00Synced
Blob · CSV · daily05:15Synced
REST · on completionLiveRunning
Webhook · per eventLiveRunning
Scoped as its own piece of work.
Integration is the part of an RFID program most often underestimated, so we price it separately and specify it before anything is built. You can buy it without buying a rollout.
Interface workshop
Your architects and ours, working out which exchanges you need, which transports your systems already support, and where the difficult one is.
Specification
Each exchange written down: direction, transport, format, cadence, and what happens when a file is late or a payload is malformed.
Build and test
Delivered against the specification in your test environment, with your data, before anything touches production.
Cutover
Planned, rehearsed, and reversible. An integration cutover that cannot be rolled back has not been planned properly.
Bring your stack to a scoping call.
Tell us what you run and how it likes to exchange data, and you will get a straight answer about what the integration involves before anyone quotes you for it.