Connect Shopify B2B Companies to your business systems
Enable this ShopifyConnector Extension to capture and sync Shopify’s B2B structure: companies, contacts, locations, and role assignments.
Why enable this extension in your Shopify Connector?
In B2B, success isn’t just orders, it’s knowing who buys, for which company, from which location, and with what role/permissions. Companies events help you:
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
CRM & B2B sales ops (account onboarding and hierarchy)
Systems:HubSpot, Salesforce, Dynamics, Pipedrive.
Why: Auto-create/update Accounts, Contacts, and location relationships
Example:
When a company is created (event sc.companies/create), the CRM creates an Account with name, external_id, and timestamps, and links the main contact via main_contact_admin_graphql_api_id.
ERP / Billing / Tax (Locations, Exemptions, Tax IDs)
Systems:ERP, Invoicing, Tax Engines.
Why: B2B billing depends on location, billing address, tax registration, and exemptions.
Example:
On sc.company_locations/create / sc.company_locations/update, you can sync:
billing_address, tax_settings and tax_registration_id / tax_id, tax_exemptions
Access Control & Approvals (roles per location)
Systems: Internal IAM, B2B portals, Approval workflows.
Why: Not every contact has the same permissions.
Example:
When a role is assigned (event sc.company_contact_roles/assign), you can trigger permission workflows using company_contact_role.name (e.g., “Location Admin”).
BI / Data warehouse (true B2B segmentation)
Systems: BigQuery, Snowflake, Looker/Power BI, Segment.
Why: Reporting by company/location/contact structure.
Example:
Use stable identifiers like external_id and admin_graphql_api_id plus timestamps (created_at, updated_at) to unify entities across tools.
Connect Shopify with your system
FAQ
Is this only for Shopify B2B?
Yes—this extension is designed around Companies, contacts, locations, and roles.
Can we sync billing addresses and tax settings per location?
Yes—CompanyLocation payloads include billing and tax-related fields.
How do we prevent duplicates in CRM/ERP?
Use stable identifiers like external_id and/or admin_graphql_api_id.
Is this only for Shopify B2B?
Yes, this extension is designed around Companies, contacts, locations, and roles.
Can we sync billing addresses and tax settings per location?
Yes. CompanyLocation payloads include billing and tax-related fields.
Real-world business use cases
Which events does this ShopifyConnector Extension enable?
- Company
- sc.companies/create
- sc.companies/update
- sc.companies/delete
- CompanyContact
- sc.company_contacts/create
- sc.company_contacts/update
- sc.company_contacts/delete
- CompanyLocation
- sc.company_locations/create
- sc.company_locations/update
- sc.company_locations/delete
- Company contact roles
- sc.company_contact_roles/assign
- sc.company_contact_roles/revoke
What attributes can you sync?
- A) Company
- Common fields:
name,noteexternal_idmain_contact_admin_graphql_api_idcreated_at,updated_at,customer_sinceadmin_graphql_api_id
- B) CompanyContact
- Common fields:
customer_admin_graphql_api_idtitle,localecreated_at,updated_atadmin_graphql_api_idembedded company object
- C) CompanyLocation
- Common fields:
- Identity:
name,external_id,phone,locale,note - IDs/time:
created_at,updated_at,admin_graphql_api_id - Tax:
tax_exemptions,tax_settings.tax_registration_id,tax_settings.tax_exempt,tax_settings.tax_exemptions - Relationships:
embedded company - Billing/tax id:
billing_address,tax_registration.tax_id
- D) Role assignment payload
- Common fields:
company_contactcompany_locationcompany_contact_role.name
Tell us your systems.