Description
Zellio for WooCommerce connects your WooCommerce store to the Zellio platform. You need a Zellio account to use it.
Once connected, Zellio can:
- Sync orders in real time via webhooks
- Sync products and inventory with bidirectional stock updates
- Sync customers for unified customer profiles
- Power AI support agents with your real store data
- Let support agents view orders, process refunds, and manage customers
- Connect to Zellio ERP for inventory and operations management
How It Works
Connecting starts in Zellio, not in WordPress. Zellio authorizes the connection first, then hands this plugin a short-lived code that proves the authorization.
- Install and activate this plugin.
- In Zellio, open Integrations → WooCommerce and start connecting your store.
- Zellio shows you a connection code. Copy it. (If Zellio already knows your store address it can link you straight into this plugin with the code filled in.)
- In WordPress, go to WooCommerce → Zellio, paste the code, and click Connect.
- The plugin creates a WooCommerce REST API key, exchanges it with Zellio server-to-server, and sends you back to Zellio to finish.
The connection code is valid for 10 minutes and works once. If it expires or fails, generate a new one in Zellio — the same code never works twice.
The Zellio user who generated the code must be the one who finishes the connection. Another administrator in the same workspace cannot complete it.
Webhooks are registered and maintained by Zellio using the credentials you hand over. This plugin never creates webhooks of its own. It does remove the Zellio webhooks from your store when the connection ends (see “What happens when I disconnect?”).
Before it creates a key, the plugin checks that the store can work with Zellio: pretty permalinks must be on (Plain permalinks hide the WooCommerce REST API), and your server must pass the Authorization header through to WordPress. If either fails, you are told what to change and your connection code stays valid.
After you connect, WooCommerce → Zellio AI shows a connection health block (API key, webhooks, abandoned-cart table, permalinks, Authorization header, store address, last check) and a Check connection button. The same facts, with no secrets, appear in WooCommerce → Status.
Requirements
- WordPress 6.5 or later
- WooCommerce 7.0 or later
- PHP 7.4 or later
- A publicly reachable store URL over HTTPS — Zellio must be able to call your store back
External services
This plugin is the store side of the Zellio platform (zellio.ai), a hosted customer support and ERP service run by Zellio. It sends data to Zellio only after you connect your store with a code from your Zellio account. Before that, it sends nothing.
Once connected, the plugin contacts Zellio (app.zellio.ai, and ops.zellio.ai for Zellio ERP) to:
- Exchange WooCommerce API credentials during the connection process
- Ask the platform whether it still has this store connected (a signed request that carries only the store address), once a day and when you open the Zellio screen
- Notify the platform when you disconnect or delete the plugin (a signed request with the store address and the reason)
- Tell the platform when the store address changes (a signed request with the old and new address)
- Send abandoned-cart snapshots: the cart contents and totals, and any email address, phone number, name or address the shopper already typed at checkout, plus campaign link identifiers from Zellio campaign links
- Send a marketing opt-in record, only when you turn the opt-in on (Zellio screen) and a customer says yes: the channels they agreed to (email, WhatsApp) and the time, on the order and on the customer. An empty box sends nothing
- Report store facts when Zellio asks for them with a signed request to your store: plugin, WordPress, WooCommerce and PHP versions, whether HPOS is on, payment gateways that can refund, order statuses, and connection health. No keys, secrets or customer data are included
Zellio can also turn some plugin features off from its side, with a signed request: abandoned-cart snapshots, campaign link tracking, and the checkout email and phone refresh. This is only data (on or off). The plugin never downloads or runs code from Zellio. If Zellio turns a feature off, WooCommerce → Zellio AI shows it in the connection health block.
The plugin sets two cookies: zellio_wc_cart_id (a random value that lets the store find the right cart snapshot) and, for visitors who arrive from a Zellio campaign link, zellio_wc_click_<site number> (the campaign link identifier, 7 days). It adds suggested text for your privacy policy, registers a personal-data exporter and eraser for the cart snapshots (Tools → Export / Erase Personal Data), and deletes snapshots with no activity for 60 days. Change the 60 days with the zellio_wc_cart_retention_days filter (minimum 7).
Data is transmitted over HTTPS. Your WooCommerce API credentials are sent server-to-server and never appear in a browser URL.
Installation
- In WordPress admin, go to Plugins → Add New Plugin and search for “Zellio for WooCommerce”.
- Click Install Now, then Activate. WooCommerce must be installed and active.
- Go to WooCommerce → Zellio AI to connect your store.
Updates come from WordPress.org, like any other plugin. We recommend you turn on auto-updates for this plugin (the Zellio screen has a button for it), so fixes reach your store without waiting for you.
FAQ
What permissions does the plugin need?
It creates a WooCommerce REST API key with read/write permissions. Zellio needs write access to register its webhooks, process refunds, and update order status on behalf of your support agents.
Where do I get the connection code?
From Zellio. Open Integrations → WooCommerce in your Zellio dashboard and start connecting WooCommerce — Zellio generates the code there.
My code expired. What now?
Generate a new one in Zellio. Codes last 10 minutes and can only be used once, including when an attempt fails. Never reuse a code.
Can I connect to both Zellio Support and Zellio ERP?
Yes. Each product gets its own WooCommerce API key, and each can be disconnected independently.
What happens when I disconnect?
The plugin tells Zellio first, so Zellio can remove its own side while the key still works. Then the API key for that product is revoked, the Zellio webhooks are deleted from WooCommerce → Settings → Advanced → Webhooks (whatever their status), and pending abandoned-cart messages are cancelled. Your orders, customers and products are not changed.
Disconnecting from Zellio Support in the Zellio dashboard does the same here. Zellio asks the store to disconnect, and the plugin also checks once a day, so a disconnect that could not reach the store is still applied within a day. If the plugin cannot get a clear answer from Zellio (an error, a timeout, an unexpected reply), it changes nothing. It also changes nothing while a new connection is still being finished in Zellio, or when the store address changed. Zellio ERP is unaffected by that path today.
What happens when I deactivate the plugin?
Deactivating pauses the plugin. The API key, the Zellio webhooks and the connection stay as they are, so activating the plugin again (or updating it) resumes with no reconnect. While the plugin is off, WooCommerce keeps delivering webhooks to Zellio, because the webhooks belong to WooCommerce. To end the connection, press Disconnect first, or delete the plugin.
What happens when I delete (uninstall) the plugin?
Deleting the plugin disconnects the store: Zellio is told, the API keys are revoked, the Zellio webhooks are deleted, and every setting (the marketing opt-in settings too), scheduled job, cached value and the abandoned-cart table are removed. Marketing opt-in records on orders and customer accounts stay, and no order, customer or product data is modified. Use the personal-data eraser to remove a person’s records. On a multisite network this runs for every site.
My store address changed. What do I do?
Open WooCommerce → Zellio AI. A notice shows the address Zellio has and the new one. Click Update address in Zellio. Until you do, Zellio may not recognise orders and customers from the new address. The plugin never treats an address change as a disconnect.
The plugin says permalinks or the Authorization header are a problem.
Zellio calls the WooCommerce REST API with your key in the Authorization header. Go to Settings → Permalinks and choose any structure except Plain. If the header check fails, ask your host to pass the Authorization header to PHP. On Apache, WordPress writes RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}] into the .htaccess file; saving Settings → Permalinks writes it again. Then request a new connection code in Zellio and connect again.
How do I collect marketing consent?
WooCommerce has no marketing consent of its own. Open WooCommerce > Zellio AI > Marketing opt-in. It is off by default. Turn on the checkout checkbox (never ticked for the customer; it shows on the classic checkout and, with WooCommerce 8.9 or newer, on the checkout block) and choose email, WhatsApp or both. Or enter the order meta key another plugin already fills: a value of 1, yes, true or on counts as a yes, and is recorded for email only. If you write your own checkbox text, the plugin adds the channels you chose after it, for example “(email, WhatsApp)”, so the customer sees what they agree to. Only a yes is recorded. An empty box stores nothing and is never treated as a refusal. The record is kept under the zellio_marketing_consent key on the order and on a signed-in customer, and is covered by the personal-data exporter and eraser.
Is my data secure?
Credentials are exchanged server-to-server and never appear in a browser URL or in your history. All traffic uses HTTPS with certificate verification, which cannot be disabled.
Does this work with WooCommerce HPOS?
Yes. The plugin declares compatibility with High-Performance Order Storage and with Cart/Checkout Blocks.
Does this work on WordPress Multisite?
Yes. Each site in a network connects to Zellio independently. Network activation sets up every site (including the abandoned-cart table and the scheduled jobs), a site added later is set up on creation, and deleting the plugin disconnects every site.
Changelog
2.5.0
- Changed: the plugin is now distributed through the WordPress.org plugin directory, and WordPress.org delivers its updates. The Zellio update server, the remote “update now” route and the forced auto-update are removed. Auto-updates are now your choice: the Zellio screen offers a button that turns them on.
- Changed: the text domain is now
zellio-for-woocommerce, to match the WordPress.org slug. - Tested up to WordPress 7.1.
- Changed: translations now come from translate.wordpress.org, so the plugin no longer ships its own .po and .mo files.
- New: Zellio can turn three features off from its side with a signed request (abandoned-cart snapshots, campaign link tracking, the checkout email and phone refresh). Only on or off, never code. The connection health block shows any feature Zellio turned off.
- Changed: the signed status report now reads the available version from WordPress’s own update data, and also says whether auto-updates are on for this plugin.
2.4.0
- New: an optional marketing opt-in. Turn it on under Zellio to show an unticked checkbox on the classic checkout and the checkout block (WooCommerce 8.9+), or name a field your store already fills. Off by default. An empty box saves nothing and is never a refusal.
2.3.0
- New: a clean disconnect. Pressing Disconnect tells Zellio first, with a signed request, then revokes the API key and deletes the Zellio webhooks from WooCommerce (every status). Before, the key was revoked but the webhooks stayed and kept delivering to Zellio until WooCommerce disabled them.
- New: Zellio can disconnect the store from its side through a signed route (
zellio/v1/disconnect). - Changed: deactivating the plugin no longer revokes the key or forgets the connection. Reactivating or updating the plugin resumes with no reconnect. Deleting the plugin disconnects the store.
- New: the connection state is checked with a signed request, once a day and when you open the screen. The plugin only removes a connection when Zellio clearly says it does not know this store, the store address is unchanged (and was confirmed, not guessed) and the connection is not still being finished. Any error or unclear answer changes nothing. A store whose Zellio webhooks are gone is still checked, with the question 2.2.0 asked, but only a connection made or confirmed on 2.3.0 is removed that way: an older connection keeps its key until you press Disconnect or Zellio confirms the store address.
- New: store address changes are detected. A notice offers Update address in Zellio, and the plugin tells Zellio the new address with a signed request.
- Improved: a store that moved while it ran an older version now shows Update address in Zellio. When Zellio answers the status check with the address it has, the plugin keeps it as the old address (never requested, never used to disconnect). Every signed request also names its topic in the signed body.
- New: a staging or development copy of a store is not treated as a moved store. When WordPress says the site is not a production site (
wp_get_environment_type()), the plugin does not ask Zellio about the connection and does not show the store-address notice. If Zellio answers that the address is still a live store, the plugin says this site looks like a copy of your live store; Disconnect on a copy cleans up this site only and leaves the live store connected. - New: connection health block and Check connection button on the Zellio screen, and a Zellio section in WooCommerce → Status. The signed status report gains the same facts.
- New: before it creates a key, the plugin checks for Plain permalinks and for a server that strips the Authorization header, and explains the fix while your connection code is still valid. A failed connection no longer leaves a key or a “Connected” record behind.
- New: abandoned-cart recovery links. Zellio sends the shopper a signed link; opening it on any device rebuilds the cart (items, coupons and the email) and goes to the checkout. A link stops working after about 45 days. A member’s cart opened by anyone else brings the items only, never the member’s coupons or details.
- New: the cart snapshot keeps the email and phone a shopper types at checkout, on the classic checkout and the Checkout block. A failed send is retried up to 5 times, and the last send is shown in the health block.
- Fixed: the abandoned-cart table is now created when the plugin is updated and on every site of a network (before, only on activation).
- Changed: the Authorization header self-test looks where WooCommerce looks, including
getallheaders(). - Changed: every signed call between the store and Zellio (Zellio’s calls to the store, the disconnect notice and the address update) tries each Zellio webhook secret on the store, newest active first, then disabled. A paused webhook is never used.
- Fixed: reconnecting removes the old API key even when this plugin lost track of its id.
- New: a clear message when Zellio cannot read the store’s details (HTTP 422).
- New: a connection code that arrives while the store is already connected shows a Reconnect form. The current connection keeps working until the new one is made; a failed reconnect changes nothing.
- New: privacy tools. Suggested privacy-policy text, a personal-data exporter and eraser for abandoned-cart snapshots, and automatic deletion of snapshots with no activity for 60 days.
- New: Update URI header, so WordPress 5.8 and later asks Zellio’s own host for updates. The update package is still pinned to that host. Added the
Requires Plugins: woocommerceheader. - Changed: network activation sets up every site, a new site added to the network is set up on creation, and deleting the plugin cleans every site (webhooks, scheduled jobs, transients, table).
- Changed: translations load on
init, and the “Restored from trash” order note is translatable. - Changed: the signing secret is read from an active Zellio webhook first, then from a disabled one (WooCommerce disables a webhook after repeated failed deliveries). A paused webhook is never used.
- Tested up to WordPress 7.0 and WooCommerce 10.9. Arabic translation rewritten in Egyptian Arabic.
2.2.0
- New: Zellio can restore a trashed order. WooCommerce’s REST API can move an order to the trash but has no way to bring it back, so the plugin adds a signed restore route that restores the order the same way WooCommerce’s own Restore button does, on HPOS and on posts storage, and leaves a private order note.
- New: the signed status report now includes store facts: WooCommerce and plugin version, HPOS, order statuses, gateways that can refund, the active shipment-tracking extension, and which order actions this WooCommerce version supports. Zellio uses them to show only the order actions your store can really do. No keys, secrets or customer data are included.
- Security: every signed request is now bound to the route it was signed for and carries a one-time nonce, so a captured request cannot be replayed or sent to a different route.
2.1.1
- Fixed: the update check and the update report could disagree about which version this store runs. The check read a value compiled into memory, which on a site with OPcache can still name the build that was just replaced. Both now read the version from the plugin file itself. On sites that never expire that cache, this stopped the plugin reinstalling a version it already had on every update check.
2.1.0
- Zellio can now ask this store to check for a plugin update immediately, so a published fix arrives in seconds instead of waiting for WordPress’s twice-daily update cron. Requests are signed with the shared Zellio webhook secret and can only ever say “check now” — they can never name a version or a download URL, so what gets installed is still decided entirely by this plugin, from Zellio’s own pinned artifact host.
- Zellio can now see which plugin version this store runs, and whether the site allows automatic updates at all — so a fix that did not land is visible instead of assumed.
- A bad release can now be rolled back. Previously an older version was ignored by every install and the only way out was to publish a newer one.
- New warning when the WordPress user that connected this store can no longer manage WooCommerce. WooCommerce ties every API key to its creator, so that silently stops the integration; the notice now says so and tells you to reconnect as a current administrator.
- New warning when the site blocks automatic plugin updates and therefore cannot receive fixes.
- Admin notices no longer hide one another — previously the first condition that did not apply suppressed every warning after it.
- Fixed: abandoned-cart snapshots were never sent. The plugin looked up its Zellio secret with a WooCommerce function that does not exist, so the lookup failed on every store and every snapshot was skipped in silence. Present since 2.0.3.
- Fixed: a remote update no longer switches the plugin off. WordPress deactivates a plugin it upgrades outside its own cron and expects a browser to switch it back on; the plugin now restores its own active state.
2.0.3
- Added store-side abandoned-cart tracking. The plugin sends a snapshot to Zellio’s support-api whenever the cart changes; Zellio decides abandonment and handles recovery messaging.
- Cart snapshots are signed with the shared Zellio webhook secret and POSTed asynchronously so storefront performance is unaffected.
- Converting orders are stamped with
_zellio_cart_keyso Zellio can deterministically match recovered carts to orders. Both the classic checkout and the Checkout block are stamped.
2.0.2
- This plugin now enrolls itself in WordPress’s background auto-updater — future fixes, including security fixes, install automatically without waiting for you to notice the Plugins-screen nag. WordPress core removes the manual Enable/Disable auto-updates toggle for this plugin as a result; that is normal, expected behavior for a plugin that manages its own update policy.
- The WooCommerce sidebar entry is now labelled “Zellio AI”, and the settings screen shows the Zellio logo.
- Added a “Manage integration” link next to Disconnect on a connected card, for jumping straight to that integration’s settings in Zellio.
2.0.1
- Zellio Support now notices a disconnect made in the Zellio dashboard and clears its own “Connected” state — previously only a disconnect started in WordPress took effect here.
- Removed the Advanced settings dashboard-URL fields. Every install now always uses
app.zellio.ai/ops.zellio.ai; a staging or local Zellio is set via awp-config.phpconstant instead (developer use only, not exposed in the UI).
2.0.0
- Breaking: connecting now starts in Zellio. Paste the connection code Zellio gives you, or follow the link Zellio provides. The old “connect straight from WordPress” flow no longer works against Zellio Support.
- Send the required
install_stateon credential exchange, which fixes connection failures against current Zellio Support. - Separate WooCommerce API keys per product, so connecting Zellio ERP no longer revokes the key Zellio Support is using.
- Clear, actionable errors for expired codes, reused codes, rate limiting, and unreachable stores, instead of a raw HTTP error page.
- Plugin updates are now delivered through the WordPress Plugins screen from Zellio’s own update service.
- Split the codebase into
includes/modules; the root file is now bootstrap only. - Arabic translation added.
- Refreshed WordPress and WooCommerce compatibility.
1.0.0
- Initial release
- One-click connection to Zellio Support and Zellio ERP
- Secure server-to-server credential exchange via one-time tokens
- Automatic WooCommerce REST API key generation and revocation
- Configurable dashboard URLs for self-hosted deployments
- Full cleanup on uninstall (API keys + all plugin options)
- WooCommerce HPOS and Cart/Checkout Blocks compatibility
- CSRF-protected admin actions with nonce verification
