Online Stores
WooCommerce from your own WordPress.
Yes. Connect WooCommerce with a key from your own WordPress admin, with nothing to register on our side, and your catalog and every order, through fulfillment, cancellation, refund and return, flow into your restock plan automatically. Payments stay with your own gateway.
WooCommerce
LiveConnect with a key from your WordPress admin. Your catalog and every order, through fulfillment and refund, flow into your plan automatically.
What to expect before you connect
Availability reviewed October 2, 2026
- Brings in
- Catalog, stock observations, and the order lifecycle.
- Sends back
- Nothing to WooCommerce.
- Update cadence
- Ongoing sync; use its status to see the latest completed pass.
- Before you connect
- A self-hosted WooCommerce store plus a Consumer Key and Secret from WordPress.
- First useful outcome
- Use store demand with inbound supply in one restock plan.
- Important limit
- Payment-gateway settlements, stock write-back, and fulfillment write-back are not included.
From WooCommerce to a first useful plan
This source feeds the same planning cycle: plan, forecast, replenish, monitor, learn. A supported file is also a complete starting route when you are not connecting this source yet.
Source
WooCommerce
Set up
Add Consumer Key + Secret from WordPress
Data direction
In: Catalog, stock observations, and the order lifecycle.
Out: Nothing to WooCommerce.
Keep current
Ongoing sync; use its status to see the latest completed pass.
5. First useful plan
Use store demand with inbound supply in one restock plan.
The problem
WooCommerce holds the store. Purchasing still needs one plan across that store and every other place you sell.
What it does
Connects with a Consumer Key and Secret from your own WordPress admin, then syncs your catalog and every order through fulfillment, cancellation, refund and return. Nothing to register on our side.
What it does not
Skuvelo does not import settlements (your own gateway takes payment) and does not push inventory counts or fulfillments back to WooCommerce.
In your restock plan
WooCommerce orders join the same demand history as every other channel you sell on, so the forecast and the reorder see the whole business, not one storefront. Skuvelo recommends how much to buy and when, and a recommendation becomes a draft purchase order with each deposit and balance dated from the supplier’s payment terms in the cash plan, so you see what the buy does to cash before you place it.
Set it up
- In WordPress, go to Plugins, then Add New, search for Skuvelo Connector, choose Install Now, then Activate.
- In Skuvelo, open Integrations, choose Connect WooCommerce, enter your store address (it must start with https://) and choose Connect via plugin.
- Approve the connection in your WordPress admin. The plugin creates the store key and hands it to Skuvelo server to server, so nothing is copied or pasted, and Skuvelo shows Waiting for WordPress until it arrives.
- Prefer to make the key yourself? Create one under WooCommerce, Settings, Advanced, REST API, paste the store address, Consumer Key and Secret into Skuvelo, and choose Verify and connect WooCommerce.
- Skuvelo checks the key with a read-only request, then syncs your catalog and orders. Each SKU’d product and variation becomes a product in the plan.
Questions before you connect
- Can I give Skuvelo a read-only WooCommerce key?
- Yes, on the manual path: create a Read key under WooCommerce, Settings, Advanced, REST API and paste it in. The plugin path creates a Read/Write key for you. Either way, Skuvelo does not push stock or fulfillments back to your store, and the key is stored encrypted and never shown in your browser.
- Does my store need HTTPS?
- Yes. The store address must start with https://. Plain HTTP stores cannot connect.
- What happens to products without a SKU?
- They are listed as unmatched rather than dropped, so you can add a SKU in WooCommerce and they join the plan on the next sync. Each variation with its own SKU plans as its own product.
- How are refunds and cancellations handled?
- A cancelled order is recorded as cancelled, a fully refunded order as returned, and a partly refunded one as partially returned, so demand reflects what customers kept. Webhooks prompt a refresh, and regular polling with a daily full check means a missed webhook never leaves an order stale.
See the plan before connecting anything.
The sample workspace uses realistic data and makes no external changes.
