A merchant planning the next range needs one competitor's assortment placed side by side with its own. In this case, the immediate task is to compare a competitor's product assortment with your own. The output should mark where the two overlap, where the merchant is thinner and where specifications differ.
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 compare a competitor's product assortment with your own.
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 competitor's categories with variants, options and published specifications, the merchant's corresponding SKUs, identifiers, specification units and currency per line, and notes wherever a defining attribute is missing]. Line the two ranges up on the attributes that carry the buying need rather than on category names, marking direct overlaps, the categories where the merchant carries fewer variants, and any specification stated in units that cannot be converted into the merchant's own units.
Return a competitor change log and specific opportunities to investigate verified against the supplied catalog 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.Split the work into input, judgment, and deliverable phases. Verify each step's output before moving to the next.
List the competitor's categories with their variants, options and published specifications alongside the merchant's corresponding SKUs, keeping the identifier, the unit used for every specification and the currency on each line and noting wherever a defining attribute is missing.
Line the two ranges up on the attributes that carry the buying need rather than on category names, marking direct overlaps, the categories where the merchant carries fewer variants, and any specification stated in units that cannot be converted into the merchant's own units.
Deliver a side-by-side comparison with opportunities ranked by the merchant's own demand evidence, reconcile the count of compared lines against both source lists, and list every competitor line left unmatched with the reason it could not be paired.
Cover decision rules, frequent misunderstandings, and required inputs so the team aligns on prerequisites before execution.
On the attributes that carry the buying decision, meaning size, pack and any specification written in comparable units. Pairing on product name alone produces matches that look obvious to everyone yet compare nothing that influences whether a shopper chooses between them.
Nothing on its own. It may be unmet demand or a deliberate narrowing of focus, so the row is recorded as a difference worth investigating and checked against the merchant's own sales and support history before anyone recommends adding products to that category.
As unmatched on that attribute with both original values quoted side by side. Converting through an assumption would create a comparison the records cannot support, whereas a kept gap stays visible and can be resolved once better sourcing data arrives.
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.