V Vendor OS

Square-connected TCG shops

Synchronize reviewed SKUs, not ambiguous guesses.

VendorOS guides Square setup, surfaces mapping and inventory drift, and keeps the VendorOS SKU authoritative while preserving per-location stock and operational history.

Reviewed mappings

Connect the intended VendorOS inventory item to the correct Square item variation before automatic updates begin.

Issues-first reconciliation

Prioritize missing mappings, stock drift, and failed writes instead of forcing operators through every healthy record.

Location-aware changes

Keep store and storage-location quantities visible while Square remains connected to the right sellable item.

Connected workflow

Move from intake to a trustworthy record

  1. Connect

    Authorize the Square account and choose the locations VendorOS should manage.

  2. Review

    Confirm safe SKU mappings and resolve ambiguous or missing catalog relationships.

  3. Reconcile

    Monitor drift and failed writes, then use the guided recovery action for the affected item.

Common questions

What operators need to know

Does VendorOS overwrite Square automatically during setup?

No. The guided setup separates connection, mapping review, and synchronization so unsafe relationships can be resolved first.

Which identifier remains authoritative?

Every sellable item keeps a unique VendorOS SKU. A manufacturer UPC can be stored separately when it is safe to use as an alias.

What happens when stock differs?

VendorOS surfaces reconciliation issues with the affected location and mapping context so an operator can review the discrepancy.