Shopify Plus B2B Replatforming Guide for APAC Distributors

Quick Answer: A Shopify Plus B2B replatform starts with weighted criteria — account modelling, pricing complexity, ERP integration and 36-month cost — not a demo. Plus lists from US$2,300/month. Expect 16–24 weeks for single-entity distributors, 28–40 for multi-entity APAC groups.

A Greater China distributor of industrial components came to us with a familiar shape of problem: 14,000 SKUs, 600 trade accounts across Hong Kong, Taiwan and Malaysia, dealer-specific pricing maintained in three spreadsheets, and a Magento 1 storefront that no longer received security patches. Their sales team was keying orders from WhatsApp screenshots into an on-premise ERP. The board had approved a digital budget; nobody could agree on what to buy.

Related reading: Salesforce Agentforce Pricing Strategy: An APAC Buyer's Verdict

Related reading: Enterprise Ecommerce AI Agent Trust Framework: An APAC Playbook

That situation is why this Shopify Plus B2B replatforming guide exists. Most migration content answers "how do I move my data?" The harder question for an APAC manufacturer or distributor is whether Shopify's native B2B model actually fits how you sell — tiered dealer pricing, credit terms, multi-entity tax, regional warehouses, and a sales rep who still closes 60% of revenue by phone. Get the fit assessment wrong and you spend two years rebuilding B2B logic that your old platform gave you for free.

Related reading: Shopify Plus vs BigCommerce B2B Enterprise APAC 2026

Related reading: Shopify Plus Cross-Border Repeat Customer Growth: The 149% Playbook

Related reading: Salesforce Marketing Cloud CDP Strategy: An APAC Retail Playbook

What follows is the evaluation sequence we use: criteria first, platform second, cost third, timeline last.

Start With Buying Criteria, Not the Demo

Vendor demos are optimised to show what the platform does well. Your job is to find out what it does badly in your specific context. Before you look at a single storefront, write down your weighted criteria.

The nine criteria that actually decide B2B platform outcomes:

• Account and catalog modelling. Can the platform represent your real hierarchy — parent company, multiple buying locations, different price lists per location, different payment terms per location?
• Pricing complexity. Percentage-off-retail by tier is easy. Contract pricing per SKU per customer with volume breaks and promotional overrides is where platforms break.
• Order capture pathways. Self-service portal, rep-assisted ordering, quote-to-order, CSV/quick order pad, and EDI or punchout if you sell to large enterprises or government.
• ERP and WMS integration surface. How many systems, which direction, how real-time does inventory need to be, and does your ERP have a modern API or a nightly file drop?
• Multi-entity and multi-currency. APAC groups frequently invoice from Hong Kong, Singapore and Australia entities with different tax treatments. This is a legal-structure question disguised as a platform question.
• Tax and compliance. GST in Singapore, Australia and Malaysia; VAT in Vietnam; no sales tax in Hong Kong; e-invoicing mandates that keep arriving.
• Performance in-market. A storefront hosted in us-east serving buyers in Ho Chi Minh City will feel slow regardless of Lighthouse score.
• Total cost over 36 months, including apps, middleware, payment fees and the internal headcount to run it.
• Partner availability in your time zone. The best Adobe Commerce architect is useless at 3am your time during a go-live.

Weight these against your revenue model before any vendor conversation. If 70% of your orders come through sales reps, "beautiful self-service UX" is a nice-to-have and "rep-assisted draft order workflow" is a must-have.

What Shopify Plus Actually Includes for B2B

Shopify's native B2B capability shipped with Shopify Editions Winter 2023 and has been extended in every edition since. It is no longer a bolt-on — it is part of the Plus and Enterprise plans, documented in the Shopify Help Center.

What you get without custom development:

