How to run a Shopify Plus agency profitably

A profitable Shopify Plus agency is mostly an operations business, not a development one. The platform is mature and well documented, so most of the difference between a struggling Plus shop and a healthy one comes from four decisions: how you price replatforms (by integration, not by page), how you structure retainers after launch, how you staff against utilization, and how you use Shopify's partner program.

This guide is for owners and operations leads who already build on Shopify and want the agency-business mechanics. If you are earlier in the journey, start with how to start a Shopify agency. All prices, hours and margins below are illustrative examples to show the math; replace them with your own numbers.

Platform facts to build your offers around (checked October 2026):

• Shopify Plus starts at $2,300 a month on a 3-year term or $2,500 on a 1-year term; higher-volume merchants move to a variable platform fee based on revenue (Shopify Plus pricing).
• The plan includes the main store plus 9 expansion stores; more cost extra (Shopify Plus pricing).
• checkout.liquid is gone. It is no longer supported on the information, shipping and payment pages, and was sunset for the Thank you and Order status pages on August 28, 2025 (Shopify developer docs). Custom checkout work now means Checkout UI extensions and Shopify Functions.
• Agencies access client stores as collaborators, and merchants control access with a collaborator request code (Shopify Help Center).
• Partner tiers (Select, Plus, Premier, Platinum) are earned on revenue from merchants you bring and support, plus the number of new merchants, alongside certification and case study requirements, and are reviewed quarterly (Shopify Partner Program tiering guide).

What a Plus agency actually sells

Most Plus agencies sell four things, and the mix decides the operating model.

The common mistake is chasing replatforms because the contract values look large. They carry the most overrun risk and the longest sales cycles, and they end when the store launches unless you have sold what comes next. Treat each replatform as the start of a retainer relationship, and price it so it is profitable on its own anyway.

Pricing a Plus replatform from integration units

A Plus replatform is an operations project with a storefront attached. Agencies lose money when they scope the theme and treat everything else as "configuration". Estimate it in units instead:

1. Theme and templates: number of unique templates, sections and custom components.
2. Integrations: each ERP, OMS, PIM, 3PL or custom API connection is its own unit with discovery, build, testing and failure handling. ERP connections (NetSuite, Microsoft Dynamics and similar) are usually the largest units in the project.
3. Data migration: customers, orders, subscriptions, loyalty balances, gift cards and redirects. Each has its own mapping and validation.
4. Apps and app configuration: subscriptions, reviews, loyalty, search, helpdesk. Each needs setup, theme integration and QA.
5. B2B: company accounts, catalogs and price lists, payment terms.
6. Content and merchandising: product data cleanup, collections, PDP content. Often underestimated when the client has hundreds of SKUs.
7. QA, launch and training: test plans, launch checklist, training each role on the client's team.
8. Project management: a percentage of the total, commonly 12 to 20%.

Worked example (illustrative): a mid-size brand moving from another platform, with one ERP, subscriptions and a B2B price list.

At a blended rate of $150 an hour, that is about $170,000. If the client's budget is $90,000, the conversation is about which units to cut or phase (for example, B2B in phase two), not about working faster.

Rules that protect the margin:

• If you can't map the deal to units in discovery, sell a paid discovery phase first. The project estimation guide covers how to run one.
• Cap order history migration in the SOW (for example, 24 months). Older orders rarely justify the work.
• Lock the product catalog a fixed number of weeks before launch.
• Price every integration separately so a client can see what each one costs.

Retainers that pay after launch

How you structure retainers decides how many clients one project manager can run. Three common shapes:

Capacity math for a care plan (example): if a care plan includes up to 10 hours a month and clients use an average of 6, one developer with 120 billable hours a month can carry about 20 care-plan clients with room for spikes. Track actual use monthly; if the average creeps toward the cap, raise the price or tighten the scope.

Care plans are low revenue each but sticky, and they keep you close to the client for the next larger project. Growth retainers usually carry the margin. Embedded teams look good on revenue but behave like staffing: review utilization on them weekly.

A useful target is for retainers to cover your fixed delivery payroll, so project wins become upside rather than survival. See recurring revenue for agencies for structuring retainers in general.

Team structure and capacity math

Plus agencies are often heavy on theme developers and light on the roles that protect margin: senior project managers, an integrations engineer, QA and launch operations, and a CRO or merchandising lead.

An example 12-person shape:

• 1 partner or commercial lead
• 1 head of delivery
• 2 senior project managers
• 3 Shopify developers
• 1 senior front-end or Hydrogen lead
• 1 integrations engineer
• 1 designer or merchandising lead
• 1 QA and launch operations
• 1 strategy or CRO lead

What it can produce (example math): say 10 of the 12 do billable work, each has about 1,800 working hours a year, and the team hits 65% billable utilization. That is about 11,700 billable hours. At an effective rate of $160 an hour, capacity is roughly $1.9M a year. If revenue is far below that, the team is underused or underpriced; if it is above, utilization is unsustainable or prices are high enough to fund another hire.

When integration work is causing overruns, the next hire is usually a second integrations engineer rather than another theme developer. For margin benchmarks across agency types, see the agency profit margins guide.

Scope creep traps specific to Plus

