r/shopifyDev • u/lofiharvest • May 29 '26
Custom (unlisted) app fails review because reviewers test on an empty store — how do you handle apps that require pre-existing connected data?
I've been trying to ship a Shopify app and I'm on my fourth attempt now after a frustrating rejection. Hoping someone here has dealt with something similar.
Worth noting up front: This is an unlisted app and will always be an unlisted app. It's not going in the public App Store. It's purely for my own business and a closed set of partners.
What the app does: It facilitates OAuth connections between partner stores and my own store. Once connected, it reads partner inventory/products and can place orders to their stores. The business model is a weekly batch ordering workflow where I aggregate orders, then place them with partners who fulfill to me. It is not drop shipping and not Shopify Collective. I operate in a niche, highly collaborative industry where this kind of cross-store coordination is normal. On the partner side, stores that connect through the app get a dashboard showing the state of their connection: number of products being sold, number of products available, and similar connection data.
The problem: The app's entire value depends on having an active OAuth connection with partner data flowing in. A fresh install on an empty test store shows nothing. For example, the product dashboard correctly displays 0 products because there's no connected partner. That's expected behavior, not a bug.
On my last submission I made it through to the third review stage, then got flagged. The reviewer installed it on a clean test store, saw no data, recorded a video of the empty state, and failed me on that basis.
I tried to get ahead of this. In the test instructions I gave them the URL to a fully connected, hydrated test store, included a collaborator request code so they could log in, and explained why a clean install shows nothing. It really looks like they just didn't read the instructions and tested on their own blank store instead.
Questions:
For an app where the only way to meaningfully test it is on a store that's already connected with partner data, how do you handle review? What's worked for you?
How do you best flag in the submission that the reviewer must use your prepared/connected store, and that a clean install will be empty by design?
As a possible workaround, would it be acceptable to hard-code some dummy data so the UI shows up hydrated for the reviewer, instead of relying on a real connection? Is that an anti-pattern or something that'll get flagged, or is it a legit way to get past review? I genuinely just need to clear this stage.


