Who: Mariusz Szatkowski with senior specialists brought in per engagement. We design and ship process automation that sits next to WordPress and WooCommerce, not a generic consultancy slide deck.
What: Wiring orders, leads, stock signals and support events between WordPress, WooCommerce, ERP, CRM and the ops tools you already pay for. Tooling may be n8n, Make, Zapier or own code. The product is a reliable flow with monitoring, not a demo zap.
Where: Remotely for EU teams. We work against your staging APIs and agreed runbooks. NDA is standard before any production credentials change hands.
How much: Individual quote after we agree the first flow, the systems involved and the failure policy. Use the automation ROI calculator with your own labour and error costs before you ask for a build.
Business process automation around WordPress and WooCommerce
Most “automation projects” fail for a boring reason: nobody measured the manual process, nobody named the system of record, and the first release tried to do five flows at once. This page is the offer for teams that want one reliable path from trigger to write, with a stop button and a baseline.
Browse concrete cases in the process automation use-case library. For store-to-ERP sync architecture, see WooCommerce ERP integration. For assistants that call tools under scopes, see AI integration for WordPress.
Who you are hiring
- Shipping commercial WordPress since 2006, before Gutenberg and the REST API
- Senior-led: the engineer at discovery is the engineer at the keyboard at week six
- No offshore handoff, no PM layer billed back to you
- WordCamp Europe organiser, WordPress Foundation Credits mentor
- Shopify Academy: CRO learning path plus Partner Marketing (Credly, 2025)
Shopify Academy credentials
What we automate in WordPress and WooCommerce ops
We automate processes that already happen by hand or by brittle spreadsheet import. Typical categories map to the use-case library:
| Area | Examples | Start here |
|---|---|---|
| WordPress and WooCommerce | Order hand-off, stock signals, consent-aware messaging | WordPress and WooCommerce |
| Sales and e-commerce | Invoices after payment, courier labels, channel stock | Sales and e-commerce |
| Lead generation and CRM | Form capture, enrichment, owner assignment | Lead generation and CRM |
| Marketing | Cart recovery, consent sync, campaign metrics | Marketing |
| Finance and admin | Document packs, payment status fan-out | Finance and admin |
| Warehouse and logistics | Reservation, WMS hand-off, tracking updates | Warehouse and logistics |
Three flows buyers ask about first:
- WooCommerce orders to ERP - paid order becomes an ERP document without re-keying.
- Form leads to CRM - form submit creates or updates a CRM record with ownership rules.
- Abandoned cart reactivation - timed follow-up with stock and consent gates.
If your process is not listed yet, describe the trigger and the write. The library shape still applies.
n8n vs Make vs Zapier vs own code
Pick the runtime from hosting, audit and how close the logic sits to checkout. Vendor docs change; verify current limits on the linked sources before you lock a stack.
| Option | Strength | Weak fit | Source |
|---|---|---|---|
| n8n | Self-host option, visual workflows, good for EU data residency debates | Teams that refuse to run any workflow host | n8n docs |
| Make | Strong visual scenarios and HTTP modules for mid-complexity maps | Ultra-tight WooCommerce tax/stock paths that need PHP hooks | Make help |
| Zapier | Huge connector catalogue, fast experiments | High-volume checkout-critical paths and strict audit trails | Zapier platform docs |
| Own code (PHP worker, Action Scheduler, queue) | Deterministic, testable next to WooCommerce | One-off marketing zaps that never touch money | WordPress Cron / scheduling |
We often split the stack: critical money and stock writes stay in code next to WooCommerce; enrichment and notifications ride an iPaaS. A pure SaaS zap that posts invoices without idempotency keys is how duplicate documents appear.
Where AI belongs in process automation
AI is useful when the input is messy (ticket text, free-form forms, category guesses) and the output is a suggestion a rule can reject. It is a bad owner for:
- stock quantity and reservation,
- invoice totals and tax lines,
- payment captured vs pending,
- GDPR consent state.
For scoped assistants that call tools, use the AI integration pillar. Process automation on this page keeps models off the write path unless a human or a deterministic gate confirms the action.
When process automation is not worth it
Skip or delay the build when:
- the process runs fewer than a handful of times per month and errors are cheap,
- the team still redesigns the process every week,
- two systems claim to own the same field with no conflict rule,
- credentials and sandbox access are not available for 30 days,
- success is defined as “make it smarter” with no measurable baseline.
In those cases, fix ownership and measurement first. The ROI calculator only helps when you can type honest volume and minutes.
How a pilot and baseline should look
A pilot is one flow, not a platform rewrite.
- Baseline - executions per month, minutes per run, error rate, and the cost of one bad write (duplicate order, missed lead).
- Contract - trigger, source of truth, target write, idempotency key, retry and dead-letter behaviour.
- Evidence - staging run with anonymised payloads, before/after identifiers, pause procedure.
- Release - monitored production with a named owner for alerts.
- Stop - criteria to pause the flow without taking the store offline.
ERP-heavy order sync belongs with WooCommerce ERP integration for mapping and reconciliation detail. This pillar owns the wider process map and the tool choice.
What the client prepares before we start
Send a short brief, not a wish list:
- the single first flow and why it hurts now,
- systems and versions (WooCommerce, ERP, CRM, ESP),
- API docs or export samples with personal data removed,
- who can create sandbox credentials,
- current manual SOP or a screen recording of one run,
- legal constraints on marketing sends and personal data,
- who receives failure alerts after launch.
Without sample payloads and a named credential owner, we will not invent a schedule.
Next step
- Skim two or three cases in the automation library.
- Run your numbers in the automation ROI calculator.
- If the first flow is still worth it, contact us with the brief above.
Frequently asked questions
Questions about scope, delivery, pricing, and execution quality.
What counts as business process automation here?
#Do you always use n8n, Make or Zapier?
#Where does AI fit without creating risk?
#How do we know the first automation is worth building?
#What do you need from us before a pilot?
#Need an FAQ tailored to your industry and market? We can build one aligned with your business goals.
Let’s discuss
