Skip to main content
Version: Current guides

Create, apply and disable coupons

Availability and scope​

Public merchant access to coupons, promotion codes and their dashboard remains unconfirmed. This guide supplies preparation steps and a workflow for accounts and environments with confirmed access. It does not establish that current Checkouts accept coupon parameters or redeem codes automatically. If controls are missing, ask your verified onboarding contact rather than calling unpublished marketing interfaces.

Coupons reduce amounts due for a collection or selected subscription periods. They are distinct from platform-plan discounts, customer credit and completed funds refunds. This guide covers collection discounts, without promising email campaigns, customer segmentation or campaign-management tools.

Define the rules before publishing​

Prepare the purpose, eligible products or payment entries, discount type, currency, minimum spend, total and per-customer limits, and start and end times. For subscriptions, identify whether the discount applies to the first period, selected periods or an ongoing duration. A fixed-amount discount must match the amount-due currency; do not assume automatic conversion into another asset.

Assign creation, approval and disabling responsibilities, set a budget and prepare customer-facing terms. Before release, test that the discounted amount matches the business order in an authorized environment. Creating a code alone is insufficient.

Create and verify an enabled coupon​

  1. Search coupon management for the intended code and purpose first. Enter the code, name and description using current form requirements rather than assuming character, case or editing rules.
  2. Choose a fixed amount or percentage and review the value, currency and minimum spend. Ensure the reduced amount meets the business agreement and collection-entry restrictions.
  3. Select the product, payment-link, Checkout or subscription scopes actually offered. Support in one entry does not establish support in every other entry.
  4. Set offered total and per-customer limits and validity, checking timezone and start and end times. For subscriptions, verify the affected periods; a first-period discount does not discount every renewal.
  5. If drafts and previews are offered, save a draft and test eligible and ineligible orders: sufficient or insufficient spend, wrong currency, excluded products, not-yet-started or expired validity, and exhausted limits.
  6. Verify the payment display, discounted amount and real order records before publishing, and retain internal approval. Do not calculate the order as if multiple coupons stack; use only combinations actually offered and tested.
  7. Share the code and terms with intended customers without dashboard links, customer access tokens or credentials. Confirm every payment using orders; redemption does not establish payment success.

Reconcile use and results​

Using available coupon details, reconcile redemptions, linked orders, discounts and receipts for the same period, currency and entry. Distinguish claiming or entering a code, redemption and successful payment. Usage counts are not new revenue.

Sample normal, unpaid and refunded orders to understand statistics and post-refund limit handling. Do not assume refunds restore usage or reactivate expired coupons. For exports, check scope and permissions and preserve definitions using reports.

Change, pause or end an offer​

Inspect usage and generated orders before editing supported fields. If the code, type or amount is locked, preserve the original and create a new offer rather than overwriting historical discounts.

When the budget is exhausted or the offer ends, use an offered pause or disable operation and verify its result. Inspect new orders separately from existing Checkouts and subscriptions; disabling does not establish that historical discounts were reversed, existing amounts changed or payments canceled. Delete only where allowed and retain associations needed for reconciliation.

Resolve failures​

SituationChecks and action
Missing or duplicate codeCheck environment, code and existing records without overwriting another offer
Not started, expired or pausedCheck current state, time and timezone; explain eligibility and separately approve any replacement
Total or customer limit exhaustedInspect redemption and customer associations rather than assuming a counting error or restored limits after a return
Wrong spend, currency or productCompare the original order; do not change it to an incorrect asset or product to force eligibility
Preview and payment amounts differStop sharing affected entries and inspect the real order, discount association and generated session; handle paid differences through support
Save timeout or concurrent editingReload the current coupon and change record before retrying, without publishing duplicates

Funds returns require refund availability. For customer billing, see products and subscriptions; for your own platform plan, see fees and plan review.