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

E-commerce Marketing › Expert

Running a Winter Peak and Its Close-Down for a Jigsaw Puzzle Shop

You run an invented jigsaw puzzle shop's winter peak as one programme instead of a set of team plans that meet on the first morning. You finish with a promotion signed off on its break-even, a stock and delivery gate, a build, freeze and readiness plan, a decision table for the window, a close-down list for every channel at the end time and a reading plan that judges the peak on what it added rather than on its headline.
ExerciseExpert levelModule 1: Peaks, promotions and full price11 minUpdated

Why this matters

The advanced ecommerce level judged a sale on contribution margin, segmented a catalogue by margin and valued customer cohorts. Each of those is one decision made well. A peak is different: the promotion plan, stock, merchandising, the feed, paid media, email, partners, customer service and measurement all land in the same few weeks, each owned by someone different, and most of what goes wrong is decided weeks earlier at the joins between them. The expert job is to own the sequence rather than any one part of it.

For the puzzle shop in this exercise, the peak season trading playbook means one trading lead taking last winter's loose parts through a fixed run of checkpoints. The offer is agreed only once its break-even is known; the hero puzzle and the packing bench are checked before anything is built; the build ends with the service team briefed, changes frozen and a readiness gate passed; a short morning meeting steers the window; and the review counts what the sale added and whom it brought in. The promotion close-down SOP covers the moment the shop got wrong last year: one person switching the offer off everywhere at the stated end time, in a fixed sequence, because a code that still works or a stray last-call text either breaks the promise of a deadline or spends money for nothing.

The puzzle shop and its winter

Plevusel Puzzles is an invented online shop selling jigsaw puzzles, puzzle boards and mats. Its winter gifting weeks carry most of its year, and last winter's sale went wrong at the joins rather than in any one channel.

Illustrative example — not a real result

Plevusel Puzzles: the team, last winter and this winter's proposal

The team: the owner; a merchandiser who also keeps the product feed; a freelance paid media manager running Shopping, Performance Max and Meta; an email and social marketer; two customer service staff; a warehouse lead; a part-time bookkeeper.

Last winter's sale was 25% off every puzzle for six days, Thursday to Tuesday.

What went wrongHow it was found
The code still worked at checkout three days after the deadlineA customer asked why
The feed showed sale prices for two days after the site reverted, because sale prices had been typed over the normal onesPrice mismatch warnings in Merchant Center
Customer service learned the offer from customers on the first morningThe first hour's enquiries
A last-call email went out the morning after the sale endedComplaints
The review reported "orders up 70% on the week before"Nobody questioned it
Last winter, promoted puzzlesOrdersBaseline: same days, two years ago, no sale
The six sale days1,360800
The four weeks after2,0502,300

Contribution margin on puzzles at full price, after goods, delivery and payment fees: 50%.

This winter's proposals:

  • The owner: 25% off every puzzle for six days, as last year.
  • The merchandiser: 15% off the gift range (boxed puzzles and puzzle-and-mat sets) for five days, Thursday to Monday, new releases excluded, aimed at gift buyers new to the shop.

Stock and capacity: the year's hero design, a 1,000-piece puzzle, has 240 units and no delivery before the peak; at last winter's sale its predecessor sold about 70 a day. The warehouse packs up to 400 orders a day, and the courier's last collection for delivery before the celebrations is fixed.

The offer would appear in: checkout codes and site prices; the product feed for Shopping and Performance Max; the Meta catalogue and sale ads; an announcement email, a reminder email and a last-call text; the abandoned basket email, which quotes the current code; the homepage banner and the sale page; a pinned social post; two deal-site partners with their own codes; customer service saved replies.

Day two of the window, at the stand-up:

  • The paid media manager reports Performance Max returning well above its target and wants to raise its budget beyond the plan for the weekend.
  • The merchandiser finds one boxed puzzle at the sale price on the site and the full price in the feed.
  • Customer service reports customers asking whether the code works on mats and boards.
  • The warehouse lead reports 95 hero puzzles left.

