Connect Shopify products to your systems (PIM, ERP, marketplaces, BI, marketing)

Enable this ShopifyConnector Extension to sync your catalog in real time: products, variants, tax-exclusive and tax-inclusive prices, and images.

Shopify states sc.products/update also fires when variants are added, removed, or updated.

Why enable this extension?

Because catalog accuracy drives revenue. When variants, pricing, or imagery drift across systems, you get:

Broken/missing variants (size/color).
Wrong pricing across channels.
Tax display inconsistencies by market.
Incorrect variant imagery.
Unreliable marketplace feeds and ad catalogs.

Keep your CRM/ERP aligned

With account lifecycle changes.

Enforce B2B governance

Locations, billing, tax registration, exemptions, and access roles.

Automate B2B onboarding

With fewer manual steps.

Improve reporting

By company / location / contact, not only by individual customers.

Real-world business use cases

1) Variant-first operations (the sellable unit)

Systems: ERP, PIM, BI, marketplaces. Why: variants are where real commerce happens: identifiers, pricing, attributes, and often inventory. Example: structural variant changes are captured via sc.products/update (Shopify explicitly includes variant add/remove/update behavior).

2) ERP-driven pricing (net vs gross)

Systems: ERP/accounting, pricing engines. Why: many businesses manage net prices internally and need consistent gross representation by market/customer. Example: ERP maintains net per variant; Shopify publishes the selling price; the integration applies tax rules/validation for BI and feeds.

3) Images and visual consistency across channels

Systems: DAM, PIM, marketplaces, marketing stacks. Why: incorrect images reduce conversion and increase returns/support tickets. Example: image updates propagate to feeds and ad catalogs; Shopify supports one image per variant, which matters for modeling.

4) Marketplace feeds and ad catalogs

Systems: feed managers, marketplace integrators. Why: price/variant/image drift causes disapprovals and performance loss. Example: sc.products/update enables incremental feed rebuilds only for impacted variants.

5) Catalog analytics and QA

Systems: BigQuery/Snowflake, Looker/Power BI. Why: you need catalog change history to explain performance shifts after pricing or imagery updates. Example: events feed a catalog “versioning” log for before/after analysis.

Connect Shopify with your system

FAQ

Does sc.products/update include variant changes?

Yes—Shopify explicitly states it fires when variants are added, removed, or updated.

Can I attach images per variant?

Yes, with the constraint of one image per variant.

Why do you highlight the 2-decimal limitation?

Because Shopify enforces 2-decimal precision in key contexts, which impacts ERP-to-Shopify pricing sync.

Real-world business use cases

Which events does this ShopifyConnector Extension enable?

sc.products/create

sc.products/update (includes variant add/remove/update)

sc.products/delete

Tell us your systems.

Connect Shopify products to your systems (PIM, ERP, marketplaces, BI, marketing)

Why enable this extension?

Keep your CRM/ERP aligned

Enforce B2B governance

Automate B2B onboarding

Improve reporting

Real-world business use cases

1) Variant-first operations (the sellable unit)

2) ERP-driven pricing (net vs gross)

3) Images and visual consistency across channels

4) Marketplace feeds and ad catalogs

5) Catalog analytics and QA

Connect Shopify with your system

FAQ

Does sc.products/update include variant changes?

Can I attach images per variant?

Why do you highlight the 2-decimal limitation?

Real-world business use cases

Which events does this ShopifyConnector Extension enable?

We’ll propose the best integration plan.

Connect Shopify with your ERP or business systems