Skip to content

Connect WooCommerce

The WooCommerce tool connects your KonversAI assistant to your WooCommerce store. You add the tool on the Assistant tools screen in the KonversAI console. Select Settings in the left sidebar, then select AI tools. With only your store address, the assistant searches your product catalog and fetches the full description of one product. With a read-only API key, it also lists a customer’s five most recent orders and reports whether an order has been dispatched. The same key fills in the contact card in the KonversAI console with the customer’s recent orders. Order answers need a verified email address from the customer. Product answers do not. The tool only reads from your store. It never changes an order, a refund or your stock.

A team member with the View tools permission opens the Assistant tools screen in the KonversAI console. A team member with the Modify tools permission adds, edits, validates and deletes the tool. A Tenant Admin holds both permissions, always. Without View tools, the item AI tools does not appear under Settings in the left sidebar. Ask a Tenant Admin to grant Modify tools on the User permissions screen. In WordPress you need an account that can change Permalinks and create a REST API key.

Check three things on your store.

  • HTTPS. The store address must start with https://. KonversAI refuses a store on plain http:// when you test the connection.
  • Permalinks. In WordPress, open Settings > Permalinks and choose anything except Plain. With Plain, WooCommerce has no REST API routes, and the connection check says the route was not found.
  • Published products. The assistant only finds products that are published and visible in your catalog.

For product questions only, you need nothing else. For order and dispatch questions and for contact cards, create a read-only API key in the first part of the steps below.

Sign in to the KonversAI console and select your tenant. See Give the assistant a tool for the fields every tool shares, such as Display name and Slug.

Skip this part when you only want product questions answered.

  1. In WooCommerce: Select WooCommerce > Settings > Advanced > REST API, then select Add key.
  2. Type a Description you will recognise later, for example KonversAI.
  3. Choose a User with administrator rights.
  4. Set Permissions to Read. The tool never writes to your store.
  5. Select Generate API key.
  6. Copy the Consumer key, which starts with ck_, and the Consumer secret, which starts with cs_. WooCommerce shows the secret once.

The key needs Read access to orders, products and customers. A key that lacks one of them still saves, with a warning, and the assistant does less. See the FAQ below.

Add the WooCommerce tool in the KonversAI console

Section titled “Add the WooCommerce tool in the KonversAI console”
  1. In KonversAI: Select Settings in the left sidebar, then select AI tools.
  2. Select + Add tool.
  3. Select WooCommerce in Tool type. You cannot change the type later.
  4. Type a label in Display name, for example WooCommerce. KonversAI fills Slug while you type.
  5. Type your instruction in Usage guidance for the AI assistant, for example Use this for product questions, and for order and dispatch questions once the customer’s email is verified.
  6. Keep the Enabled checkbox selected.
  7. In the Connection card, type your address in Store URL, for example https://shop.example.com. A store in a subfolder, such as https://example.com/shop, works too.
  8. To use order and dispatch lookups, select Add secret on Consumer Key. In the Add secret window, paste the key into Secret value, then select Apply. Do the same for Consumer Secret. Fill in both or neither. KonversAI refuses a test with only one of them.
  9. Select Test connection. On a new tool, KonversAI saves the tool first, then opens it with the heading Edit tool. A success banner starts with WooCommerce settings are valid. and names your store, its WooCommerce version, its currency and which search engine the assistant uses. With a key, it also lists what the key can read: orders, products and customers.
  10. Read any warning under the banner. A warning still lets you continue, but the assistant does less until you fix it.
  11. After a successful test, check the remaining settings:
    • Use the public Store API for product search — on. Leave it on. Product search then uses the public product feed of your store, which shows stock and prices the way your shop front does. Turn it off only when a security plugin blocks that feed and you added a key.
    • Send credentials as query parameters — off. Turn it on only when the test tells you the host strips the Authorization header. It writes your key into the access logs of your store.
    • High-Performance Order Storage — on. Turn it off only when your store still uses the older order storage. It only decides where the order links on contact cards open. The test warns you when the setting does not match your store.
    • Catalog language — leave it unset unless your product titles are all in one language. Then pick that language. The assistant writes every product search in it, whatever language the customer writes in.
  12. Select Save changes.

