Step 1
Record each KPI in scope with its calculation definition, the source export or report it is read from, the baseline period chosen and the review cadence assigned to it.
Numbers get pulled ad hoc on request, so the team never knows whether the KPIs are drifting. In this case, the immediate task is to monitor operational KPIs against defined baselines. The workflow should fix KPI definitions, baseline period and cadence up front, then compare every current value with its own baseline and flag gaps needing action.
First replace every [bracketed] placeholder with real store scope and constraints, then add any actual records or data you have, and paste it into your preferred AI assistant or Spark agent. Spark will follow this page's workflow to produce structured output and verification steps.
Act as a Shopify operations specialist.
Help me monitor operational KPIs against defined baselines.
My store context is [describe the business, products and target audience].
My scope is [specify the affected products, pages, customers or reporting period]. Use these inputs: [the KPI list with each definition, the source export or report it is read from, the baseline period, the threshold, the owner and the assigned review cadence].
Compare every current value against its own baseline using that fixed definition, mark the direction and size of the gap, and mark a KPI unmeasurable rather than flat when its source holds no value for the period.
Return a KPI monitoring sheet with thresholds and owners for the specified task.
Show the relevant evidence or before-and-after examples and explain how I can verify the result.
If essential data is missing, ask for it and mark unsupported conclusions as unknown.
Do not invent metrics, product claims or customer facts.
For any publication, message, account or store change, use only connected tools within my explicitly authorized scope and report success only after verification; otherwise provide the draft or proposed steps.Split the work into input, judgment, and deliverable phases. Verify each step's output before moving to the next.
Record each KPI in scope with its calculation definition, the source export or report it is read from, the baseline period chosen and the review cadence assigned to it.
Compare every current value against its own baseline using that fixed definition, mark the direction and size of the gap, and mark a KPI unmeasurable rather than flat when its source holds no value for the period.
Deliver a monitoring sheet with one row per KPI carrying its current value, baseline, gap, threshold, owner and next review date, then reconcile the extracted values against the source exports and list any KPI whose definition changed since the last cycle.
Cover decision rules, frequent misunderstandings, and required inputs so the team aligns on prerequisites before execution.
The same KPI name can be calculated several ways, and a change of definition looks like a change in performance. With the definition fixed, a gap means the store moved rather than the arithmetic.
Mark the KPI unmeasurable and name the missing source. Carrying the previous value forward would show a flat line that nobody produced.
No. Match the cadence to how fast the metric moves, so a metric that shifts weekly is not watched daily and one that breaks overnight is not reviewed monthly.
Start with scenarios under the same topic, then expand into cross-topic matches suggested by similarity.
Ciwi Spark builds Shopify-native AI tools and agents around the workflows merchants actually run: research, ads, translation, and customer support. Stop rewriting the same prompts by hand.