The BigCommerce connector contains a list of existing fields by default, which are generally very intuitive to map. However, there are others that need some mapping rules:
- Do not map unused fields. We recommend not mapping or disabling unused fields. Otherwise, the connector will overwrite the information in BigCommerce.
- For example, suppose that in BigCommerce there is a custom field called Technical Specification filled by the client for all products. Later, this field is created and mapped in Sales Layer inside the Output data section, but its values are not filled. As a result of synchronization, the values of Technical Specification will be overwritten.
i
Note: Synchronizations are carried out in only one direction.
- Use formulas. You can use formulas to fill in any field you need. For more information, access Formulas in the Support Center.
- Custom fields are supported both in BigCommerce and Sales Layer in products and variants.
- Custom fields are unsupported in categories either in BigCommerce or this connector.
- Custom fields can be sent to BigCommerce by creating additional fields in the Products and Variants tabs. If the custom field in BigCommerce does not exist, it will be created. If it exists, it will be updated. If it is deleted in Sales Layer, it will be deleted in BigCommerce.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article