A merchant wants to keep taking orders on items waiting for restock, but only where the supplier can deliver by the promised date. In this case, the immediate task is to define when eligible products may remain available on backorder. The workflow should produce an item-by-item decision plus the wording that must appear at checkout for anything kept on sale.
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 when eligible products may remain available on backorder.
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: [sellable and committed quantities per product awaiting replenishment, supplier replenishment dates with their past reliability record, inbound purchase order quantities, and the delivery promise stated per destination]. Decide item by item that a product may stay purchasable only where a confirmed replenishment date exists, the supplier's record supports it and the date lands inside the promise made to the customer, set the quantity exposed to no more than the inbound quantity on record, and hold every product failing one of those tests with the failed condition named.
Return a backorder policy with eligible items and customer wording 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.
Review, per product waiting on replenishment, the sellable quantity and the committed stock, the supplier's confirmed replenishment date with their record of meeting past dates, the inbound quantity already on a purchase order, and the delivery promise the merchant states for that product's destination.
Decide item by item that a product may stay purchasable only where a confirmed replenishment date exists, the supplier's record supports it and the date lands inside the promise made to the customer, set the quantity exposed to no more than the inbound quantity on record, and hold every product failing one of those tests with the failed condition named.
Deliver a backorder policy listing each product with its decision, the exposed quantity, the expected ship date and the condition that would reverse the decision, give the exact checkout wording each approved product must carry including the expected ship timing, and check that every product left on sale has that wording attached in the supplied channel settings.
Cover decision rules, frequent misunderstandings, and required inputs so the team aligns on prerequisites before execution.
When a confirmed replenishment date exists, the supplier has met dates before, and that date still lands inside the promise made to the customer, with anything short of all three held. A supplier's verbal estimate with no date on record does not qualify.
The expected ship timing the merchant states for that product, shown at checkout and in the confirmation, because silence about delay is what turns a backorder into a complaint. Where a channel cannot display it, the product is held rather than sold.
Yes, at the inbound quantity already on a purchase order, so sales cannot exceed what is arriving. Unlimited backorders build a queue the supplier may not fill, and the cap is raised only when a further confirmed receipt is recorded.
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.