A target market has defined requirements, but the supplier files on hand were never checked against them. In this case, the immediate task is to organize product compliance evidence for a target market. The workflow should produce a sourcing feasibility matrix and follow-up questions, marking each requirement as evidenced or pending confirmation.
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 organize product compliance evidence for a target market.
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 target market's requirement list, each candidate product's specification sheet, supplier test reports, declarations and labelling artwork with their issuing body and issue date, and the product identifier shown on each document]. Mark a requirement evidenced only when a document names that product or the material and model scope it declares, answers the requirement in the issuer's own wording and is still inside its stated validity period, marking everything else pending confirmation and never writing compliance for a requirement whose evidence names a different product, model or production batch.
Return a sourcing feasibility matrix and follow-up questions 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 target market's requirement list as supplied by the merchant, each candidate product's specification sheet, the supplier documents on hand including test reports, declarations, labelling artwork and origin records, and the issuing body and issue date recorded on each document, matching one requirement at a time to a named document.
Mark a requirement evidenced only when a document names that product or the material and model scope it declares, answers the requirement in the issuer's own wording and is still inside its stated validity period, marking everything else pending confirmation and never writing compliance for a requirement whose evidence names a different product, model or production batch.
Deliver a sourcing feasibility matrix with one row per requirement carrying the requirement text, the linked document reference, the evidence status and the exact question still outstanding, add a follow-up question list, and reconcile the requirement count in the matrix with the merchant's requirement list before it is published.
Cover decision rules, frequent misunderstandings, and required inputs so the team aligns on prerequisites before execution.
A document counts only when it names the product it was issued for and the requirement it answers, and it stays valid only inside its stated validity period. A report for a similar model, an expired certificate or a supplier's own claim is recorded as pending confirmation, never as compliance, because the matrix is what a later market review will be judged against.
It is listed as pending confirmation together with the question that would close the gap, so it is neither a failure nor a pass. Absence from the merchant's list is not permission either: an unlisted requirement still has to be checked against current official sources before any conclusion about the market is stated.
Only within the scope the report itself declares, meaning the same material, model and production batch, and each product covered is still listed as its own row so the evidence can be checked per requirement. Where the scope wording is ambiguous the product is marked pending confirmation rather than assumed covered.
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.