Launch checklist · Promo codes
Manage a promo-code offer from request to redemption.
A useful promo-code program controls who can receive an offer, which code they receive, how often they can use it, what happens when something goes wrong, and what the brand can see afterward.
The code is the easy part. The rules around it make the offer work.
The program still has to decide who qualifies, which offer applies, how the request is verified, what limit is enforced, and what the person sees after a code is issued.
A controlled program keeps the person, offer, code, decision, expiration, redemption, and exception history connected. That gives the brand room to change the offer without losing track of what happened.
Decisions to work through
1.Define the offer
Write the business purpose, eligible product, value, timing, and intended action in plain language.
- What should this offer help the brand accomplish?
- Which products, bundles, or purchase paths does it cover?
- What should the person do after receiving or using it?
Take away: A one-page offer definition with a clear outcome and next action.
2.Set eligibility and limits
Name the qualifying partner organizations, roles, markets, and any training or employment requirements.
- How will employment or partner affiliation be verified?
- Can different groups receive different values or products?
- How many codes can one person request and during what period?
Take away: An eligibility and limit matrix that can be applied consistently.
3.Prepare the code inventory
Use separate groups of unique codes when offers, markets, products, or eligible groups need different inventory and reporting.
- Which code inventory supports each offer and group?
- What happens when the inventory runs low or a code fails?
- Who can add, remove, or replace codes while the offer is live?
Take away: Named code inventories with minimum thresholds and an accountable owner.
4.Design issuance and status
Make it clear whether a code is available immediately, requires review, has expired, or needs help.
- What does the person see before and after requesting a code?
- When is manual approval required?
- Can an expired or failed code be reissued, and under what rule?
Take away: A request-to-code-to-status path with the messages people will receive.
5.Connect redemption and reporting
Decide how the commerce or delivery system will return usage information and how often the records will be matched.
- Can the commerce system report which codes were redeemed and when?
- Which product, order value, partner, or market fields are available?
- What will the team review weekly while the offer is active?
Take away: A reporting cadence that connects issued codes with known usage and open exceptions.
A launch opportunity arrives with two weeks to act.
Illustrative example
A consumer brand learns that a retail partner will feature a new product. The brand wants verified store employees to try it before the promotion begins, but the offer needs different limits by role and must end with the retail event.
- Who qualifies
- Eligible retail employees are verified against the partner's employee list and grouped by store and role.
- Offer
- Each eligible employee can request one product-specific code from the inventory assigned to that role.
- Control
- The code expires after the launch window. Failed codes can be replaced once, while duplicate requests move to review.
- Record
- The brand can see eligibility, requests, issued codes, known redemptions, remaining inventory, and exceptions by store.
Before launch
- The offer and intended outcome are written in one sentence.
- Eligible partners, roles, markets, and products are defined.
- Verification, limits, expiration, and repeat-request rules are documented.
- Every offer is connected to the correct code inventory.
- Low-inventory and failed-code owners are assigned.
- Confirmation, denial, expiration, and help messages are ready.
- Redemption data and reporting frequency are understood.
- The team has a date to review, adjust, extend, or close the offer.
Common questions
Should every person receive a unique promo code?
Use unique codes when the program needs individual limits, expiration, replacement history, or a reliable view of who used the offer. A shared code can fit a broad public offer, but it provides much less control.
Do codes need to be issued immediately?
No. A verified and eligible request can be issued immediately, while unusual requests or missing information can move to review. The person requesting the code should always see the current status.
What if the commerce system cannot report redemption in real time?
Use the most reliable cadence available, such as a daily or weekly file. Keep issuance and redemption as separate statuses so the team does not imply that every issued code was used.
Publication details
Published by Incenify on .
This guide reflects Incenify’s practical approach. Adapt the decisions to your market, partners, and applicable requirements.
See a controlled product-access offer.
See how eero uses Incenify to offer its own products to a verified partner audience.