minipim started life as a catalog automation tool for BigCommerce merchants, and BigCommerce is still its deepest connector. It imports almost everything about your store’s catalog into a typed, schema-backed PIM — then keeps BigCommerce updated as you edit.

What the connector imports

A Pull brings across:

  • Products — name, URL slug, visibility, description (converted to Markdown, with embedded images copied into minipim), SEO page title and meta description, and the featured flag as a tag.
  • Pricing — price, retail, sale and cost price, on the product and on any variant that differs.
  • Dimensions — weight, height, width and depth.
  • Variants — SKUs, plus UPC, MPN and GTIN identifiers.
  • Options — each BigCommerce option becomes a select attribute on the variant, so variant axes are structured data.
  • Modifiers — including their price adjusters.
  • Custom fields — discovered automatically and turned into typed attributes.
  • Categories (with their tree) and brands.
  • Images — copied into minipim’s own storage; the BigCommerce thumbnail becomes the product’s hero image. Variant images come across too.
  • Web pages and blog posts — body, SEO fields, author, publish date and tags, with blog thumbnails as hero images. Turn on content pages in your minipim settings to include them.

What it pushes back

Every product that came from BigCommerce stays linked to its BigCommerce product. When you change one in minipim, the connector pushes the update automatically, and there’s a Push button for a full resync.

Push updates the product’s name, visibility, description (back to HTML), SEO title and meta description, prices, dimensions and brand, plus each variant’s SKU, price, cost price and weight. It doesn’t create new products in BigCommerce, and categories, images, custom fields, modifiers and identifiers stay pull-only.

Inbound webhooks

Optionally, minipim can listen to BigCommerce. Open the connector’s Webhooks section and click Enable, and minipim subscribes to BigCommerce’s product created, updated and deleted events: a change in BigCommerce refreshes that one product in minipim, and a deletion archives it rather than removing it.

Setup

  1. In BigCommerce, go to Settings → API → API accounts and create a V3 API token with:
    • Products: modify (read-only is enough if you’ll only pull)
    • Content: read-only, to import web pages and blog posts
    • Channel Settings: read-only — optional, used for storefront names
  2. In minipim, open Connectors, find BigCommerce under Available, and click Install.
  3. Enter a Name, your Store hash (it’s in your BigCommerce admin URL: store-abc123.mybigcommerce.com) and the Access token. minipim checks the credentials when you click Install.
  4. Click Pull to import your catalog. The connector also creates a BigCommerce channel whose required attributes drive readiness scoring — edit them under Channels.

Know before you connect

  • A full pull replaces what it imported. Each pull re-creates the products this connector owns from BigCommerce’s current data, so values typed into minipim on those products are overwritten. Edit in minipim and let push carry changes to BigCommerce, rather than editing both.
  • Seeded attributes. Pulls create a set of optional attributes (price, retail, sale and cost price, dimensions and so on) on every run, so deleting them doesn’t stick.
  • Multi-storefront. BigCommerce’s multichannel features — per-channel pricing and price lists — aren’t imported yet.
  • No content scope, no pages. Without the Content scope, the sync still succeeds but imports no pages.
  • Units. Prices import as USD; dimensions as pounds and inches.
  • Reconnecting. Uninstalling the connector keeps your products but forgets which BigCommerce product each came from, so reconnecting the same store imports them again as new products.

Want to keep a custom storefront in sync too? The REST API and webhooks read from the same catalog.