Black Friday Trust Checklist for Online Stores (2026)

Before Black Friday 2026, verify that customers can understand your offer, see what they will pay, judge when their order should arrive, and find help if something goes wrong. Then test whether your store actually delivers the shopping experience those promises describe, on both mobile and desktop.

This checklist turns that goal into practical checks with clear pass conditions. Start with problems that could mislead customers or prevent a purchase, assign someone to fix each one, and retest after your final promotional changes.

Start with the fixes that should block your sale launch

Not every issue deserves the same urgency. A slightly oversized image and a checkout that charges the wrong amount should not sit in the same queue. Use the following editorial priorities to organize work, not as research findings or a legal compliance classification.

Give every issue a named owner and a clear expected result. Close it only after a successful retest, preferably by someone other than the person who made the change.

Visibility deserves its own check. In the Welo Badge 2026 Trust Gap Report, an analysis of over 200 US and Canada brands, 39% did not show returns information or a returns link directly on the product page, while 32% did not show costs or a cost calculator there. Information could have existed elsewhere on those sites.

These observations concern the brands analyzed, not all online stores, and describe visible information rather than actual delivery, return, or refund performance. The transaction tests below are recommendations for your store, not activities performed in that research.

1. Make the product and Black Friday offer clear

A customer should be able to tell exactly what the advertised price buys. Check specifications, dimensions or sizing, materials, included accessories, available variants, stock status, and relevant restrictions. For bundles, make the contents and quantities explicit rather than relying on the promotional image.

Compare the advertised discount with your pricing records and promotion settings. Confirm the reference price used for comparison, the calculation, excluded products, minimum spend, start and end times, and whether codes can be combined. Any countdown, limited-stock message, or other urgency claim should reflect real conditions.

The FTC's advertising guidance for small businesses explains that truthfulness standards apply to sale prices and price comparisons as well as other advertising claims.

• Open a promoted product and an excluded product on mobile and desktop.

• Select different variants, including an unavailable option, and check that images, prices, and stock messages update correctly.

• Add a bundle and a single item to the cart, then compare the result with the offer terms.

• Save dated screenshots and the relevant pricing and promotion settings.

Pass condition: Product details and promotional terms agree with what the cart and checkout actually provide.

2. Show costs and shipping charges before payment

Show the amounts you know early, and explain what depends on the customer's destination or selections. Review the item price, shipping, applicable taxes, mandatory charges, and any duties relevant to supported destinations. If an amount cannot be calculated immediately, provide a useful estimate or calculator where practical and state its assumptions.

Build carts below, exactly at, and above your free-shipping threshold. Check whether discounts change eligibility and whether excluded items count toward the threshold. Try valid, expired, excluded, and conflicting discount codes, then confirm that the explanation matches the calculation.

Repeat these checks for domestic destinations with different shipping rates and for international destinations only if your store serves them. Compare the advertisement, product page, cart, and final payment screen. A destination-based change should be understandable, not look like an unexplained surcharge.

Pass condition: The final amount is clear before payment authorization, and earlier estimates accurately explain what they include and what may change.

3. Give delivery estimates your team can support

Processing time is the period before an order is ready to ship. The shipment date is when it leaves your operation, transit time is the carrier's journey, and estimated arrival is when the customer should receive it. Avoid presenting one as another: “ships within two business days” is not a promise of arrival within two business days.

Use destination-aware dates or clearly bounded delivery windows supported by inventory, warehouse capacity, carrier schedules, and order cutoffs. Make the applicable time zone clear when a cutoff affects eligibility.

Ask fulfillment staff to check the estimate for an in-stock item, a preorder, a split shipment, and destinations with different service levels, where applicable. Then enter those scenarios on the storefront to confirm that shoppers see the same expectations.

For covered US merchandise orders, the FTC's Mail, Internet, or Telephone Order Merchandise Rule requires a reasonable basis for the advertised shipping timeframe, or shipment within 30 days if no timeframe is stated. That default concerns shipment, not a universal 30-day delivery deadline. When sellers cannot ship as promised, the rule requires obtaining the buyer's consent to a delay or refunding payment for unshipped merchandise.

Pass condition: Customer-facing dates match your fulfillment plan, and your team has a documented process for delay consent, cancellation, and refunds.

4. Make sale-item returns and refunds easy to understand

Put a useful return summary or descriptive policy link near the buying decision. Customers should not have to discover after ordering that a Black Friday product has different rules from the rest of your catalog.