• Companies and company locations. A company record with multiple locations, each carrying its own catalog, payment terms, tax exemptions and shipping addresses.
• Catalogs and price lists. Percentage adjustments off retail, fixed per-variant prices, quantity rules (minimums, maximums, increments) and volume pricing tiers.
• Payment terms. Net 15/30/45/60/90, due on fulfilment, or fixed date, with credit limits now supported at the company location level.
• B2B customer accounts with buyer roles (ordering versus location admin), order history, and reordering.
• Checkout to draft order, which routes a buyer's cart to your sales team for review before it becomes an order — the lightweight substitute for a quoting engine.
• Shopify Flow for approval routing, tagging and ERP-adjacent automation without code.
• Shopify Functions and checkout extensibility for custom discount logic, shipping rules and checkout UI — replacing the old checkout.liquid customisation model, which Shopify sunset for all plans in 2025 per Shopify.dev.
• Markets for multi-region pricing, domains and duties.
• Nine expansion stores on Plus, which is how most APAC groups handle separate entities or a D2C brand alongside the trade channel.

Creating the account structure is API-first, which matters because your ERP should own the customer master, not your storefront:

1mutation CreateTradeAccount {
2  companyCreate(input: {
3    company: { name: "Kwun Tong Industrial Supplies Ltd", externalId: "ERP-CUST-10482" }
4    companyContact: { email: "[email protected]", firstName: "Wing", lastName: "Chan" }
5    companyLocation: {
6      name: "HK Warehouse"
7      billingSameAsShipping: true
8      buyerExperienceConfiguration: {
9        checkoutToDraft: false
10        paymentTermsTemplateId: "gid://shopify/PaymentTermsTemplate/3"
11      }
12    }
13  }) {
14    company { id }
15    userErrors { field message }
16  }
17}

And dealer tiers map to price lists attached to catalogs:

1mutation CreateTier2Pricing {
2  priceListCreate(input: {
3    name: "APAC Tier 2 Dealer"
4    currency: USD
5    parent: { adjustment: { type: PERCENTAGE_DECREASE, value: 22.0 } }
6  }) {
7    priceList { id }
8    userErrors { field message }
9  }
10}

Per-SKU contract pricing then gets written as fixed prices into that list via priceListFixedPricesAdd, synced from the ERP on a schedule. The pattern works. The question is volume — if you have 600 accounts each with 2,000 negotiated SKU prices, you are managing 1.2 million price records through the Admin API, and you need to think carefully about bulk operations and rate limits.

Where Native B2B Stops and Custom Work Starts

Honest constraints, because every one of these becomes a line item in your statement of work:

No native quoting engine. Checkout-to-draft plus Shopify Flow covers simple review-and-approve. Multi-round negotiation with expiry dates, version history and margin guardrails needs an app (Sparklayer, BSS, Zapiet-adjacent tooling) or custom build.

Approval workflows are shallow. Buyer roles separate ordering from admin. Three-level spend approval with thresholds is not native.

One currency per catalog. A company location sees one presentment currency. Groups selling the same catalog in SGD and MYR run separate catalogs or separate expansion stores — which multiplies your maintenance surface.

Punchout and EDI are third-party. If your largest customers procure through SAP Ariba or Coupa, budget for a punchout provider or middleware. This is routinely the single biggest surprise in enterprise-heavy B2B scopes.

Mixed B2B/B2C carts are not supported. A buyer is in a B2B context or a retail context, not both in one basket.

Variant ceilings. Shopify raised the limit from 100 to 2,048 variants per product on the newer product model documented on Shopify.dev, which relieved a long-standing pain for configurable industrial goods — but genuine CPQ-style configurators still need external logic.

No native PIM. Metafields and metaobjects are good, and taxonomy-heavy catalogues with multi-language attributes across Traditional Chinese, Simplified Chinese, Japanese and Bahasa still usually justify Akeneo or Pimcore upstream.

If four or more of those are hard requirements, Shopify Plus may still win on TCO — but you are buying a platform plus a custom layer, and you should price it that way.

Why Shopify Plus Costs What It Costs

Shopify's published list price for Plus is from US$2,300 per month on a three-year term, or US$2,500 per month on a one-year term. Above roughly US$800,000 in monthly GMV, pricing converts to a variable model — the greater of the base fee or 0.40% of monthly GMV, capped at US$40,000 per month — per Shopify's own plan documentation. Shopify Enterprise Commerce, aimed at the tier above, is quote-only.

That headline number is not your cost. The real 36-month picture for an APAC B2B rollout:

