Back to topic
Spark playbook scenarios · Spark: AI Store Assistant

Create a sale page with clear eligibility and terms

A sitewide sale is running but the exclusions sit only in a spreadsheet, so shoppers argue at checkout. In this case, the immediate task is to create a sale page with clear eligibility and terms. The workflow should produce a page draft placing the qualifying range, exclusions and end date beside the prices, each term checked against the merchant's records.

Topic
Promotional Landing Pages
Target keyword
shopify sale landing page
Copyable AI prompt

A prompt you can drop directly into Spark

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.

ai-prompt.txt
Act as a Shopify operations specialist.
Help me create a sale page with clear eligibility and terms.
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: [discount rules as recorded, marked-down collections and variants, excluded products with reasons, sale start and end dates in the store timezone, and supported prior prices of featured items].

Draft the page so the qualifying range, exclusions and end date sit beside the displayed prices, keep products that are not actually marked down off the page entirely, and show a prior price only where the merchant's records and local comparison rules support it.
Return the page draft and launch checklist, then verify every stated term against the supplied records 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.
Use in Spark
How to solve

A recommended resolution workflow

Split the work into input, judgment, and deliverable phases. Verify each step's output before moving to the next.

01

Step 1

Collect the discount rules as recorded, the collections and variants actually marked down, the excluded products with reasons, the sale's start and end dates in the store timezone, and the prior prices of featured items where the records support showing them.

02

Step 2

Draft the page so the qualifying range, exclusions and end date sit beside the displayed prices, keep products that are not actually marked down off the page entirely, and show a prior price only where the merchant's records and local comparison rules support it.

03

Step 3

Deliver the page draft with a launch checklist and a defined end state including whether prices revert automatically, verify every displayed price and stated term against the supplied records, and confirm no excluded or unmarked product appears on the page.

FAQ

Common questions when running this scenario

Cover decision rules, frequent misunderstandings, and required inputs so the team aligns on prerequisites before execution.

Why keep unmarked products off the sale page?

Presence on the page implies participation, and shoppers argue the discount at checkout when it does not apply. Removing them is cheaper than fielding the disputes. If business reasons require showing one, it is labelled clearly as not participating beside its price.

How is the end-of-sale state verified?

The checklist specifies the page state and price revert behaviour at the end date, and the revert is tested before launch. A page left running advertises expired terms. Manual steps in the end state are assigned a named owner, automatic ones are checked against the records.

How are displayed sale prices checked?

Each displayed price is matched to the recorded discounted price for that product or variant before launch. A page price that disagrees with checkout creates disputes and support load. Any mismatch blocks that item block from publishing.

Related scenarios

Continue with adjacent or same-topic scenarios

Start with scenarios under the same topic, then expand into cross-topic matches suggested by similarity.

Next step

Want these AI scenarios embedded directly into daily operations?

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.