Shopify Dev Stores: The 'Coming Soon' Page Dilemma for Agencies & Pre-Launch Marketing

Hey everyone, your friendly Shopify expert here, diving into a really important discussion that recently caught fire in the Shopify Community. It's about a specific bottleneck that many agencies and developers face when building stores for clients, especially around that crucial pre-launch 'Coming Soon' phase. If you've ever built a store for a client on a development store and tried to get a custom landing page up before transfer, you're going to want to read this.

The conversation was kicked off by Marcel (Omineus), a fellow Shopify Partner, who hit a structural limitation that's causing a real headache. He called it 'expected platform behavior,' but it's definitely not ideal for anyone in the trenches building stores.

The Frustrating 'Coming Soon' Page Problem

Here’s the core of the issue, as Marcel laid it out: when you're building a client transfer store, you often want a custom 'Coming Soon' page. This isn't just a placeholder; it's a vital marketing tool with custom typography, announcement text, and often a newsletter signup form to start capturing leads before the big launch. Marcel's team, using the modern Horizon theme (an Online Store 2.0 theme), designed a fantastic custom 'Coming Soon' section in their templates/password.json file.

Everything looked great in the Theme Editor and via preview links. The custom page rendered perfectly, just as intended. But here's where the frustration kicks in: when external visitors or prospective buyers went to the store's actual URL (say, in an incognito window), they didn't see that beautiful custom page. Instead, they were greeted by the generic, default Shopify password page.

After a detailed support session, it was confirmed: Shopify, at a platform level, forces this generic password page for all public visitors as long as the store remains under a Partner organization. That custom 'Coming Soon' content? It only becomes publicly visible after ownership is officially transferred to the client. Talk about a buzzkill for pre-launch excitement!

Why This Creates a Major Bottleneck for Agencies & Store Owners

This isn't just a minor inconvenience; it's a significant workflow blocker with real financial and marketing implications. Marcel highlighted three key reasons why this 'expected behavior' is a problem:

1. Financial Risk & Payment Security

Think about it: as an agency, you can't transfer store ownership until your client has paid the final invoice in full. It’s standard practice, protecting your work and ensuring you get compensated. But if you have to transfer ownership prematurely just to make the custom 'Coming Soon' page live, you effectively strip yourself of leverage and project control. That's a huge financial risk no agency should have to take.

2. Missed Pre-Launch Marketing Opportunities

Clients are eager to hit the ground running. They want a branded 'Coming Soon' page that reflects their identity, builds anticipation, and allows them to start collecting email addresses from interested customers. Forcing a generic Shopify page means they miss out on crucial early lead generation and brand building. It's a lost opportunity for those critical first impressions.

3. The Partner Catch-22

This limitation puts Partners in an impossible situation. They're forced to choose between two unacceptable options:

• Transfer an unpaid store to the client, risking payment security, just so the custom 'Coming Soon' page is visible.
• Keep the store under the Partner organization, ensuring payment security, but forcing visitors to see an unbranded, generic Shopify password page.

Neither option is good, and it clearly demonstrates a gap in the platform's support for agency workflows.

The Added Frustration: Incorrect Guidance from AI Support

As if the core issue wasn't enough, Marcel also pointed out another frustrating experience: getting incorrect guidance from Shopify's own support tools. While troubleshooting this very issue, both Sidekick (Shopify AI) and even tier-1 support advisors were advising edits to old code files like password.liquid or main-password.liquid.

For those of us building with Online Store 2.0 themes like Horizon, we know that sections are managed via JSON templates (password.json). These old .liquid file instructions are simply invalid in this context. What's worse, Sidekick and AI support tools currently lack the context to understand a store's Partner / Client Transfer status. This leads to hours of wasted troubleshooting time, sending developers down rabbit holes that can't possibly lead to a solution.

What We Need: Solutions for a Smoother Workflow

Marcel didn't just highlight the problem; he also put forward some excellent, actionable feature requests that would resolve this bottleneck:

1. Allow Custom Password Sections on Client Transfer Stores: Shopify should enable Partners to publicly display their configured password.json template while the store is still under the Partner organization. This seems like the most straightforward fix.
2. Separate 'Coming Soon' Visibility from 'Store Transfer': Maintain development store password protection without forcing a generic layout override. Essentially, decouple the visual customization from the ownership transfer.
3. Update Sidekick / AI Context Awareness: It's crucial that Sidekick and other AI tools recognize a store’s Partner / Client Transfer status. This way, they won't recommend invalid code edits for platform-level constraints, saving countless hours for developers.

This discussion really underscores the need for Shopify to evolve its platform to better support the agency and developer ecosystem. It's a powerful platform for entrepreneurs looking to start their own online store, but these workflow snags can make the journey unnecessarily difficult for those building them. If you're a Partner or a store owner who's faced this, or similar issues, jump into the community and share your feedback. The more voices, the better chance we have of seeing these crucial updates implemented by the Shopify Product Team. Let's keep the conversation going and push for improvements that make building and launching on Shopify an even smoother experience for everyone involved.