Blog · Stripe campaigns

How to generate Stripe promo codes in batches for campaigns

Short answer: define the campaign, choose the coupon settings, set usage and expiration rules, generate unique Stripe promo codes, then export the list before the campaign goes live.

Promo codes are useful for launches, partner offers, winback campaigns, conference giveaways, and renewal incentives. The hard part is not creating one code in Stripe. The hard part is creating a clean batch of unique codes with consistent rules, then handing that list to marketing without losing track of which codes belong to which campaign. Workestic's Bulk Promo Code Generator is built around that campaign-first workflow.

When batch promo codes make sense

Use a batch when each customer, partner, channel, or campaign placement needs its own code. One shared code can work for a public sale, but unique codes are easier to limit, distribute, and audit.

• Launch lists: send unique codes to a waitlist or product announcement audience
• Partner campaigns: issue partner-specific codes with a common prefix
• Winback offers: give inactive customers single-use discounts
• Events: hand out codes through badges, cards, or QR-linked landing pages

Step 1: Name the campaign before generating codes

Start with a campaign name that will still make sense later. A good name includes the audience, offer, or timing, such as summer_launch_2026 or partner_acme_q3. That name should connect the Stripe coupon, the promo code batch, and the spreadsheet or campaign tool that receives the exported list.

Step 2: Choose the coupon settings

Decide whether the offer is a percentage discount, fixed amount discount, or another coupon structure supported by your Stripe setup. The coupon is the financial rule. Promo codes are the customer-facing codes that redeem that rule.

Step 3: Add redemption limits

Limits keep campaign distribution under control. For individual outreach, single-use codes are usually cleaner. For partner or field campaigns, you may want a total redemption cap across the batch, plus an expiration date so unused codes do not linger forever.

Common controls include one redemption per code, a total maximum redemption count, a minimum purchase amount, and an end date. The more public the campaign, the more important these controls become.

Step 4: Preview the generated batch

Preview matters because code mistakes spread quickly. Check the prefix, number of codes, expiration date, discount value, and redemption limits before the codes are shared outside the billing team.

A useful preview shows the first few generated codes and summarizes the rules behind the batch. That gives marketing, finance, and support a fast way to confirm the offer before it reaches customers.

Step 5: Export the code list for campaign operations

Once the batch is approved, export the codes to the system that will send or track them. For email campaigns, that may be a CSV upload. For partner teams, it may be a shared list. For events, it may be a print or QR workflow.

Keep the campaign name, coupon settings, export date, and owner with the list. Those details make support questions easier when someone asks why a code did or did not work.

Common mistakes to avoid

• Using one public code for every channel: reporting and abuse controls become weaker
• Skipping expiration dates: old offers can be redeemed after the campaign is over
• Generating codes before the offer is approved: cleanup gets harder later
• Exporting without campaign context: support teams cannot trace what each batch means

Manual workflow: generating campaign promo codes in Stripe

The manual workflow is to create a coupon, generate promotion codes, set redemption limits, define expiration dates, and export or copy codes for the marketing team. For a small test, that is fine. For a partner campaign, event, launch, or winback list, the code batch needs naming rules and review before it reaches customers.

A batch workflow should make the campaign rules visible: discount type, code prefix, number of codes, expiration, redemption limits, and whether each code can be used once or many times.

Where teams get stuck

• Code prefixes are inconsistent, making campaign attribution harder later.
• Marketing asks for more codes after the original batch rules are forgotten.
• Expiration and redemption limits are checked manually after codes are shared.
• Promo code campaigns are disconnected from Payment Link tracking.

Promo code batch checklist

• Name the campaign and code prefix before generating any codes.
• Set expiration and redemption limits in the same review step.
• Export the first batch with enough context for marketing operations.
• Use localized pricing review before running region-specific discount campaigns.