Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Standard Operating Procedures

Discount Code Request SOP

A standard procedure for issuing a discount code to a partner, creator, email, insert or service team: approved offer, code type, register, test and expiry.
SOPintermediate10 min readUpdated

Owner, trigger and scope

The ecommerce manager owns the code register and creates every code: nobody else sets up codes in the shop. The promotion owner approves the offer each code carries and its limits, and can refuse a request that fits no approved offer. The requesting marketer briefs the recipient and confirms the code works where it will be used. The customer service lead holds the service team's batch of gesture codes.

The trigger is someone needing a discount code for an affiliate or creator, an email or text campaign, a printed insert, an event or a customer service gesture, beyond the public code a promotion already provides. The UTM link request SOP routes every tagged link through one issuer and one register; this procedure does the same for codes. The coupon diagnosis ends with the rule it enforces: "no code leaves the business without a line in the register".

Neighbouring jobs belong to other pages:

SituationWhere it is handled
Designing a promotion: its mechanic, eligibility, reference prices and end timePromotion brief template
Deciding which partners get which offer during a promotionRunning promotions through affiliates
Switching off a sale's codes and prices at its end timeEnding a sale or promotion SOP
An expired or wrong code still shown in a live ad or pageLive ad and page error response SOP

The SOP library routes the other recurring tasks, from the email campaign send that carries a newsletter's code to the end of a sale.

Before you start: inputs and access

InputOwnerNotes
The approved offer: what it gives, to whom, on which products and until whenPromotion ownerFrom the promotion brief or the offer's owner; no approved offer, no code
The recipient, the channel and how use will be creditedRequesting marketerCommission, a fee or nothing
The margin limit the offer must stay withinPromotion ownerWorked from the contribution margin of the products in scope
Access to the shop's discount settings and the code registerEcommerce managerOne issuer, so every code has a line
The programme terms or brief the recipient works underRequesting marketerAffiliate terms, a creator brief, the email brief or the service team's guidance

A discount code with no register line cannot be traced to an owner, and validation cannot reject an order that uses it through the wrong partner. If no register exists yet, start one with this request.

The procedure

  1. Check the request against an approved offer and its margin

    A code must carry an offer someone has approved: a promotion brief, an exclusive agreed with a key partner, a creator agreement or the service team's standing batch. The contribution margin guide explains that a discount lowers the contribution margin by the full amount, because the goods, delivery and fees still cost the same. Work out what an order keeps after the discount and any commission or fee, and compare it with the promotion owner's limit; the break-even calculator shows what a sale at that margin can afford. Decline a request that would undercut an offer already running or add a second public code: the diagnosis of customers who only buy in the sale counts sitewide codes among the habits that teach customers to wait. If the right depth is uncertain, the discount depth test answers it better than a guess.

  2. Choose the code type: public, tied to one recipient or single use

    The recruitment, compliance and fraud guide sets the coupon rules: a code handed to a single partner, a newsletter's readers or one unhappy customer travels to voucher sites, so every code belongs to whoever received it, and valuable offers are safer as codes that work once.

    Code typeUse it forWhat protects it
    PublicThe offer every customer and partner may useIts end time and the brief's eligibility rules
    Tied to one recipientA creator, a review site's exclusive, a key partnerThe terms: no commission when it arrives through someone else
    Single useService gestures, email offers, valuable or first-order offersEach code works once; service batches belong to no partner

    The guide to managing key affiliate partners ties every exclusive to its partner, and the creator tracking guide adds that short-lived codes and codes tied to a first order leak less.

  3. Write the register line before the code exists

    The coupon diagnosis asks for a register that gives each code its owner, its purpose and its end date, names who received it and whether it works once, and is read at validation. Record the code, its type, owner, purpose, recipient, offer, eligibility, products, start and end time and approver, leaving room for the test result and the closing note. Goodwill codes need an end time too, since the diagnosis warns that an open-ended one reaches deal pages like the rest. Where creator codes come from a roster sheet, as in the micro-creator programme tutorial, the sheet feeds the register rather than replacing it.

  4. Create the code with its eligibility, products, end time and limits

    Copy the settings from the offer, not from memory. The promotion brief template sets the fields: who can use the offer, how eligibility is enforced, for example by checking order history, the products included and excluded, the limits, whether it combines with other codes, and the end date with its time and time zone. Its working rules rest on general direction for the UK, where consumer protection law, which the Competition and Markets Authority enforces, reaches reference prices and urgency claims, and the Advertising Standards Authority's codes apply to price and savings claims in ads: a reference price must have been genuinely charged, deadlines have to be kept and the advertised price has to be payable. That is general direction, not legal advice. The shop platform's help centre holds the current settings screens; this procedure does not quote them.

  5. Tie the code to its recipient in the partner and reporting records

    The guide to running promotions through affiliates ties every code beyond the public one to the partner who received it, and the brief says an order carrying another recipient's code earns no commission. Record the code against the partner wherever validation and reporting read it: the partner record, the creator report, the send's record or the insert version. The code works beside the credit rule in the attribution and deduplication guide, not instead of it, and the placement's link tagged with UTM parameters goes on the same line. Whether an order carrying the code and no partner click earns the recipient anything, and who is paid when the code and the click belong to different partners, is settled in the guide to crediting affiliates for orders made with their codes.

  6. Test the code at the checkout on a phone, including a case that should fail

    The sale promotion readiness checklist has a phone run through the checkout with a code in it, because late changes to the site often break the way codes are applied. Test logged out and, where eligibility depends on order history, from a test account with past orders. An eligible basket takes the discount and shows it clearly, as the checkout optimisation guide recommends. Then test what should fail: an excluded product, an existing customer on a first-order code, a second use of a single-use code. Discount code entry is one of the failure points the tutorial on tracking errors and failed actions lists, so a rejected-code event later shows whether real customers are being refused. Write the result on the line.

  7. Send the code with the wording, dates and rules the recipient must follow

    The tutorial on writing affiliate programme terms puts the coupon clause in the terms: the codes each partner is allowed to publish, the rule that a code belongs to whoever received it, and whether an order carrying another recipient's code earns commission. A creator receives the code in the brief with where it should appear, as the creator brief tutorial sets out. An email's code travels with the offer terms in writing through the email send SOP, the service team receives its batch with the approved wording, and a printed insert follows the packaging and order inserts guide: one job per card.

  8. Read redemptions and look for the code where it was never issued

    The creator tracking guide explains why codes are read beside links: a code catches some buyers a link misses, but codes leak, so redemptions are an indicator rather than a count. At each commission validation run, match the code on every partner order to the register; the recruitment guide's fraud table reads a code turning up on a site nobody gave it to as the sign of code hijacking. Send the partner a stray code was issued to the evidence, ask how it travelled, and withhold commission only on the orders affected, as the terms allow. The month-end commission tutorial carries the rejections into the close.

  9. Expire the code at its end time and close the register line

    A code that belongs to a sale ends with everything else in the ending a sale or promotion SOP; a code issued alone is expired by the ecommerce manager, who tests it once more at the checkout. Tell the recipient it has ended and what replaces it, then close the line with the redemptions read and any leak found. An ended code still shown in a live ad or on the brand's own pages goes to the live ad and page error response SOP, and the guide to reviewing a marketing error finds out why the end time was missed.

