ConnectWiz Commerce
One product truth. Five surfaces. Zero copy-paste catalogs.
Your catalog lives once — variants, media, multi-currency prices — and feeds the panel, the AI assistant, the in-chat shop, your shopping feeds and a public API simultaneously. With a WooCommerce sync that’s genuinely two-way and a price model no untrusted caller can touch.
The catalog
Deep enough for real merchandising
Products, services, bundles
SKU, barcode/GTIN, brand, condition, cost and list and sale prices with sale windows, VAT handling, units, weights and dimensions, Google product categories, translations, tags — the whole merchandising vocabulary.
Variants, generated
Size × Color axes expand into variant items with their own price, barcode, image and weight — the cartesian tedium done by the machine.
Media, managed
A per-item media library with a primary image, alt-text translations and ordering — served from CDN storage, sanitized on upload.
Price lists without FX fiction
Prices per currency and country — deliberately without automatic conversion. A price you never set simply doesn’t exist, because an invented exchange-rate price is a refund waiting to happen.
Relations that sell
Bundle components, add-ons, upsells, cross-sells and accessories in one relation model — the "goes well with" answer your AI can actually give.
Bulk in, bulk out
CSV import and export, list filters and a bulk bar — catalog maintenance at spreadsheet speed with database integrity.
Five surfaces
Enter a product once. It’s everywhere conversations happen.
The AI sells from it
Wiz looks up the catalog and orders mid-conversation — availability, variants, "where’s my order" — grounded in the same record the panel edits, never a stale copy.
A shop inside the chat
Visitors browse, order and check their own orders inside the website widget — and the shop appears only when you actually have active, priced items. No empty storefront theater.
Shopping feeds, tokenized
A Google-schema product feed (Meta Commerce Manager reads the same format) plus CSV, served at a secret tokenized URL with caching — your ads and shops stay in sync without an app review in the path.
A public Commerce API
Scoped tenant API keys (catalog read, orders read/write) let your own storefront or mobile app build on the same catalog and order engine — documented, rate-limited, real.
Flows can transact
The commerce node lets automations look up items and place orders as part of a conversation — order-taking that happens where the customer already is.
One door, no price parameter
Widget, flow and API orders all pass through a single order writer that structurally cannot accept a price — name and price snapshot from the catalog at order time. Tampering isn’t rejected; it’s impossible.
WooCommerce & WordPress
Two-way sync with an ownership contract
Most "integrations" are an import button and a prayer. This one is a governed, two-way sync where you decide — per data domain — which system owns the truth.
One-click pairing
The standard WooCommerce authorization flow provisions API keys and webhooks automatically — no key-copying ritual, no webhook checklist.
Deep import, real write-back
Images, category trees, sale prices with windows, GTINs, tags, upsells, variation prices and images flow in; product edits can write back to Woo — both directions, honestly.
Field-level ownership
Per domain, you choose: data lives with Woo, lives here, or syncs both ways. Owned-elsewhere fields render read-only with the reason on screen — no two-masters chaos.
Rehearse before live
Every write-back operation has its own switch with a rehearse mode — see what would change before anything does. Deterministic idempotency keys make retries safe.
Conflicts, on a ledger
Failed or conflicting syncs land in a visible conflicts ledger with resolve-and-retry — never a silent overwrite, never a mystery divergence discovered at inventory time.
The WordPress plugin
Embeds the chat widget and mints signed single-sign-on tokens — a logged-in WooCommerce customer is recognized in the chat without re-registering, orders and all.
Orders, sales & stock
The paper trail, modeled like it really works
Orders on three axes
Document status, fulfilment stage (with carrier and tracking) and source — panel, widget, AI, flow, API or WooCommerce — move independently, because "confirmed", "shipped" and "came from chat" are different facts.
Paid is computed, not checked
Quotes, sales orders, payments and a per-contact receivables ledger — "paid" derives from the ledger, so partial payments and balances are facts, not checkbox fiction.
Stock as a real ledger
Double-entry stock movements across locations — record, count, transfer, consume — and a booking can consume stock, so the service appointment and the parts it used reconcile.
The honest fine print
What Commerce deliberately isn’t
No hosted storefront
We don’t host a public web shop for you — the surfaces are the chat shop, the feeds and the API your own site builds on. A hosted vitrine is a possible later chapter, not a quiet promise.
No in-chat payments
Orders happen in chat; charging cards doesn’t. Payment flows belong to payment providers, and pretending otherwise is how platforms end up half-bank, badly.
Meta catalog: read-only
Your Commerce Manager catalog is read for product pickers in WhatsApp conversations; we deliberately don’t write into Meta’s catalog — the feed URL is the sync path, and it needs no extra Meta review.
No invented numbers
No FX conversion, no auto-generated wholesale tiers, no reservation stock — each refused because a made-up number in commerce becomes a real dispute with a real customer.
Your catalog is already written. Stop rewriting it per surface.
Import from WooCommerce or CSV, and every conversation surface starts selling from the same truth.