A loyalty tier is about to launch, but the proposal describes desirable customers in adjectives while the benefit budget only stretches so far. In this case, the immediate task is to define a VIP segment from explicit value criteria. The workflow should produce a customer segment table and interpretation guide showing who clears the agreed threshold.
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 define a VIP segment from explicit value criteria.
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: [customer order history with dates and values, the chosen value basis and currency, the proposed membership criteria with their thresholds, the refund treatment, and the benefit capacity of the tier]. Turn every criterion into a testable condition with an explicit operator, unit and window, apply the full set to each customer in the order the merchant states, record which criterion each customer cleared or failed, and flag any customer the criteria disagree about plus any value sitting exactly on a stated boundary instead of rounding it into or out of the tier.
Return a customer segment table and interpretation guide 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.
Collect the customer order history with dates and values, the value basis the merchant has chosen for the tier, each membership criterion proposed with the threshold attached to it, the benefit capacity that limits how many customers the tier can carry, and the currency and refund treatment used to compute the value.
Turn every criterion into a testable condition with an explicit operator, unit and window, apply the full set to each customer in the order the merchant states, record which criterion each customer cleared or failed, and flag any customer the criteria disagree about plus any value sitting exactly on a stated boundary instead of rounding it into or out of the tier.
Deliver a customer segment table and an interpretation guide naming the qualifying customers with the criteria they satisfied, compare the qualifying count against the stated benefit capacity and report the shortfall or overrun, and list near-threshold customers and conflicting criteria so the merchant can tighten the definition before the tier launches.
Cover decision rules, frequent misunderstandings, and required inputs so the team aligns on prerequisites before execution.
The merchant's rule decides whether the criteria are conjunctive or alternatives, and the page states which it applied; requiring every criterion tends to produce a small stable tier, while accepting any one produces a wide tier whose members differ in kind rather than in degree.
At the point the benefit budget can actually carry, worked back from the merchant's stated capacity rather than from a round number; the page reports how the qualifying count moves around the chosen threshold so the merchant sees the trade before committing budget.
They are listed as near-threshold with the gap to each criterion rather than silently dropped, because a boundary set without reference to the budget usually has to move, and those customers are the first ones the move affects.
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.