A defective order, resolved end-to-end — without leaving WordPress

A customer of an online store receives a faulty product and asks for a return. Follow the ticket from the WooCommerce order all the way to a return label generated on the merchant's own computer — each step handled by the right tool in the suite, nothing bolted on, no external SaaS.

1WooCommerce

It starts with a real order

Marta Ruiz bought the Halcyon HX-90 Wireless Headphones — order #50 in the store's WooCommerce. The order, the product and the customer are the source data; the whole support cycle will reference them by their real, human-readable values, never raw database IDs.

2WP-PFManagement

The customer opens support

Marta opens a support interaction from her account — describing the defect and linking it to her order. It lands as an ITSM interaction in WP-PFManagement, the low-code platform, carrying the order number, product and customer right on the ticket. She only sees her own interactions; staff see them all.

3WP-PFManagement

Triaged to a confirmed-defect incident

Support triages the interaction: category "Confirmed defect" → it converts to an incident. The order/product/customer context copies straight over, and the incident is prioritised from its impact and urgency — a standard ITIL matrix, no custom code.

4WP-PFWorkflow

A workflow routes and drives it

WP-PFWorkflow listens to the platform's record events as native triggers: it routes the incident to the right team, keeps the priority in sync, and orchestrates the steps that follow — visually built, really executed (queue, retries, timeline).

5WP-PFAgent

The agent drafts the reply — and asks first

WP-PFAgent reads the incident and drafts the customer reply in natural language. Before anything is sent or written, it stops at its confirmation gate and asks for a human OK — the agent never takes a side-effect on its own. Bring your own LLM; your keys, your bills.

6wp-executor

The return label is made on the merchant's own machine

Generating the RMA label means touching a tool that lives outside WordPress — on the merchant's computer. A workflow step hands the job to wp-executor, the open-source runner: it runs the merchant's own local label tool, on their own machine, and hands the finished label back. Automation that reaches beyond WordPress into your own environment.

7End to end

Attached to the ticket, and resolved

The generated RMA label is attached straight onto the incident, the reply goes out, and the incident is resolved — the whole journey logged in the ticket's journal. Order to resolution, inside your own WordPress, with the source code you can read.