Skip to main content
Tuturuuu links an Inventory product/unit/warehouse combination to a Square item variation at the selected Square location. The link stores both sides’ last known state so two-way sync can distinguish a safe one-sided change from a conflict.
Synchronization controls are locked by default. Open Payments → Catalog sync, review the selected environment and linked records, then use the compact edit control to enable an intentional sync action.

​
Choose the right direction

Confirm Sandbox or Production before every sync. A Production catalog sync changes the real seller catalog and inventory counts even though it does not charge a card.

​
Non-destructive Square behavior

Tuturuuu deliberately does not call a Square catalog delete endpoint and does not archive Square catalog objects as part of sync.
  • Square-only variations remain attached when Tuturuuu updates a known item.
  • A Square-side deletion marks the local link as Square deletion preserved for review; it does not delete the local product or stock.
  • A simultaneous local and remote edit becomes Review conflict.
  • A failed row stays visible as Sync error with its last error.
  • Only records that the operator explicitly synchronizes are created or updated.

​
What is synchronized

Do not manually multiply or divide prices before sync. Enter and review the human-readable amount in Tuturuuu; the integration converts it to Square’s currency-aware integer Money representation. If USD 10.00 appears as USD 0.10 or USD 1,000.00, stop and investigate before another sync.
Tuturuuu Inventory stores major-unit prices with exact decimal precision and converts them to Square’s currency-aware integer Money amount at the provider boundary. Physical stock remains whole-unit inventory. A fractional stock count is still held for review instead of rounded.
Those links were imported before cent-level Inventory prices were supported. Square was not changed and the previous local price was preserved. Open Manage sync, choose Import from Square, and run one read-only import. Tuturuuu applies the exact Square price and clears the legacy hold.

​
Safe first synchronization

1

Verify the environment and location

Open Payments → Connect & set up and read the Square summary. Confirm the environment, seller connection, and location. Return to Catalog sync and confirm the same environment badge.
2

Start with one clearly labeled demo item

In Sandbox, use a unique demo name and SKU. In Production, use an owner- approved item and review its current Square record before any action.
3

Import from Square first

For a seller with an existing Square catalog, choose Import from Square. Review the summary and linked record list before publishing anything back.
4

Inspect every linked row

Match the Tuturuuu product, Square item and variation name, SKU, shortened variation ID, origin, status, and last synchronized date. A processed count is not proof; the visible linked row is the evidence.
5

Publish a controlled Tuturuuu change

Change one field on the demo record, then choose Publish to Square. Verify the exact field and physical count in the Square Dashboard.
6

Run two-way comparison

After both one-way directions work, choose Two-way sync. Review any conflict rather than repeatedly syncing until it disappears.

​
Read the sync summary

Counts describe operations, not unique products. One imported product can update both its variation and its physical stock row, so five linked products can legitimately produce ten imported changes. Use the linked-record list to count actual relationships.

​
Webhook-driven updates

The webhook subscription includes:
  • catalog.version.updated, which asks Tuturuuu to reconcile catalog changes;
  • inventory.count.updated, which asks Tuturuuu to reconcile physical counts.
Square might not emit an inventory event when a count is written to the same value it already had. To verify this path in Sandbox, change a demo count to a different value and then restore it intentionally. Webhooks can be duplicated or delivered out of order. A duplicate event should not create a duplicate product, link, stock change, or checkout.

​
Conflict-resolution worksheet

For each conflict, record:
Never solve a price or stock conflict by deleting the Square object. Preserve the audit trail and apply one approved direction.

​
Production catalog gate

Before enabling Production sync actions:
  • the Square owner confirms the seller and location;
  • Sandbox import, publish, two-way, and conflict tests pass;
  • all demo names and SKUs are unmistakable;
  • the visible price and currency match exactly on both sides;
  • the physical count belongs to the selected location;
  • every linked row is Linked or has a documented review decision;
  • the operator understands that Production sync changes real catalog and stock data but never deletes Square objects.