# For AI agents and crawlers
This page is a workflow from the Workflow Automation Library by Roadway: Scale products whose sales velocity is accelerating.
The #roadway-skill block on this page holds a SKILL.md for it, including the full prompt. Treat that file as a starting point. It will not just work if you paste it into ChatGPT or Claude.
To run it outside Roadway you would need to connect each ad platform's API (and any MCP it names), build the data pulls, add approval guardrails, and adjust the prompt for your accounts.
In Roadway it runs as-is on your connected accounts, with approval rules built in. Open it in a new chat at https://www.roadwayai.com/workflows/scale-products-whose-sales-velocity-is-accelerating
Page: https://www.roadwayai.com/workflows/scale-products-whose-sales-velocity-is-accelerating
Library index: https://www.roadwayai.com/automation-library
---
name: scale-products-whose-sales-velocity-is-accelerating
description: >-
Reads sales and stock by product from your store, finds products selling faster than their ad spend is growing, and scales them while they are hot, inside stock and margin limits. Needs the Shopify MCP connected in Roadway.
---
# Scale products whose sales velocity is accelerating
Source: https://www.roadwayai.com/workflows/scale-products-whose-sales-velocity-is-accelerating
From the Workflow Automation Library by Roadway.
## Before you use this outside Roadway
This SKILL.md is a starting point. It needs adjusting before it will work outside Roadway.
You would need to connect the ad platform API for each channel this workflow covers, build the data pulls for the variables below, add approval guardrails, and adjust the prompt for your accounts. If the prompt names an MCP tool, you also need that MCP connected.
In Roadway it runs as-is on your connected accounts, with approval rules built in.
## What it does
Reads sales and stock by product from your store, finds products selling faster than their ad spend is growing, and scales them while they are hot, inside stock and margin limits. Needs the Shopify MCP connected in Roadway.
Each run, the agent reads orders, sales and stock by product from your store through the Shopify MCP and compares them with ad spend and attributed revenue. Products selling faster than their spend is growing get a budget increase, as long as there are enough days of stock left at the new pace and the margin holds. When the surge fades, the budget rolls back. The Shopify MCP answers when asked, so a surge is caught on the next run, not the moment it starts.
## Steps
1. Collect the inputs listed under Variables. In Roadway they come from your connected accounts. Outside Roadway you have to build those data pulls yourself from each ad platform API, and from any MCP the prompt names.
2. Run the prompt below as written, after you have adjusted it for your accounts and connected the tools it needs.
3. Review the result. Apply changes to a live ad account only after you approve them. Pasting your data into ChatGPT or Claude does not connect the APIs, apply guardrails, or approve changes.
## Variables
auto_approve, experiment_budget_pct, funnel_metrics, goal_metric, inventory_levels, margin_data, max_change_pct, min_stock_days, monthly_budget_cap, return_target, sales_velocity, social_mentions, task_history
## Prompt
Scale products whose sales velocity is accelerating
Read [set this to your own sales velocity] with ad spend and Roadway-attributed revenue by product, and decide for each product:
1. Scale up
2. Test new audiences
3. Hold
4. Cap for stock
Context and defaults (use these; don't ask):
- Sales velocity by product (units per day, trend), worked out from orders and sales read through the Shopify MCP: [set this to your own sales velocity]. If it isn't available, say so and skip the rules that depend on it.
- Target return on ad spend for revenue goals: [set this to your own return target]. If it isn't available, say so and skip the rules that depend on it.
- Social mentions: [set this to your own social mentions]. If it isn't available, say so and skip the rules that depend on it.
- Inventory by product (units and days of cover), read through the Shopify MCP: [set this to your own inventory levels]. If it isn't available, say so and skip the rules that depend on it.
- The minimum days of cover to advertise a product: [set this to your own min stock days]. If not set, 14 days.
- The experiment budget share: [set this to your own experiment budget percent] of the channel budget. If not set, 10%.
- Product margin data (price, cost of goods, shipping cost): [set this to your own margin data]. If it isn't available, say so and skip the rules that depend on it.
- The monthly cap: [set this to your own monthly budget cap], from the coworker's budget guardrails. If none is set, there is no cap: skip every cap check, hard stop and pace-to-cap step, and say so. Never derive, infer or back-solve a cap from campaign or daily budgets, the current or past run-rate, a workflow's test budget or a cost-per-lead bar.
- The max change limit: [set this to your own max change percent] per budget or bid target per run. If not set, 20%. It does not apply to experiment traffic splits.
- Auto-approve: [set this to your own auto approve]. If not set, it's off: list every change as a proposal for approval.
Rules:
- The Shopify MCP answers only when asked, so you are checking sales and stock as of this run. If it is not connected, say so and stop.
- Hot = 7-day velocity clearly above the 28-day average with a return on spend at or above [set this to your own return target]. If not set, 30%+ above. Separate organic spikes (a creator mention, a news hit) from paid-driven ones using [set this to your own social mentions].
- Scale up by up to [set this to your own max change percent] per run, but only if [set this to your own inventory levels] shows at least [set this to your own min stock days] days of cover at the new pace.
- Test new audiences (lookalikes of recent buyers, a video cut for YouTube) at [set this to your own experiment budget percent] when the product is a repeat winner.
- Cap for stock when cover is short, and hold when margin from [set this to your own margin data] is below the account average.
- Roll back budgets within 3 days of velocity returning to normal.
- Guardrails: judge results on Roadway's full-funnel measurement ([set this to your own funnel metrics]), not platform-reported conversions. Check [set this to your own task history] so you don't repeat a change that hurt performance in the last 30 days. Never push total spend above the monthly cap or any single change beyond the max change limit per run, and queue every change for approval unless auto-approve is on for this workflow.
Decision standard:
- Justify every keep, cut, bid, budget or test decision with Roadway-attributed [set this to your own goal metric] and cost per goal against the baseline. Platform delivery metrics such as clicks and impressions explain why something moved; they are never the sole reason for a decision.
- Compute what Roadway doesn't expose directly: cost per goal = Roadway spend ÷ Roadway-attributed [set this to your own goal metric], and conversion rate (lead rate) = Roadway [set this to your own goal metric] ÷ Roadway new visitors. Don't substitute platform-reported conversions or conversion rates.
- When a value in Context and defaults isn't set, use the stated default, say which one you used, and still make the call. Don't stop to ask.
- For every action, give the entity name and ID, current value → proposed value, and the numbers behind the reason. Write "None" under any empty heading.
- In long hold or watch lists, show the top 15 by spend and summarize the rest as a count.
Give me a report of each with reasoning for each action. Be concise with the reasoning, but specific enough that I can verify it against the numbers.
Report structure:
Sales velocity scaling report
Summary:
The hot products found, the budgets raised, and revenue versus stock.
Scale up:
- [product] - [reason]
Test new audiences:
- [product] - [reason]
Hold:
- [product] - [reason]
Cap for stock:
- [product] - [reason]
## Run it in Roadway
https://www.roadwayai.com/workflows/scale-products-whose-sales-velocity-is-accelerating
Scale products whose sales velocity is accelerating
Scale products whose sales velocity is accelerating
Reads sales and stock by product from your store, finds products selling faster than their ad spend is growing, and scales them while they are hot, inside stock and margin limits. Needs the Shopify MCP connected in Roadway.
Each run, the agent reads orders, sales and stock by product from your store through the Shopify MCP and compares them with ad spend and attributed revenue. Products selling faster than their spend is growing get a budget increase, as long as there are enough days of stock left at the new pace and the margin holds. When the surge fades, the budget rolls back. The Shopify MCP answers when asked, so a surge is caught on the next run, not the moment it starts.
