Steps in the screenshots correspond to the numbers in the headings.
This article is meant to be a reference for common errors that can occur when loading a new product into Salesforce CPQ.
When a new product is added into Salesforce CPQ and the product price type is either "-LEG", "-REP" or "-NEW", the integration will attempt to automatically add that product to Big Commerce (or the eCommerce online store). This automated process can be susceptible to errors if certain fields do not match up to expected values.
Some of the common errors are listed below:
1. Spacing between the Product Name and its Type – There should be no spacing between the product name (Part123) and its type (-NEW). As an example, Part123-NEW will go across successfully to eCommerce; Part123 – NEW will not.
No spaces in product name or between the type and "-"
2. Missing Product Type – There have been many records that do not have the product type as part of the Product Name. For instance, a Product Name of Part123 may be given, with no –NEW, -REP, etc. We need the part type on the end of the Product Name in order to successfully create the related parts in eCommerce, as we use this in assigning product SKUs and pricing. (Part123-NEW is acceptable; Part123 is not.)
For go live, Product names must end with "-LEG", "-REP", or "-NEW" to be successfully created in eCommerce.
3. Mismatch between Product Name and Product Price Type – We have seen some product records that have a Product Name that references a different type of part than is listed in the Product Price Type field. For example, the Product Name would show Part123-NEW and the Product Price Type would be listed as Refurbished. This mismatch causes the integration to fail as it is trying to create SKUs in eCommerce.
Make sure that the Product Name and Product Price Type MATCH ! If they don't the integration will fail.
4. Duplicate Product Records – There have been cases where the Product Names of two products are unique, but their Product Code field or Part Number field contains matching values. This may be due to a field that wasn’t updated when using the “Clone” function in Salesforce. The only products that should share a Part Number are those that are different product types of the same part (Part123-REP and Part123-NEW). Product Codes should never be duplicated across multiple product records.
Duplicate product records will cause the integration to fail. This can occur when the Clone feature is used in Salesforce.
5. If the Product is displayed in the eCommerce Store, you will see a number in the Big Commerce ID field and the eCommerce Ready flag will be checked.
The eCommerce Ready checkbox is the final step to having the product displayed in the store. The Data Integrity team will check that box after ensuring that the data is correct, the picture is ready, OEM is correct, etc.
6. Additionally, the Service Area can be used to direct the work to the proper group in Salesforce. For example, products with Harvard as the Service area that are purchased by ATS Buyers for FMS Sites will go straight to the IPS Pricing team.
0 Comments
Add your comment