A Black Friday discount can increase conversion and still leave the store with less contribution after variable costs. The offer that attracts the most orders is not always the offer you should scale.
Black Friday discount testing compares the commercial effect of an offer, including price, product costs, shipping, and returns. Begin by deciding whether you are testing how an offer is described or changing the economics of the transaction.
Separate framing tests from offer tests
A framing test might compare “20% off” with “Save $20” on the same $100 item. The customer pays the same amount under the same conditions. This is primarily a presentation question.
An offer test might compare 20% off with a bundle or free shipping. That changes costs, eligible baskets, or both. It requires commerce-platform support and a scorecard that can account for those differences.
Do not present a bundle at one price in a page variant while the cart charges another. The promotion must be implemented through the transaction system before a customer-facing experiment begins.
Calculate the contribution you are trying to protect
For an operational comparison, define contribution as net product sales less the variable costs you choose to include. Those often include product cost, payment fees, shipping subsidy, and expected return costs. Keep the cost definition identical across variants.
The following is a simplified hypothetical example. The $40 variable cost is assumed constant per order, and fixed costs and acquisition spend are excluded.
| Metric per 10,000 eligible visitors | Offer A | Offer B |
|---|---|---|
| Purchase conversion | 3.0% | 3.6% |
| Orders | 300 | 360 |
| Net sales per order | $80 | $65 |
| Net sales | $24,000 | $23,400 |
| Variable cost per order | $40 | $40 |
| Contribution per order | $40 | $25 |
| Total contribution | $12,000 | $9,000 |
| Contribution per visitor | $1.20 | $0.90 |
Offer B converts more visitors but produces less contribution in this example. Real costs can change with basket composition, discounts, fulfillment, and returns, so replace the assumptions with your store's data.
Choose one commercial comparison
Pick an offer decision supported by a customer problem. If buyers hesitate over delivery cost, compare a shipping offer with an alternative of similar expected cost. If customers already buy complementary products, a bundle may be worth investigating.
Document eligibility, maximum redemption, inventory dependencies, and compatibility with other promotions. Decide whether all assigned visitors can receive the offer throughout the test.
Avoid comparing several deeply different offers at once unless traffic and analysis support it. A simpler two-group comparison is easier to implement and explain when the calendar is tight.
Write the experiment contract
Specify the randomization unit and preserve assignment across the journey. Define when exposure begins and how orders are associated with that exposure. Work with the testing platform and commerce team to handle repeat visits and offer sharing.
Choose contribution per eligible visitor as the primary metric when reliable cost data is available. Otherwise, use net sales per visitor with an explicit margin constraint and disclose that contribution is estimated separately.
Set supporting metrics: purchases, order value, discount redemption failures, cancellation rate, and returns when mature enough. The revenue measurement guide explains why the denominator and revenue definition need to stay consistent.
Keep the promise consistent across pages
Write a short offer specification that a teammate can check without interpreting marketing copy. Include the products, discount calculation, shipping threshold basis, dates, timezone, and exceptions.
Then inspect the ad, landing page, product page, cart, and checkout. For a bundle, remove one item and check the result. For a threshold offer, cross the threshold in both directions.
Test the order confirmation as well. A promotion can look correct before payment and still produce confusing receipt lines or fulfillment instructions.
Look for leakage and mixed eligibility
A public coupon may be shared between test groups. A shopper can also encounter the offer on one device and buy on another. Decide how your platform will record or limit that behavior, and document the remaining uncertainty.
Watch changes in product mix and stock. If one group loses its featured item halfway through, the observed comparison now includes that inventory event. Do not silently remove an inconvenient period after seeing the results.
Returns and cancellations may arrive after the campaign. Plan a follow-up view so the immediate net-sales result does not become the final profit claim too early.
Prototype copy while the commerce team owns the offer
Use VibeVariant to build supported presentation changes, such as equal-price savings copy or a clearer bundle explanation. Keep pricing and redemption logic in the commerce platform. The generated JavaScript and CSS can then be reviewed and handed to your experiment workflow.
Run the QA checklist with eligible and ineligible baskets. The preview should never imply an economic benefit that the customer cannot redeem.
Interpret the result as a business decision
A small sales increase with a large margin decline is a different outcome from a smaller, more profitable basket. Report uncertainty, inventory effects, and outstanding return data alongside the main metric.
For metric background, VWO's ecommerce metrics guide explains the relationship between conversion, order value, and revenue per visitor. This article's cost model and numerical example are original illustrations, not claims from that source.
If traffic is insufficient for a reliable randomized comparison, choose an offer using the best available economics and customer evidence. Record the decision as a commercial judgment rather than a statistically proven winner.
