Shopify or the registrar? Route the notice before you write it

A lookalike shop has at least two layers. The domain is registered somewhere. The storefront is hosted or operated somewhere. Those layers may offer different complaint paths, ask for different facts, and control different parts of the problem. Sending the same generic paragraph to both is not routing; it is hoping.

Shopify currently publishes a dedicated copyright infringement notice and a separate trademark or trade dress infringement notice. Both Shopify pages were checked on August 6, 2026. That makes a Shopify reporting path relevant when the complaint concerns content or marks on a Shopify storefront. A registrar abuse desk remains a different destination for a complaint about the domain and the abuse associated with it.

Hosting is an assessment, not a guess

Brand Protector evaluates domain evidence for signs that the site is Shopify-hosted. The assessment records both a reason and a strength, using DNS and page signals rather than presenting every clue as equally conclusive. When that assessment supports Shopify, the draft recommends Shopify’s intellectual-property path. The reviewer can still choose the registrar route.

That override matters because infrastructure evidence does not decide the legal basis of a notice. A site can use Shopify while the actionable fact in front of you concerns the domain itself. Conversely, a registrar may have supplied the name while Shopify controls the storefront content named in your complaint. The system can recommend a destination; the reviewer must connect the chosen destination to the evidence.

The claim type changes the Shopify path

“Shopify form” is still too vague. Brand Protector builds a claim-specific destination: copyright complaints route to the copyright notice, while trademark complaints route to the trademark notice. The prepared package includes a field guide for the selected form rather than pretending that one complaint body fits every intake.

Because those forms are browser-mediated, the resulting package is marked ready to file, not submitted. Review and authorization happen in Brand Protector; the platform’s declaration and final submission happen on the platform. The case advances only when an operator records the external filing.

The registrar route needs its own evidence chain

On the registrar path, Brand Protector first uses registrar evidence already attached to the detection and can resolve missing registrar details through RDAP. A known abuse destination may support a system email. A form-only destination produces a form-paste package instead. If the registrar cannot be resolved, the record keeps that uncertainty visible rather than manufacturing a mailbox.

The delivery method then controls the lifecycle label. A system email is marked submitted only after the send path completes. A registrar web form remains prepared until somebody files it. The recipient and status are separate pieces of truth: resolving a destination does not prove delivery to it.

Changing the route must change the package

A destination toggle that changes only the label is unsafe. Brand Protector permits a Shopify-versus-registrar change only while the takedown is still a draft. It then regenerates the platform, delivery method, body, form fields, and destination record together, and writes a destination-change audit event. Once the notice has moved beyond the draft state, that switch is refused.

The product also rechecks the hosting assessment before accepting a Shopify choice. A stale interface cannot force the old recommendation onto a domain whose current draft no longer supports it. That is a small implementation detail with a large operational consequence: the package you review is the package for the destination now selected.

A routing review should be short and explicit

Before authorizing the notice, the reviewer should be able to answer four questions from the case itself:

• Which signal supports the hosting assessment, and how strong is it?
• Is the complaint about storefront content, a mark, or domain abuse?
• Which recipient can act on the specific URLs and facts supplied?
• Will this route transmit directly or leave an external filing step?

Good routing does not guarantee a faster decision by either recipient. It does something more basic and more defensible: it sends a claim-specific package to the party selected to receive it, then records only the delivery event that actually occurred.