--- id: "offerings/product-editor-configure" title: "Configure products with Product Editor" description: "This article shows you how to create and update App Store and Play Store products in bulk with Product Editor. By the end, you will have reviewed a plan and committed it to the store." permalink: "/docs/offerings/product-editor-configure" slug: "product-editor-configure" version: "current" original_source: "docs/offerings/product-editor-configure.mdx" --- > **AI agents:** This is the Markdown version of a RevenueCat documentation page. For the complete documentation index, see [llms.txt](https://www.revenuecat.com/docs/llms.txt). This article shows you how to create and update App Store and Play Store products in bulk with [Product Editor](https://www.revenuecat.com/docs/offerings/product-editor). By the end, you will have reviewed a plan and committed it to the store. ## Prerequisites - [App Store Connect API key](https://www.revenuecat.com/docs/service-credentials/itunesconnect-app-specific-shared-secret/app-store-connect-api-key-configuration) or [Google Play service credentials](https://www.revenuecat.com/docs/service-credentials/creating-play-service-credentials) connected for the app you will edit. Play Console also needs **Manage store presence** on the service account. - An [Administrator, Growth, or Developer](https://www.revenuecat.com/docs/projects/collaborators) role (or project owner). View Only and Support cannot upload or commit. - App Store or Play Store products :::warning Each file is **one app and one store**. You cannot mix App Store and Play Store products in the same upload. A file can include at most **50 products**. Play Store exports include subscriptions only. ::: ## Step 0: Open Product Editor 1. In your project, go to **Product catalog → Products**. 2. Click **Product editor**. ![Product editor button on the Products page](https://www.revenuecat.com/docs_images/products/product-editor/products-page-button.png) The editor is a three-step flow: **Update product file**, **Review changes**, and **Commit to store**. ![Product Editor sidebar with steps and beta badge](https://www.revenuecat.com/docs_images/products/product-editor/sidebar.png) ## Step 1: Download a product file 1. Choose **App Store** or **Play Store**, then the app. 2. Select the products to include (up to 50). 3. Click **Generate export**. 4. When the file is ready, click **Download file**. ![Download product file card](https://www.revenuecat.com/docs_images/products/product-editor/download-card.png) Generating the file can take a few minutes for large catalogs. You can wait for it to finish, or click **Notify me by email** to receive a download link when it is ready. ![Notify me by email while generating an export](https://www.revenuecat.com/docs_images/products/product-editor/notify-by-email.png) If you already have a file in the Product Editor format, click **Skip, I have my own file**. Still select the correct app first so the upload is associated with that store. The **Files** tab lists previous exports. Do not reuse an old file if you changed products directly in the store afterward. That data can be stale. ## Step 2: Edit the CSV Open the downloaded file in Excel, Google Sheets, or any spreadsheet tool. :::tip Always start from an export of **your** products instead of building a spreadsheet from scratch. Headers differ by store (App Store files omit Play Store columns, and the reverse). Use the [sample App Store](https://www.revenuecat.com/docs_files/products/product-editor/app-store-sample.csv) and [sample Play Store](https://www.revenuecat.com/docs_files/products/product-editor/play-store-sample.csv) files only to inspect the layout. Do not upload them to a live project. ::: A typical price change: 1. Find the `price` row for the product and territory (country name, for example `United States`). 2. Update `amount` (the customer-facing price, such as `9.99`, not micros). 3. Leave unrelated cells blank or unchanged. Blank or unchanged cells mean “keep the current value.” See [Product Editor CSV format](https://www.revenuecat.com/docs/offerings/product-editor-csv) for every column and row type. :::warning\[Excel and dates] `start_date` values are exported with a leading apostrophe (for example `'2026-09-01`) so Excel does not rewrite them. Keep dates as `YYYY-MM-DD`. If Excel converts a date to another format, the upload can fail. ::: ### Example: change one price | `row_type` | `store` | `store_identifier` | `territory` | `amount` | `currency` | `available` | | ---------- | ----------- | ------------------ | ------------- | -------- | ---------- | ----------- | | `product` | `app_store` | `rc_pro_monthly` | | | | | | `price` | `app_store` | `rc_pro_monthly` | United States | `12.99` | `USD` | `true` | That updates the US price for `rc_pro_monthly` to `$12.99`. Other territories stay as they are if you leave those rows unchanged. To **create** a product, add a `product` row with a new `store_identifier` and the required fields (type, duration, prices). RevenueCat can create the matching catalog product when you commit. You cannot delete a product from the store with this flow. To stop selling it, set `available` to `false` for the relevant territories. ## Step 3: Upload the file 1. Drop the `.csv` on **Upload product file**, or click to select it. 2. Wait until the plan is ready. You can get email when planning finishes. 3. Click **Review changes**. ![Upload product file card](https://www.revenuecat.com/docs_images/products/product-editor/upload-card.png) Nothing is sent to Apple or Google at this step. ## Step 4: Review changes The review screen lists each product as **CREATE**, **UPDATE**, or **NO CHANGES**, with grouped diffs such as price increases, new prices, localizations, and offer changes. ![Review changes with product diffs](https://www.revenuecat.com/docs_images/products/product-editor/review-changes.png) Fix **red blocker** warnings before you can commit. **Yellow** warnings do not block you. If the plan has no changes, upload a different file. **Reupload** starts a fresh plan instead of resuming the previous one. ## Step 5: Commit to store Click **Commit to store** to apply the plan to App Store Connect or Google Play. ![Commit to store button on Review changes](https://www.revenuecat.com/docs_images/products/product-editor/commit-button.png) ![Commit to store](https://www.revenuecat.com/docs_images/products/product-editor/commit-to-store.png) Applying changes can take several minutes and continues in the background if you leave the page. You can optionally click **Notify me by email** to get a notification when it is complete. When it succeeds, the products are updated in the store. If one product fails, the products that already applied stay applied. The plan shows an error, and failed products keep their error on the card. Click **Try again** to retry the failed items. You still need to complete any store-side review Apple requires (for example submitting in-app purchases with an app version). See [iOS Product Setup](https://www.revenuecat.com/docs/getting-started/entitlements/ios-products) and [Google Play Product Setup](https://www.revenuecat.com/docs/getting-started/entitlements/android-products). For how customers experience a price change after it is live, see [Changing Prices](https://www.revenuecat.com/docs/subscription-guidance/price-changes). ## Next steps - [Learn how Product Editor works](https://www.revenuecat.com/docs/offerings/product-editor) - [Product Editor CSV format](https://www.revenuecat.com/docs/offerings/product-editor-csv) - [Troubleshooting Product Editor](https://www.revenuecat.com/docs/offerings/product-editor-troubleshooting)