Emergency Magento
support during UK
working hours

Magento incidents we investigate

Your store is unavailable

A blank page, critical error or unavailable storefront can stop trading completely. We investigate the application and its hosting environment to establish where the failure is occurring. That can mean examining recent changes, application logs, server resources and the services your store depends on. We explain what we find and agree the next practical step.

Checkout or payments are failing

A store can appear healthy while customers are unable to place an order. Payment errors, broken shipping options, checkout exceptions and failed integrations all need careful investigation. Midoriweb considers the customer journey as well as the underlying technical behaviour, helping distinguish a Magento problem from a payment-provider or third-party issue.

A release or update has caused disruption

Problems after a deployment can involve code, configuration, generated assets, dependencies or caches. We review what changed and the evidence available before recommending a corrective action. If a rollback or recovery is appropriate, it depends on the backups, release history and access available; we will not assume a safe recovery point exists without checking.

Orders, stock or integrations are blocked

ERP connections, shipping services, background jobs and other integrations can disrupt operations even when the storefront is still online. We investigate the affected workflow and its dependencies, clarify which systems we can access, and identify where another supplier may need to help. Our aim is to give you a usable plan, including any external dependencies.

How we investigate and communicate

Midoriweb brings together Magento development, integrations and server support. That matters when the symptom appears in one place but the cause sits somewhere else. A checkout issue may involve an extension or an external service; a slow or unavailable store may involve application behaviour, background processes or hosting resources.

We start by understanding the business impact and the technical evidence. We agree the immediate scope rather than treating an emergency as an open-ended development project. Where access and circumstances allow, we review logs, recent changes and recovery options before making changes. If the investigation changes our understanding of the problem, we explain what that means for the next step.

Your support case is the shared record of the work. You can follow updates, respond to questions and see requests for additional time in one place. You should know what has been attempted, what remains uncertain and what is needed from you. We will ask before continuing beyond the time you have approved.

Clear pricing and control over additional work

The initial £140.00 charge includes up to two hours of engineering time on the accepted issue. It is payable in full even if the work takes less than two hours; unused initial time does not produce a pro-rata refund. It is a charge for engineering work, not a fixed-price promise to resolve every problem.

If more time is needed, approved additional work costs £60 per hour. We explain the proposed extension and ask you to authorise it before work continues. Additional time follows the existing time-recording and payment-authorisation process: the used portion is charged and any unused portion of the authorisation is released. A released authorisation is different from a refund of a completed charge, and its appearance in your account depends on your bank.

Access shared with care

Do not put passwords in the initial request or ordinary case messages. Once your case is accepted and access is requested, use the secure access area for the relevant administration or server details. Provide temporary accounts or restricted access where possible, with only the permissions needed for the agreed work.

Shared credential entries expire from the support vault after the configured retention period, currently 24 hours. That expiry does not disable the original account or change its password. When the work is finished, revoke temporary access or change the credentials you shared. This keeps the end of the support engagement under your control.

Working-hours support: practical questions

Do I have to be an existing Midoriweb customer?

You can create an account and submit a request for review. Acceptance depends on the issue, the access and information available, and our capacity to take on the work. We confirm scope and start time before payment.

What if I need help outside working hours?

For a new emergency outside working hours, use the out-of-hours Magento support page at its published rates. If we already accepted your case during working hours, work can continue after the time change at the agreed initial charge and extension rate. Further time still needs your approval.

Can you work with my existing developer or hosting provider?

We can review the technical information you provide and identify when another supplier needs to be involved. Tell us about existing support arrangements and any restrictions on access or changes. This helps avoid conflicting work and makes responsibilities clearer.

Can you take on planned improvements at the same time?

The emergency case focuses on the agreed incident. Larger improvements, redesigns and routine development should be scoped separately so they do not obscure the immediate priority or create unexpected costs.