Platform and transaction fees

• Plus subscription: US$27,600–US$30,000 per year at base rate.
• Shopify Payments card rates vary by region; where you use a third-party gateway on Plus, Shopify charges an additional 0.20% transaction fee (0.15% in some markets) per Shopify's pricing pages. For B2B invoicing on Net terms, much of your volume never touches a card gateway at all — which is a genuine cost advantage of the B2B model over D2C.
• Expansion stores: included up to nine on Plus, which saves real money versus per-instance licensing on competing platforms.

Apps and middleware

• ERP integration: iPaaS platforms such as Celigo, Alumio, Patchworks or Workato commonly land in the US$800–US$4,000 per month band depending on connector count and transaction volume, based on their published tiering.
• B2B feature extensions (quoting, advanced price rules): US$300–US$1,500 per month.
• Search and merchandising at catalogue scale: Algolia or Searchanise, low hundreds to low thousands monthly.
• Tax automation (Avalara, Vertex) where you have multi-entity GST/VAT exposure.

Implementation

Published agency estimates for Shopify Plus B2B migrations — including Optimum7's 2026 migration cost guide and similar vendor breakdowns — cluster between US$50,000 and US$300,000+, with integration count as the dominant variable, not SKU count. A single-ERP, single-entity distributor sits at the bottom of that range. A three-entity group with a legacy ERP, a WMS, a PIM and punchout requirements sits above it.

The comparison

Adobe Commerce licensing is quoted against GMV tiers, with commonly reported bands running from roughly US$22,000 to US$125,000+ per year before Adobe Commerce Cloud hosting, and before the specialist developer rate that Adobe work commands. The platform is more capable out of the box for complex B2B — native quoting, requisition lists, company credit, shared catalogs — and it costs more to own, in both licence and labour. BigCommerce Enterprise sits between the two and is quote-only.

So: why is Shopify Plus expensive? It isn't, relative to Adobe Commerce at equivalent GMV. It is expensive relative to Shopify's standard plans, and teams making the jump from a US$79/month store feel that as a 30x increase. The honest framing is that Plus is priced as mid-market enterprise software, and the question is whether you need the B2B APIs, expansion stores, checkout extensibility and Functions that come with it.

A Weighted Decision Matrix You Can Run in a Day

Score each candidate platform 1–5 against your weighted criteria. Weights below are a starting point for a mid-market APAC distributor selling 70% through dealers; adjust them to your revenue mix before you score anything.

Suggested weights

• Account and catalog modelling fit — weight 5
• Pricing complexity support — weight 5
• ERP/WMS integration effort — weight 5
• 36-month total cost of ownership — weight 4
• Rep-assisted and quote-to-order workflows — weight 4
• Multi-entity, multi-currency, tax — weight 4
• Regional performance and CDN coverage — weight 3
• Partner availability in APAC time zones — weight 3
• Internal team's ability to operate it unaided — weight 3
• Roadmap and release cadence — weight 2

Multiply score by weight, sum, and compare. The useful part is not the total — it is the argument that happens when your sales director scores "rep-assisted ordering" a 2 and your CTO scores it a 4. That disagreement is the actual finding.

Decision rules that override the score

Some criteria are binary, not weighted. Fail any of these and the platform is out regardless of total:

• Your top five customers require punchout and the platform has no viable connector.
• Your ERP is the system of record for pricing and the platform cannot accept bulk price writes at your volume within rate limits.
• You need per-line-item approval against purchase order budgets and no app covers it.
• Your group structure requires separate legal invoicing entities that the platform cannot represent without duplicating the catalogue nine times.

We have seen a dealer-network manufacturer run this exercise and conclude, correctly, that Shopify Plus won on nine of ten criteria and lost on the one that mattered most — and that deferring the replatform by two quarters to re-architect their pricing master was cheaper than forcing the fit. The honest constraint beat the success framing.

Integration Architecture: Where Projects Actually Fail

Data migration is a solved problem. Integration is not. In B2B replatforms, the integration layer is typically 40–60% of the build effort, and it is where timelines slip.

Three patterns, in ascending order of cost and control:

