WooCommerce runs an outsized share of the small-store internet. W3Techs has it at roughly 48.9% of all ecommerce systems with a known platform in 2026, which means the median two-person store, the side-hustle skincare brand, the indie bookshop with a back office of one, is on Woo. Those teams are the ones already letting agents triage refunds, draft customer briefs, and flag suspicious orders. The shop owner can see the agent did something. They cannot always see what, or why, or against which order. That gap is what Dock closes for Woo stores: a workspace where every agent action is recorded, attributed, and reviewable, while WooCommerce stays the system of record.
WooCommerce plus WordPress remains the source of truth for products, orders, and customers. Dock holds the agent OUTPUT: triage recommendations, refund flags, customer briefs, the working notes a human teammate would otherwise keep in a private doc. Each row in Dock references a wc_order_id so the link back is exact. Agents read fresh from the WooCommerce REST API every time, never from a stale cache. When the agent needs to write back, refund issued, status changed, note added, the Dock consent gate fires the mutation. The data loops through Dock for the human read and the audit log, but it never leaves Woo's database. The store stays portable. The audit trail stays in Dock.
One workflow that lands hard for a one-to-three-person team is refund triage with an attached customer brief. The agent watches the Woo refund-request webhook. For each request it reads the order, the customer's prior orders, the product's recent return rate, and any open support thread. It writes a row to a Dock surface with the recommendation (approve, hold, escalate), the dollar amount, the customer's lifetime value, and a two-paragraph brief the human can send back. The owner skims the brief, hits approve in Dock, and the consent gate posts the refund through the Woo REST API. Five-step data flow:
- Woo webhook fires on
refund.createdororder.note.added. - Agent reads order, customer, product, and prior tickets via Woo REST.
- Agent writes a triage row to Dock keyed on
wc_order_id, with brief. - Human reviews in Dock, approves or edits inline.
- Consent gate sends the mutation back to Woo; Dock logs the actor, the diff, and the timestamp.
Woo is worth treating as its own use case because the constraints are different from a hosted platform. The plugin ecosystem means every store is a slightly different shape, so the agent has to read schema fresh rather than assume. Self-hosted means the owner already cares about not being locked in, and Dock matches that: WooCommerce stays the system of record, Dock holds only the agent's working memory. And small teams feel audit fragility the most, because there is no compliance department to reconstruct who did what from server logs. The agent audit trail is the safety net the team did not have to build.
If your store is on Woo and you already have an agent in the loop, start with the ecommerce overview, then the agent collaboration primer. For other stack shapes, see Shopify order pipelines, Stripe payments, and the broader piece on running an ecommerce stack with AI.
FAQ
Does Dock work with my WordPress plugin stack? Yes. Dock reads through the WooCommerce REST API, which respects whatever plugins extend the order, product, or customer schema. The agent reads schema fresh each run, so a custom field added by a subscriptions or bookings plugin shows up without reconfiguration.
Hosted Woo or self-hosted? Both. Dock connects the same way whether your store is on WooCommerce.com hosting, WP Engine, or a self-managed VPS. The REST endpoint and an application password are all the agent needs.
Can a small team share the same Dock workspace? Yes. A one-to-three-person store typically runs one shared workspace where the owner, an assistant, and the agent all see the same triage queue. Every action is attributed to a specific actor, human or agent, so the audit log stays clean even with overlapping hands.
How does this handle GDPR audit?
Customer PII stays in Woo. Dock stores the wc_order_id reference and the agent's working notes, not the underlying customer record. When a GDPR deletion request comes in, you delete in Woo and the Dock row points to a now-empty reference, with the full audit trail of who touched what still intact.