Service
WordPress and WooCommerce technical support and troubleshooting
Technical support for WordPress and WooCommerce sites that are running but have a feature that fails or produces errors. The cause is located before any change is made: the problem is reproduced, logs and recent changes are reviewed, and the fix is tested on a copy of the site where practical. Each fix is delivered with a record of the cause, the change and how to reverse it.
You work directly with the developer responsible for the project. We usually reply within one business day.
Typical support cases
Support work applies to sites that are already in use, where a specific function has stopped working or behaves differently from what is expected.
- Error messages, a blank page or an inaccessible admin area after an update.
- A conflict between plugins, or between a plugin and the active theme.
- Stock, orders or customer records not synchronising between WooCommerce and another store, ERP, CRM or external service.
- Scheduled tasks, webhooks or API connections that fail without a clear error.
- Checkout, payment or order notification emails that fail for some or all customers.
- A site built by another developer that now needs fixes and has limited documentation.
Support services
- Diagnosis
- Reproduction of the problem, review of error logs, server configuration and recent changes, and identification of the component responsible.
- Repair
- Correction of the faulty code, configuration or data, with the change limited to the identified cause.
- Update and compatibility fixes
- Resolution of problems caused by WordPress, PHP, theme or plugin updates, including replacement of components that are no longer maintained.
- Integration and sync repair
- Correction of data mapping, authentication, retries and error logging in connections between WordPress and external systems.
- Ongoing maintenance
- Updates, checks and fixes for an existing site under an agreed arrangement.
Working method
- 01
Reproduce the problem
The conditions under which the problem occurs are confirmed first: which pages, which users, which actions and since when.
- 02
Locate the cause
Logs, recent updates and the components involved are reviewed until the cause is identified, rather than disabling features until the symptom disappears.
- 03
Fix on a copy where practical
Changes are tested on a staging copy before they are applied to the live site, and the live site is backed up first.
- 04
Record the change
The handover states the cause, the change made, how to reverse it and how to recognise the problem if it returns.
Examples
The client site below is a delivered production project. AumCreate also develops and maintains plugins published on WordPress.org, each with a public version history and support forum.
Common questions
- Can you take on a problem when the cause is unknown?
- Yes. Most support requests start with a symptom rather than a cause. Diagnosis is scoped first, and the repair is quoted once the cause has been identified.
- Can the fix affect other parts of the site?
- Changes are limited to the identified cause, tested on a copy where practical and applied after a backup. Each change is recorded so that it can be reversed on its own.
- Do you work on sites built by other developers?
- Yes. The existing implementation is reviewed before any change. Where documentation is missing, the relevant parts are documented as part of the work.
- Is ongoing maintenance available?
- Yes, under an agreed arrangement covering updates, checks and fixes for the site. The scope is agreed in advance.
Project enquiry
Send the current site or the requirement, together with any examples, documents, or workflow notes that help explain it. We review the scope and may ask follow-up questions before providing a written quote.
You work directly with the developer responsible for the project. We usually reply within one business day.
AumCreate