Point-to-point apps. A prebuilt connector for NetSuite, Business Central or SAP B1. Fast, cheap, and brittle if your ERP has been customised — which, in Greater China and Southeast Asia, it almost always has.

iPaaS middleware. Celigo, Alumio, Patchworks or Workato sitting between Shopify and your systems, with mapping, retry and observability built in. This is the right default for most mid-market distributors. You pay a monthly fee to avoid owning queue infrastructure.

Custom middleware. A service you own, usually when you have a legacy ERP with a file-based interface, or data residency requirements that rule out a multi-tenant iPaaS. More control, more maintenance.

Whatever you choose, the non-negotiables are idempotency, retry with backoff, and a dead-letter queue you actually monitor. A minimal webhook handler for order flow-through:

1// POST /webhooks/shopify/orders-create
2import crypto from 'crypto';
3
4export async function handler(req, res) {
5  const digest = crypto
6    .createHmac('sha256', process.env.SHOPIFY_WEBHOOK_SECRET)
7    .update(req.rawBody, 'utf8')
8    .digest('base64');
9
10  if (digest !== req.get('X-Shopify-Hmac-Sha256')) {
11    return res.status(401).send('invalid hmac');
12  }
13
14  // Ack within 5s, then process async — Shopify retries for 48h on non-2xx
15  await queue.publish('erp.sales_order.create', {
16    idempotencyKey: req.get('X-Shopify-Webhook-Id'),
17    shopifyOrderId: req.body.admin_graphql_api_id,
18    companyLocationId: req.body.purchasing_entity?.location?.id ?? null,
19    poNumber: req.body.po_number ?? null,
20  });
21
22  return res.status(200).send('ok');
23}

Register it against the current API version rather than clicking through the admin, so it lives in version control alongside the rest of your configuration:

1shopify app generate webhook --topic orders/create
2# or, directly:
3curl -X POST "https://your-store.myshopify.com/admin/api/2025-07/webhooks.json" \
4  -H "X-Shopify-Access-Token: $ADMIN_TOKEN" \
5  -H "Content-Type: application/json" \
6  -d '{"webhook":{"topic":"orders/create","address":"https://mw.example.com/webhooks/shopify/orders-create","format":"json"}}'

One deliberate design decision: pick your system of record per data domain and write it down. Products and pricing from ERP or PIM. Customers and company structure from ERP or CRM. Orders from Shopify. Inventory from WMS. Ambiguity here produces the circular sync bugs that eat month four of your project.

A Realistic Timeline for an APAC Manufacturer or Distributor

For a single-entity distributor with one ERP, two to three integrations and a catalogue under 20,000 SKUs, plan 16 to 24 weeks from kickoff to go-live. Multi-entity groups with punchout, PIM and multiple warehouses run 28 to 40 weeks. Anyone promising 8 weeks is either scoping a shop window with no integrations or is going to discover your ERP in week 6.

Weeks 1–4: Discovery and data audit. Catalogue and pricing extract, customer hierarchy mapping, ERP API assessment, integration specification, URL inventory for SEO. The deliverable is a signed data model, not a wireframe.

Weeks 3–8: Architecture and environment setup. Dev store, theme repo with CI, middleware scaffolding, staging ERP sandbox. If your ERP vendor needs six weeks to provision a sandbox — common with on-premise deployments in the region — you find out now, not in week 14.

Weeks 5–14: Build. Storefront, B2B account structure, catalogs and price lists, checkout extensions and Functions, Flow automations, middleware mappings.

Weeks 12–18: Integration testing with real data. Not sample data. Real dealer pricing, real tax codes, real partial fulfilments. Budget double what you think.

Weeks 16–20: UAT with actual buyers and sales reps. Pick ten dealers across your markets and have them place real orders in staging. Reps will find things no QA script finds.

Weeks 20–24: Cutover and hypercare. Freeze pricing changes, final delta migration, DNS, 301 map deployment, then two to four weeks of elevated support.

A regional note that costs people money: schedule go-live away from Lunar New Year, Golden Week, Ramadan and the Singles' Day to Christmas trading window. In APAC that leaves fewer clean windows than you expect, and partner availability thins out sharply in late January.

