How to Change Prices on All Gumroad Products at Once (2026)

Updated 2026-07-27 · GumKit guides

You decided to raise your prices. Or run a 30%-off sale across the whole store. Or round everything to clean numbers before a launch. Whatever the reason, you open your Gumroad dashboard expecting a "set prices" control near the top, select your products, type a number, and you're done.

That control doesn't exist.

Gumroad edits prices one product at a time, inside each product's own editor. Five products is mildly annoying. Forty products is a lost afternoon of opening, clicking, retyping, and saving, hoping you didn't fat-finger a zero on product 23. There is no native "change all prices at once" button, and no built-in percentage adjustment that sweeps your catalog.

This guide covers how Gumroad pricing is actually structured (including the version behavior almost every guide gets wrong), the native step-by-step flow, the decisions worth making before you touch 40 products, and a faster way to handle a Gumroad change all prices at once job when your catalog gets too big to do by hand.

How Gumroad pricing actually works

A few facts up front, because they explain why this is repetitive rather than hard:

• A Gumroad product can be free, or priced up to USD 5,000, per Gumroad's help center. A paid purchase has to clear a $0.99 minimum, which is why "pay what you want" buyers can pay nothing or at least $0.99, but nothing in between.
• Prices live on the product, not at the account level. There is no global price setting that cascades down, and no catalog-level percentage control.
• Your product's display currency is chosen in Settings. Gumroad's help center notes checkout converts to USD at the exchange rate at purchase time, so the currency picker is display, not settlement. Display currency also can't be changed after creation on membership and bundle products.
• Versions and tiers add a second layer of numbers inside a single product, and the two behave differently from each other. This is the part that trips people up, so it gets its own section below.
• Memberships have their own rules. A price change can optionally apply to existing customers, and price increases send subscribers a notification email with 7 days' notice before taking effect.

Because prices are stored per product, "change all my prices" really means "open every product and edit every price field," repeated by hand. That's the whole problem in one sentence.

Versions vs. tiers: the distinction that changes your math

Sellers use "versions" and "tiers" interchangeably. Gumroad doesn't, and the difference decides whether a bulk change does what you expected.

Versions on a digital product are offsets. Gumroad's help center describes each version as having a name, a description, and an "Additional amount" over the base product price — plus an optional quantity limit. So a $10 product with three versions at +$0, +$5, and +$15 sells at $10 / $15 / $25. The version numbers are add-ons, not standalone prices.

That has a consequence nobody mentions: raise the base price and every version moves with it, by the same dollar amount. Take that $10 base to $12 and your ladder becomes $12 / $17 / $27. The gaps stay fixed at $5 and $15 — they don't scale. If you wanted a true across-the-board 20% increase, the top version should have landed at $30, not $27. The base price got its 20%; the add-ons got 0%.

Membership tiers are different. Tiers are set up individually with their own names, descriptions, and enabled payment frequencies, and each tier carries its own price. Changing one tier doesn't move the others.

So before any bulk operation, know which of the two you're dealing with. A catalog of one-time digital products with a couple of versions each behaves predictably under a base-price sweep. A catalog of memberships does not.

The manual method: changing a product's price

Here's the native flow. Learn it even if you later automate, because every shortcut is just this, faster.

Step 1: Open the product

From your dashboard, go to Products and click the product you want to reprice. This opens the product editor. (Gumroad redesigned this editor in 2026, so older screenshot-heavy tutorials may not match what you see — the fields below are what matter, not their exact position.)

Step 2: Set the price type

For a standard fixed-price product, it's a single amount box. For pay-what-you-want, Gumroad uses a + syntax in the price field:

• 0+ lets buyers pay anything, including nothing. Paid purchases still have to clear the $0.99 minimum.
• 5+ sets a $5 minimum while still allowing more.
• The Suggested amount box sets the anchor buyers see first, which is the single biggest lever on what people actually pay.

Step 3: Update every number the product has

Type the new base price. If the product has versions, scroll through them and check each Additional amount — remember these are offsets, so you may not need to touch them at all, or you may need to rewrite all of them if you're scaling proportionally. If it's a membership, walk the tiers individually; each one is its own price.

Missing a nested number is the most common repricing mistake. A "$49 course" with three versions is really four numbers: one base and three offsets.

Step 4: Save (and handle subscribers)

Click Save changes. A new price isn't live until it's saved. If it's a membership and you want current subscribers moved to the new price, toggle "Apply price changes to existing customers" — otherwise the change only affects new buyers. Gumroad lets you customize the notification message and send yourself a sample first, and on increases, existing customers get that 7-day notice before the new rate applies.

Step 5: Repeat for every other product

This is the part that doesn't scale. To take your whole catalog up 10%, or drop everything 30% for a weekend sale, you run Steps 1 through 4 again for each product, recalculating the new number every time and trusting yourself to stay consistent across dozens of tabs.

