Shopify store care retainers: what to sell and how to price

Short answer

Define a small list of recurring tasks, a response time, and a monthly hour limit. Price from your time and the value of having someone on call. Sell it to people who already trust you.

Reactive and proactive care

Reactive care means fixing things when they break: a theme error after an app update, a checkout bug, a payment method that vanished. Proactive care means checking before it breaks: app audits, speed checks, backups, broken link checks, small improvements.

Most plans mix both. Reactive work is what owners think they are buying. Proactive work is what keeps them from needing it, and it is easier to show as a monthly report.

What to include

• Monthly check of apps and theme updates
• Speed and mobile check
• Broken link and form tests
• Test order on checkout
• A short written summary each month
• A number of hours for small changes
• A response time for urgent problems

Say what is not included: redesigns, new features, large app setups. Those are quoted separately.

The 90 day access trap

Shopify's help pages say collaborator access can expire if the collaborator does not log in for 90 days. If you only work on a store when something breaks, you can lose access right when you need it. Put a login check into your monthly routine. Also make sure the owner understands how access requests and request codes work so that restoring it is easy. Check Shopify's current help text for exact wording.

How to price it

Do not copy a number from someone else's price page. Pricing depends on your hourly rate, how many hours you expect to spend, and what the store earns.

A workable approach:

1. Estimate monthly hours for the tasks above on a normal store.
2. Multiply by your rate, then add a margin for unplanned requests.
3. Create two or three tiers by hours and response time.
4. Tell the client what happens if they exceed the hours.

Any price range you find online is the seller's claim. We do not give a figure because we have no verified market data. See how to price automation and store work for the models.

How to sell it

Do not sell it in the first message. After a good project, say what usually breaks over the following months and offer to watch for it. If the owner seems relaxed about it, drop it and check back later.

Tiers: a sketch

The hours below are examples of structure, not recommended prices or hours.

• Light: monthly checks and a summary, a small number of change hours, replies within two working days.
• Standard: the light plan plus more change hours, a speed review, and replies within one working day.
• Active: the standard plan plus a monthly improvement task agreed in advance, and priority for urgent problems.

Three tiers are common in service pricing because they let the client choose. Whether that raises your average price for store care, we have no evidence. Test with your own clients.

Onboarding a new retainer client

The first month decides how it goes. Do these in order:

1. Get access the right way. Ask for collaborator access through the store's settings or exchange a request code, so you are not using the owner's login. Never ask for the owner's password.
2. Take notes on the current state: theme version, installed apps, payment methods, shipping setup, known problems.
3. Run a test order and screenshot the key pages. This is your baseline.
4. Agree who to contact and how for urgent problems.
5. Send the first summary after two weeks, even if it says nothing broke.

The baseline matters. Without it, a client who says "it was fine before you touched it" is hard to answer.

What to do when something breaks

Check whether the problem is new. Look at the recent app and theme changes. Reproduce it on a draft or duplicate theme where possible, so you do not make things worse on the live store. Fix it, test the checkout, and tell the owner in two or three lines what happened and what you changed. Keep that message in your records.

If you are not sure of the cause, say that. A plain "I have not found it yet, here is what I checked" builds more trust than a guess.

Keep a record

Log what you did each month: updates applied, issues found, time spent. This helps with renewals and disputes. Never invent results for the report. If nothing happened, say so.

What store owners worry about

Owners rarely ask for a "care plan". They say things like "I am afraid to update the theme" or "the site felt slow last month" or "I do not know who to call when checkout fails". Use those words when you describe the plan. Describe it as a person to call and a routine that catches problems early, not as a list of technical tasks.

Some owners already have a developer. Do not attack that relationship. Offer to be the backup, or to take the monthly checks while the other developer builds new features. If the other person is good, you will hear about overflow work later.

Terms worth writing down

• The monthly fee, what it covers, and what it does not.
• Response times, stated as working hours and not as promises of a fix.
• Who pays for apps and themes you recommend.
• How the client gives and removes access.
• Notice period for both sides.
• What happens to unused hours. Most plans say they do not carry over. Whatever you choose, say it.

A one page agreement is enough for a small store. For anything larger, ask a lawyer in your country. We are not giving legal advice here.

Add automation

Retainers pair well with small automations: order alerts, low stock messages, simple reports. See getting your first automation clients without Upwork.

Find the clients

For channels, see how Shopify freelancers find clients.

Delegating the client side

If you want the care work without handling invoices and renewals, Thomas Partners handles the client side. Partners keep 90% of the profit after documented costs. There is no fee if there is no profit. Read more and apply here. It also helps to read about what partner programs offer so you know what to ask.

See also: Shopify collaborator access: a freelancer's guide and Error handling for client automations in n8n and Make.