Enterprise›Integrations
Every POS. Two ways in.
Every point-of-sale and ERP system exports its item list and imports counts. TracStor Count reads any of those exports with no setup and writes counts back in any layout, so it works with your system on day one. Where a system has a public API, it also connects directly: products and stock in, counts out, with one click.
In the pilot Native connectors are built to each vendor's published API and tested against it; each is verified with a vendor test account before its first live store.
Integrations›Direct connections
Connect, pull, count, post.
Sign in with the system (or paste an API token), choose the store's location, and pull every product with its barcode, cost, price and stock. After the count, preview exactly what will be sent, send it, and retry only the lines that failed.
Square
Retail, restaurants, services
Counts are sent as physical counts at the time each shelf was counted; Square applies later sales on top.
Shopify
Retail and e-commerce
Counts are sent as cycle-count corrections, so sales made during the count stay applied.
Clover
Retail and restaurants
Clover takes a new stock level, so TracStor reads today's stock just before posting and applies the count's correction to it.
Lightspeed Retail (R-Series)
Retail
Posted through Lightspeed's own inventory counts, so the count shows in Lightspeed's history.
Lightspeed Retail (X-Series)
Retail
Posted as a Lightspeed stocktake, the path Lightspeed recommends to integrations.
Next: Heartland Retail, KORONA POS
Public APIs
Through files today; direct connections are next on the list.
Integrations›Through files
Your system's own import and export.
Item files in CSV, tab, pipe or fixed-width, from any system. Columns are recognised from the names systems actually use ("Item Lookup Code", "Variant Barcode", "Qty On Hand") or from the values themselves, and shown for a check. Counts come out in the layout your system imports: by item or by area, all lines or adjustments only, delimited or fixed-width.
| System | How it connects today | Direct connection |
|---|---|---|
| NCR Counterpoint | Item export in, physical count import out | Through an NCR reseller (the API is per merchant) |
| Epicor Eagle | Item export in, handheld upload file out | Partner program |
| Oracle Xstore / Retail Cloud | Files | With the retailer's IT team |
| Microsoft Dynamics 365 Commerce | Counting journal import | With the retailer's IT team |
| SAP S/4HANA | Files | Physical inventory documents, with the retailer's SAP team |
| Retail Pro Prism | Files | Per install |
| Toast, Revel, NCR Aloha | Files | Partner programs |
| Anything else | Any item export in, any count layout out | Ask us |
Integrations›Safe by design
Your POS only changes when you say so.
- Every posting is previewed line by line before anything is sent.
- Partial counts never touch items they didn't cover.
- Each line's result is kept; a retry sends only what failed, and can't apply anything twice.
- POS sign-ins are approved on the POS's own site; tokens are stored encrypted and never shown again.