Bulk Update Amazon Listings with Flat Files

Creating a flat file gets all the attention. But for most sellers, the daily reality is updating existing listings — prices, inventory levels, descriptions, images — across hundreds of SKUs. This is where flat files truly earn their keep. One well-structured update file can change pricing on your entire catalog in minutes. One careless one can wipe out months of listing optimization. This guide covers the right way to do it.

If you're not yet familiar with what a flat file is, start with our complete guide to Amazon flat files before reading further.

Update vs. PartialUpdate vs. Delete: What's the Difference?

Every Amazon flat file has a column called update_delete. This single field controls what Amazon does with your data when you upload the file. Get it wrong, and you can accidentally destroy listings you spent weeks perfecting. Get it right, and you can surgically update exactly the fields you need across thousands of products.

Here's what each value does:

The critical difference is in the "Empty Fields" column. With Update, every column you leave blank in your flat file tells Amazon: "I want this field to be empty." That means if you upload a file with just SKU and price, Amazon will erase your titles, bullet points, images, descriptions — everything you didn't include.

With PartialUpdate, empty columns are simply skipped. Amazon only modifies the fields where you actually provided a value. Everything else stays exactly as it is on the live listing.

This distinction has caused more accidental data loss than probably any other flat file feature.

When Should You Use Each Mode?

Choosing the right mode isn't complicated once you understand the tradeoff. The rule of thumb: use PartialUpdate by default. Only switch to Update when you have a specific reason and complete data.

PartialUpdate: The Safe Default

Use PartialUpdate when you want to change specific fields without touching everything else. This is the right choice for the vast majority of day-to-day updates:

• Price changes — Update standard_price across 500 SKUs without worrying about any other field
• Inventory adjustments — Change quantity values without risking your listing content
• Title optimization — Improve titles while keeping bullet points, descriptions, and images intact
• Adding a single field — Fill in a newly required compliance field across your catalog
• Image URL updates — Swap image URLs without touching product data

Update: The Full Overwrite

Use Update only when you intentionally want to replace the entire listing with your file's data. This makes sense when:

• Complete data refresh — You've rebuilt your product data from scratch and want to overwrite everything
• New product onboarding — Creating listings for the first time (where there's nothing to lose)
• Category migration — Moving products to a new category with entirely new attribute requirements

The danger: if your file is missing any field, that field gets blanked on the live listing. This is why Update mode demands a complete, validated flat file with every single field accounted for.

Delete: Removing Listings

Use Delete only when you want to permanently remove a product from your catalog. Once deleted, the listing is gone — you'll need to create it from scratch if you want it back. Amazon may also remove your connection to the ASIN, making re-listing harder.

Step-by-Step: How to Do a Partial Update

Let's walk through a concrete example. Say you need to update prices for 200 SKUs after a supplier cost increase.

1. Download Your Current Flat File Template

Go to Seller Central > Catalog > Add Products via Upload. Download the category-specific flat file template for your products. You need the template to ensure you're using the correct column headers — Amazon rejects files with wrong or outdated headers.

2. Prepare Your Update File

You don't need to fill every column. For a price update, you only need three columns:

That's it. Every other column stays empty. Because you're using PartialUpdate, Amazon will only touch the standard_price field. Your titles, images, bullet points, descriptions — all untouched.

3. Set update_delete on Every Row

This is where people make mistakes. Every single row needs the update_delete value set. If you leave it blank on some rows, Amazon may skip those rows entirely, or worse, interpret the missing value unpredictably.

Tip: fill the entire update_delete column with "PartialUpdate" before you start entering data. Don't leave it for later.

4. Validate Before Upload

Check your file before uploading:

• Every SKU matches an existing listing in your catalog
• The values you're updating are in the correct format (prices as numbers, not "$24.99")
• No accidental data in columns you didn't intend to change (stray characters, leftover data from copy-paste)
• The update_delete column is filled on every row

See our guide to common flat file errors for the full list of validation issues that cause upload failures.

5. Upload to Seller Central

Go to Catalog > Add Products via Upload > Upload Your Spreadsheet. Select your file and submit. Amazon processes the file and returns a processing report. Check the report for errors — any row with an error was not processed.

For large files (1,000+ rows), processing can take 15 to 30 minutes. Don't re-upload while waiting.

Common Bulk Update Scenarios

Here are the most frequent update tasks sellers face, with the specific columns you need for each.

Price Changes Across Your Catalog

This is the most common bulk update. Whether you're adjusting for a seasonal sale, responding to competitor pricing, or reflecting supplier cost changes, the approach is the same.

Columns needed: sku, standard_price, update_delete

Optional additions: sale_price, sale_from_date, sale_end_date if you're running time-limited promotions.

Watch out for: Currency format. Amazon expects a plain number (24.99), not a currency symbol ($24.99) or a comma decimal separator (24,99 in European formats). This is one of the most common flat file errors — and one of the easiest to avoid.

Inventory and Quantity Updates

If you manage your own fulfillment (FBM), you may need to update quantities regularly. FBA sellers generally don't need this — Amazon manages FBA inventory automatically.

Columns needed: sku, quantity, update_delete

Optional: fulfillment_latency (lead time in days) if your shipping speed has changed.

Tip: If you need to update inventory more frequently than weekly, consider using the Inventory Loader instead of a full flat file. More on that below.

Title and Bullet Point Optimization

SEO improvements, A/B test results, or Amazon policy changes often require bulk title updates. The same applies to bullet points.

Columns needed: sku, item_name (title), bullet_point1 through bullet_point5, update_delete

Critical: If you're updating bullets, include all five bullet point fields — even the ones you're not changing. With PartialUpdate, you can technically leave unchanged bullets empty, but it's safer to include them all to avoid ambiguity. Some sellers have reported inconsistent behavior when only partial bullet fields are included.

Image URL Updates

Swapping product images — whether for seasonal photography, updated packaging, or fixing broken URLs — is a common bulk operation.

Columns needed: sku, main_image_url, other_image_url1 through other_image_url8, update_delete

Important: Image URLs must be publicly accessible HTTPS links. Amazon downloads the image from your URL during processing. If the URL is behind authentication or returns a 404, the image won't update. Broken image URLs can even trigger listing suppression.

Adding New Required Fields (Compliance Updates)

Amazon regularly introduces new required fields for specific categories. When this happens, you need to update every affected listing with the new data or risk suppression.

Columns needed: sku, the newly required field(s), update_delete

Example: Amazon has progressively rolled out requirements for battery information, chemical safety data, and product weight declarations. Each rollout gives sellers a deadline to add the data. PartialUpdate is perfect here — fill in just the new field across your catalog without touching anything else.

The Biggest Mistake: Accidental Data Loss with Full Updates

This is the scenario that keeps experienced sellers up at night. It happens more often than anyone likes to admit.

The story goes like this: A seller needs to update prices across their catalog. They download the flat file, fill in SKUs and new prices, and upload it. But they use "Update" instead of "PartialUpdate." Every column they left blank — titles, bullet points, descriptions, images, backend keywords, product dimensions, everything — gets wiped. Hundreds of listings are now bare shells: just a SKU and a price, with no content.

The damage:

• All titles gone. Listings show only the ASIN or a generic placeholder.
• All bullet points and descriptions erased. No product information for buyers.
• All images removed. Products show Amazon's default "no image" placeholder.
• Backend keywords wiped. Search visibility drops to near zero.
• Listing suppression kicks in because required fields are now empty.

How to recover:

1. Don't panic, but act fast. The longer listings sit with missing data, the more sales you lose and the harder it is to recover search ranking.
2. Download your listings report from Seller Central. This gives you the current state of your listings — which may still show the old data if Amazon hasn't fully processed your bad upload yet.
3. Re-upload a complete flat file with all your original data using "Update" mode. If you have a backup of your complete listing data, this is the fastest fix.
4. If you don't have a backup, pull what you can from the Listings Report, Amazon's "Manage Inventory" export, or your product data source. This is painful and time-consuming.
5. File a case with Seller Support if critical listings are suppressed. They can sometimes revert to a previous version, but don't count on it.

Prevention is simple: Use PartialUpdate for everything except full listing creation. There is almost never a good reason to use Update on existing listings unless your file contains every single field.

Inventory Loader vs. Flat File: Which to Use for Updates?

Amazon offers two file-based tools for updating listings. Knowing which to use saves time and reduces risk.

When to use the Inventory Loader:

• Daily or frequent price changes
• Inventory quantity updates (FBM sellers)
• Simple operational adjustments

When to use a flat file:

• Updating content fields (titles, bullets, descriptions, images)
• Adding newly required fields
• Any change beyond price/quantity/handling time
• When you need full control over every listing attribute

The Inventory Loader is essentially a stripped-down flat file. If all you're changing is price and quantity, it's faster and safer because there are fewer columns to accidentally populate or leave blank.

How Flat Magic Handles Updates

Bulk updates are where most flat file mistakes happen — and where Flat Magic adds the most value. Instead of manually managing hundreds of rows and hoping you set update_delete correctly, Flat Magic validates your update file before it reaches Amazon.

Here's what the workflow looks like:

• Upload your changes — Bring in your update data in any format. It doesn't have to be a pre-formatted flat file. Flat Magic maps your fields to Amazon's template automatically.
• Validation catches problems first — Every cell is checked against Amazon's rules for your specific category. Missing required fields, format errors, invalid values — they're flagged before you generate the final file. This is the difference between catching a problem at your desk and catching it in Amazon's processing report 30 minutes later (or worse, not catching it at all).
• Prevents accidental data wipes — The system highlights when fields are being sent as blank in Update mode, so you can catch unintentional overwrites before they happen.
• AI-assisted corrections — When validation finds an issue, the AI suggests a fix based on Amazon's rules and your existing data. No cryptic error codes to decode.

The goal is straightforward: by the time you download the final flat file, every known issue has been caught and resolved. Upload once, succeed once.

FAQ

Can I mix PartialUpdate and Update in the same file?

Yes. Each row has its own update_delete value, so you can use PartialUpdate for most rows and Update for specific ones. However, this is risky — it's easy to accidentally set the wrong value on a row. Unless you have a strong reason, stick with one mode per file to keep things predictable.

What happens if I upload a PartialUpdate with a SKU that doesn't exist?

Amazon will ignore the row. PartialUpdate can only modify existing listings. If you want to create a new listing, you need to use Update (which doubles as the "create" mode) or submit the product through the standard Add a Product workflow.

How often can I upload flat file updates?

There's no hard limit, but Amazon recommends waiting for one file to finish processing before uploading the next. Uploading multiple files simultaneously for the same SKUs can cause race conditions where the final state is unpredictable. For most sellers, one update file per day is plenty.

Can I undo a flat file upload?

Not directly. Amazon doesn't have a "rollback" feature for flat file uploads. If you make a mistake, you need to upload a corrected file. This is why validation before upload is critical — once the data reaches Amazon, the only way back is forward. If you accidentally wiped data with an Update, see the recovery steps in the "Accidental Data Loss" section above.

Bottom Line

Flat files aren't just for creating listings. For most sellers, they're an essential tool for maintaining and updating an existing catalog at scale. The update_delete column is the most important field in any update file, and getting it right is the difference between a smooth, five-minute operation and a days-long recovery effort.

Use PartialUpdate as your default. Only use Update when you have complete data and a specific reason. Always validate before uploading. And keep a backup of your complete listing data — your future self will thank you.

If you want to skip the manual process entirely, try Flat Magic and let the validation catch problems before they reach Amazon.