Shopify Plus agency: what the plan adds, the skills to insist on, and when the upgrade is justified

A Shopify Plus agency builds and runs stores on Shopify's enterprise plan, and the work differs from standard Shopify development in a specific way: Plus opens up the parts of the platform everyone else cannot touch. Checkout customisation through checkout extensibility and Shopify Functions, B2B selling with company accounts and price lists, expansion stores for additional brands and markets under one organisation, scheduled sale events, higher API limits and organisation level administration. An agency worth paying Plus rates to is fluent in those, not just in themes and apps. Before you brief anybody, write down which of those capabilities you are actually going to use, because that list is the whole basis for choosing between shops.

This page covers the Plus tier and the partner skills it needs. For scoping and judging a standard Shopify build, see the four capability stacks of an ecommerce agency.

What Plus actually adds

Capability	What it lets you do	What the agency needs
Checkout extensibility	Customise checkout through supported extension points rather than editing templates	Checkout UI extensions, and the discipline to stay inside supported APIs
Shopify Functions	Custom discount, delivery, payment and cart logic that runs on Shopify's own infrastructure	Developers who write and deploy Functions, and can migrate legacy Scripts
B2B on Shopify	Company accounts, buyer permissions, price lists, payment terms, quantity rules	Experience modelling a real trade channel, not a retail store with a login
Expansion stores	Additional storefronts for brands, regions or languages under one organisation	A plan for shared theme code and a single source of truth for product data
Scheduled events	Automated launches, flash sales and theme swaps at a set time	Rehearsed runbooks, not a person clicking publish at midnight
Organisation administration	Central user management, permissions and reporting across stores	A role and access model designed rather than accumulated
Higher API limits	Heavier integrations and faster bulk operations	Integration experience with an ERP or 3PL at volume

Shopify's own Plus page sets out the plan, and the Plus partner directory lets you confirm that an agency claiming the status actually holds it. Checking takes a minute and is worth doing before the second meeting.

When the upgrade is justified

• Your checkout needs logic the standard plan cannot express. Tiered discounts, bundles with their own rules, delivery logic driven by your own data.
• You sell wholesale as well as retail and are currently running a separate system or a password protected store for it.
• You operate several brands or several markets and are maintaining the same theme by hand in each one.
• Your sale events are large and timed, and a manual launch is a business risk.
• Volume has reached the point where the variable fee structure works in your favour. Run that arithmetic with your finance team using your own revenue, not an example.

If none of those apply, the standard plan plus a good agency is the better use of the money. The upgrade is a capability decision, not a status one.

The questions that test real Plus experience

1. Show me a checkout you customised with checkout extensibility. Ask what the extension points were and what the request was that you had to decline because no supported extension point existed.
2. Have you migrated Scripts to Functions? Many older Plus stores still carry legacy checkout scripts, and migration is specific, time boxed work. An agency that has done it will describe the process precisely.
3. How have you modelled B2B? Listen for company accounts, price lists, catalogue visibility and payment terms, plus how they handled a customer who buys both wholesale and retail.
4. How do you manage theme code across expansion stores? Expect a shared repository, a release process and a view on where stores are allowed to diverge.
5. What does your launch runbook look like for a timed sale? Expect a rehearsal, a rollback plan and a named person watching.
6. When would you recommend headless, and when would you not? A partner who recommends headless for every project is selling capacity rather than advising.
7. Who on your team holds Plus experience, and will they be on my account or only in this meeting?
8. What is your approach to apps at this scale? Enterprise stores accumulate apps, and replacing the heaviest with Functions or custom code is a measurable win.

How a Plus engagement is usually structured

• Paid discovery. A data model, an integration map, a checkout requirements list and a phased plan. Buy this separately where you can.
• Build, in phases. Core storefront first, then checkout logic, then B2B or additional markets. Trying to launch everything at once is the most common cause of a slipped date.
• A retained team after launch. Plus stores are products rather than projects. A monthly allocation of developer days against a backlog you prioritise is the model that works.
• Named roles. A technical lead, a front end developer, a project manager, and access to a Functions capable developer. Ask for the names and their allocation.

Terms to settle before signing

• The Shopify organisation and its billing stay in your company's name, with your staff holding the owner role.
• Theme code lives in your Git organisation; the agency is a collaborator.
• Custom apps and Functions are registered to your organisation, with source delivered and licensed to you.
• Documentation covers the data model, every integration, the release process and the launch runbooks.
• A support window with response times during sale events, written as hours rather than best efforts.
• A thirty day offboarding obligation, so changing partner is a handover rather than a rebuild.

Do not let the growth work wait for the build

A Plus replatform absorbs attention for months, and the commercial work that pays for it runs on a separate track. Three things belong in the plan from week one: the platform level search constraints a developer should design around, covered in Shopify SEO; the product data quality that feeds both organic results and shopping surfaces, covered in product schema; and the feed and account structure that decide paid performance, covered in ecommerce PPC. Launch day is far easier when those three were requirements rather than follow ups.

Asked and answered: Shopify Plus agency

What is the difference between a Shopify agency and a Shopify Plus agency?

A Plus agency works daily with the capabilities only the enterprise plan exposes: checkout extensibility, Functions, B2B, expansion stores and organisation administration. Ask for evidence of each one you plan to use, because the Plus label alone does not tell you which of them a shop has actually shipped.

How much does Shopify Plus cost?

Shopify quotes Plus on a platform fee with variable pricing at higher volumes, so get the figures from Shopify for your own revenue. Then add the agency retainer, the app subscriptions and the internal time, because the platform fee is the smallest line in the total.

Do I need Plus to sell wholesale?

B2B on Shopify with company accounts, price lists and payment terms is a Plus capability. Simpler wholesale arrangements can be run on the standard plan with apps and discount codes, which is workable at low volume and gets awkward as the trade channel grows.

Is headless worth it on Plus?

Headless suits content heavy brands, unusual front end requirements and teams with their own developers. It adds a front end to maintain, so take it when you have a reason you can state in one sentence and keep the standard storefront when you do not.

How long does a Plus migration take?

Ask each agency for a dated plan with dependencies named, then look at who on your side owns each dependency. Integration partners and data readiness set the critical path far more often than storefront development does.

Can I use more than one agency?

Yes, and many Plus merchants do: one for the build, one for growth and performance. Define the boundary in writing, give each a separate backlog, and make one of them accountable for the storefront code.

Growth work for the shopper who asks a machine

An enterprise store has traffic to protect and a catalogue large enough that no one person reads all of it. The shopper who skips the search page and asks an assistant, "which retailer ships this fastest?", gets one paragraph naming two or three stores. Which stores appear depends on what the assistant can read about each, not on your Plus configuration.

Ask your agency who owns that answer. AI Knows Us gives the owner a record of it across the assistants, which is a sensible thing to hold in a quarterly review.