Addon SKU on my Chargebee site has not been synced to Shipstation. Why?

Problem Statement

This article explains why addon SKUs may not sync to ShipStation and how to map Chargebee addons to ShipStation SKUs.

Solution

Addon SKUs may not sync if the custom field used for the SKU does not have the correct API name.

Steps to fix

1. Create a custom field at the plan and addon level with API name cf_inv_sku.
2. Use this field as the Inventory SKU for each item you want to map to ShipStation.
3. Chargebee maps this field to the SKU field at the line item level in ShipStation.

Mapping logic

• Plan: plan price[cf_inv_sku]
• Addon: addon price[cf_inv_sku]
• Charge: charge price[cf_inv_sku]

Mapping depends on order_line_items[entityType] (plan, addon, or charge). The custom field Field Label and API Name must both be cf_inv_sku.

If this custom field is not configured, order_line_items[sku] is used for ShipStation mapping.