Protecting Traffic and Revenue During Cutover

B2B replatforms carry less organic SEO risk than D2C — most of your traffic is direct and logged-in — but you still have a long tail of product and category pages that generate inbound enquiries, and you have account continuity risk, which is worse.

The short list:

• Crawl the legacy site before you touch anything and produce a complete URL inventory with traffic data. Build the 301 map from that, not from the new sitemap.
• Preserve order history visibility. Dealers reorder from history; if it disappears, your support queue explodes on day one. Migrate historical orders or keep a read-only archive.
• Do not force a password reset for every buyer in the same week you change the storefront. Stagger activation by region or tier.
• Keep the legacy platform readable for at least 90 days post-cutover. You will need it for a reconciliation question.
• Validate tax and pricing on a sample of 50 real accounts before DNS changes, not after.

Google's Search Central documentation on site moves remains the authoritative reference for the URL-mapping mechanics, and it has not meaningfully changed in years — which is to say there is no excuse for getting it wrong.

Why This Is Trending Now

The demand signal is real. McKinsey's B2B Pulse research has consistently found that B2B buyers now use a mix of remote, digital and in-person channels across the buying journey, with digital self-service and remote interaction preferred for the majority of purchase stages. Gartner has projected that the large majority of B2B sales interactions between suppliers and buyers will take place in digital channels. Shopify, for its part, reported full-year 2024 GMV of US$292.3 billion in its investor materials and has repeatedly highlighted B2B as one of its fastest-growing surfaces in quarterly commentary.

For APAC manufacturers and distributors, the practical driver is narrower: generational handover in procurement teams, plus the operational cost of keying orders from messaging apps. Those are the two arguments that get budget approved.

How to Evaluate

Run this sequence, in order, and you will reach a defensible decision in six to eight weeks rather than a year of circular meetings.

1. Document your commercial model before you shortlist. Pricing tiers, approval chains, credit terms, entity structure, order channels with revenue share against each. One page. If you cannot write it, you are not ready to buy software.

2. Score against weighted criteria with the matrix above, with your sales leadership in the room. Record disagreements rather than averaging them away.

3. Apply the binary disqualifiers. Punchout, pricing volume, approval depth, entity structure. These override totals.

4. Demand a technical proof of concept, not a demo. Give two shortlisted partners your real pricing extract and ERP API documentation, and ask each to stand up a working company account with tiered pricing and one live ERP call in a dev store. Two weeks, fixed fee. It is the cheapest money in the whole project and it tells you more than any reference call.

5. Price 36 months, not 12. Licence, apps, middleware, payment fees, implementation, and the internal headcount to run it. Compare against your current all-in cost including the sales admin hours spent re-keying orders.

6. Check partner coverage in your time zone and your languages. A go-live spanning Hong Kong, Taipei and Kuala Lumpur needs someone awake in those hours who can write a Traditional Chinese error message correctly.

7. Commit to a cutover window with a rollback plan, and keep the old system readable for a quarter.

The pattern worth internalising from any Shopify Plus B2B replatforming guide is this: the platform decision is usually the easy part. Shopify Plus fits most mid-market APAC distributors well, costs less to own than Adobe Commerce at equivalent GMV, and its B2B feature set has improved every release cycle since 2023. What determines whether your project succeeds is the integration architecture, the pricing data model, and whether your sales team will actually use what you build. Decide those three things first.

If you are scoping a B2B replatform across Hong Kong, Singapore, Taiwan or Southeast Asia and want a second opinion on the integration architecture before you sign a statement of work, talk to the Branch8 team — we will tell you honestly if Shopify Plus is the wrong answer for your model.

Sources

• Shopify — Shopify Plus plan and pricing
• Shopify Help Center — B2B on Shopify
• Shopify.dev — Admin GraphQL API reference
• Shopify — Investor Relations and quarterly results
• Adobe — Adobe Commerce product overview
• McKinsey & Company — Growth, Marketing & Sales insights (B2B Pulse)
• Gartner — Sales research and insights
• Google Search Central — Site moves with URL changes