Emergency
out-of-hours
Magento support.

This package provides urgent engineering attention outside the ordinary support schedule. It is intended for problems that are affecting essential operations now, where waiting for normal support would materially extend the disruption. The initial £380.00 charge includes up to 120 minutes of engineering work on the accepted case. The charge applies in full if less time is used; there is no pro-rata refund for unused initial time. Payment covers engineering work and does not guarantee resolution.

Planned development, routine maintenance, feature requests and non-urgent improvements are usually better discussed through our standard project or support enquiry. If your request can safely wait, tell us. The assessment helps establish an appropriate next step rather than assuming that every technical problem needs an emergency package. We cover evenings, nights, weekends and bank holidays. The scope and start time are confirmed before payment; resolution within 120 minutes is not guaranteed.

Storefront unavailable or server errors

An outage may present as a blank page, a maintenance message, an application error or a service that only fails for certain visitors. We ask which parts of the store are affected, what the public error says, when it last worked and whether the host has reported a wider problem. This helps distinguish an application issue from a hosting, network, certificate or CDN dependency before work is accepted.

Checkout and payment failures

Checkout problems can have different causes and different business impact. A single payment method failing is not the same as every order being blocked. We ask when the failure occurs, whether another method works, whether customers receive a confirmation and whether the store records an order. Share a redacted error or reproduction steps if available; never include card details, customer records or payment credentials in the request.

Failed updates, deployments and customisations

An extension update, release or configuration change may coincide with a new fault. A useful assessment starts with the timeline: what changed, who made it, whether a previous working release is available and what has already been tried. Repeated, uncoordinated changes can make a problem harder to understand. Tell us if another engineer or hosting provider is working on the same incident so that responsibilities can be agreed.

Integrations and operational disruption

Failures in stock, order, fulfilment or payment integrations can block operations even while the storefront appears healthy. Explain which systems are involved, whether data is missing, delayed or duplicated, and whether a safe manual workaround is possible. The first objective may be restoring an essential flow or stabilising the service; a permanent redesign or broader integration project may require a separate scope.

Suspected security incidents

Unexpected redirects, unknown administrator accounts or security alerts require careful assessment. Mark a suspected compromise in the request and explain the visible symptoms without sending sensitive evidence. We will assess whether the work can be accepted under this service or needs a different incident-response scope. A standard emergency repair package is not a promise of a full forensic investigation. Avoid deleting evidence or making speculative changes while responsibility for the incident is being established.

Start with your website, the main problem, your name and email address. The following four steps cover the incident and its impact; recent changes and attempted fixes; recovery options and access readiness; and the person authorised to approve the work. Sign in or create an account to submit and track the case. Case notifications use your account email. Most answers use choices, and “Not sure” is available for technical details. Relevant follow-up questions appear only where they help an engineer understand the situation.

We want enough information to make a responsible decision. That includes whether a backup exists, whether the problem is reproducible, whether someone can arrange access and whether an approver will remain available. We do not need your passwords to make the initial acceptance decision. If more information is required, the case will clearly show what is missing. If we cannot accept, we will say so; no initial package payment is taken merely because you submitted a request.

Your account shows the accepted scope, package price and proposed start. The initial package is an ordinary payment, collected before paid work begins. Once the case has been accepted, you can be invited to provide credentials in the dedicated Secure access area. The engineer confirms the required access and begins work when payment and access are ready.

The case timeline shows published updates, screenshots and requests for your input. Time used, remaining approved time and payment status are presented separately. You can distinguish the initial engineering charge from additional funds on hold. Waiting for information or approval should not look like active billable work. Important case changes and each public support update are also sent by email, with links back to the authenticated case.

If further work is needed beyond the initial allowance, the engineer explains the findings and estimates the extra time required. Work pauses at the approved limit. You see the rate and maximum amount before deciding whether to continue. Your case shows the current rate, estimated duration and maximum authorisation before you approve.

When an extension is fully used, its full amount is collected. If more time is needed, the engineer requests another approval and a new hold. If the case finishes part-way through an extension, only the additional minutes used are collected and the unused portion is released. The closing invoice shows the initial engineering charge, actual additional time and payments already received. The bank’s display of a released hold may take time to update.

You may decline further work. The engineer then provides the current findings and a safe handover; the initial package and additional time already used remain payable. There is no automatic charge for another extension and no promise of unlimited work within the initial price.

Credentials are not requested in the initial form, email or messaging alerts. After acceptance, the case’s Secure access area is the intended route for protected submission. The secure-access design includes encrypted transmission and storage, separate key management, restricted access for authorised assigned staff, staff MFA and an audit of access without recording secret values in logs.

Where practical, create a temporary account with only the permissions needed or grant a suitable SSH public key. Keep passwords out of screenshots and support messages. When the work is over, revoke temporary access or rotate the relevant secrets at your service. Removing our stored copy is separate from disabling a login on your system. Secure access is available only when configured and enabled for your accepted case.

For ongoing maintenance and planned improvements, explore our Magento support retainers. Any follow-up work has its own agreed scope and approval.

The closing report explains the work performed, the outcome, remaining limitations and any follow-up that needs separate agreement. A restored service, a temporary workaround and a completed permanent repair should be described accurately. Your final bill reconciles the initial payment and actual extension charges without collecting the same money again. Invoices and any refund-linked credit notes remain available in your account and are emailed to you.

If the incident reveals a need for maintenance or longer-term improvements, we can discuss those after the urgent work. They should have their own scope and approval. The emergency case should leave you with a clear record of what happened, what was changed and what needs attention next.

Is this regular support? No. This package is specifically for accepted urgent work outside regular support hours. For a new urgent request during UK working hours, see working-hours emergency Magento support. Use the standard enquiry route for planned or non-urgent requirements.

What if the issue is fixed in 20 minutes? The initial £380.00 charge covers up to 120 minutes of engineering work and remains payable in full if less time is used. There is no pro-rata refund for unused initial time. The charge does not guarantee resolution.

Do I pay before you accept? No. Submit the assessment first. Payment is requested once support accepts the case.

What if you cannot accept? We will tell you. You do not purchase the initial package merely by sending a request. Acceptance depends on the issue, scope and available expertise/capacity.

How will I know what is happening? Read your case timeline and email updates. Both distinguish work in progress, waiting for information and waiting for approval.

What happens to unused additional funds? At completion, only actual additional usage is captured and the unused hold is released. This differs from refunding a payment already collected.

Tell us what is failing, what changed and what your business needs to restore essential operations. We will use that information to decide whether we can accept the case and propose the next step. Request urgent support.