Summary: Step-by-step guide to create a new 7Mind app subscription SKU that the app can show on its paywall and sell: store products, Contentful role, product and package, the productsConfig.json allow-list, an optional Braze intro offer experiment, and how to verify each layer. The app needs no change.
Sources: app-subscription-products and its sources; Contentful space m5ivwq1dbwv8 (live entries multi.7mind.sub.ios.yearly, plus_buddyfit_android_202511_1m, the 7Mind tier cards); Gymondo-git/terraform-workspace-service-gateway product-change-v3; sevenmind/7mind-mobile-apps-monorepo lib/features/monetization/ and PR 1568 (MIND-846); Notion “How to create new products and all around it”; Slack fitness-checkout-helpdesk, fitness_ask-product; function-product-v1 status handling, read again on 2026-10-27; the app side re-read on 2026-11-09 from origin/main at 4.0.9 (api_monetization_repository.dart, in_app_purchase_product_service.dart, intro_offer_arm.dart, braze_configurations_provider.dart, PRs 1577, 1586, 1591)
Last updated: 2026-11-09
Read app-subscription-products first for how the pieces fit together. This page is the checklist. Steps 1 to 5 are needed for every SKU. Step 6 only applies to experiments. Step 7 verifies.
Who does what
| Part | Usually done by | Access needed |
|---|---|---|
| Store products | Whoever administers the 7Mind Play Console and App Store Connect accounts | Play Console and App Store Connect admin |
| Contentful role, product, package, tier card | Gymondo backend (Ale) or anyone with Contentful admin on the Gymondo space | Contentful space m5ivwq1dbwv8 |
productsConfig.json | Gymondo backend, as a PR to Gymondo-git/terraform-workspace-service-gateway | Gymondo-git write access and a deploy |
| Braze experiment (experiments only) | 7Mind product, with mobile | Braze, 7Mind workspace |
| App | Nothing for a regular SKU. A new experiment flag, another paywall card or a length other than 12 or 1 months needs a release by the 7Mind mobile team | 7mind-mobile-apps-monorepo |
Gymondo has a request process for new web products: the “Product Creation Template” sheet and a CH Jira ticket in fitness-checkout-helpdesk, built by Ahmed or Luke. The Notion page “How to create new products and all around it” has a video of the Contentful part. Neither covers store products end to end, which is why this page exists.
0. Decide the ids
- Pick the article number, which is the store product id.
- Follow the Gymondo scheme
[vendor]_[tier]_[platform]_[department]_[descriptor]_[country]_[YYYYMM]_[period], for examplesevenmind_plus_android_202610_12m. - For an experiment SKU, put
abtestin the descriptor so the id contains_abtest_, for examplesevenmind_plus_apple_abtest_202610_12m. The app hides such ids from the regular paywall and only sells them to the Braze arm that names them (step 6). Do not use Gymondo’stest_a,test_bdescriptors: the app does not recognise them, so such a SKU shows up for everyone and competes with the regular product for its card. MIND-915 will replace this naming rule with a catalog tag. - End it with the period (
_12m,_1m); the backend derives the subscription label from it. - Keep it under 50 characters, lowercase, without spaces.
- Follow the Gymondo scheme
- Decide whether staging gets its own id.
- The staging apps are separate store apps. Every existing 7Mind SKU has a separate staging id (for example
multi.7mind.google.yearly.staging). - Apple may refuse to reuse a product id across apps in the same account. A separate staging id avoids that.
- Every id you decide on goes through steps 1 to 5.
- The staging apps are separate store apps. Every existing 7Mind SKU has a separate staging id (for example
- Write down per platform: duration, price per country, trial length, and which existing product the new one replaces or sits next to on the paywall. The app only shows 12-month and 1-month products.
1. Store products
Play Console, app de.sevenmind.android (and de.seven_mind.android.stg for a staging id):
- Create a subscription with the product id.
- Add an auto-renewing base plan with the billing period (for example 12 months) and the prices per country.
- For a free trial, add an offer on that base plan: free trial phase of 7 days, eligibility “new customer acquisition”.
- Activate the base plan and the offer.
App Store Connect, app de.7mind.iphone (and de.7mind.ios.stg for a staging id):
- Create an auto-renewable subscription in the same subscription group as the existing 7Mind subscriptions.
- Set the duration and the prices.
- For a free trial, add an introductory offer: free, 7 days.
- Fill in the localized name and the review information. A new subscription goes to review with the next app version, or on its own if the app is already live with in-app purchases.
Never delete or unpublish a store product people have bought: that cancels their subscriptions.
2. Contentful role
In space m5ivwq1dbwv8, environment master:
- Create a
userRole. Name itROLE_+ the upper-cased article number (for exampleROLE_SEVENMIND_PLUS_ANDROID_202610_12M). The name is how everything downstream matches it. - Set
roleListto the publisheduserBaseRoleentriesROLE_SEVENMINDandROLE_SEVENMIND_PLUS. Do not add shadow or vendor roles. - Publish it. Production only syncs published entries.
3. Contentful product
-
Country configs. For each country the product is sold in, create a
ProductCountryConfig: Country Code, Currency, Unit Price and Total Price (the yearly price, for example 77.99). Do not edit an existing country config to change a price, because other products may link to it. Reusing one with exactly the right country, currency and price is fine. -
Condition. Create a
ProductCondition: Duration12, IntervalMONTHS, Trial Duration7, Trial IntervalDAYS. Use months for yearly plans. -
Product. Create a
Productand fill it in:Field Value Article Number the exact store id. Check for leading or trailing spaces Payment Service Provider GOOGLEorAPPLEType ONE_OFF, like every live store product, until Gymondo says otherwiseCountry Config the configs from step 3.1 User Role the role from step 2 Status DRAFTfor nowConditions the condition from step 3.2 Vendor SEVENMINDGroup empty -
Check, then lock. Review every field, then set Status to
PUBLISHEDand publish the entry and its linked country configs and condition. Once the status has leftDRAFT, the product cannot be changed: function-product-v1 drops every later field edit. Decide price, trial, duration and role before you publish. A later change means a new plan (see Changing a live SKU).
4. Contentful package on the paywall
- Create the package. Open the package of the plan the new one sits next to, for example
[DEF][SEVENMIND] Google 12M Reducedfor the Android yearly trial. Use the ”…” menu, then Duplicate. The copy is an unlinked draft. - Fill it in. Change only the internal name (for example
[DEF][SEVENMIND] Google 12M Test A 202610) and the article number. Keep the title, banner, highlight and voucher definitionNONE. - Publish the package.
- Link it. Open the platform’s tier card (
[DEF][SEVENMIND][GOOGLE][PLUS] Tier Cardor[DEF][SEVENMIND][APPLE][PLUS] Tier Card). Under “The packages that are available for this tier”, choose Add content, then Add existing content, and pick the package. The order matters only when two products of one store fill the same card (same length, both with or both without a trial): the app shows the first one in the catalog response. To replace a product, take the old package out instead of adding the new one next to it. - Publish the tier card.
- Republish the root. Publish the root again:
[DEF][SEVENMIND][GOOGLE] Google Go Premium Globalor[DEF][SEVENMIND][APPLE] Apple Go Premium Global. The page snapshot is only rebuilt when the root is processed.
This changes the paywall page in staging and production at the same time. On its own it is harmless, because the Lambda drops the package until step 5 is deployed. Once step 5 is live, the app offers the product to every user whose store app sells it, unless the id contains _abtest_.
5. productsConfig.json allow-list
In Gymondo-git/terraform-workspace-service-gateway:
- Open
resources/gateway/cmd/product-change-v3/data/productsConfig.json. - Add the article number to
sevenmind, thenDEFAULT_INT, thenROLE_DEFAULT, then the platform (googleorapple), tierPLUS,products. - Do not add a country key under
sevenmind; that changes the page slug and breaks the response. - Open the PR (previous example: commit
2dac7c07, “TP-556 add 7Mind products to productsConfig”) and get it deployed. The file is compiled into the Lambda for both environments.
6. Braze intro offer experiment (experiments only)
The paywall reads one experiment, the Braze feature flag ff_app_intro_offer_experiment (MIND-910). Its arms decide which users get an experiment SKU at its introductory price. A new flag id needs an app release.
- Create the SKU as usual. Steps 1 to 5 apply, with
_abtest_in the article number (step 0). The catalog then returns it to everyone, and the app hides it from users outside the arm. - Set up the store offer.
- Google Play: on the SKU’s base plan, a new-customer offer with one discounted payment for the first 12 months, optionally after a free trial phase.
- App Store: an introductory offer with the discounted price for the first year. The App Store allows one introductory offer type per SKU, so an iOS test SKU has no free trial. The app reads the price over the
seven_mind/storechannel. - If the store does not discount the SKU for a user, or the offer is not one payment for exactly 12 months, the app drops it and the user sees the regular paywall. Nobody is charged a price the paywall did not show.
- Set up the arms. Every arm keeps the flag enabled and sets the string property
varianttocontrol,treatmentorchallenger. A user without the flag is not in the test. - Fill the arm’s JSON property
offer(contract inlib/features/monetization/models/intro_offer_arm.dart):product_ids: the article number per store, with the keysiosandandroid.badge: the yearly card badge per language code.{discount}stands for the discount in percent; English is the fallback. Without a badge the card shows the regular discount badge.badge_no_trial: the badge for the card without a trial. Leave the discount out; that card shows it already.product_ids_no_trial(optional): the product for users who are no longer eligible for a trial.- A campaign arm sells at the regular price and only dresses the yearly card: the badge, with
{discount}against twelve monthly payments, and those payments struck through. Anofferwithoutproduct_idsis a campaign on the regular products;"campaign": truemakes it a campaign on the named product. The control arm can carry a campaign this way (Black Friday, PR 1591). An emptyofferkeeps the regular paywall.
- Test first. Add tester accounts to the arm by their numeric account id. Staging and production user ids are different accounts. The paywall reads the arm on every load, but Braze only refreshes flags when a new session starts (at most every five minutes) and after login. Reading the arm logs a Braze impression, control included, which Braze needs to count users.
- Start the experiment only after steps 1 to 5 are live. Otherwise the app logs “The catalog lacks the introductory price test product” and the arm’s users see the regular paywall while Braze still counts them in the arm.
7. Verify
Check each layer, cheapest first:
- Contentful. The product, role, country configs and condition are published. The status field says
PUBLISHED. The package is in the tier card and the root was republished. - Catalog response. On staging, run a profile build of the staging app. It logs full response bodies, so redact tokens when sharing. Open the paywall (deep link
sevenmindstg://monetization/false/false) and check thatapi/v3/sevenmind/products/{platform}lists the article number with the right price,lengthInMonthsand_trialchild.- Missing completely: step 4 or 5 is not live.
- Listed with an empty product: step 3 is missing for that country.
- Store. The app shows the new price on a device signed into the store with a license tester (Play) or sandbox account (Apple). The paywall shows the store price. For Android, check that the trial offer is offered and the price is not 0.
- Purchase. Buy with a test account. Then check that
monetization/subscriptions/statusreports premium and that the app unlocks. Use the accounts in test-accounts on staging. - Experiment. A tester in the arm sees the test SKU on the yearly card at its introductory price, with the badge from Braze. A user outside the arm never sees the
_abtest_SKU.
Changing a live SKU
A product cannot be changed once it has left DRAFT. To change the price, trial, duration or role of a SKU, create a new plan: go through this guide again with a new store product id, which becomes the new article number. Then take the old package off the paywall as described under Rollback. Until it is off, both products compete for the same paywall card and the app shows the one that comes first in the catalog response. Leave the old store product and Contentful product in place while anyone holds a subscription to it.
Rollback
- Remove the package from the tier card, publish the tier card and the root, and remove the id from
productsConfig.json. The paywall stops offering it. - For an experiment, remove the product from the arm’s
offeror stop the experiment in Braze. - Do not delete or unpublish the store product or the Contentful product while anyone holds a subscription to it.
Related
- app-subscription-products: how the pieces work together, with diagrams
- adding-a-web-sku: the same for web plans, insurance partners and paid prevention courses
- subscription-billing, gymondo-platform, 7mind-mobile-apps-monorepo, test-accounts