A hiking sock maker handles a month of code requests (illustrative)

Illustrative example — not a real result

Six code requests, five register lines and one leak

Snoxburl Socks, an invented hiking sock maker, received 6 code requests in October while a public autumn sale of 15% off ran on its site. Its average order was £40, goods, delivery and payment fees cost £22 an order, and the promotion owner's limit was £10 of contribution per order after discount and commission. Two creators each got a tied code for 10% off, ending after 30 days: an order of £36 kept £14, and £11.12 after the creators' 8% commission of £2.88. A review site got a tied code for 10% off its readers' first order. The newsletter editor asked for a second public code of 20% off; the promotion owner declined it because it would undercut the running sale. An insert card for gift orders, whose recipients had never bought, got a first-order code checked against order history, and the service team got a batch of 40 single-use codes for £5 off, tied to no partner. The month ended with 5 new register lines, 1 of them for the batch, and 1 declined request with its reason. The phone test found the gift code accepted on an account with past orders; the setting was fixed and retested before the cards were printed. At the validation run, 37 voucher-site orders carried a spring creator code set up with no end time. It was expired that day, the 37 orders earned the voucher site no commission under the coupon clause, and the line was closed with the leak noted.

QA checks

The ecommerce manager confirms each check before the code is sent and again when its line is closed; a failed check goes back to the step that owns it.

  • Every live code has a register line with an owner, a purpose, a recipient and an end time.
  • The code works for the customers and products it is meant for and is refused for those it is not.
  • Every code beyond the public one is tied to its recipient, and the terms or brief say what happens when someone else's code is used.
  • The offer stays inside the margin limit the promotion owner approved.
  • Codes past their end time are refused at the checkout and their register lines are closed.

Hand-offs and records

The requesting marketer receives the code with its register reference, wording, dates and rules, and passes them to the recipient. The affiliate manager receives the register for each validation run. The customer service lead receives the batch and its end date. The promotion owner receives declined requests and closing notes, which feed the next promotion brief. A leak that keeps recurring goes to the coupon diagnosis.

The lasting record is a line in the code register for every code: the code, its type, owner, purpose, recipient, offer, eligibility, products, start and end time, approver and test result, closed later with the redemptions read and any leak found.

Common mistakes

  • Creating the code first and the register line later. Later rarely comes, and an untraced code cannot be enforced.
  • A second public code during a sale. It undercuts the running offer and teaches customers to hunt for codes.
  • Codes with no end time. A goodwill or creator code with no end keeps working on deal pages.
  • Untied partner and creator codes. A code nobody owns earns commission for whoever publishes it.
  • Testing only the case that should work. Customers notice the code that works for everyone.

Frequently asked questions

Should every partner and creator get their own discount code?

Only where a code beyond the public one is needed. Partners who carry the public offer can share the public code, so no partner shows a worse deal than the brand's own site. A creator, a review site with an exclusive or a key partner gets a code tied to them, which shows whose audience used it and lets the terms say that commission is not paid when the code arrives through someone else. Tied codes still leak, so their redemptions are read as an indicator of what the recipient produced, not an exact count.

Can customer service give an unhappy customer a code without asking each time?

Yes, within a rule set once. The promotion owner approves the value and the end date of a batch of single-use codes tied to no partner, the batch gets its own line in the register, and agents draw from it for gestures the service lead's guidance describes. Each code works once, so a code that reaches a deal page is worth nothing to the next shopper. What agents should not do is invent a public code or a deeper discount on the spot, because that code has no register line, no end time and no owner, and it is the kind that ends up on voucher sites.

What should happen when one of our codes appears on a voucher site?

Look it up in the register first: who it was issued to, what it was for and whether it should still be live. A code past its end time is expired at once and its line closed with the leak noted. A live code tied to a partner earns that voucher site nothing if the programme terms say commission is not paid on a code issued to someone else, so validation rejects those orders with that reason. Send the partner the code was issued to the evidence and ask how it travelled before drawing conclusions, and issue them a replacement if the offer still has time to run.

Terms used on this page

Tools to try

Where this page is used

Sources

  1. Competition and Markets Authority — GOV.UK
  2. Advertising Standards Authority — ASA

Related