WooCommerce

Connect your WooCommerce store with a Consumer Key and Consumer Secret. Both credentials are encrypted at rest, Unyo only ever sends read requests, and you can connect several stores across several platforms at once.

Bu sayfa senin dilinizde henüz mevcut değil - İngilizce sürümü gösteriyor.

Connect the store you already run on WordPress. Unyo validates your credentials against your live store, encrypts them at rest, and registers the store against your account - alongside as many other stores as you want to add.

Read this before you connect

WooCommerce support today is a secure connection, not a queryable one. Unyo stores and validates your credentials and keeps your store registered, but the agent tools that read a catalogue, look up an order, or summarise revenue are Shopify-only right now. If what you want is "ask Blake how sales are going", see Shopify - or use the Neural Core route below, which works with WooCommerce today.

What connecting does today

Validates your store for real. Unyo calls your live WooCommerce REST API with the credentials you paste. If they're wrong, you're told immediately - you never get a card that says "connected" over a connection that isn't.
Reads your store name back. Your site title is pulled from your store and shown on the card, so you can tell your stores apart at a glance.
Encrypts both credentials. Consumer Key and Consumer Secret are encrypted before they touch a database row, and the encryptor refuses to store anything it couldn't encrypt.
Registers the store. Your store is keyed by platform and URL, so several stores - WooCommerce, Shopify, PrestaShop, in any combination - coexist on one account.
Only ever reads. Every request Unyo makes to your store is a read. There is no code path in Unyo that writes to a WooCommerce store.

What it does not do yet

Being precise about this is more useful to you than a longer feature list:

Capability	WooCommerce	Shopify
Connect, validate, encrypt, multi-store	✅	✅
Look up an order by number ("where is #1001?")	❌ not yet	✅ (Sam)
Revenue / AOV / refunds summary	❌ not yet	✅ (Blake)
Catalogue with prices and inventory	❌ not yet	✅ (Blake)
Products synced into your Neural Core automatically	❌ not yet	✅

The reason is simple: those tools are implemented against the Shopify Admin API and are wired to Shopify connections only. WooCommerce equivalents aren't built yet. When they are, this page changes.

Why we still ship the connection

Two reasons. Your credentials live in the same encrypted vault as every other connection from day one, so nothing has to be migrated later. And connecting now tells us the store exists - the tooling is the missing half, not the plumbing.

How to connect

You'll need administrator access to your WordPress site.

In WordPress, go to WooCommerce → Settings → Advanced → REST API.
Click Add key.
Give it a description (e.g. Unyo), pick your user, and set Permissions to Read. Unyo never writes to your store, so Read is all it needs - see the permissions table below.
Click Generate API key. WordPress shows you a Consumer Key (ck_…) and a Consumer Secret (cs_…) once. Copy both now - you cannot see the secret again.
In Unyo, open Integrations from the sidebar.
Filter to E-commerce and click Connect on the WooCommerce card.
Paste your store URL, Consumer Key, and Consumer Secret. Both are required for WooCommerce.
Click Connect. Unyo checks the credentials against your live store and shows your store name on success.

Store URL format

Paste it however you like - https://mystore.com, mystore.com, or with a trailing slash. Unyo strips the protocol and trailing slash for you. Your store must be reachable over HTTPS: Unyo sends your credentials over Basic Auth and will only do that on an encrypted connection.

What each permission level means

WooCommerce API keys are different from OAuth: you choose the permission level when you create the key, and Unyo cannot request or narrow it. That makes Read the right answer, and it's a control you hold rather than one we grant ourselves.

Key permission	What Unyo would be able to do	What Unyo actually does
Read ← recommended	Read products and orders	Reads published products and recent orders. Nothing else.
Write	Create and modify store data	Nothing. No write code path exists.
Read/Write	Both	Reads only - the write half sits unused.

Deliberately not requested, and worth noting:

No write access is needed or used. Every call Unyo makes to WooCommerce is a GET. Pick a Read key and Unyo loses nothing.
No customer-data endpoints are called. Unyo reads your products and your recent orders. It does not call your customers endpoint.
No plugin, no app install. Unyo is not a WordPress plugin and executes nothing on your server. It's an outside client making read requests, which means it cannot slow your store down or break your checkout.

Several stores, several platforms, at once

Your connections are keyed by platform and store URL. In practice:

Two WooCommerce stores? Connect both.
WooCommerce plus a Shopify store plus PrestaShop? All three, at the same time.
Each store gets its own card, its own name, and its own Disconnect.

What Unyo does with your data