One programme, one trading lead

At Plevusel the programme's owner is a trading lead with a named deputy. The trading lead runs each checkpoint and each morning's meeting, keeps the decision log, and is alone in being able to alter the plan once the sale is live. Every phase closes with a brief phase-gate review: each owner brings their evidence, and the trading lead rules whether the work carries on as planned, changes course or halts. In a team this small several jobs sit with one person, yet each job still gets a name on paper; last winter's surprises came from work nobody had been given.

The window stays workable because of the playbook's rules on decisions. Anything the plan already settled, such as a budget step agreed in advance with the paid media manager, goes ahead without asking anyone; only the unforeseen reaches the trading lead. Each ruling is logged with the hour and the reasoning, so that the review can later separate what a decision did from what the season would have done anyway.

Task

  1. Run the first gate: say which promotion goes ahead and why, using the break-even the playbook asks for before anyone agrees a discount, and say what the shop's reference prices and deadline must be.
  2. Run the stock and delivery gate: decide what happens to the hero puzzle and what promise the shop makes about delivery.
  3. Plan the build, the service brief and the change freeze: what is built when, what the freeze covers, what stays allowed and who decides exceptions.
  4. Say what the readiness gate checks and what happens to an item that fails it.
  5. Take the four items from day two's stand-up and decide each one: who decides, what is done and what is logged.
  6. Write the close-down for the end time: the order, the owner of each step and the checks the next morning.
  7. Write the reading plan: when the peak is judged, against what, and what happens to the customers it brought in.

Worked answer

Who leads. The owner is the trading lead and the merchandiser the deputy; the bookkeeper is the finance partner, the warehouse lead the stock contact and the senior of the two service staff the service lead. Every role in the playbook's list has a name, including the two it names as the ones most often left unowned, the stock contact and the service lead.

The promotion and its break-even. The guide to planning promotions starts with the job, and the merchandiser's proposal has one: bring in gift buyers new to the shop, with full-price new releases protected. Plevusel's break-even follows the contribution margin and break-even guide: a discount comes off the margin on every order, so the uplift needed just to stand still grows fast as the discount approaches the margin. Last winter's sale did not clear its own break-even even before the weeks after are counted, so repeating it is refused. The smaller offer needs a far smaller uplift; the trading lead signs it off with the break-even written into the plan, and with the review told to check whether it was cleared after pull-forward, because that answer decides next winter's mechanic. The brief also carries the playbook's price checks, applied to Plevusel: the normal price shown beside each gift-range price is one the shop actually charged, Monday's end time is kept, and the price in the ads is the price at checkout. Whoever handles compliance reviews the offer; none of this is legal advice.

Illustrative example — not a real result

Plevusel Puzzles: the first gate in figures

Row labelLast winter, 25% offThis winter, 15% off
Break-even uplift: discount ÷ (margin − discount)0.25 ÷ (0.50 − 0.25) = 100%0.15 ÷ (0.50 − 0.15) = 43%
Uplift during the sale days(1,360 − 800) ÷ 800 = 70%To be read
Orders after the sale against baseline2,050 − 2,300 = −250To be read

Stock and delivery. Stock is a planning input in the marketing within capacity guide, and the playbook settles low stock at the gate rather than in the window, so the hero puzzle's advertising is decided now, before anything is built around it. The hero puzzle stays on the landing collection but is excluded from Shopping, Performance Max and the Meta catalogue, using the lifecycle labelling the product lifecycle guide describes. The warehouse lead and the courier's last collection set the last order date, stated the same way on pages, feed and ads, as the delivery promises guide asks.

Build, brief and freeze. Everything is built before the window: the landing collection, the permanent sale page from the seasonal sale pages guide, sale prices in the feed set with effective dates rather than typed over, the Meta peak structure launched early so the ad sets relied on have left learning, reminder emails held back from anyone who has already ordered, and partner codes and notice given through the affiliate promotions guide. The service briefing tutorial puts the offer, its terms, the saved replies, who to escalate to and the end date on a single sheet for the service staff. The freeze tutorial then names the period from the end of the build to the end of the window, lists the kinds of change frozen (tags, templates, feed rules, campaign structures and targets), keeps routine sends and posts moving, and names the trading lead as the person who decides exceptions. The freelancer and the site developer are told in writing.

