01
Step 1
Gather the seasonal offer terms, the featured products with their stock status, the shipping cutoffs the merchant confirmed per destination, the campaign dates with timezone, and the chosen post-holiday page state.
Back to topic
Spark playbook scenarios · Spark: AI Store Assistant
Create a holiday promotion landing page
Holiday traffic needs its own page, and the last shipping date for arrival before the holiday is easy to bury. In this case, the immediate task is to create a holiday promotion landing page. The workflow should produce sections where shipping cutoffs and campaign dates sit with the offer, plus a checklist and a defined post-holiday state.
Topic
Promotional Landing Pages
Target keyword
shopify holiday 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 holiday promotion landing page.
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: [seasonal offer terms, featured products with stock status, confirmed shipping cutoffs per destination, campaign dates with timezone, and the chosen post-holiday page state].
Draft page sections so the shipping cutoffs and campaign dates appear alongside the offer rather than in a footer, give each featured product a predefined replacement or removal rule for when it sells out, and specify the post-holiday state, whether archived, redirected or updated for the next season.
Return the page draft and launch checklist, then verify the content 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.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.
02
Step 2
Draft page sections so the shipping cutoffs and campaign dates appear alongside the offer rather than in a footer, give each featured product a predefined replacement or removal rule for when it sells out, and specify the post-holiday state, whether archived, redirected or updated for the next season.
03
Step 3
Deliver the page draft with a launch checklist covering cutoffs, dates, featured products and the end state, verify every cutoff and date against the supplied records, and confirm each destination's cutoff shown is one the merchant actually confirmed.
FAQ
Common questions when running this scenario
Cover decision rules, frequent misunderstandings, and required inputs so the team aligns on prerequisites before execution.
Where on the page should cutoffs sit?
In the main sections alongside the offer, not buried in a footer. Cutoffs hidden at the bottom shift delivery questions onto support during the busiest period. At minimum they repeat near the product listing and the checkout entry.
What happens to featured products that sell out?
Each one carries a replacement or removal rule defined in the draft, executed automatically rather than edited ad hoc during the holiday. A sold-out hero product wastes peak traffic. The rule's execution is verified, not assumed.
How is a cutoff verified before publishing?
Every cutoff shown is matched destination by destination against the merchant's confirmed cutoff records. An estimated cutoff creates a delivery promise the store may not keep. Unconfirmed destinations show no cutoff and are flagged in the checklist for sign-off.
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.