BigCommerce is a leading e-commerce platform that enables businesses to set up an online store and sell their products online. You can connect your BigCommerce store and export your catalog data from PCC to the BigCommerce platform after the connection is established between PCC and BigCommerce.
The PCC BigCommerce connector enables you to connect PCC with your BigCommerce store and transfer data between these applications seamlessly.
Click the View Details
icon to view the details and features of the connector and the following is displayed.
Figure 210: Big Commerce connector description
Configuring the Connector
You need to configure the connector and add the token and API path for setting up the store. Once the store is configured, the product information present in the PCC catalog can be exported to the relevant store in the BigCommerce platform.
NOTE | You can add multiple stores for a BigCommerce connector if a customer has multiple stores configured for different vendors in the BigCommerce platform. |
The first step is to generate the token and API path to configure a BigCommerce store using these details. A detailed description about the same is explained in the Appendix section Generating Token and API Path to Configure BigCommerce Store.
To add a new BigCommerce store configuration:
Go to the PCC Platform Connectors screen and click the Set Configurations
icon available for BigCommerce as shown below.
OR
Click Configure Big Commerce Connector as shown in Figure 210: Big Commerce connector description.
By default, the Setup Credentials tab is selected.
Click Add New Store Configuration and the following dialog box appears to add the store details.
Type the Store Name, that is, the name of the BigCommerce store to which the product is to be mapped from PCC. For example, Test store.
Copy-paste the API Path, that is, the URL of the BigCommerce store (in this case Test store) to be configured which is mentioned in the text file generated as explained in the Appendix section Generating Token and API Path to Configure BigCommerce Store.
Copy-paste the Access Token required for authentication as mentioned in the text file generated as explained in the Appendix section Generating Token and API Path to Configure BigCommerce Store.
The
icon next to each field provides details on what data must be added.
NOTE | All fields are mandatory. |
Once all the values are entered, click the Check connection with entered values 
icon next to the Store Name to check whether the access token entered as well as the store URL is valid.
If the details are not valid, an error is displayed as follows.
Make the necessary changes and ensure that the connection is valid. If the connection is valid, the following message is displayed.
Click Add Store and the store is added successfully and is visible in the list on the PCC Big Commerce Connector page as shown below.
The following table lists the various fields along with its description that are visible on the Setup Credentials screen.
Fields | Description |
|---|---|
Actions | Displays the icons of the various actions that can be performed:
|
Store Name | Displays the name of the store added while configuring a store |
Created By | Displays the name of the user who configured the store |
Created On | Displays the date when the store was configured |
Updated By | Displays the name of the user who made any changes to the store |
Updated On | Displays the date when any modifications / changes were made to the store |
- To edit the store configuration details
- To delete the store configuration detailsYou can sort / filter the data in the columns in ascending or descending order as needed. By default, the latest store created is displayed first based on the date when it was created in descending order.
NOTE | The Setup Attribute Mapping tab is disabled as the attribute mapping is not required here. |
Editing the Store Configuration
Sometimes, the connectors might have some updates (a new feature / version update) which might result in changes in the tokens of the stores configured. You can edit the details configured in case of any such changes.
To edit the store configured:
In the Actions column, click the Edit Store Configuration
icon next to the store to be edited. The following screen appears.
Make the changes as needed and click Edit Store. The details are updated successfully.
Deleting the Store Configuration
You can also delete the store configured if the store is no longer required for exporting the product data.
To delete the store configured:
In the Actions column, click the Delete Store Configuration
icon next to the store to be deleted. The following screen appears.
Details about the store to be deleted are displayed.
Click Delete Store and the store is deleted successfully.
Syncing SKU Data from PCC to BigCommerce Store
The process to export any data and view it remains the same as explained in chapter 22 Export Catalog.
You can sync the product data, that is, SKUs along with their attribute values and linked assets from the catalog in PCC to the BigCommerce store by exporting the data using the BigCommerce sync option.
NOTE | In case of assets linked to SKUs, BigCommerce supports photo assets only. If a SKU has any other type of asset linked to it such as documents / videos, those will be ignored when the data is synced. Also, photo assets delinked from SKUs in PCC will be deleted through sync from BigCommerce as well. |
Let us understand how to export the data using the BigCommerce sync option in the following section.
Exporting the Data Directly to BigCommerce using API
This option will directly export / sync the catalog data to BigCommerce. Depending on the option selected, that is, SKUs present in the selected categories / entire catalog will be synced to BigCommerce directly.
Following are some of the key points to be noted while exporting data to BigCommerce:
No categories (taxonomy nodes) will be created in BigCommerce when the data is exported from PCC to BigCommerce. Thus, it is important to create the categories in BigCommerce before exporting the data. For example, SKUs being exported belong to the taxonomy Accessories > Watches > Analog and if this taxonomy does not exist in the store, the import will fail. You cannot change the name of the category after it is imported to BigCommerce. Once the categories are created in BigCommerce, all SKUs being imported in future will be added to the relevant categories.
If a SKU being exported to BigCommerce has incorrect attribute data, no error messages will be displayed. However, such SKUs will not be imported in BigCommerce.
For example, in the case of attributes Price and Weight, only numeric values are acceptable. If a non-numeric value is sent for these attributes, those values will be ignored in the sync.
If SKU title is not present for any SKU in PCC, the export will fail as SKU title is a mandatory field for BigCommerce. The SKU title is referred to as Product Name in the BigCommerce platform.
Currently, SKUs belonging to the same category will be shown in related SKUs (This is a BigCommerce functionality), that is, if a SKU belonging to Accessories > Watches > Analog is synced, the related SKUs will be displayed by default from the node Analog only. In this case, photo assets linked to other SKUs belonging to the Analog node will be displayed as related SKUs.
By default, UoM has been set for the following attributes in the BigCommerce store:
Unit Price – In the Currencies section under Store Setup, the default currency is already set to Rupees. You can change the currency as per the requirement in this section.
Weight – In the Store Settings section under Store Setup, the default UoM is already set to Kilograms (Kg). You can change the measurement unit as per the requirement in this section.
Length – In the Store Settings section under Store Setup, the default UoM is already set to Centimeters (Cm). You can change the measurement unit as per the requirement in this section.
The following metatags are relevant for BigCommerce and can be associated to respective attributes in the PCC catalog. If any of these metatags are associated to a SKU attribute, the values will reflect for the respective fields in BigCommerce:
BC_PRICE – The value of the attribute with this metatag will reflect in the Default Price field as part of the Pricing section in the store.
BC_COST_PRICE – The value of the attribute with this metatag will reflect in the Cost field as part of the Pricing section in the store.
BC_RETAIL_PRICE – The value of the attribute with this metatag will reflect in the MSRP field as part of the Pricing section in the store.
BC_DESCRIPTION – The value of the attribute with this metatag will reflect in the Description field in the store.
BC_META_DESCRIPTION – The value of the attribute with this metatag will reflect in the Meta Description field as part of the Search Engine Optimization section in the store.
BC_META_KEYWORD – The value of the attribute with this metatag will reflect in the Meta Keyword field in the store.
BC_DEPTH – The value of the attribute with this metatag will reflect in the Depth field as part of the Dimensions & Weight section in the store.
BC_HEIGHT– The value of the attribute with this metatag will reflect in the Height field as part of the Dimensions & Weight section in the store.
BC_WIDTH – The value of the attribute with this metatag will reflect in the Width field as part of the Dimensions & Weight section in the store.
BC_WEIGHT – The value of the attribute with this metatag will reflect in the Weight field as part of the Dimensions & Weight section in the store.
BC_AVAILABILITY – The value of the attribute with this metatag will reflect in the View Products section where the values will be appended in the name of the products if disabled or pre ordered. If the value is available, it will not be displayed as the product is available.
BC_AVAILABILITY_DESCRIPTION - The value of the attribute with this metatag will reflect in the Availability Text field as part of the Storefront Details section in the store.
BC_BRAND_NAME – The value of the attribute with this metatag will reflect in the Brand field as part of the Basic Information section in the store.
BC_PAGE_TITLE – The value of the attribute with this metatag will reflect in the Page Title field as part of the Search Engine Optimization section in the store.
BC_GTIN – The value of the attribute with this metatag will reflect in the Global Trade Number (GTIN) field as part of the Product Identifiers section in the store.
BC_UPC – The value of the attribute with this metatag will reflect in the Product UPC / EAN field as part of the Product Identifiers section in the store.
NOTE | Any SKU attribute associated with the above mentioned metatags should only have a single value. If there are multiple values, all the values will be ignored as BigCommerce accepts single values only in attributes associated with metatags. |
The acceptable values for an attribute with metatag BC_AVAILABILITY are any of the following:
Available
Disabled
Preorder
If an attribute associated with this metatag does not have any value, the default value ‘Available’ will be added after the data is synced to the store.
The custom attributes, that is, all those SKU attributes which are not associated with BigCommerce specific metatags will be added as custom fields in the BigCommerce store. If there are multiple values for these attributes, only the first value will be accepted by default while syncing to the BigCommerce store as multiple values are not supported. Also, the length of the characters in the attribute value should not be more than 250, else an error will be generated during the export process.
An image linked to a SKU marked as primary is displayed twice in the store. It shows both the actual image as well as the thumbnail which is the same image.
NOTE | The metatags BC_PRICE and BC_WEIGHT are mandatory and should be associated with the respective attributes in the PCC catalog for SKUs being synced to the store else the export will fail. Similarly, the SKU title for SKUs should not be blank else the export will fail too. |
To export the product data to BigCommerce:
Open the catalog in PCC from which the data is to be synced to BigCommerce as shown below.
Select the nodes which have the SKUs to be exported / you can export the entire catalog if all SKUs from all the nodes must be exported. Let us select a node Analog which contains SKUs to be synced to BigCommerce.
Right-click the node and then click Export Node to export SKUs from specific nodes as shown below.
The following screen appears.
Click the Export Catalog
icon for file type BigCommerce Sync and the following screen appears.
Enter the Export Name for the file to be saved.
Move the Nodes(s) To Be Exported toggle to All if you need to export the data from the entire catalog. Here, we will export product data from the selected node.
Select the Store Name from the drop-down list to which the data is to be synced as shown below.
Click Export and the export process is initiated. Refer section Viewing the Export File for more information on how to view the status of the export. Once the export process is successfully completed, you can go to the BigCommerce platform and view details in the Home page as shown below.
As shown above, the SKU Anaq7852 present in the Analog node selected to be synced to the BigCommerce site is displayed here. You can scroll the page further to view the SKU attributes and related SKUs synced to the store for this specific SKU.
Also, if the SKU has any related SKUs which are part of the same node Analog, it will be displayed in the Related products section.
Thus, you can make changes to the SKUs, update values in the PCC catalog which will be reflected in the BigCommerce platform after the sync is done successfully.
However, if an error occurs during the export process, an error file will be generated with details of the errors. The Export page will display the following information in case of an error.
You can download the error file and make the necessary changes and export again after correcting the errors listed. Following is a sample error file.
An error ‘Missing Required Fields Please provide a price., Please provide a weight.’ is displayed for a SKU ID. As the price and weight values are mandatory in the BigCommerce store, any SKU which does not have the necessary metatags associated will throw an error. In this case, the BC_PRICE and BC_WEIGHT metatags are missing for SKU attributes with SKU ID ABC_123. Once the metatags are associated with relevant attributes and the export is processed again, the sync will be done successfully.
NOTE | If some or all of the SKUs fail to sync, the process will be still shown as completed. However, since there is a failure, an error log will be generated. The sync process will be marked as ERROR only if an exception occurs before the actual loading is started, in which case an error file containing the cause of the error will be generated. |
The Product load summary will be shown for all records, and it will have the following fields:
Total products – displays the total count of SKUs being exported
Products processed – displays the total count of SKUs processed
Products successfully loaded – displays the count of SKUs loaded successfully from the processed SKUs
Failed to load – displays the total count of SKUs that have failed from the processed SKUs