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

E-commerce Marketing › Expert

Checkpoint: Peaks, Promotion Close-Downs and Full-Price Protection

Scenario questions set in an invented bird care shop test the judgement behind the first expert e-commerce module. They cover decision rights in the window, the stock gate, freeze exceptions, closing an offer and its temporary bidding settings in every channel, and setting up and reading a test of fewer coded offers, with each answer explained.
CheckpointExpert levelModule 1: Peaks, promotions and full price4 minUpdated

What this checkpoint covers

Kruvass Bird Care, an invented online shop selling bird food, feeders and nest boxes, runs a spring nesting event and emails codes fortnightly. The questions apply the peak season trading playbook, the sale and promotion close-down SOP and the full-price protection test.

Illustrative example — not a real result

Kruvass Bird Care: the nesting event

  • Event: 20% off nest boxes and feeders for seven days, ending Sunday at 23:59; the owner is trading lead.
  • Hero product: a camera nest box, 150 in stock, no delivery before the event; last spring it sold about 40 a day in the event, at the best return in Shopping.
  • Draft close-down: codes expire at 23:59; the buyer retypes normal feed prices on Monday at 10:00; a last-call text goes on Monday at 09:00. Not listed: the basket email quoting the code, a garden birds club's own code, and the seasonality adjustment, hand-lowered target and raised budget set for the event.
Last spring, promoted linesOrdersBaseline: same weeks a year earlier
The seven event days1,450900
The three weeks after2,3002,700

Task

  • Note what you would do in each scenario and why, before reading on; a correct move backed by the wrong reasoning still counts as a miss.
  • Go back over the page section an answer points to whenever you miss it.

Questions

  1. On day three a planned budget step and a scheduled non-buyer reminder are due, and the buyer wants to extend the event because feeders arrived. Which goes to the trading lead?
  2. At the stock gate the paid media manager wants the camera nest box kept in Shopping for its return. Your call?
  3. On day two the developer finds the purchase tag firing twice on the event page and plans a quiet evening patch. What should happen?
  4. What does the draft close-down miss, and in what order should it run?
  5. The owner would stop the fortnightly codes for everyone and compare with last summer; the email marketer, only for rare openers. How should the test be set up?
  6. At the end of the window the reduced cell shows lower revenue per customer. Is it a loss?
  7. Last spring's review called the event the best week of the year. Should it be repeated as it was?

Answers explained

  1. Only the extension. Planned steps need no approval. An extension would make a published deadline untrue, so it goes to the trading lead with the compliance check, and the published end date normally stands. See what the trading lead decides.
  2. Take it out of the advertising. It sells out mid-window, so its return buys visits to an empty page. The gate settles it once, before the build. See the stock and capacity phase.
  3. A freeze exception, decided and logged. Under the change freeze the trading lead decides, and the fix is tested and logged with its time and reason; a quiet patch leaves a jump in recorded orders nobody can explain later. The readiness gate also missed a tracking check. See freeze exceptions.
  4. Four leftovers and the bidding. Feed sale prices should carry effective dates and revert with the site; the text is cancelled, the basket email stops quoting the code and the club's code is withdrawn in writing. The adjustment ends with the window; target and budget return to pre-event values. Order: end time and list, codes and prices, feed, ads and bidding, emails, pages, partners, service, annotation, next-morning checks. See the close-down procedure.
  5. Assign customers at random, once. Last summer differs in season, stock and prices; rare openers differ from everyone. The control keeps the rhythm, the reduced cell gets codes only at planned events, and public sales, prices and offer-free messages stay identical. List every code route, send nothing in place of a withheld code and fix a window of several cycles. It is not a full holdout group: planned events still go out. See the test design.
  6. The reduced cell wins. Revenue favours whichever cell discounts more, so the test reads profit at gross margin per assigned customer, then checks active customers, unsubscribes and public-sale orders against their limits. See the decision rule.
  7. Not on that evidence. Most of the event's gain was borrowed from the weeks after, and the net falls well short of what the discount needed. Read baseline, pull-forward, margin and new customers before choosing the mechanic. See measuring the peak.
Illustrative example — not a real result

Answers two, six and seven: the arithmetic

Camera nest box: 150 ÷ 40 ≈ 4 days of stock in a 7-day event.

Cell, 9,000 eachRevenue per customerGross profit per customerActive at endUnsubscribesOrders in public sales
Fortnightly codes£58.40£21.1061%3.4%18%
Planned events only£54.90£22.6060%2.9%21%

Difference £1.50 per assigned customer, interval roughly £0.20 to £2.80. Limits set before launch: active customers no more than 2 points below control, unsubscribes no more than 1 point above control, public-sale share no more than 5 points above. All guardrails hold.

Event: 1,450 − 900 = 550 extra orders, then 2,300 − 2,700 = −400, net 150. Break-even uplift at a 45% contribution margin: 0.20 ÷ (0.45 − 0.20) = 80%, against 61% in the event and 17% net.

Where to go next

Struggled with the first four? Work through the jigsaw puzzle shop peak exercise again; for the others, revisit the advanced e-commerce level. The next module opens with the aquarium store Shopping audit and Performance Max test.

Pages this lesson applies

Terms used on this page

Also related

Related