I am building an app that handles fulfillment orders. The app sets up integration with my backend system, so that when a fulfillment order is created, it’s sent to my system for fulfillment (shipping). The constraint here is that the store name must be setup & configured for a given customer and their store ahead of time on my backend.
In the app submission form, there are sections for a screencast and testing instructions.
The screencast and testing instructions are for the app review team and NOT for the merchant.
A chat support rep mentioned that it would be best to re-do the app review questions & screencast with this in mind.
To accommodate this:
I created a new staff/admin account in one of my Development stores, for the testers to login with. T
This development store already has the app installed, and the store has been pre-provisioned on my backend.
The new testing instructions, will simply step the user (reviewer) through clicking on the app name from within the store to show a basic ui, placing an order, and sending the fulfillment request.
Will the above meet the review process needs?
For now, my app is in “shopify jail”, due to either myself not understanding the directions enough, or ?
Just confirming one important piece here: for App Review, I’d avoid relying only on a pre-installed app in a pre-provisioned development store. Reviewers may test by installing the app on their own review/test store, so the safest path is for the app to work from a fresh install as much as possible.
If your backend needs to know about the store before fulfillment testing can work, I’d recommend one of these review-safe options:
Auto-provision on your app’s side during install or onboarding on the shop
Add a review/test/sandbox flow that provisions the reviewer’s shop without manual work on your side
Provide very clear instructions for a pre-provisioned test store as a fallback, while still explaining how a normal merchant store gets provisioned
In the screencast and testing instructions, I’d show the full expected flow: install/open the app, complete any provisioning/onboarding step, place an order, request fulfillment, and confirm the request reaches your backend.
The main thing is that the reviewer shouldn’t be blocked if they install the app on a fresh test store that your backend has never seen before. A pre-provisioned dev store can help demonstrate the best path, but I wouldn’t make that the only way the app can be reviewed. Sometimes, though, the reviewer can request to become a collaborator on your dev store if it is absolutely required to test the app, so I’d just make sure to mention that if it is definitely required in your app submission.