What can the assistant do once WooCommerce is connected?

Section titled “What can the assistant do once WooCommerce is connected?”

The WooCommerce tool gives your assistant four abilities. It searches your product catalog and shows up to eight products, with the title, price and a link. It fetches the full description of one product, by its handle or by the URL of the product page the customer is on. It lists the customer’s five most recent orders. It reports whether one order has been dispatched. The two order abilities need a verified email address and an API key. The two product abilities need neither.

Not for products. With only Store URL, the assistant searches products and fetches product details. Without a key, the order abilities answer that order lookups are not set up, and the assistant offers to pass the question on. Contact cards need the key too. Add the Consumer Key and Consumer Secret later to switch on orders.

Only orders whose billing email matches the email the customer verified in the conversation. KonversAI checks the billing email of every order itself before the assistant sees it, so an order billed to another address is never shown, even when your store’s search found it. The assistant sees the order number, the status, whether the order is dispatched, what was ordered with size or colour choices, the price of each line, the total and the destination city. It does not see the street address, the customer’s name or the phone number. A customer who checked out with another email must verify that email first.

Section titled “Can the assistant give a tracking link or say an order was delivered?”

No. WooCommerce itself keeps no tracking number and no delivery date. Tracking sits in shipment plugins, and KonversAI does not read them. The assistant says whether the order has been dispatched, which means the status Completed, and offers to pass the question on. A Processing order is paid and being prepared. The assistant never calls it unpaid.

Why does product search miss products that are in my store?

Section titled “Why does product search miss products that are in my store?”

WooCommerce search matches words, not meaning, and it does not rank by relevance. Every word the assistant searches must appear in a product title or description. The assistant starts with one short, specific word and retries once with a shorter form when nothing matches. When your product titles are all in one language, set Catalog language, so the assistant searches in that language. When customers still search in ways your store misses, a search plugin on your store helps.

What does the contact card show for WooCommerce?

Section titled “What does the contact card show for WooCommerce?”

The WooCommerce tool fills in the contact card in the KonversAI console when the conversation has an email address, and the tool has an API key. The card lists the customer’s recent orders with the order number, the status, the products and the total. The status reads Awaiting shipment, Dispatched, Payment pending, Cancelled, Refunded or Partially refunded. The card never says an order was delivered. The name comes from the customer account in WooCommerce, or from the order for a guest checkout. The card can lag a minute behind your store. Select Open order → to open the order in WordPress.

The test says the route was not found. What now?

Section titled “The test says the route was not found. What now?”

WooCommerce is inactive, or your permalinks are set to Plain. In WordPress, open Settings > Permalinks, choose anything except Plain, and select Save Changes. Then select Test connection again.

The test says the key was rejected. What now?

Section titled “The test says the key was rejected. What now?”

Check the Consumer Key and Consumer Secret first. The secret is shown once in WooCommerce. When you did not copy it completely, create a new key. When both are right, your host may strip the Authorization header. The test says so. Turn on Send credentials as query parameters, then test again.

The test says the store returned a web page instead of data. What now?

Section titled “The test says the store returned a web page instead of data. What now?”

A security plugin, a firewall or a staging login page blocks requests to the REST API. Allow requests from KonversAI, or remove the staging login, then test again.

The test warns that the key cannot read orders, products or customers. What now?

Section titled “The test warns that the key cannot read orders, products or customers. What now?”

Create the key again with Read permission, as in the steps above. Without orders, the assistant cannot look up orders. Without customers, the contact card lists orders without the customer’s name. Without products, product search still works through the public product feed, unless a plugin blocks that feed too.

Last reviewed . Tell us when a step no longer matches the product.