Here's the arithmetic of that grind at different catalog sizes, assuming two versions per product:

Nothing there is hard. It's just fifty chances to make one mistake you won't notice until a customer does.

Why there's no bulk button (and what that means for tools)

Gumroad's seller dashboard simply doesn't ship a multi-select price action. Its 2026 updates have improved the product edit page and added creator admin tools, but repricing is still a per-product editor task.

The API tells a similar story. Gumroad exposes a public REST API (v2) at api.gumroad.com/v2, and a token with the edit_products scope can read and write your products, variants, and offer codes. What it can't do is create products — that path returns a 404, and there's an open request on Gumroad's own issue tracker asking for a public create/edit product API.

The practical takeaway: any third-party tool can help you edit what already exists — prices, discount codes, listings. Nobody can bulk upload products to Gumroad, and any tool claiming otherwise is either scraping the dashboard or overpromising.

Three decisions worth making before you touch 40 products

Bulk operations are fast, which means bulk mistakes are fast too. Get these settled first.

1. Fixed price or percentage? A fixed price is for normalizing ("every template is $29 now"). A percentage is for shifting a spread you already like ("everything up 10%"). Percentages preserve your existing price ladder; fixed prices flatten it. If your catalog spans $7 to $199, a fixed price will destroy information your buyers use.

2. Price change or discount code? These solve different problems:

If your sale has an end date, a code is almost always the right instrument, because the "put it all back" step is where manual repricing goes wrong. The bulk discount codes guide covers that path in full. Gumroad's codes can be a percentage or a fixed amount, can cap total uses with a quantity limit, and can be scheduled with a validity period.

3. Does the new price still clear the fees? Gumroad's pricing page lists 10% + $0.50 per transaction on direct sales, with payment processing charged separately, and a flat 30% on sales that come through the Discover marketplace. The flat $0.50 is the part that matters here: it's a rounding error on a $99 product and a real bite on a $4 one. Before you sweep a catalog of cheap items down 30%, check what's left. The full fee breakdown has the worked math.

The faster way: bulk price changes in one pass

Once your catalog crosses ten or fifteen products, especially with versions, manual repricing is the reason sellers quietly skip running sales or postpone a needed price increase. That's the gap a small tool can close.

GumKit is an independent Chrome extension for Gumroad sellers who are tired of one-at-a-time editing. It is not affiliated with, endorsed by, or sponsored by Gumroad — it's a third-party tool that drives Gumroad's own official API on your behalf.

Here's the honest picture of how it works, so there are no surprises:

• It calls the official Gumroad API v2 (api.gumroad.com/v2) directly from your browser. No scraping, no automating UI clicks, no rate-limit workarounds. A price update is a PUT to /products/:id with the price as an integer in cents — $29.00 is 2900.
• You connect with your own Gumroad access token, generated under Settings → Advanced → Applications: create an application, click Generate access token, paste it in. The full token walkthrough covers the redirect URI field and scopes if you've never done it.
• The token is stored only in your browser (chrome.storage.local). There is no GumKit server holding your credentials, and revoking the token in Gumroad cuts off access instantly.

What the flow actually looks like

1. Load my products. GumKit pulls your product list through the API and shows each one with a checkbox and its current price, so you're deciding against real numbers rather than memory. Drafts and unpublished products come through the same list and aren't labelled as drafts, so read the names and uncheck anything you don't want swept.
2. Pick the mode. Set fixed price takes a dollar amount. Adjust by percent takes a signed number, where -30 means 30% off and 10 means a 10% increase.
3. Confirm before it sends. Nothing goes to Gumroad until you accept a confirmation that states how many products are about to change and roughly how long the paced run will take. Check that count against the list — the checkbox list is showing you current prices, so this is the moment to catch a stray selection or a decimal-point typo.
4. Run it. A progress bar tracks the queue, each item is logged as it finishes — Product name: $19.00 → $29.00, with a ✓ or an error — and a Cancel button stops the run mid-flight.

Two guardrails are built in: within percent mode, any product whose adjusted price would land below one cent is dropped from the run rather than pushed to $0 (use fixed mode if you actually want a product free), and -100% or lower is refused outright rather than silently zeroing your catalog.

Why it's paced, not instant

Gumroad rate-limits writes and returns 429 Too Many Requests if you push too fast. Its API documentation acknowledges rate limiting and the 429 response but doesn't publish a specific ceiling, so GumKit uses a deliberately conservative number of its own: roughly 30 writes per minute as the assumed cap, and it paces one write every 2.4 seconds — about 25 per minute — to stay under it. Fifty products lands around two minutes.

That's slower than firing everything at once, on purpose. Two details matter when a run is long:

