BigCommerce product upload, without the option-set mess.

BigCommerce imports are forgiving about some things and unforgiving about others. A variant without a SKU or a modifier mistaken for a variant option can leave you with a store that looks complete in the admin and sells wrongly at checkout. We treat that distinction carefully.

What you get

• Products with names, descriptions, brand, categories, weight and dimensions populated
• Variant options built with their own SKU, price, stock and image per combination
• Modifier options (such as engraving text or gift wrap) set up separately from variants
• Custom fields added for specs and attributes that sit outside the standard fields
• Category assignment, brand matching and page titles
• Images matched to products and variants, with alt text
• Channel assignment for each product across storefronts
• Product weights, dimensions and tax or shipping-related fields filled where your data has them
• Product page SEO fields and clean URLs, with 301 redirects prepared if URLs change
• A QA report listing changes, flags and anything we could not resolve

How it works

1. You send source files and an export of a few existing products if the store is not empty.
2. We inspect and send a fixed quote, plus a free 10-product sample if it is a fit.
3. Our AI engine handles mapping and writing at volume. A person reviews every output.
4. We load as non-visible products through the access you set up. You review.
5. You approve, we publish, and you keep the final files.

BigCommerce details we plan around

Variants versus modifiers

Variant options change what you stock: size and colour each create a purchasable variant with its own SKU and inventory. Modifier options add choices that do not create inventory, such as a text field or a checkbox for an add-on. Putting a stocked attribute into a modifier means you cannot track its stock properly, so we sort each attribute into the right bucket before loading.

Option sets and legacy structures

Older BigCommerce stores, and many migrated ones, were built around option sets and rules. Newer stores define options directly on each product. We check which model your store uses and shape the data to match, instead of mixing the two.

Custom fields

Custom fields are simple name and value pairs shown on the product page. They are useful for specs, but they are not filterable the way categories and brands can be. We use them for display-only details and keep the naming consistent so the product page reads cleanly.

Channels and multi-storefront

With multi-storefront, products live in one catalog and are assigned to channels. A product missing from the right channel will not appear there, even though it exists. We include channel assignment in the import plan and check it afterwards, so a wholesale storefront is not accidentally empty.

Variant limits

BigCommerce caps how many variants a single product can hold. If a source product has an enormous combination matrix, we propose splitting it into separate products or reducing options, and agree that with you before building.

Updating existing products

If your store already has products, we match on SKU, change only the fields you name and keep a before and after file. The control panel importer can add and update but a careless file can overwrite good data, so we export your current catalog first as a safety copy. For regular refreshes, such as seasonal price changes, ask about Monthly Catalog Ops.

Pricing

Starting prices for catalog listing, per project. The fixed quote follows once we have seen your files. See /pricing.

Is this a fit?

It suits BigCommerce stores adding a large range, opening a second storefront, or cleaning up a catalog where variants and modifiers have been mixed together. It also suits merchants who have hit importer errors they cannot decode.

If you have a small catalog and a clean file from the BigCommerce template, import it yourself; the BigCommerce bulk import guide shows the format. If you are considering leaving the platform, see BigCommerce to Shopify migration. For custom app integrations or ERP syncs, you will need a developer.

Request the free 10-product sample, or ask for a fixed quote. More on the wider service: bulk product upload.