SKU mapping
Documentation on Salesforce SKU mapping
This guide covers how to create, edit, and manage SKU mappings at GitLab. Administrators should review the Administrator tasks section.
Understanding SKU mapping
What is SKU mapping
SKU mapping is the process we use to map a Product Rate Charge from Salesforce to a support subscription tier (Ultimate, Premium, ASE, etc.) in Zendesk.
Why is this needed
Because names can often change in the backend (of Salesforce) and are not always clear what exactly they correspond to. Having a mapping for these allows for backend systems to translate a “name” to an actual subscription tier.
Current SKU mapping
Due to the large number of them, we document the mapping via the Product Rate Charge Name mapping google sheet.
Administrator tasks
Danger
- This directly impacts the calculated support entitlement of our customers in Zendesk. You can render a customer with no support entitlement unintentionally. Exercise extreme caution in making changes.
Note
- All sections in this section require
Developerlevel access to the Zendesk-Salesforce sync processor project. - All sections in this section require
Editorlevel access to the Product Rate Charge Name mapping google sheet. - All tasks below should only be done if there is a corresponding request issue (Feature Request, Administrative, Bug, etc.). If one does not exist, you should first create one (and let it go through the standard process before working it).
Technical Details
- Deployment type:
Ad-hoc - Project repo: Zendesk-Salesforce sync processor project
- Google sheet: Product Rate Charge Name mapping
Adding a new SKU mapping
To add a new SKU mapping:
- Add an entry to the Product Rate Charge Name mapping google sheet
- Set the first column (
Product Rate Plan Charge Name) to theRate Plan Charge Namevalue in Salesforce (hyperlinked to the Salesforce URL of the item) - Copy the previous row’s second column (
Subscription Tier) to your new row’s second column - Select the correct corresponding subscription tier in the drop-down for your new row’s second column
- Copy the previous row’s third column (
In ZD-SFDC sync?) to your new row’s third column - Select
Nofor your row’s third column - Set the issue URL you are working from as your row’s fourth column (
Notes)
- Set the first column (
- Create a merge request to add the new mapping to the Zendesk-Salesforce sync processor project
- For this merge request, you will be editing the
data/plans.yamlfile. You need to locate the subscription section it fits into and add a new array entry using theRate Plan Charge Namevalue in Salesforce
- For this merge request, you will be editing the
- Get a peer to review your merge request’s changes
- Merge your merge request
- Finalize the row on the Product Rate Charge Name mapping google sheet
- Set the value of the third column (
In ZD-SFDC sync?) toYes - Delete the value in the fourth column (
Notes)
- Set the value of the third column (
Editing a SKU mapping
Note
- It is often better to instead add a new SKU mapping instead of editing an existing one. Consider adding a new SKU mapping instead of directly editing an existing one.
To edit a SKU mapping (i.e. change the Product Rate Charge Name used):
- Create a merge request to edit the existing mapping to the Zendesk-Salesforce sync processor project
- For this merge request, you will be editing the
data/plans.yamlfile. You need to locate the existing SKU by its original name and change it to the newRate Plan Charge Namevalue in Salesforce
- For this merge request, you will be editing the
- Get a peer to review your merge request’s changes
- Merge your merge request
- Edit the entry on the Product Rate Charge Name mapping google sheet
- Change the value of the first column (
Product Rate Plan Charge Name) to theRate Plan Charge Namevalue in Salesforce (hyperlinked to the Salesforce URL of the item)
- Change the value of the first column (
Removing a SKU mapping
To remove a SKU mapping:
- Create a merge request to edit the existing mapping to the Zendesk-Salesforce sync processor project
- For this merge request, you will be editing the
data/plans.yamlfile. You need to locate the existing SKU by its original name and delete its entry.
- For this merge request, you will be editing the
- Get a peer to review your merge request’s changes
- Merge your merge request
- Delete the entry on the Product Rate Charge Name mapping google sheet
Last modified February 12, 2026: Remove aliases from frontmatter (
f895738e)