Both credentials are encrypted at rest, through the same vault as every other credential on the platform. The encryptor is fail-closed: if encryption fails for any reason, it raises an error and refuses to store the value rather than falling back to plaintext.
Your credentials are never logged, never shown in an error message, and never returned to the browser. Failures tell you what went wrong, never with what.
Nothing you connect trains a model. Every model Unyo runs is under a no-training guarantee.
Retention is a live job, not a promise. A daily cron at 03:00 UTC prunes cached data on a fixed schedule.
Deleting your account purges it all. Account deletion removes your store connections along with roughly 80 other tables, atomically.

Get your catalogue into the Neural Core today

This is the route that works with WooCommerce right now, and it's a good one: put your products in your Neural Core, where every agent can read them - not just the commerce agents.

In WordPress, go to Products → All Products → Export.
Export a CSV of your products.
In Unyo, open the Neural Core and import the CSV into Products.

The importer already speaks WooCommerce's export format - it recognises name, regular price, sale price, description and short description and maps them onto your product fields, so you shouldn't need to rename a single column.

Once imported, this works today:

List the products in my Neural Core with their prices, and flag anything without a description.

Using my product catalogue in the Neural Core, write me an Instagram post for the three products with the highest price.

Build me a spreadsheet of my Neural Core products with one tab per price bracket.

Unlike a live sync, an import is a snapshot - re-import when your catalogue changes meaningfully. It also means your agents read what you chose to give them, which some people prefer.

Disconnecting and revoking

In Unyo: open Integrations from the sidebar, find the store's card, and click Disconnect. Your connection row is deleted and any cached store data for that source is purged with it.

Unyo cannot revoke your API key for you - you must delete it yourself

This one matters, so we won't bury it. WooCommerce offers no revocation endpoint, and Unyo does not delete keys from your WordPress site.

Disconnecting in Unyo means Unyo forgets the key. It does not deactivate it in WooCommerce. To finish the job, go to WooCommerce → Settings → Advanced → REST API in WordPress and revoke the key you created for Unyo. Until you do, that key remains valid on your store.

Deleting your Unyo account purges the stored credentials, but the same caveat applies: revoke the key in WordPress yourself.

Troubleshooting

"Invalid Consumer Key or Consumer Secret." Your store returned a 401. Usually one of: the secret was copied with a trailing space; only the key was pasted (WooCommerce needs both); or the key was revoked in WordPress. Generate a fresh key and try again.

"WooCommerce REST API not found. Make sure WooCommerce is installed and permalinks are configured." Your store returned a 404 at /wp-json/wc/v3/. Two usual causes: WooCommerce isn't active, or WordPress permalinks are set to Plain. Go to Settings → Permalinks, choose any option other than Plain (Post name is fine), and save - that alone republishes the REST routes. Then reconnect.

"Could not connect to store (HTTP …)." Unyo reached your server and got an unexpected response. Check that your store is publicly reachable over HTTPS and that a security plugin, firewall, or "hide REST API" setting isn't blocking /wp-json/. Staging sites behind HTTP auth or an IP allow-list will fail here.

The connection worked, but the agent doesn't know my products. Expected - see what it does not do yet. Use the Neural Core import.

FAQ

Can Blake give me a revenue summary from my WooCommerce store?

Not today. Revenue summaries, order lookups, and abandoned-cart reports are built against the Shopify Admin API and only run on a Shopify connection. Asking Blake for WooCommerce revenue won't produce a number from your store. If you want those workflows now, Shopify is the supported path; otherwise the Neural Core import gets your catalogue in front of every agent today.

Should I create a Read key or a Read/Write key?

Read. Unyo only ever sends read requests to WooCommerce - no write code path exists. A Read key gives you a hard, store-side guarantee that Unyo cannot change anything, and costs you no functionality. That guarantee is yours to enforce, not ours to claim.

Can I connect more than one store?

Yes. Connections are keyed by platform and store URL, so several WooCommerce stores can be connected at once, and they coexist with Shopify and PrestaShop connections on the same account. Each store gets its own card and its own Disconnect.

Does disconnecting revoke my API key?

No, and we'd rather say so than let you assume otherwise. Disconnecting deletes Unyo's copy of your credentials and purges cached store data. It does not touch your WordPress site - WooCommerce offers no way for Unyo to revoke a key remotely. Delete the key yourself under WooCommerce → Settings → Advanced → REST API.

Is my store data used to train AI models?

No. Every model Unyo runs operates under a no-training guarantee, and your credentials are encrypted at rest with an encryptor that fails closed rather than ever storing a plaintext value.

Does connecting Unyo slow down or risk my store?

It shouldn't. Unyo is not a WordPress plugin - nothing is installed on your server and no code of ours runs there. Unyo is an outside client making occasional read requests to your REST API, so it cannot affect your checkout or your page speed.