Skip to content
Developer platform · Versions & review

Every version is reviewed before merchants get it

Fill in the listing, configuration and the data you need, pass the pre submission checks, and Submit for review. Nothing reaches merchants until a reviewer approves it.

In short

Apps ship as versions: a developer completes the Listing, Configuration, Data and Pre-submission checks steps and presses Submit for review. A reviewer approves, rejects or requests changes, and only an approved version reaches merchants.

The problem it solves

An update pushed straight to every store can break checkout on a Friday evening. Merchants need to know a person looked at what changed.

How it works

4 steps, start to finish

  1. 1

    Prepare the version

    Fill in the Listing, Configuration and Data tabs.

  2. 2

    Ask for the least

    The scopes you list are exactly what merchants see on the consent screen.

  3. 3

    Submit for review

    Pass the pre submission checks and submit.

  4. 4

    Get a decision

    The version goes Live, or comes back as Changes required.

In detail

What versions & review does for you

Common queries

Questions people ask

  • No. Nothing reaches merchants until a reviewer approves the version.
  • Approve, Reject or Request changes. Requested changes show on your app as Changes required.
  • A version replaced by a newer one is marked Superseded.

Versions & review · Free to start

Try versions & review on your own business

Set up in a couple of minutes. Your catalogue, orders and books stay yours to export.

  • Live in 2 minutes
  • Free to start
  • No credit card
The dashboard open on a laptop, a tablet and a phone