Configure Settings once per app

Highlights

What you get out of this flow

Outcomes you can expect when you run this playbook on Shopify.

Domain, brand, mapping, and schedules in one pass per app
Prevents “empty Overview” syndrome
Hand off cleanly to teammates via documented settings

Why settings-first beats KPI-first

Empty charts usually mean incomplete Settings—not a broken product. Spending 45–60 minutes across three apps up front saves weeks of “why is this blank?” messages.

How it works in EShopSet

Each app exposes Settings beside Overview and Logs. Set SEO domain/locale/limits, AI Presence brand and keywords, Data Sync mapping and cadence. Revisit only when the business changes (new market, new sheet, plan upgrade).

Example: agency handoff

An agency configured Settings for a client, exported a 1-page settings checklist (domain, 40 SEO keywords, 25 AI prompts, sheet ID + mapping). The merchant’s ops lead needed ~10 minutes/day thereafter—mostly Overview and Logs—not reconfiguration.

Playbook

Block one setup meeting for all three Settings pages.
Write values in a shared doc as you save.
Trigger a sync/preview to validate.
Restrict who can edit Settings vs who reads Overview.
Re-open Settings only for plan limit or catalog structure changes.

What to measure

Time from install → first meaningful Overview
Settings change frequency (should be low)