Traitement WooCommerce pour les commandes ecommerce canadiennes
La connexion utilise l’API REST WooCommerce. La mise en place exige identifiants API et boutique HTTPS accessible. Commandes et mises à jour sont testées avant le traitement réel.
The connector, and its version
- API
- WooCommerce REST API
- Version
wc/v3
La connexion utilise l’API REST WooCommerce. Autorisations, sécurité et extensions sont examinées avant les commandes réelles.
3 credentials, and where each one lives
You create these in your own admin and paste them into ours. They are stored encrypted and masked after saving, and you can revoke them without involving us.
Consumer key
Où WooCommerce → Settings → Advanced → REST API. Create a key with Read/Write permission.
Why Read/Write because orders come in and fulfilments go back. Read alone would leave your store showing every order as unshipped.
Consumer secret
Où Shown once, alongside the key, when you create it.
Why Paired with the key to sign API requests. Stored encrypted and masked in the admin after saving.
Webhook secret
Où WooCommerce → Settings → Advanced → Webhooks, on the webhook you point at us.
Why Every inbound delivery is verified against it. WooCommerce webhooks are ordinary HTTP POSTs to a URL anybody could guess, so the signature is the only thing separating a real order from an invented one.
The events we handle, and what each one does
Webhooks, so a change on your store reaches the floor when it happens rather than at the next poll. Anything a webhook misses is caught by the reconciliation below.
| Événement | What it means here |
|---|---|
order.created |
A new order to fulfil. |
order.updated |
Anything changed on the order. |
order.deleted |
Treated as a cancellation: pulled from the pick queue. |
Every delivery is verified
HMAC-SHA256 over the raw body, base64-encoded. WooCommerce's own scheme, which differs from Shopify's hex encoding.
The signature arrives on
X-WC-Webhook-Signature.
A webhook endpoint is a public URL. The signature is the only thing separating a real order from an invented one, so a delivery that fails the check is refused rather than queued.
Your store stays the record
-
Fulfilment
Tracking and status written back to the WooCommerce order, so the store is the record and your existing order emails keep working.
-
Cancellation
An order we cannot ship is marked, rather than sitting in processing indefinitely.
Les commandes peuvent être importées depuis une date pour démarrage ou rapprochement. Convenez des dates et commandes ouvertes pour éviter de dupliquer le travail.
What people ask before connecting
Do I have to install a plugin?
La connexion utilise l’API REST, sans exiger d’extension Ecom pour la boutique. Accès, autorisations et flux de commandes restent à tester.
Which WooCommerce versions work?
Le connecteur utilise l’API REST wc/v3. Indiquez version WooCommerce et extensions de commandes pour confirmer points d’accès et autorisations.
My store is not on WordPress.com, does that matter?
No, and self-hosted is the commoner case. What matters is that your store is reachable over HTTPS and that REST API keys can be created, which is standard on self-hosted WooCommerce.
What if a webhook does not arrive?
L’importateur peut rapprocher les commandes par API et recevoir des webhooks. Si une commande manque, donnez sa référence boutique pour vérifier connexion et importation.
The rest of the stack
Prêt à faire avancer vos commandes plus rapidement?
Dites-nous ce que vous expédiez et en quelle quantité, et un spécialiste vous répond en un jour ouvrable.