1. "Just one more app." Each app added after the SOW needs installation, theme work and QA. Bill it as a change order.
2. Historical data. Clients ask for full order history late in the project. Cap it in the SOW.
3. Custom checkout requests. With checkout.liquid retired, custom checkout logic means Checkout UI extensions and Shopify Functions. Scope each requirement explicitly; some requests are not possible within Shopify's checkout rules at all, and the client should hear that during discovery.
4. B2B price lists. The first catalog and price list are in scope; each additional one is new work.
5. Late catalog changes. New SKUs added in the last two weeks before launch break QA plans. Lock the catalog.
6. Subscription app migration. Moving subscribers between subscription apps is a project with its own risks (payment method migration, billing dates), not a task.
7. Expansion stores. Plus includes 9 expansion stores, so clients assume more stores are "free". The platform fee may be, but your work is not. If expansion stores come up in discovery, scope them as a separate phase.

The defense is a one-page change-order policy referenced in every SOW: any request outside the SOW gets an estimate within a set time, and the client approves it before work starts. See agency MSA vs SOW for where those terms belong.

Headless and Hydrogen: when it pays

Headless builds (Hydrogen or another framework on Shopify's Storefront API) are the highest-value and highest-risk Plus work. They make sense when:

• The brand has a clear performance or content need that a theme cannot meet, such as content published to several surfaces.
• The client has, or will hire, a front-end developer who can own the codebase after launch, or will sign a support retainer.
• You can name the retainer that follows the build.

They don't make sense when the client wants headless because a competitor has it. The common failure pattern: the brand launches a custom storefront it can't maintain, small changes start requiring developer time, and the agency absorbs unpaid support to protect the relationship. If you can't picture the post-launch retainer, don't sign the build.

Using the Shopify Partner Program

Shopify's partner tiers (Registered, Select, Plus, Premier and Platinum) are based on commercial measures: revenue from new merchants you refer or co-sell, revenue from existing merchants you support, and the number of new merchants you bring to Shopify, together with certification and case study requirements. Tiers are reviewed quarterly, and the exact thresholds are in Shopify's partner tiering guide.

What that means for how you run the agency:

• Track partner-attributable revenue yourself. Know which merchants you brought to Shopify and which you support, by quarter, so tier reviews hold no surprises.
• Plan case studies from the start of each project. Get permission in the contract and capture before-and-after metrics at launch.
• Plus and Enterprise merchants count more toward higher tiers. An agency built on many small standard-plan stores will find it harder to climb than one with fewer Plus clients.
• Don't treat a tier as a sales plan. Referrals help, but most agencies still need their own pipeline. See agency lead generation.

Metrics to watch per client

Tracking these needs time data tied to clients and retainers. AgencyPro includes time tracking and capacity management on the Pro plan and per-client profitability reports on the Plus plan; see capacity planning and pricing. Other options are compared in time tracking for agencies and retainer management software.

Productized offers worth building

Fixed-scope offers collapse discovery and keep junior staff busy between large projects. Example offers (prices illustrative):

1. Plus migration sprint from Shopify's standard plans to Plus, with checkout extensibility setup and B2B or expansion store configuration.
2. CRO audit plus 90-day test plan: analytics review, funnel analysis and three rounds of tests.
3. Subscription review: setup, churn points and app configuration.
4. B2B configuration sprint: company accounts, catalogs, price lists and payment terms.
5. Performance sprint: Core Web Vitals (LCP, CLS, INP), app script review and image handling.

Each one needs fixed inputs, fixed outputs and a fixed price. See productized services for how to package them.

When to walk away from a Plus deal

• Plus is chosen for status, and the brand's needs fit a standard Shopify plan.
• The client wants headless with no one to own the code after launch.
• The client has fired two previous agencies in a short period and can't say why.
• The decision-maker won't join discovery.
• The client wants a fixed bid before any technical discovery.
• The integration list includes a custom ERP and the client has no engineer who knows it.

When a Plus specialization is not the right fit

• Your clients are mostly small stores. Plus work needs Plus budgets. If your pipeline is standard-plan merchants, a productized Shopify offer will serve them better.
• You don't want integration work. Much of the risk and value in Plus projects sits in ERP and data work, not theme design.
• You need fast cash cycles. Replatforms run for months with milestone billing, and enterprise clients often pay on longer terms. Plan working capital accordingly; see agency cash flow management.

Frequently asked questions

How long does a Shopify Plus replatform take?

It depends on integrations more than design. A replatform with no ERP and a lightly customized theme can take two to three months; one with an ERP, custom theme, subscriptions and B2B often takes four to six months or more, plus a stabilization period after launch.

What gross margin should a Plus agency target?

Set targets from your own data: estimate margin per project unit and per retainer, then compare actuals monthly. Retainers usually earn higher margins than replatforms, which carry overrun risk. If projects regularly finish below your target, the problem is usually integration estimates, not delivery speed.

How many Plus clients can one project manager handle?

It depends on the mix. A project manager can usually run more care plans than growth retainers, and an active replatform takes a large share of one person's week. Measure PM hours per client type for a quarter, then set caps based on what you see.

Is it worth climbing Shopify's partner tiers?

For an agency focused on Plus, usually yes, because tiers bring visibility in Shopify's ecosystem and access to partner programs. Plan for it: tiers are based on revenue from merchants you bring and support, the number of new merchants, certifications and case studies, reviewed every quarter.

Should we offer Hydrogen builds?

Only if you have a senior front-end developer who can lead the codebase and a clear post-launch retainer for each build. Without both, headless projects tend to turn into unpaid support.