A read-only REST key is the whole integration — no plugin, no theme edit, nothing new running on your WordPress. The bot reads real orders, recommends from products you actually stock, and links shoppers into your cart or checkout with the item in it.
WooCommerce → Settings → Advanced → REST API → Add key. Read permission is enough for everything here — we never need write access to your store.
In Tendabot: Settings → Store. We check the credentials against your store before saving, so a typo fails immediately instead of quietly at 2am.
One click pulls published products with prices, images, categories and stock status. We also read your cart and checkout page URLs at this point, because those slugs are yours to rename.
A WooCommerce cart is a session on your own site, belonging to the shopper’s browser. Nothing on our servers can reach into it — so we do not pretend to. Instead the buttons use WooCommerce’s own add-to-cart query parameter, the one core has handled on every page load for years.
Because that handler runs wherever the shopper lands, appending it to your cart or checkout page adds the item and arrives in one hop. Everything happens on your site, under your theme, through your checkout and your payment gateways.
The visitor also has to confirm the email used at checkout, the phone number on the order, or the delivery postcode — any one of the three. So nobody can walk order numbers to read other people's addresses.
That rule lives in our code and is checked before your store is ever queried. It is not an instruction in a prompt that a determined visitor can talk the AI out of.
Worth knowing before you connect, not after.
No. A read-only REST API key is the entire integration. Nothing new runs on your WordPress, which also means nothing new to keep updated or patched.
Never. Every button opens your own site. We do not see card details, we do not process payments, and we hold no payment credentials. The only thing we generate is a URL your store already knows how to honour.
No. We read the real page URLs from your store when you connect, so custom slugs work. If a configured page ever pointed off your own domain we ignore it and fall back to your store — a shopper should never be sent off-site mid-purchase.
It only needs Read permission, so it cannot change anything in your store. It is encrypted at rest, never shown back to you in full, and you can revoke it from WooCommerce at any time without touching Tendabot.