Summary: Step-by-step guide to create a new 7Mind plan outside the app stores: a paid web subscription sold through the Adyen checkout on app.7mind.de, a discount voucher, free access for a health insurer’s members (by insurance number or voucher code), and a paid prevention course. Covers who does what, the Contentful and Back Office entries, the developer steps and how to verify.
Sources: Gymondo-git code read on 2026-10-23: Gymondo-2.0 (gpscheduler ProductComponent, ProductRepository, DefaultProductService, TransformationsV1, NextProductsMap, DefaultVoucherRedeemService, DefaultPurchaseService), frontend-public-pages origin/develop (src/service/product/, product-selection-step.tsx, product.slice.ts), service-backoffice (campaignSingle), function-payment, function-sevenmind-legacy-gateway origin/main and PR 109 (MIND-879), terraform-workspace-service-gateway productsConfig.json; sevenmind/website-next-js lib/checkout/, components/forms/InsuranceNumberForm.tsx; the live catalog on app.7mind.de/de/packages/signup (2026-10-23); Notion “How to create new products and all around it” and DNA-5245; Slack 7m_product-team-public (MIND-879 thread, 2026-10-09 to 2026-10-23) and Dana’s “Creating new plans (SKUs)” thread (2026-09-28); the Gymondo Contentful entries themselves (userBaseRole bundles, the defaults of a new Product), read in the UI while setting up MIND-879 on 2026-10-23; function-product-v1 main (interfaceadapters/handlers/eventhandlers/producteventhandler.go, application/product/service.go, validator.go) and gpscheduler ProductComponent, read again on 2026-10-27 for the status rules
Last updated: 2026-11-09
This is the web and partner counterpart of adding-an-app-store-sku. Read app-subscription-products for the Contentful model: the same Product, ProductCountryConfig, ProductCondition and userRole entries are used here, with different values. Nothing is created in Chargebee any more (see subscription-billing).
Which case are you in?
| You want | Example | Section | Developer needed? |
|---|---|---|---|
| A new paid web plan, or a new price or duration | a 6-month plan for affiliates, a yearly plan without trial | A | No |
| A discount on a web plan | 54 % off the yearly plan with an influencer code | B | No |
| Free access for an insurer’s members, who register with their insurance number (KVNR) | BMW BKK, BIG direkt, AOK Rheinland/Hamburg | C | Yes, in the gateway |
| Free access with a voucher code on a partner page | BARMER30 | D | No, unless the grant must exclude Plus |
| A new paid prevention course, or a new duration of one | a 6-month ABSM next to the 12-month one | E | Yes: Gymondo, website and gateway |
Who does what
| Part | Usually done by | Access needed |
|---|---|---|
| Contentful product, role, country configs, condition | 7Mind product, or Gymondo backend | Gymondo Contentful space m5ivwq1dbwv8 |
| Back Office campaign and voucher | The stakeholder who needs it (marketing for discounts, partnerships for insurers), or Gymondo through a CH ticket in fitness-checkout-helpdesk | Gymondo Back Office, on test and prod separately |
| Storyblok page or price card | The stakeholder | Storyblok space 148196 |
| Gateway code and voucher secret (C, and D when the grant excludes Plus) | 7Mind developer | Gymondo-git/function-sevenmind-legacy-gateway, AWS Secrets Manager |
| Store product row for a paid prevention course (E) | Gymondo backend | Gymondo-2.0 database |
| Website code (E only) | 7Mind developer | sevenmind/website-next-js |
| Reporting and CRM | Tell DnA and CRM the article number, the campaign title and, for C, the profile marker |
The parts of one case can be done in parallel. The one order that matters: the Back Office only offers a product once it is published in Contentful and synced.
Questions people ask first
- Where do I create a new plan? In Gymondo Contentful, as a
Product. Chargebee is not used for anything new. - How do I add a price point to an existing plan? There are no plans with several price points any more. Each duration, price level or trial variant is its own
Productwith its own article number. The price per country is aProductCountryConfigon that product. A temporary or partner discount is a voucher, not a new product. - Can I change a plan that is already live? No. A product cannot be changed once its Status has left
DRAFT. A new price, trial, duration or role is a new plan: a newProductwith a new article number (section A). Then point the price cards and links at the new article number. - Where are the old plans? The web plans sold today are Contentful products too, for example
multi7mindsubyearly-deand themulti7mindsubexperiments*family; step 2 of “Verify” lists them. Old subscribers keep their Chargebee and FastSpring subscriptions as shadow records (subscription-billing). - How does a plan decide what the user can open? Product, then its
userRole, then theroleList. The gateway turns roles into content packages: an active subscription unlocks Plus, andROLE_PREVENTION_*roles unlock prevention courses. Packages are no longer linked to plans in Contentful. 7Mind’s own Contentful space still holds the content, not the products. - What about app store plans? See adding-an-app-store-sku.
0. Decide the article number
- Reuse first. Gymondo’s rule is one product per distinct setup. If a product with the same price, duration, trial and roles exists, reuse it and create a new campaign or voucher instead.
- Follow the naming scheme
[vendor]_[tier]_[platform]_[department]_[descriptor]_[country]_[YYYYMM]_[period], with vendorsevenmindand platformweb.- Paid plans, live examples:
sevenmind_plus_web_perf_infl_202610_12m,sevenmind_plus_web_perf_infl_trial_202610_12m,sevenmind_plus_web_affiliate_202610_6m. - Prevention-only insurance grants use tier
preventionand departmentb2b, for examplesevenmind_prevention_web_b2b_bigdirekt_202610_6m.
- Paid plans, live examples:
- Keep it clean. Lowercase, no spaces, at most 50 characters, ending with the period (
_12m,_6m). The gateway derives the plan name users see from that ending. - One id for both environments. There is one Contentful space, and staging and production each sync their own copy from it.
A. Paid web plan
-
Country configs. Create one
ProductCountryConfigper country the plan is sold in: country code, currency, unit price and total price. The total price is what Adyen charges for the whole period. The web catalog is chosen by the visitor’s country, so a country without a config does not get the plan. Do not edit an existing config to change a price; other products may link to it. Leave Affiliation empty unless the plan is bound to a channel (see the end of this section), and leave Program empty. The easiest way to get a new config is the product’s own “Add content” button under Country Config, which creates a new entry in place; the same works under Conditions. -
Condition. Duration and Interval, for example
12/MONTHS,6/MONTHSor1/MONTHS. For a trial set Trial Duration7and Trial IntervalDAYS; leave both empty for no trial. On the web the Gymondo backend runs the trial: with a trial the first payment is only authorised, without one it is charged right away. -
Role. Create a
userRolenamedROLE_+ the upper-cased article number (all live web plans follow this), withroleListROLE_SEVENMINDandROLE_SEVENMIND_PLUS, as for app plans. Publish it. -
Product. Create a
Product. A new entry starts with Payment Service ProviderADYEN, TypeRECURRING, VendorGYMONDOand StatusDRAFT, so Vendor always needs changing:Field Value Why Article Number from step 0 Check for leading or trailing spaces Payment Service Provider ADYENMakes it a web product. Store plans use GOOGLEorAPPLEType RECURRINGWith ONE_OFFthe plan does not renew. Store plans useONE_OFFbecause the store renews themCountry Config from step 1 User Role from step 3 Conditions from step 2 Vendor SEVENMINDGroup empty PARTNER,CORPORATEandB2Bchange the product type, and the plan drops out of the web catalogNext Product empty Ignored by the sync Status DRAFTwhile editing -
Check, then publish. Review every field, set Status to
PUBLISHEDand publish the entry with its country configs and condition. From then on the product cannot be changed: a mistake or a later change means a new plan with a new article number (see Gotchas). The web catalog only showsPUBLISHEDproducts, on staging too. You cannot test a web plan before it is locked, and publishing makes it live on staging and production at the same time. -
Link to it.
- On www.7mind.de, a Storyblok price card with
ctaHref?buy=<article number>(add&code=<voucher>for a discount). The website passes unknown ids through to the checkout, so it needs no code change. The price on the card (priceLabel) is typed by hand: keep it in line with the country config. - Anywhere else, link to
https://app.7mind.de/signup?article_number=<article number>, optionally with&voucher=<code>and&channel_id=<id>. - If the checkout cannot find the article number for the visitor’s country (unknown, not published, no country config), it sends the visitor to www.7mind.de/preise.
- On www.7mind.de, a Storyblok price card with
A web plan needs no productsConfig.json, tier card or gateway change. Those are only for the app.
Renewing into a different plan (an introductory price that renews at the regular price) needs a code change and deploy in Gymondo-2.0 (NextProductsMap). There are no 7Mind entries today. The same goes for struck-through “fake” discounts (fakeDiscountsMap).
Channels. A channel (type INFLUENCER, PARTNER or CRM) ties a product to an acquisition source. A plan only needs one if it should only be offered to visitors who arrive with that channel_id, like the /study university pages. The channel must exist before its id is set in the country config’s Affiliation. How new channels are created today was not found (earlier ones were database migrations); ask Gymondo.
B. Discount voucher
- Campaign. In the Gymondo Back Office, create a campaign with the discount (relative or fixed), the validity dates and the maximum uses. Pick the exact article number as the product, or no product for “all products”. The dropdown only lists published, active Adyen products, so Contentful comes first. Create it on test and on prod separately.
- Voucher. Add the voucher code to that campaign.
- Name the campaign carefully. DnA reads the intent tag from the title (
[INF],[SM],[B2B],[CRM],[MAR]and so on), followingXX-[GRP]-7M-..., for exampleDE-[B2B]-7M-7Mind_Insurance_-_GWQ_BKK_default. A malformed title lands in the wrong report and cannot be fixed afterwards. - Link it with
?buy=<article number>&code=<code>on a price card, or on a Storyblok coupon page. - Match the SKU. A voucher only applies if its campaign lists the exact article number the page links to. If it does not, the coupon card on www.7mind.de says the code is invalid, and the checkout charges full price without an error.
C. Insurance partner with insurance number
How it works. The partner page is a Storyblok b2b-pages/<slug> story with an InsuranceNumberForm. The form posts the provider key and the insurance number to the gateway (/insurances/generic/activate). The gateway:
- checks the key and the number’s checksum;
- writes the marker
<MARKER>_<KVNR>to the profile; - redeems the partner’s Back Office voucher.
The voucher’s campaign points to the product, whose role grants the courses. Nobody pays.
Steps.
-
Role. In Contentful, create a
userRolenamed exactlyROLE_+ the upper-cased article number. ItsroleListlinks existinguserBaseRoleentries, and those are bundles. The roles are flattened when they reach the user (app-subscription-products), and the gateway maps courses from the innerROLE_PREVENTION_*names, so you link the bundle that contains the course role, not the course role itself:userBaseRole to link Contains Use for ROLE_SEVENMIND_PREVENTION_ONLYROLE_FREEMIUM,ROLE_PREVENTION_ALLAll courses, without Plus ROLE_SEVENMIND_PREVENTION_<COURSE>, for example_SLEEPor_ABSMROLE_FREEMIUM,ROLE_PREVENTION_<COURSE>One course, without Plus ROLE_SEVENMIND_PLUS_PREVENTION_<COURSE>ROLE_FREEMIUM,ROLE_PLUS,ROLE_PREVENTION_<COURSE>One course and Plus, like the reward products in E. Not for a prevention-only grant ROLE_SEVENMINDnothing (empty roleList)Every grant links it as well The contents were checked for
_ONLY,_SLEEP,_ABSMand_PLUS_PREVENTION_SLEEP. Course names as the gateway uses them:ABSM,RESILIENCE,SLEEP,PME,ABSM_PARENTS,AUTOGENIC_TRAINING,TOBACCO. The picker lists look-alikes next to each other (ROLE_SEVENMIND_ALLnext toROLE_SEVENMIND,_ABSM_PARENTSnext to_ABSM, the_PLUS_variants), so select by the exact name and open a bundle to check itsroleListwhen in doubt.For a prevention-only grant the role’s name matters: the gateway recognises the grant by it.
-
Product. Change the defaults of a new entry (A, step 4): Payment Service Provider, Type and Vendor all start with other values. Create the country config and the condition as new entries from the product’s “Add content” buttons; never link existing ones, other products share them.
Field Value Why Payment Service Provider NONEMakes it a free grant (type FREEBIE) Type ONE_OFFA grant does not renew Group empty B2Bgrants nothing;PARTNERchanges the typeConditions 6/MONTHS, no trialThe length of the access Country Config DE, EUR, price 0 User Role from step 1 Vendor SEVENMINDStatus DRAFT, thenPUBLISHEDA product that is not active makes its vouchers fail -
Back Office. Create a
SIGNUP/FREEcampaign on that product and one multi-use voucher code, on test and on prod separately.- Leave the campaign’s end date empty. An end date cuts every grant off at that date, whatever the product’s duration.
- Name the campaign so DnA can tell the partner apart, for example
DE-[B2B]-7M-7Mind_Insurance_-_<Partner>.
-
Gateway code (developer). In function-sevenmind-legacy-gateway:
internal/domain/insurance/products.go: the provider key Storyblok sends (for examplebig_direkt) and its profile marker (for exampleBIGDIREKTGESUND). Use upper-case letters only for the marker; DnA splits partners by it.internal/config(InsuranceVouchers,secrets.go) andliveSource.genericCode: the partner’s own voucher. Without this, a non-GWQ provider redeems Melitta’s voucher.internal/entitlementpreventionOnlyArticles: the article number, if the grant must not include Plus. Without it, every insurance grant also unlocks the full Plus catalogue.- Tests and a PR. After the merge, run the manual
Buildworkflow once per environment: merged is not deployed.
-
Secret. Put the voucher code into
INSURANCE_VOUCHER_<PARTNER>in each environment’s Secrets Manager document of the gateway. Until it is there, that partner’s activations answer 502, before anything is written. -
Storyblok. Create the
b2b-pages/<slug>story with anInsuranceNumberFormblok:insuranceProvideris the provider key from step 4,insuranceNamethe name shown. The partner logo goes into the hero’slogoList. Publish. -
DnA and CRM. Send them the marker prefix, the campaign title and the article number (DNA-5864). The marker is written on a best-effort basis: if writing it fails, the activation still succeeds, and that user cannot be billed to the insurer.
Example: BIG direkt and AOK Rheinland/Hamburg (MIND-879). These are the first prevention-only partners. The gateway change is Gymondo-git/function-sevenmind-legacy-gateway PR 109. The Contentful entries must match its hardcoded values exactly:
| BIG direkt | AOK Rheinland/Hamburg | |
|---|---|---|
| Article number | sevenmind_prevention_web_b2b_bigdirekt_202610_6m | sevenmind_prevention_web_b2b_aokrh_202610_6m |
| userRole name | ROLE_SEVENMIND_PREVENTION_WEB_B2B_BIGDIREKT_202610_6M | ROLE_SEVENMIND_PREVENTION_WEB_B2B_AOKRH_202610_6M |
roleList (userBaseRole entries) | ROLE_SEVENMIND_PREVENTION_SLEEP, ROLE_SEVENMIND_PREVENTION_ABSM, ROLE_SEVENMIND | ROLE_SEVENMIND_PREVENTION_ONLY, ROLE_SEVENMIND |
| Course roles inside the bundles | ROLE_PREVENTION_SLEEP, ROLE_PREVENTION_ABSM | ROLE_PREVENTION_ALL |
| Contentful entries (published 2026-10-23) | product nZNUIV8vb5hD3zMlj6EK7, role ETvByrO7wlxD1aAXyYuaH | product 2zjPHOLVrYu01EW9TZQEQy, role 4GR6pTiLJ7stNBBqMHpJUm |
| Provider key (Storyblok) | big_direkt | aok_rheinland_hamburg |
| Profile marker | BIGDIREKTGESUND | AOKRH |
| Secret | INSURANCE_VOUCHER_BIG_DIREKT | INSURANCE_VOUCHER_AOK_RHEINLAND_HAMBURG |
D. Free access with a voucher code
The partner page hands out a code instead of asking for an insurance number.
- Product. Create a product as in C, or reuse an existing free grant with the same duration and roles.
- Back Office. A
SIGNUP/FREEcampaign and a voucher, on test and on prod. - Storyblok. A
couponSectionpage. A valid free code sends the user toapp.7mind.de/signup?voucher=<CODE>&allow_multiple=true, which redeems it even when the user already has a subscription. - Code only if the grant must exclude Plus. Then its article number goes into
preventionOnlyArticles(C, step 4).
Users of this path carry no insurance-number marker, so reporting and billing can only tell them apart by campaign and voucher.
E. Paid prevention course
How it works. The /krankenkasse page sells each course as a one-off Adyen purchase of a Gymondo store product (ids 104 to 110, 99 €). The insurer reimburses the price. The purchase creates a free “reward” subscription for the store product’s reward_product_id. That reward product’s role links the bundle ROLE_SEVENMIND_PLUS_PREVENTION_<COURSE>, and the ROLE_PREVENTION_<COURSE> inside it unlocks the course (for sleep: ROLE_SEVENMIND_PLUS_WEB_REWARD_PREVENTION_SLEEP_12M links ROLE_SEVENMIND_PLUS_PREVENTION_SLEEP).
For a new course or a new duration (for example a 6-month ABSM):
- Reward product. In Contentful, as in C:
NONE, the access duration and a role that links the course bundle (C, step 1). Its article number must containweb_reward_prevention_<course>(likesevenmind_plus_web_reward_prevention_pme_12m). The gateway reads the course from that part of the name; otherwise users see the access labelled as a Plus plan. Course tokens:absm,absmeltern,resilience,sleep,pme,autotrain,smoke. - Store product (Gymondo). A new
store_productrow with the price, vendorSEVENMINDandreward_product_idset to the reward product. There is no self-service screen for this; ask the Gymondo backend team. Use new ids and article numbers: store product ids are shared with Gymondo, and Gymondo-2.0 PR 812 (Bertelsmann BKK) once took over 7Mind’s courses 104 to 106 for 10 days. - Website (developer). Add the SKU and its store product id to
lib/checkout/preventionProducts.ts, and the SKU to the locale catalogue (krankenkassePage.selectInsurance.<course>.package). Deploy.
Verify
Check each layer, cheapest first:
-
Contentful. Product, role, condition and country configs are published, and Status says
PUBLISHED. -
Web catalog. Run
curl -s https://app.7mind.de/de/packages/signup(staging:app.6mind.de) and search the output for the article number. From Germany you always get the German catalog; for another country add-b "userRegion=FR". -
Checkout. Open
https://app.6mind.de/signup?article_number=<article number>. The plan is preselected with the right price. Ending up on /preise means the checkout did not find it. -
Purchase. Buy on staging with an Adyen test card and a staging account from test-accounts. The app then reports premium.
-
Voucher.
curl https://app.7mind.de/api/v1/public/sevenmind/vouchers/<CODE>/valid(no login needed). A free grant answers@type: FreeSignup. -
Insurance partner. On test, activate with a test insurance number for the partner. Then check:
x-userinfocarriesROLE_+ the upper-cased article number;- only the expected courses unlock and Home stays locked;
isPremiumis false;- the subscription ends after the product’s duration.
Repeat with an account that already has Plus.
Gotchas
- A product is final once it leaves
DRAFT. function-product-v1 applies field edits only while its stored copy isDRAFT, and a stored product never goes back toDRAFT. Every later edit in Contentful is dropped, whatever the Status is switched to. To change a price, trial, duration or role, create a new plan with a new article number and link to it instead of the old one. The web never shows aDRAFT, and publishing is live on both environments at once. - Prevention-only fails open. If the role name or the article number in
preventionOnlyArticlesis wrong, the user gets the full Plus catalogue whileisPremiumstays false. Check it on test. - Campaign end dates cap grants. A campaign that ends on 31.12. ends every grant on 31.12., even one redeemed the day before.
- “Already activated” can mean a configuration fault. On 7Mind routes a free voucher stacks on an existing subscription. If an insurance activation answers 409 “already activated”, the campaign has usually expired or the product is not active.
- Shared values with Gymondo. Gymondo already has its own prevention partner
BIGDIREKT, and store product ids are shared. Use distinct article numbers and markers, and check that nothing on the Gymondo side keys on the same value. - Country configs are shared. Create a new one for a new price instead of editing one.
- VAT is fixed in the sync. It is the same rate for every country. Check with finance before selling outside Germany.
Not verified yet
- How new channels are created today.
- The full campaign naming convention. Notion “Backoffice Naming Convention” points to a Google Sheet.
- Where finance’s account number per SKU (asked on 2026-09-28) is kept now.
- Whether the new role’s own name reaches
x-userinfo. Prevention-only grants depend on it; check on test. - Whether the checkout page lists every published plan or only the one in
article_number. - Who creates
store_productrows, and what store products 123 to 128 are for.
Related
- adding-an-app-store-sku and app-subscription-products: the same for the app stores
- subscription-billing: the wider billing picture
- function-sevenmind-legacy-gateway: insurance activations and entitlement
- frontend-public-pages: the checkout on
app.7mind.de - website-next-js and storyblok-cms: price cards and partner pages
- test-accounts: staging accounts for checkout tests