Hi everyone,
We’re building a standalone SaaS product that exists independently of Shopify. Merchants can use our product without ever connecting a Shopify store, and Shopify is just one acquisition/integration channel for us.
We’re planning a Public Shopify app with “Limited Visibility”. The app inside Shopify Admin would be very minimal: it would handle authentication/onboarding, and billing for Shopify merchants would go through Shopify Billing API / Managed Pricing.
After that, the actual product experience would happen in our external SaaS dashboard. We are not planning to provide core workflows, reports, or day-to-day functionality inside the Shopify app itself.
Our question is whether this setup is acceptable under the current App Store requirement around providing a consistent embedded experience.
Specifically:
- If we use Shopify billing correctly and provide a minimal embedded onboarding flow, is that enough?
Since connecting Shopify is optional to our overall product, we’re trying to understand whether a minimal embedded app is acceptable for review.
Any guidance would be appreciated.
Thanks,
1 Like
Short answer: No, this setup will almost certainly be rejected by the app review team.
Shopify actively rejects “thin shell” apps that only handle OAuth and billing. Under current App Store requirements, you cannot use the Shopify Admin simply as a billing gateway or a redirect pipe to an external product. If your embedded app is just an install screen, a pricing plan, and a button pointing to your external dashboard, it violates the embedded UX guidelines.
To pass review, you must provide a functional embedded experience. This doesn’t mean you have to rebuild your entire SaaS inside Shopify, but the merchant must be able to monitor and execute the “Shopify-specific core” of your product without leaving the admin interface.
This is the accepted architectural pattern for a standalone SaaS integrating with Shopify:
1. The Embedded App (Shopify Admin)
-
Must display a real-time summary of how your SaaS is interacting with their specific store (e.g., sync status, key Shopify-related metrics, recent API errors).
-
Must include core controls that affect Shopify data (e.g., enable/disable the integration, trigger manual syncs, adjust basic rules).
2. The External Dashboard (Your SaaS)
-
Reserved for deep configuration, multi-channel analytics, and advanced non-Shopify workflows.
-
You can provide context-aware links inside the embedded app that point merchants here for heavy, complex tasks.
When you submit for review, be explicit in your submission notes. State clearly that the product is a cross-platform SaaS, but emphasize exactly what the merchant can monitor and control directly inside the embedded UI. If you provide genuine utility inside the Shopify Admin, you will probably pass. A blank redirect shell will probably fail.
1 Like
Hi @admin_admin1,
The reply above from @storelift covers the key points well. I want to add some specific doc references so you know exactly what the review team looks for.
The main requirement is 2.2.2 from the App Store requirements:
“Your app must provide a consistent embedded experience by ensuring that any off-platform features are integrated directly within the Shopify Admin.”
That said, the docs do account for your exact situation - a cross-platform SaaS where Shopify is one integration channel. From the Integrating with the Shopify admin guide:
Apps that contain more functionality than can be reasonably integrated into the Shopify admin do not have to integrate all of their primary workflows into the Shopify admin. For example, apps that handle ad buying or enterprise resource planning (ERP) require a standalone site to enable access to their functionality in a user-friendly manner.
However, some workflows must always be present in the Shopify admin. These workflows include setup, configuration, status, dashboards, and other features that help a merchant use the app on a day-to-day basis.
So the short version: you don’t need to rebuild your whole product inside Shopify, but a shell that only handles OAuth and billing won’t pass. You’ll need to give merchants real utility in the embedded app. At minimum, that means:
- Setup and configuration for the integration
- A status dashboard showing how the connection to their store is performing (sync health, key metrics, errors)
- Controls for anything that directly touches their Shopify data
Your deeper workflows, cross-platform analytics, and advanced features can stay in your external dashboard. The docs specifically call out ERP and ad-buying apps as examples where that’s fine.
One more thing worth reading — the Built for Shopify requirements go into more detail on what “simplified monitoring or reporting” looks like inside the admin:
Hope that helps point you in the right direction and let me know if you have any other questions.
1 Like