Store Sheriff → When your developer disappears
Your developer stopped replying. What to do about your store.
It is one of the most common situations we see, and one of the most frightening if you are not technical. The store still works. Orders still arrive. But the person who built it has gone quiet — moved on, got too busy, changed career, or simply stopped answering — and you have no idea what you actually control. This is how to find out, and how to get it back.
Before anything else: do not cancel or stop paying for anything
The instinct is to cut ties with whatever the old developer set up. Resist it. Hosting accounts, domain renewals and any subscription attached to the store are the things keeping your shop online. A cancelled hosting account can be wiped within days, and a lapsed domain can be bought by someone else and is sometimes impossible to recover at any price. Keep every payment running until you know exactly what each one does.
The four things you need to control
Almost every “I’ve lost my developer” situation comes down to the same four pieces. You may hold all of them, none of them, or — most commonly — two of them without realising it. Work through them in this order, because each one gives you leverage over the next.
| What | What it is | How to check whether you have it |
|---|---|---|
| 1. The domain | Your address on the internet. The single most important asset you own, and the hardest to recover if lost. | Find which company it is registered with by looking up a public WHOIS record for your domain. Then find out whose email address is on the account. If it is yours, you can do a password reset and you are fine. |
| 2. The hosting | The server your store runs on, and where your database and files live. | Look for a recurring payment on your card or bank statement. The company name on it is your host. If the developer pays for it, that is a problem to solve early. |
| 3. Store admin | The WooCommerce or PrestaShop login where you manage products and orders. | You probably already have this one, since it is how you run the shop day to day. Check whether your account has full administrator rights, not just shop-manager rights. |
| 4. The code and data | The theme, plugins, custom work and the database — the actual store. | This lives on the hosting. Once you control the hosting, you control this. If custom code was written, ask whether it was ever handed over or stored anywhere you can reach. |
Getting each one back
If the domain is in the developer’s name
This is the most urgent item on the page. A domain registered to someone else is not yours in any practical sense, and if it expires while they are unreachable you can lose it permanently. Contact the registrar directly — not the developer — explain the situation, and ask what their process is for an ownership dispute or a transfer where the registrant is uncontactable. Registrars deal with this constantly and most have a documented procedure. Have proof ready: invoices showing you paid for it, company registration, trademark if you have one, anything tying the business name to you.
At the same time, make sure the renewal does not lapse while you are sorting it out. If you can pay the renewal, pay it, even on an account you do not fully control. Keeping the domain alive buys you time to resolve ownership. Losing it does not.
If the hosting is in the developer’s name
Same approach: go to the hosting company, not the developer. Explain that you are the business owner, the site is your trading store, and you need account access. Hosts vary in how helpful they are, and their first obligation is to their account holder, so expect to prove who you are.
If that fails, you are not stuck — you can move the store to hosting you control, provided you can get a copy of the files and the database. Which is why store admin access matters so much.
If you cannot log into store admin
On WooCommerce and PrestaShop, an administrator password can be reset from the hosting control panel by someone who understands the database, even when the email on the account is one you cannot reach. This is routine work for any competent host or developer. It is also the step where people most often cause damage by guessing, so if you are not confident, this is the point to get help rather than experiment on a live shop.
If nobody has the custom code
If your store had bespoke work done — a custom theme, a special integration, a bulk import tool — the only copy may be on the live server. There is no version control to recover it from, no repository, no backup of the source beyond the running site. Once you control the hosting, take a full copy of the files and database and store it somewhere entirely separate before you change anything at all. That copy is now your only safety net.
The order to do it in
- Secure the domain. Nothing else matters if you lose your address.
- Take a full backup, off the server. Files and database both, downloaded somewhere you control. Do this before touching anything.
- Get hosting access, or get a copy complete enough to move elsewhere.
- Get full administrator rights in the store itself.
- Remove the old developer’s access — but only once you have confirmed your own access works. In that order, never the reverse. Revoking their access first, then discovering you cannot get in yourself, is the one genuinely unrecoverable mistake here.
- Change every password and write down where each account lives.
- Then find out what state the store is actually in. A store nobody has maintained for a year or two usually has several problems that have been quietly accumulating.
That last step is what the free Store Sheriff check is for: eighteen questions that tell you what has drifted — software versions, backups, plugin hygiene, speed, whether anyone would notice if checkout broke. It takes two minutes, needs no login, and nothing leaves your browser.
Making sure it does not happen again
The underlying problem was never really the developer going quiet. It was that one person held everything and nobody else knew what they held. Whatever you do next, fix that structurally:
- Every account in the business’s name, with a business email address you control. Give contractors access to your accounts; never let accounts be created in theirs.
- Write down where everything lives. Registrar, host, store admin, payment gateway, email. One page is enough. The failure mode is not complexity, it is that the knowledge lives in one person’s head.
- Automatic backups stored off the server, and restore one at least once so you know it works. An untested backup is a hope, not a backup.
- Decide who is responsible for the store’s technical health — and make it someone whose continued existence you are not relying on by luck.
That last point is the one with no DIY answer. A store needs updates applied, backups checked, and someone to look at it when something breaks. If that is not somebody’s actual job, it drifts back to exactly where you are now.
So who looks after it now?
It depends on the size of the shop, and the honest answer is different at different sizes.
A smaller store usually cannot justify an agency retainer, and should not pretend otherwise. What it needs is hosting where the care is included — updates, backups, monitoring, SSL, plugin maintenance — for a price a small shop can actually carry. That is what GrannyHost was built for: six months free, then $290 a year, run by the same people and on the same servers as SwiftForge.
A larger store, where a day offline costs real money, wants a team on a retainer who know the code. That is SwiftForge Store Care, from $395 a month.
If the store has been neglected long enough that it needs repair before anyone can maintain it, a free store review will tell you what that involves, with fixed prices, before you commit to anything.
Related
- Who actually looks after a small online store? — the four models, what each one really costs, and where each one fails.
- What managed hosting actually does for a small store — and what it does not.
- Is your store platform still supported? — first thing to check once you have access back.
- Which PHP versions still get security fixes — the single fastest thing to look up.