The configuration uses a custom metaobject definition. First, we need to create the metaobject definition, then add entries for each selling plan.
Step 1: Create the metaobject definition for selling plan configuration
First you need to create a metabject definition on this page with this configuration:
Name:
Firmhouse Selling Plan MetadataType:
firmhouse_selling_plan_metadata
Then add these fields to that metafield:
Frequency field
Type: Single line text
Name: Frequency
Key:firmhouse_selling_plan_metadata.frequency
Description: Defines the subscription to which this metadata will be assigned
(e.g., 1_month, 3_weeks)
Description field
Type: Rich text
Name: Description
Key:firmhouse_selling_plan_metadata.description
Description: The custom description that will be shown for the plan.
Default field
Type: True or false
Name: Default
Key:firmhouse_selling_plan_metadata.default
Description: Set this field to true to make this plan the default subscription option.
After adding all items you can save the definition.
Step 2: Create metaobjects for each plan
Now that we have the metaobject definition ready, we can start adding the configuration for each plan. You can do that by clicking Add entry button on the metaobject definition page.
In the frequency field, enter the frequency configured on Firmhouse for your plan in the format <number>_<unit-in-plural-form> (e.g., 1_week, 2_months, 15_days, 1_year). To create a default description for all options without a matching meta object, use default as the frequency field value.
Step 3: Add the metaobject definitions to widget configuration
We can now assign the metaobjects to the Subscription Options configuration. To do this, go to the theme editor and open the Subscription Options widget settings.
Scroll down to the Card Layout Settings section and click the Select button next to the Selling Plan Metadata field. Then, select all the options you have configured.
Once added, confirm that the descriptions appear for each option. If everything looks correct, you're all set!
Step 4 (Optional): Translate your metaobject content (for multilingual stores)
If your store supports multiple languages, you can translate the metaobject content using the *Translate & Adapt* app.
Go to the Metaobject translation section in the Translate & Adapt app.
From the top bar, select the *market* and *language* you want to translate the content for.
On the sidebar, select the metaobject you created for the widget metadata (for example, Firmhouse Selling Plan Metadata), and update the translations for each field (such as the *Description* field).
Save your changes and test on your storefront by switching to the translated language.
Please note to not translate the values like for instance 2_months, 4_months etc, otherwise the translation will not work.
