A discount code naming scheme you will still understand in June

Open your discount codes list and read it honestly. Somewhere in there is FRIENDS, which you cannot date. There is SAVE10, which might be ten percent or ten pounds. There is a code you made for a podcast host whose name you can no longer remember, and one called TESTTEST that you are 80% sure is still live. None of this happened because you are disorganised. It happened because every code was named in the ninety seconds before it was needed, and ninety seconds is not enough time to think about February.

The real cost of a badly named code

The obvious cost is a few minutes of confusion. The actual cost turns up in three other places. First, you cannot retire what you cannot identify, so old codes stay live because deleting them feels risky. Second, you cannot compare campaigns, because the only thing distinguishing March's push from May's is your memory of them. Third, you start avoiding codes altogether, which quietly removes one of the few tools that reliably moves a hesitant buyer.

The hard part is a genuine conflict between two audiences. A code that a listener has to remember from a podcast wants to be short, human and sayable. A code that you will read back in a list wants to be precise and boring. Those are different design goals, and pretending one code can serve both is how you end up with fourteen codes named after seasons. The answer is to accept the conflict and give each audience its own class of code.

One more thing worth naming early: discount codes are not tracking links. store.fan already reports views, buyers and revenue per product along with traffic source, so the code name does not have to carry everything. It has to carry what you will want when you are deciding, months later, whether to run that campaign again.

Named as you go, versus named to a pattern

Here is the same year of codes, written both ways. Nothing about the platform changes between the two columns. The only difference is that ten seconds of thought went into the left-hand side of each name.

The four-part pattern

Four segments, separated by hyphens, always in the same order. The order matters more than the abbreviations, because a consistent order means an alphabetical list groups itself by campaign without you doing anything.

1. 1Campaign — three to six letters for what this push is: LAUNCH, SPRING, BLKFRI, RESTOCK, WEBINAR. Use the same word every time you run the same kind of push, so the list groups itself.
2. 2Channel — two or three letters for where the code went out: EM for email, IG, YT, TT, PC for a podcast read, DM for anything you sent by hand, PT for a partner.
3. 3Month and year — four or five characters, MAY26, JUN26. This is the segment that saves you, because almost every question you will ask later starts with when was this.
4. 4Value or variant — the number: 20 for twenty percent, 10 for ten off in your currency. Pick one convention for your whole store and never mix them, because a list containing both is worse than a list containing neither.

• SPRING-IG-MAY26-20 — the spring push, posted on Instagram, twenty percent.
• WEBINAR-EM-JUN26-15 — the code read out at the end of the June webinar and repeated in the follow-up email.
• RESTOCK-DM-JUL26-10 — sent by hand to the people who asked to be told when the prints came back.
• BLKFRI-EM-NOV26-30 — the one you will thank yourself for next November.

What this looks like after two campaigns

Imagine you run a June launch across three channels. You create LAUNCH-EM-JUN26-10 for the list, LAUNCH-IG-JUN26-10 for stories, LAUNCH-PC-JUN26-15 for a podcast read where the host asked for a slightly better number, and LAUNCH26 as the hero code you say out loud. Four codes, one campaign, and a list that sorts them into a block.

In September you want to know whether the podcast read was worth doing again. You open the list, find the one code with PC in it, and read its redemptions next to the others. Then you cross-check against per-product analytics, which show you views, buyers, revenue and traffic source for the product itself. Fifteen minutes, no guesswork, no scrolling back through a spreadsheet you kept for three weeks in the spring and then abandoned.

The mistake most people make

The mistake is encoding the discount's terms in the name and then changing the terms. A code called SAVE20 that you quietly edited to 25% is now actively lying to you, and it will keep lying every time you read the list. If the terms change, retire the code and make a new one with the correct name. Codes are free to create and expensive to misremember. The same logic applies to the month segment: never recycle last year's code because it is already set up, because the moment you do, your whole naming system stops being trustworthy and you are back to guessing.

Naming schemes are dull, which is exactly why they work. You are not trying to impress anyone with a code name, you are leaving a note for a version of yourself who has forgotten the entire month in which it was written. Four segments, same order, every time.