Follow

Plug Mapping

The system will check the connection and bring in the first few rows of the file to assist in the Product Mapping. This is where you will match up the Vendor’s File Headers to your Cart fields. Or, if you don’t want that information imported into your cart, just leave it as ‘DO NOT MAP’.
 
IMPORTANT NOTE: Use caution when re-mapping fields as it may alter the Plug Options section.

 

Common Field Name(s) Required? Notes
SKU / ITEM# / Manufacturer ID / Product # Yes Must be unique and one product per row
Name / Title / Product Name Yes  
Price / Cost / MSRP / MAP Yes These are really different pricing fields, we need at least one of these to be able to output your pricing for the products
Manufacturer / Brand Recommended This is required for most shopping channels and marketplaces such as Google and Amazon.
Description Recommended If no description, Title/Name can be used as a placeholder.
Inventory Recommended If an actual qty. is not provided, we can translate this to a numerical value of your choice using Field Optimization rules (i.e. In Stock = 99, Out of Stock = 0 or Available, Not Available, etc.)
Image URL / Image Link Recommended Without these, you will have to download the actual image files, and then upload into website and link to the products
Weight Recommended Some carts require it when adding new products (BigCommerce), so a default can be used if not provided. Weight often drives shipping price, so it's an important field.
Category Recommended Nice to have new products coming in already categorized and ready to sell.
UPC Code / Barcode / GTIN Recommended This is required for most shopping channels and marketplaces such as Google and Amazon.
Keywords No  
Options such as Color, Size Recommended Preferred for apparel and other options-type products. 
Parent ID / Style # / Parent # Recommended This is only required for Advanced Options plugs to be able to update inventory on child options products. Preferred for apparel and other options-type products. 
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

0 Comments

Article is closed for comments.
Powered by Zendesk