Configure Plan Mapping
Plan mapping translates internal plan identifiers into human-readable names shown to users. Add-on mapping does the same for add-on keys.
Plan mapping
Section titled “Plan mapping”- Open your Vertical in Strapi
- Find the planMapping repeatable field
- Add entries for each plan:
| Field | Purpose | Example |
|---|---|---|
| planName | Internal plan ID (from pricing engine) | BASIC |
| mappedName | Display name shown to users | Basic Plan |
Example
Section titled “Example”| planName | mappedName |
|---|---|
BASIC |
Basic |
COMFORT |
Comfort |
PREMIUM |
Premium Plus |
Add-on mapping
Section titled “Add-on mapping”- Find the addonMapping repeatable field
- Add entries for each add-on:
| Field | Purpose | Example |
|---|---|---|
| key | Internal add-on key (matches Quote-Page add-on key) | GLASS_COVERAGE |
| label | Display name | Glass Coverage |
Where mappings are used
Section titled “Where mappings are used”- Quote page — Plan columns in the coverage table use
mappedName - Checkout — The selected plan shows the
mappedName - Policy details — After purchase, the policy summary uses mapped names
- Add-on labels — Anywhere add-ons are listed,
labelis used instead of the raw key
See also
Section titled “See also”- Vertical Schema Reference – planMapping and addonMapping field specifications
- Configure Coverage Table – how plan columns use the mapping
- Vertical Ecosystem – how plan mappings propagate through the system