BigCommerce PIM: Setup, Field Mapping, Free Plan
A BigCommerce PIM keeps product data in one place and sends finished products to your store. LynkPIM connects with a store-level API account and creates and updates approved products and variants through the Catalog API, with GTINs, images, categories and SEO fields, and reads changes back. The first 25 products are free.
- Connection
- API key from your account
- Direction
- Both ways
Objects
BigCommerce to LynkPIM with Read changes, without overwriting existing values
What LynkPIM sends
- Name, description, SKU, price, weight, brand, GTIN and MPN
- Variants with their option values, each with its own SKU, price, GTIN and image
- Images, mapped categories, page title, meta description and custom URL
Direction and data
- LynkPIM to BigCommerce for approved products, matched by SKU
- BigCommerce to LynkPIM with Read changes, without overwriting existing values
Connect in 3 steps
No developer needed. You need access to your BigCommerce account.
- 1
In the BigCommerce control panel, go to Settings > API > Store-level API accounts and create an API account
- 2
Set Products to modify (and Information & settings to read-only), save, and copy the access token; the API path shown contains your store hash
- 3
In LynkPIM, open Integrations, choose BigCommerce and enter the store hash and access token
How it behaves
Mapping
- Variant options become BigCommerce product options
- The custom URL comes from the SEO slug for the channel or language
- LynkPIM categories are mapped per channel to BigCommerce category ids
When it runs
- Push all approved products or a selection
- Scheduled channel publication sends due products automatically
When something fails
- Failed products are listed per run with BigCommerce's message
- A product deleted in BigCommerce is created again on the next push
- Rate limits are waited out and retried automatically
How LynkPIM fields map to BigCommerce
LynkPIM writes to the BigCommerce Catalog API (v3) with the access token of a store-level API account. It looks up each product by SKU before creating it, so connecting a store that already has products updates them instead of adding copies. Content and prices come from LynkPIM; inventory and orders stay in BigCommerce.
| In LynkPIM | In BigCommerce | Notes |
|---|---|---|
| SKU | SKU | Used to find existing products |
| Product name | Name | |
| Description | Description | Text written for the channel or language wins over the default |
| Price | Price | Sent as 0 when the product has no price, so set prices first |
| Weight attribute | Weight | BigCommerce requires it for physical products; 0 when empty |
| Brand | Brand | |
| GTIN and MPN | GTIN and MPN | Each variant also carries its own GTIN |
| SEO title | Page title | |
| Meta description | Meta description | |
| SEO slug | Custom URL | Written as /your-slug/ |
| Categories | Categories | Mapped per channel to BigCommerce category ids |
| Images | Product images | The first image is the thumbnail |
| Variant options | Product options and option values | Created with the variants |
| Variants | Variants | Each with its own SKU, price, GTIN and image |
| Approved status | Visible | |
| Inventory, custom fields | Not sent | They stay in BigCommerce |
Before and after: a drill sold in two voltages
Before: the drill's GTINs and MPNs sit in a supplier spreadsheet, the BigCommerce product has a GTIN on only one of its two variants, the weight is missing so shipping rates fall back to defaults, and the Google Shopping feed is edited separately.
After: the drill is one record in LynkPIM with two variants. Completeness rules check that each variant has a GTIN and the product has a weight and brand before it can be approved. On approval, LynkPIM creates or updates the BigCommerce product with both variants, their GTINs and images, and the same record feeds Google Merchant Center.
Variants and product options
On the first push, LynkPIM creates the product together with its variants. BigCommerce builds the product options and their values from the option names and labels, for example Size: M and Colour: Navy. Variants without a SKU are skipped, because the SKU is how LynkPIM finds them again.
On later pushes, LynkPIM updates each known variant's SKU, price, GTIN and image one by one and adds the variants that are new. It does not rename or remove option values on existing variants; change those in BigCommerce if you need to. Products are created as physical products.
What LynkPIM reads back from BigCommerce
Read changes pages through your catalog 250 products at a time, optionally only those modified since a date. It reads the SKU, name, description, visibility and price. Products that exist only in BigCommerce are created in LynkPIM, and existing products only get empty fields filled. Brands, variants, images and categories are not read back, and BigCommerce webhooks are not used.
What it costs at 100, 1,000 and 5,000 products
The first 25 products are free. Above that, your whole catalog is billed at the per-product rate of the band it falls in, and the rate drops as the catalog grows. The BigCommerce connector is included at every size. Prices in US dollars:
| Products | Billed monthly | Billed yearly (per month) |
|---|---|---|
| 25 | Free | Free |
| 100 | $80.00 | $67.00 |
| 1,000 | $460.00 | $390.00 |
| 5,000 | $850.00 | $700.00 |
When the BigCommerce control panel is enough, and when a PIM pays off
One BigCommerce store with a catalog your team can keep up with in the control panel, plus the built-in CSV import and export for bulk changes, does not need a PIM. A PIM starts to pay off when:
- The same products also go to Google Shopping, Amazon or other marketplaces, each with its own required fields.
- Several people or suppliers contribute product data and you want a review and approval step before it goes live.
- You need GTINs, MPNs, weights and images checked for completeness before a product reaches any channel.
LynkPIM compared with the usual BigCommerce options
| Option | Works well for | Keep in mind |
|---|---|---|
| The BigCommerce control panel | One storefront and a small team | Data for marketplaces and other channels is kept separately |
| CSV import and export | Bulk changes and migrations | Variant rows and option columns take care to get right |
| PIM apps from the BigCommerce App Marketplace | Teams that want an app installed in the store | Compare which fields each app syncs and how it is priced |
| Akeneo, Pimcore and similar PIMs | Large catalogs and teams with developer capacity | Connecting BigCommerce usually takes a connector app or integration work |
| LynkPIM | Small and mid-sized catalogs going to several channels | Physical products only; inventory and custom fields stay in BigCommerce |
Questions about this integration
Where do I find the store hash?
It is the code after /stores/ in your API path, for example abc123.
Does LynkPIM change my BigCommerce stock?
No. LynkPIM sends product content and prices; inventory stays with your store.
Does LynkPIM need a weight for every product?
BigCommerce requires a weight for physical products. LynkPIM sends the value of your weight attribute when a product has one and 0 otherwise, so add weights in LynkPIM if your shipping rates depend on them.
Can I add variants later?
Yes. New variants are added to the existing product with their option values, and known variants get their SKU, price, GTIN and image updated. Option values of existing variants are not changed.
Is a pushed product visible in my store straight away?
Approved products are sent as visible. Keep a product unapproved in LynkPIM until it is ready.
Are images uploaded again on every push?
No. Images are sent as links BigCommerce downloads, when a product is created and when its images change in LynkPIM. The first image becomes the thumbnail.
Plan the rest of your setup
Related integrations
All integrationsConnect BigCommerce to LynkPIM
Start free and connect it from Integrations in the app, or book a demo and set it up with us.
