Connect once. Inspect changes when they matter.
- Connect Square. CatalogTrail requests Items read and Merchant profile read—not catalog write access.
- Build history automatically. Supported Square catalog events and recurring checks create saved Item Library versions after connection.
- Review the record. Browse by item, follow its timeline, compare versions, and export reference data for inspection or manual recreation.
Designed for changes that are hard to reconstruct
CatalogTrail records supported item names, descriptions, variations, SKUs, pricing, categories, taxes, modifier assignments, availability, and deletion state. It groups related field changes around the item instead of forcing you to interpret a stream of raw API events.
What Square provides—and what CatalogTrail adds
Native Square controls
- Manual Item Library exports before bulk changes. Square recommends keeping a distinct pre-change copy.
- Archive and unarchive to preserve items intentionally removed from active use.
- Stock-adjustment history for quantity changes on certain plans.
CatalogTrail's additional record
- Automatic saved versions after supported catalog changes.
- Readable item-level history and saved-version comparison.
- Last recorded setup retained when an item is deleted.
- Reference CSV and technical JSON exports.
Clear safety boundaries
CatalogTrail cannot change your catalog, attribute every edit to a named staff member, or recover history from before you connected it. It does not store inventory quantities, payments, customers, employees, payroll, or banking data.
Start without a call
Explore the fictional product demo first, then connect Square and confirm the initial saved version. History becomes useful from that point forward. See the current self-service offer on the pricing page.