App review feedback moves from email to Partner Dashboard. Each requirement gets a status, and with AI self-review and automated pre-submission checks, the workflow shifts to fixing issues before they're sent back. The goal is to speed up review and publishing.
Review feedback came via email. You had to track on your own what was unresolved and which requirement was holding things up.
Manage each requirement's status, comments, and questions in one place under App > Distribution. The design has you resolve everything before resubmitting.
Review feedback is now consolidated in App > Distribution . Each requirement gets its own status, reviewer comments, and a path to ask questions, so you can see at a glance what's still unresolved.
A separate status tracker for each requirement that needs attention.what failed, along with the reviewer feedback tied to it, is shown.
Work through requirements one by one,mark each as "resolved,"then resubmit.
Until all the identifiedissues are resolved, you can't resubmit. The system prevents resubmission while things are only half-fixed.
Before you submit, AI checks your app against the App Store requirements.In about 2 minutes, it catches the "obvious problems" up front that would otherwise cause weeks of rejection later.
This feature is provided within Shopify AI toolkit . You can build it in as a self-check step before you enter the submission flow.
Expands the automated pre-submission checks. Before a reviewer picks up your app,it instantly flags what needs fixing. The post explicitly names two areas covered by this expansion:
Added requirements for theme app extensions to the automated checks.
Added requirements for App Store listing information to the automated checks.
| Current status | What happens | Required action |
|---|---|---|
| Reviewed (unresolved issues) |
As before, the existing email-based processcontinues to handle the review. The new dashboard flowdoes not apply to this submission. | As before, keep handling it over email |
| Submitted (awaiting review) |
When the reviewer evaluates it, the feedback isshown in the new dashboard experience. | None Nothing to do |
Review communications are consolidated in App > Distribution . Teams that shared status by forwarding emails can switch to checking the dashboard.
Each requirement has its own status and a resolved marker.Resolve them one at a time — breaking tasks down on that assumption pairs well with progress tracking.
If even one issue remains unresolved, you can't resubmit.Fixing some and waiting to seeis not a viable strategy. You need a plan to clear every item before submitting.
the AI self-review (about 2 minutes) + the automated pre-submission checka mandatory pre-submission gate, you can clear out obvious rejection triggers in advance.
Reviewed (has unresolved issues) stays on email Submitted (awaiting review) uses the new dashboard. If you have multiple apps in review in parallel across your team, checking which flow each case is on keeps things from getting confusing. The only automated checks explicitly named so far cover two requirements—Theme app extensions and App Store Listing—and no other coverage is documented.