Native field mapping
This section provides an overview of native field mapping in the Akeneo App for BigCommerce.
Native Fields
A native field refers to a predefined and built-in attribute or data field that is available within the platform's standard functionality. These fields are provided by default and are designed to store specific types of information related to products, orders, customers, and other elements of an e-commerce store.
Native fields in BigCommerce are ready to use without any additional customization or development work. They are integral to the core features and capabilities of the platform, enabling merchants to effectively manage their online stores.
These fields are designed to capture essential information about products, facilitate organization and searchability, enable inventory management, support marketing efforts, and enhance the overall customer experience.
Mapping
Mapping refers to the process of establishing a connection between corresponding data fields in Akeneo and BigCommerce. Mapping is essential to ensure that product data is correctly synchronized between the two platforms. The process involves associating Akeneo attributes with the corresponding BigCommerce fields.
Different types of mapping for BigCommerce native fields
The Akeneo App for BigCommerce allows you to manage your mapping in two different ways:
- Simple mapping - if your data modelization in the PIM is based on the same attributes for all PIM families then you can map one particular data source to match all your products (eg. If you use the "My_short_description" field to fill in your description for all of your products independently on their family, then you will map it using simple mapping.
- Complex mapping - this option allows you to map a BigCommerce target field differently for each product family. Depending on your data modelization strategy, it can be used for each target field or only for one or a few of them.
If you wish to use a complex mapping for one of the BigCommerce target fields, please tick the checkbox ‘Define a specific attribute for each family’ below the drop-down list. Then, click on MANAGE FAMILY MAPPING. An additional family-by-family mapping modal will appear to allow you to map a PIM attribute by family.
Be aware that you can combine both types of mapping depending on your needs. If you wish to use the complex mapping for a specific field, all you need to do is to check the corresponding checkbox and click on ‘MANAGE FAMILY MAPPING’ to access complex mapping for this specific field.
Be careful if you opt for a complex mapping for the Product Name, Default Price, Weight, and Product Type (mandatory): make sure that your mapping is completed for all concerned families before launching your first import in order to avoid unnecessary errors.
You need to click on the SAVE button in the top right corner of the page to save the changes.
Please keep in mind that to avoid any errors during your import, if you decide on the Family to Family mapping for Title, you should complete your mapping for all concerned families before launching your first import.
List of Native fields
Native fields for simple products & product models
| Native fields | Supported by the App | Supported PIM attributes | Limitations |
|---|---|---|---|
| PRODUCT INFORMATION | |||
| BASIC INFORMATION | |||
| Visible on Storefront | Yes | Product status |
• Set to Yes if the Product status is enabled • Set to No if the Product status is disabled |
| Product Name - mandatory field | Yes |
Identifier, Text | 255 characters max |
| Default Price - mandatory field | Yes |
Number, Price | The values cannot be null or negative |
| Weight - mandatory field | Yes |
Measurement, Number | Not mandatory for digital products |
| Product Type - mandatory field | Yes |
Simple select | The values must be as follows in the Akeneo PIM: • physical - value set by default • digital |
| Brand | Yes |
Text, Simple select, Reference entity single link | |
| DESCRIPTION | |||
| Description | Yes |
Text, Text area | |
| IMAGES & VIDEOS | |||
| Images | Yes |
Image, Asset collection | The limitation depends on the media source: • 15 image attributes max • 5 asset collections max The maximum size of the image must be less than 2MB for image attributes and asset collections using a media file, and 8MB for asset collections using a media link. |
| PRODUCT IDENTIFIERS | |||
| SKU | Yes |
Identifier, Text | |
| Manufacturer Part Number (MPN) | Yes |
Identifier, Text, Number | 50 characters max |
| UPC/EAN | Yes |
Identifier, Text | UPC or EAN must be numeric and have a length of 6, 8, 12, or 13 numbers |
| GTIN | Yes |
Identifier, Text | |
| Bin Picking Number (BPN) | Yes |
Identifier, Text, Number | 255 characters max |
| PRICING | |||
| Tax Class | No |
||
| Cost | Yes |
Number, Price | |
| MSRP | Yes |
Number, Price | |
| Sale price | Yes |
Number, Price | |
| Tax Provider Tax Code | No |
||
| Discount type | No |
||
| INVENTORY | |||
| Track inventory | No |
||
| Stock | No |
||
| Low stock | No |
||
| STOREFRONT | |||
| STOREFRONT DETAILS | |||
| Set as a Featured Product on my Storefront | Yes |
Boolean | |
| Search Keywords | Yes |
Simple select, Multi select | |
| Sort Order | Yes |
Number | |
| Template Layout File | No |
||
| Warranty Information | Yes |
Text, Text area | |
| Availability Text | Yes |
Text | 255 characters max |
| Condition | No |
||
| Show condition on storefront | No |
||
| RELATED PRODUCTS | |||
| Automatically show related products on my storefront | No |
Set to Yes by default | |
| FULFILLMENT | |||
| DIMENSIONS & WEIGHT | |||
| Height | Yes |
Measurement, Number | |
| Width | Yes |
Measurement, Number | |
| Depth | Yes |
Measurement, Number | |
| SHIPPING DETAILS | |||
| Fixed Shipping Price | Yes |
Number, Price | |
| Free Shipping | Yes |
Boolean | |
| PURCHASABILITY | |||
| Purchasability | No |
||
| Minimum Purchase Quantity | No |
||
| Maximum Purchase Quantity | No |
||
| GIFT WRAPPING | |||
| Gift Wrapping options | No |
||
| CUSTOMS INFORMATION | |||
| Country of origin | No |
||
| Commodity description | No |
||
| HS codes | No |
||
| SEO & SHARING | |||
| SEARCH ENGINE OPTIMIZATION | |||
| Page Title | Yes |
Text | |
| Product URL | Yes |
Text, Text area | Do not include the domain name in the URL. Example of accepted URL format: /my-bigcommerce-product/ |
| Meta Description | Yes |
Text | |
| OPEN GRAPH SHARING | |||
| Object type | Yes |
Set to Product by default Option codes must be in lower case as follows: album, book, drink, food, game, movie, product, song, tv_show |
|
| Use product name | Yes |
Set to Yes by default | |
| Title | Yes | ||
| Use meta description | Yes |
Set to Yes by default | |
| Description | Yes | ||
| Thumbnail image | Yes |
Set to Yes by default |
Native fields for product variants
| Native fields | Supported by the App | Supported PIM attributes | Limitations |
|---|---|---|---|
| Purchasable | No |
Set to Yes by default | |
| Image | Yes |
Image, Asset collection | The limitation depends on the media source: • 1 image attribute max • 1 asset collection max The maximum size of the image must be less than 2MB for image attributes and asset collections using a media file, and 8MB for asset collections using a media link. |
| SKU - mandatory field | Yes |
Identifier, Text | |
| Default Price | Yes |
Number, Price | The values cannot be null or negative |
| Sale Price | Yes |
Number, Price | |
| MSRP | Yes |
Number, Price | |
| Weight | Yes |
Measurement, Number | |
| Width | Yes |
Measurement, Number | |
| Height | Yes |
Measurement, Number | |
| Depth | Yes |
Measurement, Number | |
| Cost | Yes |
Number, Price | |
| UPC/EAN | Yes |
Identifier, Text | UPC or EAN must be numeric and have a length of 6, 8, 12, or 13 numbers |
| GTIN | Yes |
Identifier, Text | |
| Bin Picking Number (BPN) | Yes |
Identifier, Text, Number | 255 max characters length |
| Manufacturer Part Number (MPN) | Yes |
Identifier, Text, Number | 50 max characters length |