Skip to main content

How to Choose a Shopify B2B Agency: 12 Questions to Ask Before You Sign

Twelve questions to vet a Shopify B2B agency, from native-feature limits to who maintains the ERP connector, published by an agency willing to answer them.

How to Choose a Shopify B2B Agency: 12 Questions to Ask Before You Sign

An agency writing a guide to choosing an agency deserves your suspicion, so let's put the cards face up: Uncap is one of the firms you would be evaluating with this list, and every question below is one we would expect to answer in your vetting call, including the uncomfortable ones. That is the point of publishing it. The generic version of this decision, how to tell real B2B experience from a retail shop with a wholesale page, is covered in our guide to choosing a B2B ecommerce agency; this one assumes you have already chosen Shopify B2B as the platform and now need to find out which agencies have actually built on it, versus which ones are about to learn on your project. Twelve questions, in the order the answers matter, with what a good answer sounds like for each.

Quick answer: Vet a Shopify B2B agency in four passes. Depth: how much of their practice is B2B on this platform, where the native primitives ran out for past clients, and proof of terms-and-payment flows in production. Data: which ERPs they have connected to Shopify's APIs, who maintains those connectors through API version changes, and what their field-mapping deliverable looks like. Mechanics: what discovery produces, how cutover happens without downtime, and who owns everything when you part ways, then the aftermath: what routine changes cost post-launch, what happens when Shopify ships a feature that replaces custom work, and what a client relationship looks like three years in. Ask all twelve of everyone, including us.

Pass One: Is Their Shopify B2B Real?

1. How much of your practice is B2B on Shopify, and what were you building before Shopify had native B2B? The platform's company accounts, catalogs, and price lists are recent enough that an agency's pre-native history is revealing: firms that were building wholesale on Shopify before the primitives existed learned the problem the hard way, and firms that arrived with the feature announcement learned it from the changelog. A good answer includes dates and what changed in their builds when the native tools landed. A bad answer treats B2B as a checkbox the platform added.

2. Where do the native primitives run out, and what did you build when they did? Shopify B2B covers a real share of wholesale requirements out of the box, and every serious build eventually hits its edges, quoting workflows, buyer-facing portals, punchout, configurators. The agency's answer tells you whether they practice the discipline that keeps budgets sane: exhaust native, then apps, then build exactly the gap. A firm that answers "we custom-build everything" is billing you for plumbing; a firm that answers "the native tools cover everything" has not shipped much of it.

3. Show me net terms and vaulted payment running in production. Not a demo store, a live client checkout where accounts buy on terms and payment collection runs the way the platform intends. This is the fastest concrete test of production depth, because payment flows are where thin B2B implementations get exposed, and an agency with real builds can show one inside a week under NDA if needed.

Pass Two: Can They Handle Your Data Spine?

4. Which ERPs have you connected to Shopify's APIs, and who maintains those connectors when the API version changes? The first half of the question every buyer asks; the second half is the one that predicts your third year. Shopify versions its APIs on a schedule, and an integration built as a one-time project decays on that schedule. A good answer names the ERPs, then describes maintained integration software with an owner, which is exactly why Uncap Connect exists as a product rather than a per-client script. A bad answer is "we build to spec and hand it over."

5. How does my contract pricing become Shopify price lists, and what stays in the ERP? The right architecture mirrors stable negotiated rates into price lists and leaves conditional pricing ERP-side behind quote flows, and an agency that has done this speaks that split fluently. The warning sign is an agency happy to rebuild your pricing logic inside Shopify, which converts your storefront into a second pricing engine that will disagree with your invoices by year two.

6. Show me a field-mapping deliverable from a past project, redacted. Every honest ERP-connected build produces one: entity by entity, field by field, which system owns which truth, which direction data flows, on what cadence. If the artifact exists, the discipline exists. If the answer is "our developers handle that in the code," your data model is about to live in one contractor's head, which is the exact fragility you are leaving your current stack to escape.

Pass Three: How Does the Project Actually Run?

7. What does discovery produce, and what does it cost me if we stop after it? Good discovery outputs artifacts you could take elsewhere: the module and integration audit, the field mapping, the phased plan, the scoped estimate. Priced discovery with portable outputs, the model behind Uncap Blueprint, aligns incentives honestly; free discovery that produces a proposal is a sales call wearing a deliverable's clothes.

