This article details how to either push data onto BigCommerce, or pull data from BigCommerce into AmberPOS.
Access the BigCommerce Integration screen as shown in the article below.
1. Uploading Products Onto BigCommerce
In the Webstore Integration Window choose the tab for 'AmberPOS View'. This will display product records that exist in AmberPOS.
Products listed here will have a linked status.
- Products in AmberPOS that are not linked to records on BigCommerce
- Products in AmberPOS that are linked to records on BigCommerce
If you select a cell in the row of a product record in this list view and click on the button in the top-right corner, the product information will push onto BigCommerce. If you do this for a product that has an not linked status, then it will create the record online. If you do this for a record that has a linked status, then it will simply update the linked record online with the data that is in AmberPOS.
An error message occurs for various reasons, though if you do receive one then check to see if a product record exists already on BigCommerce that has the same name. BigCommerce does not allow more than one record to have the same name value. Also review your product to make sure that all the values stored to it are valid. Then do an update of each of the LC resources found in the article HERE and once having done so, click on the button found in the bottom-right corner of the screen.
Once uploaded onto BigCommerce, the record will then have a linked status
2. Importing Products Into AmberPOS
When you click on the 'Web View' tab you will be able to see records that exist on BigCommerce. From here you can select products on BigCommerce that do not exist in AmberPOS and import them. First make sure the item has a not linked symbol and then you can click on the button to pull the data to be created as records in AmberPOS.
When data pulls into AmberPOS, it cannot assume certain required data values that are required in AmbePOS are valid when coming from BigCommerce. There are are some considerations to know about below.
SKU - The SKU field on BigCommerce is optional, where in AmberPOS it is required. The value on BigCommerce can also go beyond the syntax constraints AmberPOS has for only numbers and letters being used. If there is a SKU value on BigCommerce, it will be stored in the Product Number field in AmberPOS, and AmberPOS will auto-generate a SKU code for the record that is created in the AmberPOS software.
Department - BigCommerce Category field is similar, though different. Because Departments are required in AmberPOS, it will reference the category assigned to the product being imported and take the first assigned category to assign as the department value in AmberPOS. Because of this, new departments will likely be created as the structure and purpose of the field type is somewhat different.
Vendor - BigCommerce doesn't have a vendor value. Since this is a required field in AmberPOS, then a default 'No Vendor' will be assigned to the product that is imported.
Once imported into AmberPOS, the record will then have a linked status