• State which items are eligible and which, if any, are final sale.

• Explain what starts the return window, the deadline, and required item condition.

• Identify who pays return shipping and any applicable restocking fee.

• Distinguish a refund to the original payment method from an exchange or store credit.

• Explain refund-processing expectations and any holiday extension.

Have someone unfamiliar with your process find the instructions and attempt to start a return through your designated channel. Ask support how it would handle a discounted item, a gift, and an item covered by a holiday extension. These are the kinds of practical details highlighted in the FTC's online-shopping guidance.

Pass condition: Product-page summaries, the full policy, support answers, and refund procedures agree. Your stated policy should not suggest that it overrides mandatory consumer rights.

5. Use customer reviews without misleading shoppers

Invite customers to give honest feedback, not to confirm that they loved the purchase. If you offer an incentive, do not make it depend, explicitly or implicitly, on a positive review. The FTC's review-rule guidance distinguishes that prohibition from disclosure issues: failing to disclose an incentive can separately raise concerns under the FTC Act.

Check that product reviews belong to the displayed product, dates and counts are accurate, and sorting behaves as described. A new product with no reviews should have an honest empty state, not borrowed ratings presented as its own.

Explain any purchase-verification label according to the checks actually performed. Do not assume every platform's “verified” label means the same thing. Review your moderation description, reporting route, and treatment of criticism, keeping legitimate moderation separate from removing genuine feedback simply because it is negative.

Pass condition: Your collection practices, labels, displayed counts, and moderation claims are supportable, with a working way to report suspicious submissions.

6. Test checkout usability and payment security separately

A checkout can look reassuring and still fail a payment test. It can also complete purchases while needing specialist security work. Give usability and payment security separate owners and separate checks.

Walk through the purchase flow

Test the guest path where offered, returning-customer sign-in, address entry, autofill, cart editing, and each displayed payment method. On phones, check that keyboards match the field and do not hide important controls. Baymard's checkout guidance specifically recommends making guest checkout prominent and warns that mobile keyboards can obscure a poorly positioned option.

Using processor-approved test methods, try a declined payment, a retry, an invalid coupon, and an interrupted journey. Error messages should explain what to fix, preserve appropriate information, and let shoppers recover without guessing whether an order succeeded. Check that retries do not create unintended duplicate orders or charges.

Confirm payment-page responsibilities

HTTPS encrypts the connection, but it does not prove that the merchant is legitimate. Similarly, a working payment button is not evidence that every applicable security responsibility has been addressed.

Ask your processor, acquirer, or qualified adviser to confirm your applicable Payment Card Industry Data Security Standard (PCI DSS) responsibilities. The PCI Security Standards Council's payment-page guidance addresses script authorization, integrity checks, and monitoring for unauthorized changes. Responsibilities depend on the integration, so do not assume outsourced payments remove every merchant obligation.

Pass condition: Supported purchase paths complete correctly, errors are recoverable, and the responsible specialist has checked applicable payment-security requirements.

7. Make your business identity and support easy to verify

Check that your business name, contact information, and relevant operator details are consistent across the website, payment experience, and confirmation messages. If a payment descriptor uses a different name, give customers a clear explanation so they can recognize the charge.

Publish the support channels you can actually staff, along with holiday hours, time zone, and realistic response expectations. An automated acknowledgment should not be presented as a human response, and an offline chat should not imply someone is available immediately.

Send a test email or form submission and check chat both during and outside staffed hours. Confirm that someone receives the message and knows where to escalate it. Give support a current reference for discounts, delivery, returns, and payment failures rather than asking staff to infer the rules from promotional copy.

Pass condition: Advertised contact channels work, and support promises match staffing. These are practical recommendations, not a claim that every store must offer the same channels or hours.

8. Check mobile performance on the pages that sell

Test campaign landing pages, collection pages, promoted product pages, the cart, and accessible checkout steps, not just the homepage. Use real phones to select variants, open images, dismiss popups, contact support, and complete the available purchase steps. Watch for moving layouts, unresponsive controls, and chat bubbles covering the buy button.

Ask your developer to interpret Google's Core Web Vitals, which measure three aspects of the real-user experience:

• Largest Contentful Paint (LCP): Loading performance, with a good-experience target of 2.5 seconds or less.

• Interaction to Next Paint (INP): Responsiveness to interactions, with a target of 200 milliseconds or less.