• A 429 doesn't skip a product. The queue waits out the Retry-After window and retries the same item rather than advancing past it, so a rate limit can't silently leave one product at the old price. After a bounded number of retries it gives up on that item and reports it as failed, so one stuck product can't wedge the whole job.
• Closing the popup doesn't kill the job. Queue state is persisted, so the run continues in the background and picks up where it left off, including across a browser restart.

When not to do a bulk price sweep

The honest limits, because a tool that pretends it has none is a tool that will surprise you:

• Memberships. Existing-subscriber handling, per-tier pricing, and the 7-day increase notice mean membership repricing deserves a deliberate pass in the Gumroad editor. Don't fold them into a catalog-wide sweep.
• Products where the versions carry most of the price. A base-price change moves the floor and drags the add-ons along unchanged, as described above. If your $10 base has a +$90 version, a −30% sweep takes the base to $7 while the top version only falls from $100 to $97. Spot-check one versioned product before running a sweep across a catalog full of them.
• Pay-what-you-want products. PWYW is a different pricing mode, not just a smaller number. If a product's whole strategy is 0+ with a suggested amount, keep it out of the selection and handle it in the editor where you can see the minimum and the suggestion together.
• Anything you can't reverse from memory. There's no undo. The product list shows current prices before you run, so screenshot or copy that list first. And note that reversing a percentage isn't symmetrical: recovering from −30% takes +42.86%, not +30%. If a sale needs a clean revert, use a discount code instead.
• Regional pricing. If the goal is "cheaper in India and Brazil," a global price cut is the wrong tool. Region-specific discounts are covered in the Gumroad PPP pricing guide.

FAQ

Can you change all Gumroad prices at once?

Not natively. Gumroad's dashboard edits prices one product at a time, with no built-in bulk action and no catalog-wide percentage adjustment. You either reprice each product by hand or use a third-party tool that drives Gumroad's official API to apply one change across many products.

Does Gumroad have a percentage price increase or sale feature?

No automatic one. Gumroad won't compute "−30%" or "+10%" across your catalog for you — you do the math per product and type each result. A tool that applies a ± percentage over selected products is the only way to get a true one-pass percentage change.

Can the Gumroad API update a product's price?

Yes. A PUT to /v2/products/:id with the price in cents, using a token that has the edit_products scope, updates the product's price. Product creation is a different story: it returns 404, and a public create/edit product API is still an open request on Gumroad's issue tracker. Treat the API as edit-only.

What happens to versions when I change the base price?

They move with it by the same dollar amount, because Gumroad stores each version as an "Additional amount" on top of the base price rather than as a standalone price. A +$5 version stays +$5 whether the base is $10 or $12. If you want the gaps to scale too, you'll have to edit the version amounts yourself in the product editor.

Will existing customers be charged the new price?

For one-time products, no — a price change only affects new purchases. For memberships, it depends on the "Apply price changes to existing customers" toggle. If you enable it and the price is going up, Gumroad emails existing subscribers with 7 days' notice before the new rate takes effect.

What's the difference between a bulk price change and a bulk discount code?

A price change edits the actual listed price, so it stays until you change it back. A discount code keeps the list price and reduces the total at checkout, and it can carry a usage limit and an expiration. Codes are the better tool for time-boxed sales; price changes are for real, lasting repricing. The bulk discount codes guide walks through both.

Will repricing in bulk get me rate-limited?

It can if a tool hammers the API. Gumroad returns 429 Too Many Requests on writes that come too fast and doesn't publish an exact limit. GumKit paces bulk jobs at roughly one write every 2.4 seconds, retries the same product after a 429 rather than skipping it, and reports anything it couldn't complete.

Is it safe to change prices with a Chrome extension?

It depends entirely on how the tool connects. GumKit uses an access token you generate in your own Gumroad settings, stored only in your browser, and calls Gumroad's official API with the edit_products scope — no password sharing, no scraping, no server in the middle. You can revoke the token from Gumroad at any time, which immediately stops all access.

Can I undo a bulk price change?

Not with a button. The safest habits are to capture your current prices before the run, prefer discount codes for anything temporary, and remember that reversing a percentage requires the inverse, not the same number with the opposite sign.

Does changing a price change my product's URL?

No. A Gumroad product's link is its permalink, which is independent of price. Repricing doesn't break existing links, embeds, or the URLs you've already shared.

The takeaway

Changing every Gumroad price at once isn't difficult, it's repetitive — because Gumroad stores prices per product, layers versions on top as offsets, and offers no global control or percentage tool. For a few simple products, the manual flow above is fine and you should know it. For a real catalog, retyping numbers across dozens of editors while doing the percentage math by hand is exactly the kind of busywork that makes sellers avoid price changes they should be making.

If that's where you are, GumKit is free to use, and lets you set a fixed price or apply a ± percentage across every selected product in a single paced run — using your own Gumroad token and Gumroad's official API, no middleman and no scraping.