stripe Built for Stripe

Bulk PromoCodeGenerator

Generate promo codes in batches

Create promo codes in batches.
Set coupon rules, discount amounts, usage limits, and expiration dates.
Export, copy, and hand off code lists to marketing operations.

Request access See how it works

Built for Stripe. Secure validation workflow.

Create Promo Codes

Campaign name Summer Launch 2026

Campaign settings

Discount type Percentage ⌄ Discount value 20 % Code prefix SUMMER20 Code length 8 characters ⌄ Number of codes 200

Unique codes

Each code can be used only once.

Expiration date 06/30/2026 ▣ Usage limit total 500 Max redemptions across all codes. Minimum purchase $ 0 Leave empty when no minimum is required.

Preview and summary

200Codes to generate

20%Discount

06/30/2026Expires

500Total redemptions

Code preview (first 10)

Copy all

1SUMMER20-7X9K2L8A□

2SUMMER20-Q4M7B3ZJ□

3SUMMER20-H9Y2P8TR□

4SUMMER20-L3N6G7FD□

5SUMMER20-V8J4K9WE□

6SUMMER20-D6T2Y8QM□

7SUMMER20-P9R3L6XN□

8SUMMER20-K7W2M9BG□

9SUMMER20-T3N8J6HP□

10SUMMER20-Z6P4Q7MR□

Export options

Export as CSV Download .txt

Built for campaign promo code batches

Bulk generation

Create unique code batches for launches, partners, and winback campaigns.

Flexible discounts

Set percentage or fixed-amount coupon rules before codes are created.

Smart limits

Control redemptions, expiration dates, and minimum purchase rules.

Expiration control

Keep seasonal offers, trials, and partner discounts time-boxed.

Export and share

Copy or export generated code lists for marketing operations.

Review batch results

Check accepted codes and per-code errors before handing the list to campaign owners.

Bulk Promo Code Generator is a planned Stripe workflow that creates customer-facing promotion codes from an approved underlying promotion, commonly a coupon-backed discount. A campaign owner previews codes and redemption rules before confirming the write. It creates Stripe objects rather than spreadsheet-only strings. The preview is illustrative; access requests do not install a released plugin.

Preview, validate, then create

The intended workflow starts by selecting an existing coupon or defining an approved promotion, then choosing quantity, optional prefix, customer eligibility, first-order status, minimum amount, expiration, and redemption limits. Before any Stripe write, the preview should show the exact codes and inherited rules. After confirmation, each code is created separately and receives its own success or error result. A downloadable CSV or text file should include only codes Stripe accepted, plus identifiers that billing or RevOps can use for reconciliation. A partial failure should never be presented as a fully successful batch.

Write permissions and change boundaries

Unlike the reporting tools, this generator requires permission to read the selected coupon or promotion and create Promotion Code objects. If the workflow also creates the underlying coupon, that is a second explicit write and should be labeled before approval. The planned batch action does not need to edit customers, subscriptions, invoices, payment methods, or existing discounts, and it does not redeem or apply the generated codes. Teams should test the full batch in Stripe test mode before repeating it in live mode, because accepted live codes immediately become usable under their configured rules.

Important Stripe limits and edge cases

Codes are case-insensitive and must be unique among relevant active promotion codes; a prefix does not guarantee uniqueness.
A code expiration cannot be later than the underlying coupon's redemption deadline, and a code's redemption cap cannot exceed the coupon's cap.
“First transaction” eligibility can exclude a customer who previously started a PaymentIntent or subscription trial, even without a completed payment.
Minimum-amount restrictions are evaluated at redemption and can behave differently for subscription updates and future schedule phases.
Large batches need throttling, retry-safe request handling, and a per-code error log; blindly retrying can create an unintended second code.

Campaign ownership, privacy, and sources

Growth teams can prepare launch and winback campaigns, partnerships teams can issue channel-specific codes, and billing operations can approve discount policy before live creation. Promotion codes can carry real monetary value, so exported lists should be treated like confidential campaign inventory with limited access and an owner for deactivation. This page uses sample data, does not connect to a Stripe account, and never asks for a secret key. Review the Workestic privacy policy and the install permission screen before authorization.

See Stripe's coupons and promotion codes guide and Promotion Code creation reference for current restriction and API behavior.

Created and reviewed by Guy Eshel · Updated 14 August 2026.