Use case
Contractor Data Sync setup and Logs handoff
Contractors: configure Data Sync (Google Sheets → Shopify) on a client store, prove preview/apply in Logs, then hand off Settings ownership—one plan per store.
Highlights
What you get out of this flow
Outcomes you can expect when you run this playbook on Shopify.
- Scoped to one Shopify store and its plan row limits
- Preview → apply → Logs as the acceptance checklist
- Handoff packet: sheet link, mapping, schedule, owners
Why handoffs fail without Logs
Merchants inherit broken schedules when contractors leave without proof. A Logs-backed handoff shows the last successful run and who owns the sheet.
How it works in EShopSet
Enable Data Sync, map columns, match keys, run manual preview/apply, confirm Logs, optionally set schedule, then write a one-page handoff. Billing remains on the store’s plan.
Example: two-week catalog cleanup
A contractor imported 2,400 SKUs on Growth, fixed 37 barcode errors after preview, applied clean, scheduled daily, and left a Loom + sheet with match-key rules. Agency ops owned Logs thereafter.
Playbook
- Confirm store plan and row needs.
- Connect sheet; map; match keys; policies.
- Preview; fix; apply; save Logs evidence.
- Document schedule and sheet owners.
- Revoke contractor access after acceptance.
What to measure
- Preview error count at handoff = 0 critical
- Handoff doc completed before access revoke
- First post-handoff scheduled run success
