Step 1
Collect the supplier specification sheets, the listing fields that must be populated, the target schema, and the brand and copy rules the merchant enforces, recording which sheet version and date supplied each value.
Supplier specification sheets cover the range, but they use the supplier's own wording and leave required listing fields empty. In this case, the immediate task is to create product listing drafts from supplier specifications. The workflow should produce a validated import draft with a row-level exception list, checked against the merchant's own sheets.
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 create product listing drafts from supplier specifications.
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 supplier specification sheets with their version and date, the required listing fields, the target schema, and the merchant's brand and copy rules]. Carry each stated specification into its listing field keeping the supplier's own figure and unit, adjusting wording to the merchant's stated style without adding facts the sheets do not contain, and flagging every record whose required field has no supplier value, whose values conflict between two sheets, or whose description makes claims the brand rules do not permit.
Return a validated import draft with a row-level exception list 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 supplier specification sheets, the listing fields that must be populated, the target schema, and the brand and copy rules the merchant enforces, recording which sheet version and date supplied each value.
Carry each stated specification into its listing field keeping the supplier's own figure and unit, adjusting wording to the merchant's stated style without adding facts the sheets do not contain, and flagging every record whose required field has no supplier value, whose values conflict between two sheets, or whose description makes claims the brand rules do not permit.
Deliver a validated import draft with a row-level exception list naming each open field, the sheet it came from and who can close it, then check the drafts field by field against the supplied specifications and the brand rules before any record leaves draft state.
Cover decision rules, frequent misunderstandings, and required inputs so the team aligns on prerequisites before execution.
Both values stay visible with their sources and the row waits for confirmation, because choosing one silently creates a listing nobody can verify later. Suppliers usually answer quickly when shown the two documents side by side, so the conflict is reported with sheet names rather than resolved by whoever noticed it.
No. Supplier wording is the source of facts, not the finished copy, so it is rewritten to the merchant's stated style and length while every claim stays traceable to the sheet. Descriptive flourish must not be added, nor may a stated limitation be softened, since that changes what the buyer is told.
They are listed with the field name, the sheets already checked and the person able to supply the value, and the record stays unpublished until those fields are closed. Nothing is filled from another product in the range, since materials and tolerances often differ within what looks like a single family.
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.