The readiness gate. Plevusel's gate runs the sale promotion readiness checklist against this winter's offer: the gift-range prices and the claim beside them, the landing collection and the hero puzzle's absence from the ads, the media budgets, the announcement and reminder emails, and the tags, which the tracking verification checklist confirms. A line that fails, such as a reminder still addressed to people who have bought, returns to the person who owns it to be put right and checked again. The owner, as trading lead, then makes one call, launch on Thursday, launch with a named risk, or hold, and writes that call and its reason in the log.

Day two. The budget request is spend beyond the plan, which the playbook sends to the trading lead with the finance partner. The Meta peak-trading guide warns that the latest days' figures are never complete, so two days of platform return are weighed against the break-even, not read as proof; the trading lead holds the budget at the plan and logs the decision and its reason. The price mismatch is a freeze exception: the merchandiser reports it, the owner signs off the correction as trading lead, and the merchandiser makes it, tests it and logs it. The question about mats and boards is answered from the service brief, and the saved reply is corrected if it was unclear. The hero puzzle is a stock decision raised by the warehouse lead: the trading lead decides when it leaves the landing collection, once, rather than the team arguing about it each morning.

The close-down. The SOP works from the list of places the offer appears, which Plevusel builds at launch from the materials above. As promotion owner, the trading lead gives the final sign-off only once a check finds the offer gone from every one of them.

Illustrative example — not a real result

Plevusel Puzzles: the close-down at Monday 23:59

WhenOwnerStep
Friday beforeTrading leadEnd time confirmed in one time zone; each owner sent what ends with it
23:59MerchandiserCodes expired, site prices back; feed sale prices end on their effective dates
23:59Paid media managerSale ads paused or swapped; any seasonality adjustment checked to end with the window; raised budgets lowered
23:59Email and social marketerUnsent reminders and the last-call text cancelled; abandoned basket email no longer quotes the code; banner and pinned post down
Tuesday 09:00Email and social marketerBoth partners told in writing; their codes withdrawn; their deal pages checked
Tuesday 09:00Customer serviceSale replies switched off; wording for late questions in use
Tuesday 10:00Trading leadLogged-out check of codes, pages, feed and ads; dates entered in the change log

The sale page stays at its permanent address with out-of-season content, as the seasonal pages guide advises, and the start and end times go into the measurement change log.

Reading the peak. Plevusel judges the peak only after late-arriving conversions are counted and the post-sale weeks can be set against the baseline, using the promotion measurement guide: more than one baseline, incremental orders reported before, during and after with the net beside them, pull-forward, stock-up and cannibalisation, the margin given away, and new customers identified from the order system rather than assumed. The campaign wrap-up checklist closes the campaign and squares its figures with the order system, the campaign post-mortem template records causes and agreed changes, and the gift buyers the peak brought in get a second-order plan from the repeat purchase and loyalty guide. The scorecard goes to next winter's first gate.

Common mistakes

  • Choosing the discount, then the break-even. Last winter's depth was never going to pay back.
  • Letting several people decide the same thing. A budget raise, a price fix and a stock call each have one owner.
  • Advertising the hero product to the last unit. Low stock is decided at the gate, not argued about mid-peak.
  • A freeze with no exceptions route. The price fix becomes either a quarrel or an unrecorded change.
  • Typing sale prices over the normal ones. The normal price then has to be typed back, often wrongly.
  • Forgetting automations and partners. An abandoned basket email or a deal page keeps the offer alive.
  • Judging the peak on the headline. The sale days include orders borrowed from the weeks around them.

The module's checkpoint puts these judgements to a different shop and brings in the full-price protection test: whether sending customers fewer coded offers between planned events protects full-price trading.

Pages this lesson applies

Terms used on this page

Also related

Related