ShopCadence guide

Using a Google Sheet as an operations view, not an accounting system

Keep managed order fields separate from staff notes.

A shared sheet can support handoffs and follow-up. One row per store/order ID gives the team a current operational view. Appending a new row for every change creates a history of duplicates rather than that view.

Separate ownership of columns

The workflow manages status, dates, currency, totals, quantities and safe item summaries. Staff own notes, assignees and follow-up. Refreshing an order must preserve those human columns.

Recover incomplete writes

A persistent checkpoint and overlap allow missed runs to catch up. If some writes time out, do not advance the overall watermark. One serialized runner avoids ordinary overlapping updates; duplicate keys and altered headers need a visible stop.

Keep the boundary clear

Order totals and statuses are not an accounting ledger. Currencies remain separate, refunds need their own financial treatment, and deleted store orders are not automatically removed from the sheet. Avoid default customer PII and write formula-like product names safely as text.