Adjust budgets

On this page you can combine spend rate with ACoS to build daily budget raise/cut candidates, and register a monthly ad spend cap (Budget CAP) in Picaro to monitor utilization. Use it when you want to shift budget toward campaigns with headroom and trim inefficient ones.

About this page

Item	Details
What you can do	Build daily budget raise/cut candidates; register, list, and delete monthly budget caps (Budget CAP); check utilization, pacing, and trends
Applies to	Mainly Sponsored Products (SP)
Data & connection needed	Budget and spend actuals for the connected account (no additional setup)
Scope	Varies by prompt. Daily budget raise/cut candidates and pacing flags = analysis and proposal only / registering and deleting a monthly budget cap (Budget CAP) = records in Picaro (does not change Amazon Ads budgets and does not stop spend) / checking utilization and trends = read-only. Each prompt states its own in “Changes”

When to use this

You want to look at spend rate and ACoS and sort campaigns into which to raise and which to lower
You want to set a monthly ad spend ceiling to catch overspending early
You want to check how much you’ve spent so far against a registered monthly budget cap
You want to list the monthly budget caps you registered before and delete the ones you no longer need
You want to find campaigns that are overspending or underspending versus the expected pace
You want to decide the priority order for adding budget from the past 90 days of trends

Before you run

Connected account … if you handle multiple accounts, confirm the target account is correct first.
Target period / target month … since same-day and previous-day data can be unfinalized, a recent finalized period is safest. If you omit the target month on the cap-related prompts, the current month is used.
Target ACoS … if you register it in Set targets for sales, ad spend, and ACoS, the daily budget optimization prompt references it automatically, so you can skip entering it each time.

Prompt quick reference

What you want	What you learn / what gets created	Changes	Prompt
Build daily budget raise/cut candidates from spend rate × ACoS	A list of raise/cut candidates (with current / recommended daily budget)	No change (proposal only)	Prompt 1
Register a monthly budget cap (Budget CAP) and monitor utilization	A confirmation table of the registered details (target month, cap, warning level, etc.)	Records in Picaro (does not stop spend)	Prompt 2
Check monthly budget utilization status	A table of spend rate, remaining budget, and recommended daily budget	No change (read-only)	Prompt 3
List and delete registered monthly budget caps	A registration list (deletion goes through a confirmation)	List is read-only / delete removes the record	Prompt 4
Find campaigns whose pacing is off the expected pace	A list of deviations and recommended actions	No change (proposal only)	Prompt 5
Find budget-starved campaigns from 90-day trends	A table of growth rate, days to cap arrival, and bottlenecks	No change (analysis only)	Prompt 6
Register a monthly budget cap at the portfolio level	A confirmation table of the registered details	Records in Picaro (does not change Amazon budgets)	Prompt 7

For detailed specs, see Automation phases / Troubleshooting.

Prompt 1: Build daily budget raise/cut candidates from spend rate and ACoS

From the combination of spend rate and ACoS, sort campaigns into which to raise and which to lower, each with clear reasoning.

When to use — when you want to shift budget toward campaigns with headroom and trim the budget of inefficient ones.

What you need — the target ACoS (auto-referenced if you’ve registered KPI targets), and the minimum daily budget (default is 500 JPY).

Using the most recent finalized week, propose daily budget optimizations against my target ACoS {{TARGET_ACOS (e.g. 15%)}}.
- Spend rate at or above 90% and ACoS at or below target → raise candidate
- ACoS above 1.5x target with spend rate below 50% → cut candidate
Set the minimum daily budget to 500 JPY.

What you can change — the spend rate thresholds and the minimum daily budget (e.g. “spend rate at or above 80%”, “minimum daily budget of 1,000 JPY”). If you’ve registered a monthly KPI target, the target ACoS is referenced automatically, so you don’t have to type it in every time.

What you get back — a table listing, for each campaign, “current daily budget / recommended daily budget / spend rate / ACoS” (with the count of raises and cuts). The prompt specifies that each change stays within +20% / -20% per adjustment.

Changes — no change (proposal only). The actual daily budget does not change until you approve.

Next steps — to actually apply the proposals, use the approval flow in Save rules to systematize proposal approval and monitoring.

Prompt 2: Register a monthly budget cap and monitor utilization

Record a monthly ad spend cap and warning level in Picaro and enable automatic utilization monitoring. This does not change the budget on the Amazon Ads side.

When to use — when you want to set a monthly ad spend ceiling to catch overspending early.

What you need — the target month, the budget amount, the currency (defaults to Japanese yen), and the warning level (e.g. 80%).

Register the monthly budget cap for {{TARGET_MONTH (e.g. 2026-05)}} at {{BUDGET_AMOUNT (e.g. 1,000,000)}} ({{CURRENCY (e.g. JPY)}}).
Warn me when the spend rate exceeds 80%.

What you can change — the warning level (e.g. 80%) and the currency (defaults to Japanese yen). The daily spend guideline is calculated automatically by dividing the monthly cap by the number of days in the month.

What you get back — a table summarizing the registered details (target month / cap / currency / warning level / registered at). If a cap is already registered for the same month, a confirmation step asks whether to overwrite it.

