Before you connect WooCommerce
Use the WordPress dashboard for the shop you want to connect. You need permission to manage WooCommerce API keys, and the selected WordPress user needs access to the shop data. Check Settings → Permalinks: the format must be something other than Plain.
Have your shop URL ready, for example https://example.com. For a secondary shop that shares products with a main shop, contact Support before connecting so that product matching is set up correctly. Keep API keys out of ordinary messages, screenshots and correction forms; ask Support for the secure handoff when assistance is needed.
Steps to connect WooCommerce
- In WordPress, open WooCommerce → Settings → Advanced → REST API.
- Choose Add Key or Create an API key. Enter a Description identifying the Optiply connection and select the intended User.
- Choose Permissions for the agreed flows. Read retrieves shop data; Read/Write also permits updates such as the optional stock write-back. Confirm the required scope with Support if you are unsure; WooCommerce uses one permission level for the key, not separate Products and Orders checkboxes.
- Choose Generate API Key. Save the Consumer Key and Consumer Secret securely before leaving: the secret is displayed only once.
- In Optiply, open Settings → Integrations, wait for the lists to load, choose Add a source, search for WooCommerce, select it and choose Next.
- At Connect to system, enter the shop URL, Consumer Key and Consumer Secret when the credentials form is offered. Leave Pull all sell orders? off for completed orders only. Leave Update product stock automatically? off unless you have agreed to stock write-back.
- Check your choices and choose Connect. If the screen shows Contact us instead, use that action to arrange setup with Support. If WooCommerce is missing, contact Support rather than choosing another connector.
- Return to Settings → Integrations and check the linked source and Connected label. Check the imported products and orders separately; linking the source does not confirm every record has arrived.
See the official WooCommerce REST API key instructions for the key-management screen.
Fields in WooCommerce connection setup
| Field or option | Meaning |
|---|---|
| Description, User | Identify the key's purpose and the WordPress user whose access it uses. |
| Permissions | Read, Write or Read/Write access for the key. Write-only access cannot retrieve products and orders. |
| URL | The WordPress site containing your WooCommerce shop, not its administrator login address. |
| Consumer Key, Consumer Secret | The generated REST API credential pair. They are not your WordPress password. |
| Pull all sell orders? | Off imports completed orders only. Enabling it includes other eligible orders; canceled orders are still excluded from new imports. |
| Update product stock automatically? | Controls the optional update of WooCommerce stock from Optiply receipt lines. Leave it off when you do not want stock written back. |
What you see when connecting WooCommerce worked
Optiply lists the linked WooCommerce source as Connected. The selected order and stock options define what you requested; check the actual data before using it for planning.
Limits of connecting WooCommerce
API key creation alone does not connect Optiply. Do not enable the legacy REST API or install a legacy plugin for these steps: this connection uses the WordPress REST API. Secondary-shop product matching and stock write-back need the correct setup, not just a key with broad permissions.
If connecting WooCommerce did not work
For a missing secret, create a replacement key and coordinate replacement before revoking the key used by an existing connection. For a connection error, check the shop URL, key pair, user access and permissions. Wait if Add a source is disabled while lists load.
For 403 Forbidden, ask the shop administrator and Support to identify the firewall or security rule blocking the actual request. Do not assume every request has an Optiply User-Agent, whitelist a guessed value or disable security protection. Share the failing step and error category without credentials or full request URLs.