Black Friday landing page ideas: the price step

A sale page makes several promises, and each one comes from a different part of the site. The headline says sale, the countdown reads the visitor's clock, the grid shows a price from a discount rule, the product page reads the regular price field, and the cart applies the discount or does not. Any one of these can disagree with the others, and a shopper meets the disagreements in order. They see numbers, never the rule. The owner checks the page once, on the day the rule was set, when every number agrees.

• The grid, the product page and the cart show the same sale price for the same item.
• The countdown ends at one time sent by the server, and a reload does not restart it.
• A discount code states its minimum spend and what it applies to, beside the field.
• The shipping cut-off names a date and a time zone, on every page that mentions it.
• After the end time the page says the sale is over, and the sale price stops appearing.

A timer can be right on the first visit and wrong on the second. A countdown that starts from a fixed length on each load, or keeps its start in the browser, gives a shopper a new deadline every time they return. A wrong version shows Ends tonight with a timer that begins again on each load. A right version uses one end time sent by the server, and the browser only draws the time left. Test it by noting the time left, reloading after a moment, and checking that the number only went down. After the end time, the page should say the sale is over, not show zero with a live button.

The grid often reads its price from a discount rule, while the product page reads the regular price field, and the cart applies the rule at the last step. The result is a price the shopper cannot reach. Pick one item that is in the sale. Write down its price on the grid, on its product page and in the cart. A wrong version shows the sale price on the grid and the regular price in the cart, with nothing in between. A right version shows the same sale price in all three places, with the regular price struck through beside it on each.

A discount code can fail for reasons the page never names. It may have a minimum spend the cart has not reached, a product restriction, an end date set in another time zone, or a single use someone already spent. Phones make it worse, because a pasted code can carry a trailing space. Test the code by typing it, then by pasting it with a space after it. A wrong version shows Invalid code and nothing else. A right version says the code needs a larger cart or does not cover this item, in the line under the field. Then check that the code shows in the order total at checkout.

Checkout flow testing

Free shipping by a date is a promise the shopper reads in the first minutes, and the cut-off is often written as a date and a time with no zone. A shopper in another country reads the time as their own. Ask the question a shopper would ask: will this arrive by Monday? Read the cut-off line on the landing page, in the cart and at checkout. All three should name the same zone, or drop the time and keep the date. A wrong version reads Order by Monday midnight. A right version reads Order by midnight Eastern time on Monday, and repeats it in the cart.

Sale rules get added late, often in the week of the sale, and each rule is another place where the grid and the cart can disagree. Run the same shoppers through the sale path after each rule is added, and compare the three prices again. A test account, given with paid credits, can reach a members-only offer behind a login. Each sale link from an ad or an email can be checked on its own before it goes out.