Changes — records a monthly budget cap in Picaro (does not change Amazon Ads budgets and does not stop spend). Once registered, the daily budget optimization and utilization-monitoring prompts on this page reference it as a guardrail (an automatically referenced ceiling).

Next steps — to check utilization go to Prompt 3; to list or delete registered caps go to Prompt 4.

Prompt 3: Check monthly budget utilization status

See at a glance the spend rate, remaining budget, and days-remaining-based recommended daily budget against your registered monthly budget cap.

When to use — when you want to check how much budget you’ve used this month and at what pace to use the rest.

What you need — the target month (defaults to the current month). You need to have registered a monthly budget cap in Prompt 2 beforehand.

Show ad spend consumption for {{TARGET_MONTH (e.g. 2026-05)}} compared against the registered monthly budget cap.
Include the spend rate, remaining budget, and recommended daily budget.

What you can change — the target month (if omitted, the current month is used).

What you get back — a table summarizing “monthly budget cap / month-to-date actual / spend rate / remaining budget / days remaining / recommended daily budget (even distribution over the remaining period)”. If the warning level has been exceeded, a warning is included as well.

Changes — no change (read-only). It does not change any budget.

Prompt 4: List and delete registered monthly budget caps

List your registered monthly budget caps so you can clean up past months or remove mistaken registrations.

When to use — when you want to review caps you registered before, or delete a month you registered by mistake.

What you need — the target month, only when deleting.

Show me the list of registered monthly budget caps.
(If you want to delete one, tell it to delete by specifying {{TARGET_MONTH (e.g. 2025-12)}}.)

What you can change — specify the target month only when deleting.

What you get back — a table summarizing “target month / cap / currency / warning level / registered at”. When deleting, you specify the target month explicitly and a confirmation step asks whether to proceed.

Changes — listing is read-only / deleting removes the monthly budget cap recorded in Picaro (no effect on Amazon Ads budgets or spend).

Prompt 5: Find campaigns whose pacing is off the expected pace

Extract this month’s SP campaign pacing and flag campaigns that are off the expected pace by 5% or more.

When to use — when you want to find campaigns that are overspending or underspending versus what you expected, and take action.

What you need — the deviation threshold to flag on (default is 5% or more).

Extract this month's Sponsored Products budget pace (how the budget is being spent),
and flag campaigns that deviate from the expected pace by 5% or more.
Also include the direction of the deviation (overspending / underspending) and a recommended action.

What you can change — the deviation threshold (e.g. 5%).

What you get back — a table summarizing “campaign / current spend rate / expected spend rate / deviation / recommended action”.

Changes — no change (proposal only). It does not change ad settings.

Next steps — to adjust daily budgets based on the flags, go to Prompt 1.

Prompt 6: Find budget-starved campaigns from the past 90-day trend

Analyze account performance trends over the past 90 days, and identify budget bottlenecks from the fastest-growing campaigns and their budget cap arrival status.

When to use — when you want to decide the priority order for adding budget from growth trends and cap arrival status.

What you need — (the target period is fixed to the past 90 days)

Analyze account performance trends over the past 90 days,
and check the fastest-growing campaigns and budget cap arrival status.
Also identify campaigns that are budget bottlenecks.

What you can change — (none; it analyzes the past 90-day trend)

What you get back — a table summarizing “high-growth campaigns / days until the budget cap is reached / bottleneck determination”. Useful for deciding the priority order for adding budget.

Changes — no change (analysis only). It does not change ad settings.

Prompt 7: Register a monthly budget cap at the portfolio level

Register a monthly spend cap (monthly budget cap) in Picaro for a specified portfolio rather than the whole account. It does not change the portfolio budget on the Amazon Ads side; it is recorded as a Picaro-side spend ceiling, and later budget-adjustment prompts reference it automatically as that portfolio’s ceiling.

When to use — when you want to monitor separate spend ceilings per portfolio, such as by brand or by product line.

What you need — the target portfolio (can be specified by name), the budget amount, the currency, and the target month (defaults to the current month).

Register the monthly budget cap for portfolio {{TARGET_PORTFOLIO (e.g. Torani)}} at {{BUDGET_AMOUNT (e.g. 500,000)}} ({{CURRENCY (e.g. JPY)}}).
Don't change the portfolio budget on the Amazon side; record it as a Picaro-side spend ceiling,
so that later budget-adjustment prompts can reference it automatically.

What you can change — you can specify the portfolio by name (the target is resolved internally). If you omit the month, the current month is used.

What you get back — a table summarizing the registered details (target portfolio / cap / currency / target month). If a cap is already registered for the same portfolio, a confirmation step asks whether to overwrite it. When it is no longer needed, you can delete it by specifying the target month.

Changes — records the specified portfolio’s monthly budget cap in Picaro (does not change the Amazon Ads portfolio budget and does not stop spend).

Next steps — to raise or lower the Amazon Ads portfolio budget itself, use Manage the budgets of multiple campaigns together.

Adjust bids — dialing in bids before revisiting budgets is the standard order
Set targets for sales, ad spend, and ACoS — pre-register a target ACoS to skip specifying it every time
Save rules to systematize proposal approval and monitoring — turn budget-decision parameters into rules and apply proposals via the approval flow
Manage the budgets of multiple campaigns together — create and change portfolio budgets on the Amazon Ads side