• Cumulative Layout Shift (CLS): Visual stability, with a target of 0.1 or less.

Google assesses those targets at the 75th percentile, separately for mobile and desktop. In practical terms, the assessment looks beyond an average or a single fast visit to evaluate the experience of most users.

PageSpeed Insights distinguishes real-user field data from Lighthouse lab tests, which simulate a page load. Missing field data does not establish a pass or fail. Run Lighthouse several times under comparable conditions before judging a change, because scores vary between runs.

Pass condition: Critical shopping interactions work on tested devices, serious performance problems have owners, and measurements are interpreted in context rather than reduced to one score.

9. Make policies accessible and consistent with the store

Open shipping, returns, refunds, terms, and privacy links from the storefront and checkout. Look for broken links, unreadable formatting, incorrect business details, and leftover template language.

Then compare material promises across advertisements, product pages, cart, checkout, help pages, and emails. Focus on contradictions rather than rewriting every policy: a banner promising free shipping should not conflict with the cart, and a support article should not describe an expired return window.

Have the appropriate specialist check that explanations of data collection and consent choices reflect the tools actually used. If you sell subscriptions or recurring products, review renewal prices, billing frequency, and cancellation disclosures as part of this pass.

Pass condition: Shoppers can access relevant rules before paying, and material promises do not contradict one another. Applicable laws vary by selling location and customer market, so this checklist is not a complete legal compliance review.

10. Test what customers hear after they order

Use an authorized, controlled test order to check confirmation timing, purchased items and variants, discounts, totals, delivery expectations, and support links. Read the message on a phone without relying on promotional images to explain essential information.

Check that shipment messages and tracking links reflect actual fulfillment events. A message triggered by label creation should not claim delivery has occurred. Where relevant, test communications for split shipments, backorders, cancellations, returns, and refunds.

For shipping delays, verify that the notice explains the revised expectation and provides the appropriate consent, cancellation, and refund path. Customers should have a working next step, not simply an apology directing them back to an unchanged order page.

Pass condition: Transactional messages accurately describe the order's status and remain understandable without promotional content.

Where Welo Badge certification fits into your trust checklist

Once your store's promises and purchase paths are in order, business certification can give shoppers additional evidence to inspect. Welo Badge is a business verification and trust certification organization that reviews businesses against the Welo Trust Standard.

The review considers business identity and model, the website, payments, policies, support, security-related evidence, and requested documents relevant to the business. Certification is earned through review, and not every applicant is approved.

For customers, the practical value is an inspectable public record: a clickable badge opens a Welo Page showing approved public certification and check information. Only approved public information and material explicitly made public appear there, while private application evidence and documents stay private. If you already display a badge, check that it opens the correct public certification page.

Certification does not guarantee delivery, product quality, security, or an issue-free transaction, and it does not replace payment protections or consumer rights. It supports your operational work rather than replacing it. Businesses interested in review can apply for Welo Badge, without assuming approval or completion before Black Friday.

Run a final pre-sale test and record the results

Keep one shared test record so website, payments, fulfillment, and support teams can work from the same facts. Copy the structure below and create a separate row for each scenario you need to test. The entries describe suggested tests, not completed results.

Expand this record across mobile and desktop, guest and returning-customer paths where offered, relevant variants, supported destinations, and carts below, at, and above shipping thresholds. Use approved test environments or authorized controlled transactions as appropriate. Keep evidence access restricted, and do not retain payment details or unnecessary customer data.

Assign and fix issues

Start with launch blockers, then address missing information and high-impact usability problems. Name contacts for payment, fulfillment, support, and website incidents, including who can pause an affected promotion or purchase path.

Retest after final promotional changes

Repeat the critical journeys after changing prices, banners, discount settings, shipping thresholds, or delivery promises. Recheck performance under comparable conditions rather than treating one improved Lighthouse run as conclusive.

Monitor during the sale

Watch for payment errors, unexpected totals, fulfillment delays, and repeated support questions. When a promise can no longer be supported, correct the customer-facing information and coordinate the response across teams.

Your operational sign-off should be simple: no unresolved launch blockers, accurate customer promises, and a responsible person for remaining work.

FAQ

Launch with promises your store can keep

A useful Black Friday trust check connects what customers see with what your business can actually do. Before signing off, make sure the offer is accurate, the purchase path works, and support and fulfillment teams can carry out the stated policies. Keep the test record active during the sale so new issues reach someone who can fix them.