Support and maintenance
A support plan gives you engineers who already know your store, response targets in writing by severity, and a monthly report of what happened and what was done. It covers incidents, theme and app upkeep, Shopify API version upgrades, integration monitoring and the small improvements that never make a project. Plans are sized from a few hours a month for a micro brand to 24x7 coverage for enterprise.
Our oldest support client has been with us since 2018.
Standard support SLA.
| Level | What it covers | Response | Hours |
|---|---|---|---|
| S1 | Store or checkout down, payments failing for everyone | 30 minutes | 24x7 |
| S2 | Payments, search, cart or an integration degraded for some customers or orders | 2 hours | 24x7 |
| S3 | A defect with a workaround | Next business day | Mon to Sat |
| S4 | Change request or small improvement | Scheduled in the next cycle | Mon to Sat |
Response is the time to a named engineer working the issue with you informed. Resolution targets are set per system in the plan. Tighter targets are available by agreement and priced as such.
What a plan includes.
Coverage, upkeep and a budget of improvement hours, reported monthly.
Unused hours roll for a quarter. Anything larger than the monthly budget becomes a small fixed-scope project with its own quote.
Plan sizes.
Asked about support.
Yes, after a short audit so we know what we are taking responsibility for. Most of the stores we support today were built by someone else.
The plan pays for coverage, monitoring and upkeep, which happen every month whether or not there is an incident. Improvement hours are tracked and reported, and unused hours roll for a quarter.
Customers cannot buy: the store is down, checkout is failing, or payments are declining for everyone. Anything that affects some orders or some customers is S2. The plan lists examples for your stack.
30 days' notice. You keep the runbook, the documentation and the access list.


