> For the complete documentation index, see [llms.txt](https://sourcesheets.gitbook.io/sourcesheets-new-seller-blueprint/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sourcesheets.gitbook.io/sourcesheets-new-seller-blueprint/part-4-sourcing-and-buying-your-first-products/7.6.5-case-study-5-restricted-brand-with-a-clear-ungate-path.md).

# Case Study 5: Restricted Brand With a Clear Ungate Path

When analysing products, restrictions are often treated as an automatic rejection, and for good reason, many gated listings are difficult, inconsistent, or simply not worth the effort. But gating itself isn't the problem. Unplanned gating is. This case study shows the difference, and where the Gate 7 line actually sits.

## Why Gating Can Be a Problem

Gated products introduce friction. They delay selling, require additional documentation, and add uncertainty to timelines. In some cases, brands actively resist resellers, making approvals unreliable even with correct invoices. That pattern, not gating itself, is what Gate 7 treats as a hard stop (see 7.5.5): three or more rejected legitimate ungating attempts, sellers being removed after approval, or a blanket no-resale policy with no application route.

For new sellers, gating can become overwhelming, especially when it's discovered after inventory has been purchased. That's why we treat restrictions as a serious signal and route them through a dedicated decision point rather than ignoring them.

## What Makes This Restriction Different

In this example, the restriction is visible early and clearly defined. The brand asks for two supplier invoices covering the last 90 days, a standard, achievable requirement, and there's no record of this brand rejecting sellers who meet it. That falls well short of the Gate 7 hard-stop bar: no pattern of aggressive enforcement, no compliance or hazmat issues layered on top, and no sign that approvals are routinely denied. It's a procedural hurdle, not a hostile brand.

Outside of the restriction itself, the numbers hold up too: profit of £1.85 a unit at a 24% ROI, both clear of the Gate 1 and 2 floors, sales running at 65 units a month, past the Gate 3 floor, stable pricing well inside the Gate 4 band, and Amazon isn't active on the Buy Box.

> 📸 **Screenshot needed:** the restriction/gating flag, plus (if possible) the ungating requirements screen

## Using the Ungating Framework Properly

This is exactly the type of product to evaluate using the ungating section of the Blueprint (see 7.3), rather than treat emotionally or avoid by default. Ungating, when planned, is a strategic move: you understand the approval requirements before buying, accept that the first order is about access rather than profit, and unlock future products, not just a single ASIN. This turns gating from a surprise problem into a deliberate expansion step.

## Why This Product Can Move Forward

This product doesn't rely on wishful thinking. The restriction is known, the process is clear and well short of the Gate 7 hard-stop bar, and the rest of the listing is structurally sound. That makes it suitable for a Proceed Cautiously decision, provided ungating is treated as the primary objective of the purchase. This isn't an example of ignoring a gate. It's an example of applying Gate 7's actual criteria rather than rejecting on reflex.

## Core Lesson

Gating is a risk to understand, not a reflexive rejection. A gated product should never be bought accidentally. But when the ungating path is clear, achievable, and free of the enforcement pattern Gate 7 actually screens for, restrictions can represent controlled opportunity rather than unnecessary risk. If you're unsure, revisit 7.5.5 and the ungating section of this Blueprint before making any decision.