Big Commerce User Guide
Big Commerce is an e-commerce platform. Our integration consist of the following flows: Get Taxonomy Create/Update Products Get Locations Delete Products Get Orders Get Refunds Create Refund Ship Orders
The integration follows our standard flows and actions so only the differences and out of the box details will be mentioned below.
Get Locations
We want to get all available location from Big Commerce and store them as enumeration field. The field should be available In Account Big Commerce. This field is mandatory for the quantity updates which we are sending to BigCommerce
Get Taxonomy
The taxonomy is generated via the Export Taxonomy section and is send via email. There are two types of taxonomy available for BigCommerce we have brands and categories. In order to distinguish and download the correct taxonomy file you can use the “Category for Export” field. In order to download the brand you have to specify Category for Export = “brand” In order to download the categories you have to specify Category for Export = “all” (or we can specify which exact categories)
The Brand taxonomy consist of BrandId and BrandName in Hemi we expect to have populated the BrandName as a mandatory field in Product Details > Brand or Product Account > Item Specific.
The Category taxonomy consist of CategoryId, CategoryPath and CategoryName. In Hemi you must populate the CategoryName in Product Account > Primary Category ID as a mandatory field.
Create Products
Once you have downloaded the taxonomies and optimise your product the mandatory fields in order to create a product are: Product Account > Title Product > SKU Product Account > Variation Group (if variation product) Product > Weight Product Account > Price Product Account > Quantity Product Account > Primary Category ID Product > Brand OR Product Account > Item Specific Product > ConditionID Product > Main Image (different set of images is available in Product Account BigCommerce)
Please note we are supporting more than one Primary Category ID and you can add more categories as Product Account Big Commerce > Additional Categories.
The products are created as per our standards with “List Update The Whole Item” action. Once product is created we will receive two new ids which we will store in Product Account > Channel Item ID and Product Account Big Commerce > Variant Id these ids will be used for update purposes.
The protect flags works as expected as well: Closed - Stop the creation. Please note if we have a variation group with 3 variants and only one of them is Closed = Yes we will stop all the variation group creation.
Update Products
The update products follow two different flows once for single products and one for variations however everything is automated and you just have to use the Update Price, Update Quantity or List Update The Whole Item actions. However when we are updating products we are not sending the images and the Item/Variation Specifics so if you need to update these details you will have to Delete the product (End Listing) and relist it.
The protect flags works as expected as well: Protect Price - We wont update the price
Protect Quantity - We wont update quantity
Protect The Whole Item - Will allow only quantity updates.
Closed - Stop all updates. Please note if we have a variation group with 3 variants and only one of them is Closed = Yes we will stop all the variation group updates.
Delete Products
We can delete products from BigCommerce using the Product Account > End Listing. Once the product is successfully deleted it will be removed from BigCommerce and we will update the relevant statuses in Hemi so once you set it for creation again no additional actions are required.
Get Orders
Order are downloaded every 15mins in Hemi and we are constantly checking for new or updated orders. The Get Orders consist of separate calls in order to combine the full order information so with every run we will first Get the orders, Get the Order Products, Get the Shipping Address and Get the Coupons. For the user the whole order flow will be incorporated into a single flow.
Get Refunds
Refunds will be downloaded separately from the Get Orders so there might be slight delays however all refund which are created outside Hemi will be downloaded and the orders will be updated accordingly.
Ship Orders
There is a predefined carriers which we can use and we have to introduce carrier mapping. All this should be introduced in a new table called “Big Commerce Couriers Mapping“ which we want to be a dependent table of Courier. In “Big Commerce Couriers Mapping“ we want to have all the available enumerations in a dropdown field. We are following the same pattern as standard and the mapping will be first we map the Order Shipment > Courier against Carrier > Name and get the Big Commerce Couriers Mapping > Big Commerce Courier. If NO Courier is provided on the order we want to introduce a default option in Account Big Commerce. If there is no mapping for the provided Courier on the order we want to set an error in Order Error table.
Order Ship API is synchronous process and we receive the response right after the request.
**Big Commerce do support partial shipping updates so we want to implement the partial shipping logic.
The details part of the shipping update are:** Order Shipment > Tracking Number Shipment > Tracking URL OR Courier > Courier Url Order Shipment > Courier
Create Refund
We are supporting all different types of refund via the Refund UI in Hemi. There is nothing specific here apart from the VAT calculations which we are doing internally when we are making the refund. Please note in some edge and rare cases there might be a discrepancies by 0.01 cents in the calculations and you may receive and error when making the refund. Unfortunately we BC have their internal logic how are calculating and combining the VATs which we cannot completely match in Hemi and please escalate such cases to the support team if any.
Manage Custom Fields
Big Commerce custom fields are now manageable though Hemi and we are able to create, update and delete custom fields directly on BigCommerce. In order to do all this we will store each custom field as Item Specific in Hemi. Please have in mind that Item Specific > Brand is not part of the custom fields but every other Item Specific will be added as a custom field on the product. In order to track which custom field need to be created, updated or deleted we will also transfer them for reference in Item Account Big Commerce where you will be able to see the current custom fields on the product. If we have decided to add a new one we simply add it as an Item Specific and we will add it as custom field on BigCommerce and in Item Account Big Commerce. If you remove any of the Item Specifics which are already added as custom fields we will delete the custom field from BigCommerce and from Item Account Big Commerce.
MultiStore Products
Every Big Commerce account can be set as multistore directly from Account Big Commerce and we can have: Single Store - When we have single BC store we are following our standard logic and once the product is updated on BC there are no additional steps.
Multi Store - Some merchants want to sell their products in different places and manage all of this on BigCommerce. They may want to maintain multiple website-based eCommerce storefronts, or sell products from their store's catalog on other channels, such as Amazon, eBay, in-person POS (point-of-sale) systems, and so on.
This is all managed through the so called multi-store section in BC. This means that a merchant using BC can split off each of these channels in separate “channel” (similar to how we split each channel in a separate account). Those “channels” do not require any other specific information. It just helps streamline data in BC, which means we will NOT need separate accounts in Hemi for each channel.
We will automatically get all channel from Big Commerce which then you can assigned either on the Account as a default value or for each product individually. As an overlayer we are introducing additional field Product Account Big Commerce > Channels which will be picked with priority against Account Big Commerce > Channels The Channel Assignment should pick all products with status Product Account > Product Status = Product Created.