Key takeaways
- Fill the Operation column only on rows you changed, and pause instead of archive when unsure.
- Set each bid as price times conversion rate times a target ACoS taken from margin.
- Test on one campaign, keep the untouched download and log every upload.
- 1Download
Export 30 days, save an untouched copy
- 2Calculate
Bid = price x conversion x target ACoS
- 3Filter
Fill Operation only on rows you changed
- 4QA
Second person checks names, states, bids
- 5Test
Upload one campaign, read the report
- 6Ship and log
Full upload, record what changed and why
What Amazon bulk operations are
Bulk operations is the spreadsheet route into Amazon Ads. You download a file of your Sponsored Products, Sponsored Brands and Sponsored Display campaigns, edit it in Excel or Google Sheets, and upload it back. Amazon then applies every changed row as if you had made each edit by hand in Campaign Manager.
You reach it from the Amazon Ads console through Bulk Operations in the side navigation, where you can create and download a custom spreadsheet or upload a finished file. The download screen lets you pick a date range and choose whether to include terminated campaigns, campaigns with zero impressions, placement data and brand assets data.
For a small account with three campaigns, the console is faster. Once you manage hundreds of keywords, several ad types or more than one marketplace, the bulksheet becomes the only practical way to apply a weekly optimization without losing an afternoon.
- Change bids on thousands of keywords and product targets at once
- Raise or cut daily budgets across many campaigns
- Create new campaigns, ad groups, keywords and negatives from a template
- Pause campaigns, rename them or move them into portfolios
- Pull performance metrics next to every row for analysis
The columns that decide whether your upload works
The current bulksheet format is built around a few control columns. Product says which ad type a row belongs to. Entity says what the row is: a campaign, ad group, keyword, negative keyword, product target or product ad. Operation tells Amazon what to do with it, and State sets it to enabled, paused or archived.
Operation is the column most sellers get wrong. It has three values. Create is for something that does not exist yet, Update changes something that already exists, and Archive retires it. A row with an empty Operation cell is not processed, which is useful: you can leave thousands of rows untouched and only fill Operation on the rows you changed.
Archive is permanent. Several guides we read stress that an archived campaign or keyword cannot be brought back, only rebuilt. If you are not sure, set State to paused instead and archive later.
- Product: Sponsored Products, Sponsored Brands or Sponsored Display
- Entity: the level of the row, from campaign down to keyword or product ad
- Operation: Create, Update or Archive, blank means skip
- Campaign Name and Ad Group Name: must match the parent exactly
- Bid, Daily Budget and State: the values you actually change
Sponsored Products, Brands and Display managed daily to profit-capped targets. Flat monthly plans, no percentage of spend, every bid change explained.
What the top bulk operations guides miss
We read the most visible guides on this topic, from agency blogs to PPC software vendors. They explain where the button is, which columns exist and how to fix a failed upload. Almost none of them cover the three things that protect a real account: where the new bid comes from, how to test a file before it touches every campaign, and how to undo a bad upload.
That gap matters because a bulksheet multiplies whatever logic you put into it. A rule like cut every bid by 20 percent when ACoS is above 40 percent applies the same cut to a product with a 60 percent margin and a product with a 20 percent margin. One of those keywords was profitable. The spreadsheet does not know that unless you tell it.
The rest of this guide fills those gaps: margin based bid math, a small batch test, a saved rollback file and a change log that any team member can read.
Set every bid from margin, not from a flat ACoS rule
Start with break even ACoS for each product: the share of the sale price left after product cost, Amazon referral fees and FBA fees. If ad spend takes more than that share, every ad sale loses money. Your target ACoS should sit below break even so the product still earns a profit after ads.
Then set each keyword's bid with one formula: target bid equals price times conversion rate times target ACoS. Conversion rate is orders divided by clicks over your chosen date range. This bid is the most you can pay per click and still hit the target, based on how that keyword actually converts.
Add two guardrails. Only change keywords with enough clicks to trust the conversion rate, and cap any single change, for example at 20 percent up or 30 percent down per week, so one noisy week cannot swing a bid too far.
Worked example: one product, two keywords
These numbers are illustrative, not from a real account. Take a $30 product that leaves $10.50 after product cost and Amazon fees. Break even ACoS is 35 percent. You choose a target ACoS of 25 percent so the product keeps profit after ads.
Keyword A had 60 clicks and 4 orders at a $1.40 cost per click. Spend was $84 on $120 of sales, an ACoS of 70 percent. Its conversion rate is 4 divided by 60, or 6.7 percent. Target bid is $30 times 6.7 percent times 25 percent, which is about $0.50. With a 30 percent cap on cuts, this week's new bid is $0.98, and the next cycle moves it closer to $0.50 if conversion does not improve.
Keyword B had 40 clicks and 6 orders at $0.80 per click. Spend was $32 on $180 of sales, an ACoS of 17.8 percent. Its conversion rate is 15 percent, so target bid is $30 times 15 percent times 25 percent, about $1.13. With a 20 percent cap on raises, the new bid is $0.96.
A flat rule would only have cut Keyword A. The margin formula also raised Keyword B, the profitable keyword that was being held back by a low bid. That is where bulk edits earn their keep.
Bulk operations PPC checklist: 6 steps for a safe weekly upload
Run this routine every week. It takes about the same time as a careless upload and removes most of the risk.
- Download: the PPC manager exports the last 30 days from Bulk Operations in the Amazon Ads console and saves an untouched copy named with the date. Metric: you can reopen the exact pre change file at any time.
- Calculate: the PPC manager adds three helper columns in the sheet for conversion rate, target bid and capped bid, using the margin formula above. Metric: every changed bid has a target ACoS from that product's margin behind it.
- Filter: the PPC manager fills Operation only on rows with enough clicks and a bid change worth making, and leaves every other row blank. Metric: the count of filled Operation cells matches the number of changes you intended.
- QA: a second person checks bids are numeric, match types and states use Amazon's exact spelling, parent names match and no row says Archive by accident. Metric: zero rows flagged in the check.
- Test: upload one campaign or one portfolio first, then open the processing report and confirm the new bids in Campaign Manager. Metric: zero errors and live bids that equal the sheet.
- Ship and log: upload the full file, then record the date, file name, number of rows changed and the reason in a shared change log. Metric: ACoS on the changed keywords moves toward target over the next two weekly cycles.
Limits and errors to plan around
One guide lists a 32 MB file size limit and 500,000 rows per bulksheet upload. Large accounts can hit this, so split very large files by ad type or portfolio. A long date range can also make an export heavy, so stick to 30 days for routine optimization.
Common upload errors are a missing or incomplete header row, a campaign or ad group name that does not match its parent, a missing required field and a bid outside the allowed range. The minimum Sponsored Products bid is $0.02. One vendor guide notes that when a row is duplicated, only the first copy is processed and the rest are ignored, so a duplicate can quietly hide the change you meant to make.
After every upload, download the error file, fix only the flagged rows and upload those rows again. Never re-upload the whole sheet to fix five rows, because rows that already succeeded will be applied a second time.
When bulk operations are the wrong tool
Bulksheets are slow for one off changes. If you need to fix one bid or pause one campaign, do it in Campaign Manager. They are also weekly by nature: a spreadsheet cannot react to a stock out at 2 a.m. or a sudden cost per click spike during a deal.
The margin formula needs data. Keywords with only a handful of clicks do not have a reliable conversion rate, and new launches often need bids set for visibility and rank rather than short term ACoS. Seasonal products also break 30 day averages, so treat their bids separately around peak weeks.
Finally, if nobody on your team owns the weekly file, bulk operations become a risk, not a saving. A half finished sheet uploaded by the wrong person can change every bid in the account at once.
How PPC Spider runs bulk changes
PPC Spider sets every campaign's ACoS target from the product's real margin, and SpiderOS, our AI platform, monitors bids, budgets and search terms 24x7 between weekly reviews. Bulk changes follow the same test, rollback and log routine described above.
Amazon PPC management is a flat monthly retainer, never a percentage of ad spend. Launch is $995 a month for up to $10k of monthly ad spend with weekly optimization and negative targeting. Growth is $1,250 a month for up to $40k with daily bid and budget management and a campaign architecture rebuild. Scale is $2,200 a month for up to $120k, and larger accounts get an Enterprise quote. If you want a second opinion on your current bulk process first, start with the free Amazon audit.
We run these playbooks on client accounts every day. Start with a free audit.
Get a free audit