8. How do you cut over without taking my revenue offline? The answer you are listening for is a parallel-run architecture: the old system serving buyers untouched while the new one is built and validated against real data, pilot accounts before general cutover, and a rollback that is a DNS change rather than a prayer. Any answer with a "go-live weekend" in it deserves follow-up questions about what happens when the weekend goes wrong.

9. When we part ways, who owns what? Theme code, custom apps, integration configuration, the data, and the accounts they live in. A clean answer is boring: you own your store, your code, your data, and the handover is documented. Ambiguity here is not an oversight; it is a retention strategy, and it prices the relationship's exit into every year you stay.

Pass Four: What Does Year Three Look Like?

10. What does a routine change cost after launch? A new price list, a new company account structure, a checkout adjustment. The Shopify-native answer is that most of these are configuration your own team can do, with the agency reserved for real development, and an agency that builds toward its own necessity, where every change routes through their ticket queue, has rebuilt the dependency model you migrated away from. Ask a reference this exact question; their pause tells you more than the number.

11. What happens when Shopify ships a feature that replaces something you built for us? The platform moves, and every Shopify agency eventually watches native functionality catch up to its custom work. The honest answer is retirement: migrate to native, delete the custom code, shrink the bill. The revealing answer defends the custom version. You are hiring for the first instinct, because over five years the platform will hand you this test several times.

12. Show me a client running three years later, and tell me what that relationship looks like now. Launch-day case studies are marketing; year-three clients are evidence. What you want to hear about is the pattern of work across a long portfolio, relationships that shifted from build to growth, storefronts that survived platform updates without rescue projects, and a reference who will take your call. Uncap's answer to this one is on the table: 380-plus B2B projects since 2013 as a Shopify Platinum Partner, alongside the partner relationships that surround a build, and references who run operations your size.

Using the Twelve

Send the list to every agency on your shortlist before the first call, ours included, and pay as much attention to how firms respond as to what they answer. The ones who welcome the list tend to be the ones with nothing to manage around; the ones who redirect to their deck have answered question thirteen without being asked. What good looks like on the platform side, the accounts, pricing, and ordering machinery all this vetting protects, is documented across what Shopify B2B done properly means, and it is the standard any agency you hire should be building toward.

Talk to Our Experts when you are ready to run the twelve on us, we will answer them in the first call, artifacts included.

Frequently asked questions

What should I ask a Shopify B2B agency before signing?

Twelve questions across four areas: the depth of their B2B practice on Shopify specifically (including where native features ran out and what they built), how they handle the ERP data spine (named integrations, connector maintenance through API changes, field-mapping deliverables), how projects run (discovery artifacts, zero-downtime cutover, ownership on exit), and what happens after launch (routine change costs, custom work retired when native features catch up, year-three references).

How do I tell a real Shopify B2B agency from a retail Shopify agency?

Ask for production proof rather than portfolio pages: a live checkout running net terms and vaulted payment, a redacted field-mapping document from an ERP integration, and a reference client at your scale answering what routine changes cost them. Retail agencies with a B2B services page can produce none of the three quickly.

Should discovery be free?

Paid discovery with portable artifacts, an integration audit, field mapping, a phased plan you could execute with anyone, aligns incentives better than free discovery that outputs a proposal. You are buying the plan, not the pitch, and the test is whether what you receive has value if you walk away.

What is the most overlooked question when hiring an agency?

What happens when Shopify ships a feature that replaces custom work the agency built. The platform catches up to customization continually, and an agency's willingness to retire its own billable code, migrate you to native, and shrink the engagement is the single best predictor of whose interests the relationship serves.

Keep reading
All notes

Punchout Catalogs: How to Sell Into Coupa, Ariba and SAP Procurement Systems

Aug 27, 2026

Choosing a Wholesale Ecommerce Platform: What B2B Brands Should Actually Evaluate

Aug 27, 2026

Wholesale Distributor Software: What ERP, PIM and Ecommerce Each Actually Do

Aug 27, 2026

Dealer and Distributor Portals for Manufacturers: Build, Buy, or Configure on Shopify

Aug 27, 2026
The Field Notes newsletter

Insights, guides, and trends. Once a month.

One email, last working day of the month. The notes worth keeping from building commerce on Shopify.

InsightsField-tested lessons from live Shopify builds.
GuidesStep-by-step playbooks for B2B, migrations, and performance.
TrendsWhat’s actually moving in commerce and AI, no hype.
Subscribe 2,400+ operators
StrategyWholesaleGrowthAI
Monthly · no spam · unsubscribe anytime
Talk to Our Experts