Dark-Pattern Reviews Should Include Screenshots From the Customer Journey

Screens beat policy text

A business may have fair terms and still create a confusing customer journey. The risk sits in button labels, default choices, hidden fees, countdowns, cancellation steps and support messages. A policy review alone will miss that evidence.

The practical review should collect screenshots from the live flow. A reviewer should act like a customer: enter checkout, accept or reject offers, cancel, refund and contact support. The evidence is the path, not the intent.

Case pattern: cancellation that works on paper

A seller says customers can cancel at any time. In the live flow, customers must pass through several retention screens, wait for an email link and then contact support if the account was created through a promotion. The policy is simple; the experience is not.

A screenshot file would show the gap. The company could then decide which steps serve a real account-security purpose and which steps only add friction. That distinction matters when customers, platforms or regulators question the flow.

Create a journey evidence file

The review should happen after major pricing, subscription or checkout changes. Store screenshots with date, device type and market. Keep the old version when the flow changes so the team can explain what was corrected.

Support data should be part of the file. If many customers ask how to cancel or complain about fees, the journey review should reopen even if the policy text has not changed.

• Capture desktop and mobile checkout screens.
• Record default choices and price changes.
• Count cancellation steps and waiting periods.
• Compare support complaints with journey evidence.
• Keep a change log after flow edits.

Field review

A practical review starts with one live product, one active order and one current customer-facing page. Put those records beside the article topic and ask whether they still describe the same business reality. If the public page, the supplier file and the internal decision record point to different answers, the team has found the gap that will matter during a platform review, customs question or customer dispute.

The review should produce a small decision note. It should name the file owner, the missing evidence, the business action and the date for the next check. That note matters because cross-border teams change quickly. A future reviewer should be able to see why the business accepted, corrected, paused or escalated the issue without searching private messages.

Use the same test after the next supplier change, route change, campaign launch, listing edit or complaint pattern. The point is not to create a larger archive. The point is to keep the commercial record current while the business keeps moving. A file that was true last quarter can become misleading after one product edit or fulfilment change.

A good checkpoint is whether a new employee could open the folder and answer the main question in ten minutes. If the answer depends on one veteran employee, a chat thread or a supplier promise that nobody saved, the record is too fragile for a fast-moving marketplace or border process.

That simple test keeps the article grounded in operations, not theory.

The handoff should also say what the team will not claim until evidence improves. Clear limits protect the business as much as strong proof does. When a record is partial, say which market, product version, route or customer promise it can support, and which one it cannot support yet.

That boundary should be visible to sales, support and finance.

If those teams cannot see the boundary, the next public promise will drift again.

For recurring risks, sample one file each month and record whether the boundary still holds. A small monthly sample often catches drift faster than a large annual review because it follows the way sellers actually change products, routes and campaigns.

Keep that sample note with the live file.

Closing note

Dark-pattern review is practical work. It asks what the customer saw, clicked and understood.

A screenshot-based file gives teams a concrete way to fix friction before it becomes a reputation or enforcement problem.

Reference links

• FTC Review and Advertising Guidance