ERP vs. Shopify: Who Should Own B2B Pricing?
B2B pricing ownership depends on channel count: Shopify's own B2B integration guidance names three paths and takes no side on which system authors the price. Let the ERP own pricing when phone, EDI or distributor orders quote the same numbers. Let Shopify's catalogs own it when Shopify is the only channel, since 3 catalogs come with Basic, Grow and Advanced and unlimited with Plus (verified Sep 2026).
Your profile — see how the verdict shifts
- Confidence
- High — Read Shopify's B2B external-integrations page on 2026-09-05. It names exactly three integration methods: direct integrations from the Shopify App Store for select ERP, accounting and PIM systems; integrations from iPaaS providers that work as intermediaries; and custom, API-based integrations, which the page says offer maximum flexibility for unique business requirements. Named ERP and accounting partners on the page include NetSuite, Microsoft Dynamics 365, Fulfil and QuickBooks Online; named iPaaS providers include Pipe17, Patchworks and OmnifiCX. The page nowhere states which system should own or manage pricing, so the ownership call is yours to make and ours to reason about. One correction to a common framing: B2B catalogs are not Plus-exclusive. Shopify's plan-features table gives Basic, Grow and Advanced 3 catalogs assignable to B2B markets and Plus unlimited, while direct company catalogs assigned to a single company or company location are genuinely Plus only (verified Sep 2026). App-side evidence is thin: the two integration listings verified on 2026-09-05 both show zero reviews, and one prices only after a sales conversation.
- Reference scenario
- $20M–$100M GMV · Shopify Plus · an ERP already pricing phone, EDI and distributor orders · 6,000–15,000 SKUs · 40+ negotiated accounts · agency dev bench
- As of
- September 2026
Decision at a Glance
| Your profile | Verdict | Why |
|---|---|---|
| Shopify is the only B2B sales channel | WAIT | Shopify's catalogs are already the price of record, so there is nothing to synchronize and nobody to reconcile with. Publish contract prices into catalogs and let the ERP read orders back, not push prices forward. |
| ERP prices phone, EDI or distributor orders too | CUSTOMIZE | Two systems authoring the same negotiated price is how merchants end up quoting one number and invoicing another. Make the ERP the author, treat Shopify catalogs as a published copy, and let the sync run one direction. |
| Your ERP is one Shopify names: NetSuite, Dynamics 365, Fulfil, QuickBooks Online | BUY | A listed direct integration or an iPaaS connector is a maintained path, and Shopify names these systems on its own B2B integrations page. Buying the connector beats writing one, right up to the first requirement it does not cover. |
| Formula pricing, or a pricing system with no connector | BUILD | Cost-plus, index-linked and contract-multiplier pricing does not survive a field-mapping UI. Shopify's own page reserves custom API integrations for exactly this case, calling it maximum flexibility for unique business requirements. |
What B2B Pricing Data Ownership Actually Drives
| Outcome | Impact | How it works |
|---|---|---|
| Revenue — direct | High | A price that disagrees between the quote and the invoice stalls the order and puts a credit note in front of a finance team, which is how negotiated accounts get lost. |
| Operational efficiency | High | One author for negotiated prices removes the weekly reconciliation between ERP price lists and Shopify catalogs that wholesale teams otherwise run by hand. |
| Data & insight | Medium | A timestamped publishing record turns margin questions into a query, because every price in a catalog traces back to the run and the ERP record that set it. |
| Customer experience | Medium | Buyers who see their contracted price at checkout stop emailing a rep to confirm it, which is the difference between a portal and a catalog with a phone number. |
Spend ceiling: Size the spend to the pricing logic, not the pipe. Moving fields is commodity work that a listed connector does from a published $9,000 per year (verified Sep 2026); only a price your ERP cannot express as a field justifies the $25,000–$70,000 custom lane (Deploi estimate, illustrative).
What buying enables (top apps)
- + A maintained path for a named ERP, with the vendor tracking Shopify's API versions and your ERP's release cycle
- + Field mapping, retries and error dashboards out of the box, which are weeks of unglamorous custom work
- + Coverage beyond pricing, since the same connector usually moves products, inventory, orders and invoices
- + Shopify's own endorsement of the lane: direct integrations and iPaaS are two of the three methods it documents
What building additionally unlocks
- + Computed prices, including cost-plus, freight-inclusive and index-linked rules that no field map expresses
- + Bulk publishing tuned to your catalog count and SKU volume, rather than a generic scheduler
- + Reconciliation and drift alerting designed around your contracts, so a wrong price is caught before a buyer sees it
- + Portability: the logic is code you keep, and it re-points at a new ERP without a platform migration
Find Your Verdict in 3 Questions
Does any channel outside Shopify quote or invoice the same negotiated prices?
Yes: Go to question 2.
No: Your verdict: WAIT — make Shopify catalogs the price of record, publish nothing inward, and let the ERP read orders back.
Is your ERP one Shopify names on its B2B integrations page, with a connector that writes catalog prices?
Yes: Your verdict: BUY — take the listed direct integration or an iPaaS connector and keep your team on the pricing rules, not the transport.
No: Go to question 3.
Is the price a calculation, such as cost-plus, freight-inclusive or index-linked?
Yes: Your verdict: BUILD — a custom API integration is the path Shopify itself reserves for unique requirements ($25,000–$70,000, Deploi estimate, illustrative).
No: Your verdict: CUSTOMIZE — buy the transport, build only the publishing schedule and the reconciliation record.
The TCC Scorecard — 12 Dimensions
TCC — Total Cost of Capability: what it actually costs to have this capability over three years, whichever way you get it. Each dimension is scored 0–5 for both paths. How we score →
| Dimension | Buy | Build | Why |
|---|---|---|---|
| Cost | |||
| Acquisition & implementation | A listed connector or iPaaS recipe maps fields in days to weeks; a custom price integration with reconciliation and alerting runs 5–10 weeks (Deploi estimate, illustrative). | ||
| Recurring fees | Integration platforms bill annually and scale with connections or volume, one listing at $9,000 per year and the other only after a sales conversation (verified Sep 2026); a custom integration carries hosting and upkeep, not a licence. | ||
| Maintenance & upgrades | The platform vendor tracks Shopify's API versions and your ERP's release cycle; a custom integration puts both calendars on your team, inside Shopify's 12-month API support window. | ||
| Switching & exit | Field maps, transforms and error handling built inside an iPaaS stay inside it, so leaving means rebuilding the logic; a custom integration is code you keep and can re-point. | ||
| Risk | |||
| Vendor risk | Both integration listings verified on 2026-09-05 carry zero App Store reviews, so the public evidence base is thin even though the vendors are established off-platform. | ||
| Security & compliance surface | An intermediary platform holds your negotiated prices and customer records in transit and often at rest; a direct integration keeps that data between your ERP and Shopify only. | ||
| Platform-deprecation exposure | Shopify sanctions all three paths on the same page, so none is at risk of removal; the exposure is version churn, which the vendor absorbs on the buy path and you absorb on the build. | ||
| Value | |||
| Fit to requirement | Connectors move fields well and compute badly, so cost-plus and index-linked pricing needs the custom path Shopify itself describes as maximum flexibility. | ||
| Time to market | A listed connector for a named ERP can be publishing prices within a sprint; a custom integration lands in a quarter once reconciliation is included. | ||
| Performance & scale | Price publishing at 10,000 SKUs across dozens of catalogs needs batching and bulk operations, which a custom integration controls and a generic connector schedules for you. | ||
| Data ownership & AI-readiness | Whichever lane you pick, prices land in Shopify catalogs and stay queryable; the difference is whether the transformation logic that produced them is yours or the platform's. | ||
| Focus & opportunity cost | Nobody wins a wholesale account because they wrote their own ERP connector, so buy the plumbing unless the pricing logic itself is the differentiator. | ||
The App Landscape
| App | Status | Pricing | Best for |
|---|---|---|---|
| Shopify B2B catalogs and price lists | Native — First-party Shopify. Basic, Grow and Advanced each allow 3 B2B catalogs assignable to B2B markets and Plus allows unlimited; direct company catalogs assigned to a company or company location are Plus only (verified Sep 2026). Catalogs receive prices well and compute nothing. | Included with your plan's B2B entitlements | Holding the published price at checkout, whichever system authored it |
| Direct App Store ERP, accounting and PIM integrations | Category — Shopify's own B2B integrations page names this as method one, available for select ERP, accounting and PIM systems, and names NetSuite, Microsoft Dynamics 365, Fulfil and QuickBooks Online among them. Coverage is per-vendor: check whether the connector writes B2B catalog prices specifically, rather than only products, inventory and orders. | Vendor-dependent, most quote-based; confirm on the current listing | A named ERP whose connector already writes the objects you need |
| integrator.io | Live — flagged — No reviews on the listing, so there is no public track record to read. Positions itself for critical ecommerce integrations between Shopify and an ERP or 3PL, with a 30-day free trial. | Standard $9,000/year (verified Sep 2026) | A budgeted iPaaS lane with a published entry price rather than a sales call |
| Patchworks | Live — IPaaS alternative pitched at multi-system retail stacks, with a strong agency channel | Tiered platform subscription | Multi-system middleware where Shopify is one endpoint among several |
| Custom API-based price integration | Build lane — Method three on Shopify's own page, described there as offering maximum flexibility for unique business requirements. This is the only lane that computes a price rather than copying one. | $25,000–$70,000 one-time (Deploi estimate, illustrative), then upkeep | Cost-plus, index-linked or contract-multiplier pricing, and systems with no connector |
The Build Path
- Declare one author, then publish one direction: Write down which system produces a negotiated price and which one displays it, then let data flow only that way. Bidirectional price sync is where merchants lose weekends: two systems both believe they are right and the reconciliation is manual. Orders and payment status can flow back the other way without breaking the rule.
- Publish ERP prices into native catalogs on a schedule: Batch price changes out of the ERP and write them into Shopify catalogs through the Admin API using bulk operations, not per-SKU calls. Timestamp every run, alert on a stalled job, and keep a diff so a wrong price is traceable to the run that set it.
- Compute the formula in your own service: Cost-plus, freight-inclusive and index-linked prices are calculations, not fields. Run them in your own service against ERP cost data and publish the resulting number, so the catalog holds a price Shopify can charge and your finance team can defend.
- Effort band
- $25,000–$70,000 for a custom ERP-to-catalog price integration with reconciliation and alerting — Deploi estimate (illustrative); lands in the $25–75K contact-form band, or the $10–25K band when a listed connector carries the transport and you only build the pricing rules
- Typical timeline
- 5–10 weeks, with the first catalog publishing prices in about three (Deploi estimate, illustrative)
- Maintenance, honestly
- ~15–20% of build cost per year (Deploi estimate): roughly $4,000–$12,000/yr (Deploi estimate, illustrative) covering ERP field changes, new catalogs and moving the integration forward before an API version leaves Shopify's 12-month support window.
- What you own — and what you take on
- You own: the pricing logic, the publishing schedule, the reconciliation record and the prices sitting in Shopify catalogs. You take on: two release calendars, since your ERP and Shopify both ship changes, and the on-call reality that a silent sync failure shows customers last quarter's prices.
3-Year Total Cost of Capability
| Buy (app path) | Build (custom path) | |
|---|---|---|
| Year 0 (setup) | $15,000–$35,000 (licence plus implementation) | $25,000–$70,000 |
| Years 1–3 (recurring) | $27,000–$45,000 | $12,000–$36,000 (upkeep) |
| 3-year total | ≈$42,000–$80,000 | ≈$37,000–$106,000 |
- † All figures illustrative samples for the reference scenario — not quotes, not verified pricing.
- † Buy column: one integration platform at the published entry price of $9,000 per year (verified Sep 2026), plus implementation services; the quote-based alternative is excluded because it publishes no number.
- † Build column: a custom ERP-to-catalog price publisher with reconciliation, alerting and a formula service; three-year horizon.
What the Sticker Price Hides
On the buy path
- — Connector coverage is per-vendor: a listing that syncs products, inventory and orders may not write B2B catalog prices at all
- — Quote-based pricing means the budget arrives after the architecture is decided; one listing verified Sep 2026 sets billing only after a sales conversation
- — External charges from an integration platform are billed separately from your Shopify invoice, so they miss the ecommerce budget line
- — Field maps and transforms built inside an iPaaS do not come with you when you leave it
On the build path
- — Bidirectional price sync doubles the failure modes and halves the confidence; pick one author before writing any code
- — Per-SKU API calls will not publish 10,000 prices in a window; bulk operations are the only realistic transport at that size
- — A silent sync failure is worse than an outage, because the store keeps selling at yesterday's prices
- — ~$4,000–$12,000/yr upkeep across two release calendars (Deploi estimate, illustrative)
What Merchants Say
The pattern wholesale teams describe is a tie nobody broke: the ERP team assumed they owned pricing, the ecommerce team edited catalogs directly, and the mismatch surfaced when a buyer quoted a price the invoice contradicted.
Integration platform complaints cluster on cost visibility rather than capability, with merchants reporting that connector and volume charges landed outside the ecommerce budget they were approved against.
If You Change Your Mind Later
If you bought and outgrow it
Prices already published into Shopify catalogs stay there when the connector is switched off, which limits the damage. What leaves with the platform is the logic: field maps, transforms, retry rules and error handling all live in the vendor's builder, so budget a rebuild of that layer rather than a data migration. Export your mapping documentation while you still have a licence.
If you built and want out
Nothing strands. The prices sit in native Shopify catalogs, the code is yours to re-point at a different ERP, and a listed connector can take over the transport later without touching the catalogs underneath. The real exit cost is knowledge, so keep the pricing rules documented outside the codebase.
When This Answer Changes
We're watching for:
- ▸ Shopify adding a first-party price-sync surface to B2B catalogs, which would collapse the transport half of this decision
- ▸ Either integration listing accumulating real review volume, which would finally give the buy lane public evidence
- ▸ Your ERP vendor shipping a direct Shopify B2B catalog connector, which moves the reference scenario from CUSTOMIZE to BUY
Verdict change log:
No changes since first publication (September 2026).
Common Questions
Should the ERP or Shopify own B2B pricing?
The system that already prices your non-Shopify channels should own B2B pricing. Phone, EDI and distributor orders quoting the same contract numbers make the ERP the author, with Shopify catalogs holding a published copy. Shopify's own B2B integrations page names three sanctioned methods and never names an owner, so this call sits with you (verified Sep 2026).
How do you connect an ERP to Shopify B2B pricing?
Shopify documents three methods. Direct App Store integrations cover select ERP, accounting and PIM systems, and the page names NetSuite, Microsoft Dynamics 365, Fulfil and QuickBooks Online. iPaaS providers act as intermediaries, with Pipe17, Patchworks and OmnifiCX named. Custom API-based integrations are the third path, which Shopify describes as offering maximum flexibility for unique business requirements (verified Sep 2026).
What does a custom B2B price integration cost to build?
A custom ERP-to-catalog price publisher with reconciliation and alerting runs $25,000–$70,000 one-time, plus roughly $4,000–$12,000 a year in upkeep (Deploi estimate, illustrative). Buying the transport instead starts at a published $9,000 per year for one verified listing, with the other quote-based (verified Sep 2026). Scope moves both numbers, and formula pricing pushes the build higher.
Your Next Steps
If you're going with CUSTOMIZE
- Write down every channel that quotes a contract price, including phone, EDI and distributor portals
- Name one system as the author of negotiated prices and put it in writing before any integration work starts
- Check whether your ERP's Shopify connector writes B2B catalog prices, not just products, inventory and orders
- Build the publishing job on bulk operations with a timestamped run log and a stalled-run alert
- Turn off direct catalog editing in the admin for anyone who is not the named author
If you're going with BUILD
- Separate the calculation from the transport, and specify the pricing formula in business language first
- Prove the formula against last quarter's invoices before it ever reaches a catalog
- Publish to one catalog end to end, with reconciliation, before scaling to the rest
- Alert on drift between ERP price and catalog price, not only on job failure
- Diary an API version review each year so the integration never sits on a lapsed version
Official Docs & Sources
- B2B external integrations — Shopify Help Center
- Catalogs and pricing in B2B — Shopify Help Center
- B2B features by plan — Shopify Help Center
Official documentation linked for verification — our verdicts and estimates are our own.
Related Decisions
Should You Plan Around Shopify's B2B Company-Size Ceilings?
A B2B company holds up to 10,000 locations and 10,000 customers, but only 50 customers per location. The 50 is the number that actually constrains you.
Should You Build or Buy B2B Deposit Payments on Shopify Plus?
Plus's native B2B deposits collect the percent up front, but the balance is never auto-captured. Both purpose-built B2B deposit apps had 0 reviews when checked.
Can Shopify's Catalog Model Hold 30+ Price Tiers?
A company location holds a maximum of 25 B2B catalogs (verified Sep 2026). Model 30+ tiers as volume breaks, or split the account across company locations.
Should You Build or Buy Company-Specific B2B Pricing on Plus?
Direct company catalogs give one company or location its own price list natively on Plus; below Plus, an app's per-customer price lists are the workaround.
Should You Build or Buy Your NetSuite Integration on Shopify?
NetSuite integration is the honest DEPENDS: buy a connector for standard flows, build middleware when the flows are the business.
Ready to settle who owns your B2B prices?
We map the channels that quote your contract prices, name one author, and build or buy the shortest publishing path into Shopify catalogs that your team can actually keep running.
Contact us todayVerdict scored for the reference scenario above. Estimates are not quotes; app pricing carries its verification date and gets re-verified quarterly. Full scoring anchors: see the TCC methodology.
Read how we score these decisions (the TCC Framework). No affiliate links, no paid placement — no app vendor pays to appear here.