Back to topic
Spark playbook scenarios · Spark: AI Store Assistant

Consolidate stock information for operational decisions

Each team keeps its own stock file, and the figures disagree because nobody has agreed which source wins. In this case, the immediate task is to consolidate stock information for operational decisions. The workflow should produce an inventory visibility report and refresh requirements traced back to each source's own records.

Topic
Inventory Management and Visibility
Target keyword
shopify inventory management app
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 consolidate stock information for operational decisions.
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: [every stock data source with its SKU identifiers and location scope, the SKU mapping linking the sources, the agreed precedence order for conflicts, and each source's update cadence and last successful refresh]. Merge the sources into one position per SKU and location by applying the agreed precedence, keep the losing figure and its source visible beside the consolidated one rather than discarding it, and flag any SKU whose mapping is missing or whose source has stopped refreshing instead of filling the gap with another source's number.
Return an inventory visibility report and refresh requirements 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.
Use in Spark
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.

01

Step 1

Collect every stock data source with its SKU identifiers and location scope, the SKU mapping that links the sources together, the precedence order the merchant has agreed for conflicting figures, and each source's stated update cadence and last successful refresh.

02

Step 2

Merge the sources into one position per SKU and location by applying the agreed precedence, keep the losing figure and its source visible beside the consolidated one rather than discarding it, and flag any SKU whose mapping is missing or whose source has stopped refreshing instead of filling the gap with another source's number.

03

Step 3

Deliver an inventory visibility report carrying the consolidated position, the conflicts resolved and the exceptions, add refresh requirements naming each source's true interval and owner, and reconcile the row count with the SKU master and confirm every source's last refresh timestamp before publishing.

FAQ

Common questions when running this scenario

Cover decision rules, frequent misunderstandings, and required inputs so the team aligns on prerequisites before execution.

Which source wins when two disagree?

The one the merchant placed highest in the agreed precedence, applied consistently to every SKU and location. The losing figure is not deleted but shown beside the consolidated value with its source, because a source that is quietly always overridden is usually a broken feed rather than a simply wrong one.

How often can the consolidated view refresh?

No faster than the slowest upstream source actually delivers, and the true interval is shown rather than the intended one. If a source has missed its cadence, the view carries the older timestamp and lists the affected SKUs, so nobody reads a merged figure as current.

Should every SKU appear in the merged view?

Only SKUs whose mapping is complete across the sources. Unmapped and archived SKUs go to an exceptions list, retrievable for earlier reporting periods but kept out of operational decisions, since a merged figure built on a guessed mapping is worse than no figure at all.

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.