Safety

What stops a bad bid.

Your limits, the checks every bid has to pass, the kill switch, and what happens when Amazon's data goes quiet. Only what the engine enforces today.

See the seven layers
Example
Target ACoS30%

You set it. Every bid aims for it.

How far a bid may move

A bid only moves a limited step at a time. No sudden jumps.

Kill switchOne click stops every bid, on one marketplace or all of them.
A daily budget per product, enforced by Amazon itself.

The film

Your limits. Your stock. Your call.

Your target ACoS and step limits, bids that slow when stock runs low, a stop for spend spikes, and a kill switch.

40 seconds · with sound · English

Stock

Stock changes the bid

Most tools keep spending until a product sells out. Mirox checks your stock and your next shipment every time it bids.

Example
Your product
Stock left9 days
Next shipment arrives in14 days

You would sell out 5 days before the shipment lands.

Mirox slows the bid

$1.60$0.12

Fewer clicks while stock is short, so you don't sell out before the shipment arrives.

Stock healthy again? Bids go back to normal on their own.
Lost the Buy Box? Ads on that product can pause, if you turn this on.

Seven layers · all on by default

What stands between the AI and your spend.

Every bid passes through all seven gates before it reaches Amazon. If any one trips, the bid is suppressed and the trace records why.

  1. 01Kill switch

    One toggle halts all bids — instantly.

    Checked before every change goes to Amazon. You or our team can switch it on, and bidding only starts again when you resume.

  2. 02Spend-spike breaker

    A keyword that suddenly spends far above its usual level without a single sale is stopped.

    Checked per keyword before every bid. It trips when recent spend is several times the keyword's usual level and there are no sales. Every trip is logged and you get a notification.

  3. 03Daily budget per product

    You set a daily budget for each product. It becomes the budgets on Mirox's campaigns, and Amazon enforces them.

    Mirox splits the budget across its four campaigns for that product, and the parts always add up to your number. Amazon applies its normal campaign budget rules, so a busy day can run slightly over and quieter days balance it out. A failed budget update is logged as an error, never ignored.

  4. 04SP-API fault gate

    If Amazon's API is unhealthy, the system stops — it does not guess.

    If more than 10% of calls to Amazon fail within five minutes, Mirox stops sending changes for five minutes, then checks again. Failed calls are retried with growing waits, not hammered.

  5. 05No clashing changes

    Two agents cannot move the same bid at the same time.

    Every change carries a version number. If two changes to the same bid collide, one is rejected and worked out again with the latest numbers.

  6. 06Careful restart

    A stopped keyword does not jump straight back. It gets one test bid first.

    After a trip the keyword stays off for a cooldown (2 hours by default). Then Mirox places one test bid. If it converts, normal bidding resumes; if not, the cooldown starts again.

  7. 07Per-marketplace gates

    DE, FR, IT, ES, NL, BE, PL, SE, UK, US — each has its own thresholds.

    Spend-spike thresholds are tuned per marketplace, budgets are set per product in each marketplace, and the kill switch can stop one marketplace without touching the others.

Walkthrough · the worst-case

What happens if Amazon goes dark for six hours.

SP-API outages happen. The system is built to know that, freeze rather than guess, and recover without overcorrection.

  1. T+0s

    SP-API fault gate trips

    More than 10% of Mirox's calls to Amazon fail within five minutes. Mirox stops sending changes and records why.

  2. T+1s

    All writes are suppressed

    No new bids leave Mirox during the pause. Your bids on Amazon stay where they were.

  3. T+0–6h

    Telemetry continues, decisions accumulate

    Decisions keep being recorded with their reasons, so afterwards you can see exactly what was held back.

  4. T+6h

    Amazon recovers

    After five minutes Mirox checks again. If calls are succeeding, it carries on. If they are still failing, it pauses again.

  5. T+6h05

    Bids resume in small steps

    Bidding picks up from the bids Amazon already holds. Each bid can only move a limited step per cycle, and a jump of more than 3× is cut back, so a shaky recovery cannot cause a big swing.

  6. T+6h35

    Full operations · trace exported

    Marketplace returns to normal. Every minute of the outage — every gate trip, every suppressed write, every recovery step — is exportable as a CSV trace with the original Amazon IDs.

Amazon 2026 agent policy

Compliant with Amazon's 2026 agent policy.

Amazon now requires automated bidding tools to run on the official SP-API with rate limiting, complete audit logging, and human-in-the-loop control. Mirox was built this way from day one. The tool auditing your account shouldn't be a black box — especially now.

SP-API native, with rate limiting — no scraping, no unofficial endpoints.

A written reason behind every single bid.

A kill switch and complete audit logging on every action.

A human stays in control — Mirox goes live only when you switch it on, and the kill switch stops it in one click.

Try it live

Trust is a trace you can read.

Try Mirox free for 30 days on your real account. Every gate trip, every suppression, every recovery step — exportable, and yours to keep. Then decide.

30 days free · cancel anytime · no drip