ConnectWiz + Shopify
Soon — groundwork liveShopify: the groundwork is live, the native sync is next
We publish honest statuses instead of logo walls. Today, Shopify stores work with ConnectWiz through the public API and webhooks, and Shopify customer identities already federate onto contacts. The native two-way sync — in the WooCommerce mold — is in the works.
E-commerce
What it does — precisely
Identities already federate
A Shopify customer maps onto the same ConnectWiz contact as their chats — the groundwork that makes a future sync feel instant is live now.
The API path, today
Your Shopify stack can talk to the public Commerce API (scoped keys) and start flows via secured webhooks — teams run this in production without waiting for the native connector.
The native sync, next
Two-way products and orders with field-level ownership, rehearse mode and a conflicts ledger — the exact WooCommerce mold, applied to Shopify.
Under the hood
Why "Soon" here is engineering, not marketing
A port built for two tenants
The commerce layer is a provider port with a capability contract — every caller asks "can this store match by phone? create orders?" instead of assuming. WooCommerce is one adapter behind it; Shopify is the second seat the chairs were bought for.
Identity is already provider-agnostic
The contact-identity table stores a provider name and external ID by design — a Shopify customer ID federates onto a contact exactly the way a WooCommerce one does today, no schema change needed.
Even the vocabulary is ready
Order statuses pass through as the store’s own words — WooCommerce says "completed", Shopify says "fulfilled" — because the agent is best served by the word the customer sees in their own account.
What "in the works" means
The native connector means: OAuth pairing, catalog import, field-level ownership, rehearse-then-live write-back and the conflicts ledger — the WooCommerce mold, not a lighter imitation of it.
Setup
How it connects
Today: API + webhooks
Wire your Shopify events to a flow webhook trigger and read/write orders through the Commerce API.
Get notified
Leave your email and you’ll hear the day the native connector opens — and not before.
Then: one-click
The native sync will pair like WooCommerce does — approve once, choose ownership, rehearse, go live.
Better together
What it composes with
The API path, today
Scoped commerce keys and HMAC-verified webhook triggers — the developer surface Shopify teams run in production now.
Flows
Shopify events wired to a flow webhook trigger can route, notify and message today — the automation layer doesn’t wait for the connector.
The mold itself
Read the WooCommerce page to see exactly what the native Shopify sync will look like — same contract, different store.
Security & guarantees
The boring guarantees
Scoped keys, not master keys
The API path uses tenant-issued keys with explicit scopes — catalog read, orders read, orders write — revocable individually.
Webhooks proven, not trusted
Inbound triggers verify an HMAC signature over the raw body with per-trigger secrets and replay protection.
The honest fine print
Boundaries, stated
No fake "beta" theater
We don’t sell the native sync before it exists. What works today is stated plainly; the badge does the honest work.
Connected honestly beats connected loudly.
Every integration here is described by what it really does — direction, ownership and limits included.