▎ “All apps in the Shopify App Store must have a user interface that merchants can interact with. Operational errors within an app’s functionality are acceptable, but web errors (404s, 500s, 300s) are not.”
I watched the review video — the reviewer loaded the app, saw the home page, clicked the only link (a support email), and that was it. No errors occurred.
My app is a B2B integration tool — partners install it to authorize access to their product catalog and inventory. The actual work (product syncing, order routing) happens via API in the background. The embedded UI currently
shows a Polaris-based informational page explaining how the integration works, what permissions are granted, and a support contact.
My question: what constitutes a sufficient UI for an app whose core functionality is API-driven? The rejection feedback mentions web errors but the reviewer didn’t encounter any. Is the issue that the page is purely
informational with no interactive elements? Would adding a status dashboard showing connection status, sync activity, and product counts be enough?
Has anyone else dealt with this rejection reason for a backend/API-focused app? Any guidance on the minimum bar here would be really helpful.
This is an extremely painful rejection as Its now been over 60 days since my initial submission. This is completely blocking my shopify business from launching.
We were just rejected for the same reason. Would appreciate clarification as well as to what passes as a “user interface that merchants can interact with”. It would also be helpful that if in the dashboard there was a more detailed explanation. That way it will save us the hassle of having to post here.
We have a very similar use case. Our app is still pending review, so unfortunately, I can’t speak to the requirements of the UI, but I have wondered the same. Please do post here if you’re able to satisfy the requirement.
My app was just rejected for the same reason. Sounds like the same scenario, as my app is also B2B api integration, yet there IS a user interface, however minimal, if the user clicks on the app name in the admin panel. It simply shows the integration status. This is causing headaches for our team and business.
Hey @Randal_B, if it helps, merchants typically expect to be able to install an app and start using its features. Public app distribution isn’t intended solely for gaining API access. There should be meaningfull functionality behind it.
I think my solution is going to involve using a custom app rather than a store app. This seems to fit the B2B model / api integration Im using better, where the given store needs to be pre-provisioned in my backend ahead of time, and no app review is needed.
Granted, I will have to setup individual custom apps per partner store, each with their own client id / app secret, but that should be acceptable given that there wouldn’t be more than a dozen or so, at least for now.