# For AI agents and crawlers
This page is a workflow from the Workflow Automation Library by Roadway: Reweight spend toward products with the best margin.
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/reweight-spend-toward-products-with-the-best-margin
Page: https://www.roadwayai.com/workflows/reweight-spend-toward-products-with-the-best-margin
Library index: https://www.roadwayai.com/automation-library
---
name: reweight-spend-toward-products-with-the-best-margin
description: >-
Reads price, cost and shipping changes by product, and moves bids and budgets to what makes profit after costs, not just revenue.
---
# Reweight spend toward products with the best margin
Source: https://www.roadwayai.com/workflows/reweight-spend-toward-products-with-the-best-margin
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 price, cost and shipping changes by product, and moves bids and budgets to what makes profit after costs, not just revenue.
Reads price, cost and shipping changes by product, and moves bids and budgets to what makes profit after costs, not just revenue. When a product's margin moves because of a price, cost, discount or shipping change, it will raise or lower its return target and budget to match. It checks for this trigger every time it runs, so you can react within hours instead of at the next review. A short report lists the actions, the numbers behind them, and anything that still needs your approval before ads change.
## 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, funnel_metrics, goal_metric, margin_data, margin_pct, max_change_pct, monthly_budget_cap, product_catalog_changes, promo_calendar, return_rates, return_target, task_history
## Prompt
Reweight spend toward products with the best margin
Read [set this to your own margin data] and [set this to your own product catalog changes], join them to ad spend and revenue by product, and decide for each product or product group:
1. Raise budget and target
2. Lower budget
3. Change return target
4. Hold
Context and defaults (use these; don't ask):
- 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.
- Price, shipping and stock changes by product: [set this to your own product catalog changes]. If it isn't available, say so and skip the rules that depend on it.
- Return rates by product and category: [set this to your own return rates]. If it isn't available, say so and skip the rules that depend on it.
- Profit margin used to turn revenue into profit: [set this to your own margin percent]. 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.
- The promo calendar: [set this to your own promo calendar]. 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:
- Profit margin = price - cost of goods - shipping - payment fees - expected returns ([set this to your own return rates]). Use [set this to your own margin percent] only when product-level data is missing.
- Break-even return on spend = 1 ÷ profit margin. Set each product's return target with a safety margin over break-even, and compare it with [set this to your own return target]. If not set, 20-30% over break-even.
- Raise budget and target for products with margin clearly above the account average and return on spend above target. If not set, 25%+ over the average. Lower budget for products below break-even after returns.
- Change return target when price, discount or cost moves margin by 5+ points. Do not act on moves that last less than 3 days, such as flash promos listed in [set this to your own promo calendar].
- Report revenue and profit after costs side by side, and flag products that bring revenue but lose money.
- 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:
Margin reweighting report
Summary:
The products changed, new return targets, and the revenue and profit effect.
Raise budget and target:
- [product] - [reason]
Lower budget:
- [product] - [reason]
Change return target:
- [product] - [reason]
Hold:
- [product] - [reason]
## Run it in Roadway
https://www.roadwayai.com/workflows/reweight-spend-toward-products-with-the-best-margin
Reads price, cost and shipping changes by product, and moves bids and budgets to what makes profit after costs, not just revenue. When a product's margin moves because of a price, cost, discount or shipping change, it will raise or lower its return target and budget to match. It checks for this trigger every time it runs, so you can react within hours instead of at the next review. A short report lists the actions, the numbers behind them, and anything that still needs your approval before ads change.
