An automation that works once is a demo. Reliable commerce automation behaves predictably when the network stalls, an item changes halfway through a run, or an instruction is accidentally submitted twice.
Validate at the store boundary
Agent output should never travel directly into product or order records. Normalize fields, check required values, and reject impossible state transitions before calling WooCommerce.
For prices and inventory, show the proposed change alongside the current value. A small comparison prevents expensive interpretation errors.
Reliability is the discipline of knowing what the system will do when the happy path disappears.
Design every write to be replay-safe
Retries are unavoidable. Attach a stable operation key to each requested mutation and store the result. If the same instruction returns, the system can return the original outcome rather than applying it again.
- Read before writing when a current value affects the result.
- Use explicit status transitions for orders.
- Split bulk work into individually traceable items.
- Surface partial completion instead of reporting a false success.
Escalate ambiguity
The right response to uncertain intent is not a best guess. If a request can affect tax, refunds, payment status, or a large product set, pause it and present the smallest useful confirmation.
Good automation removes repetitive judgment. It does not hide consequential judgment inside a prompt.