BigCommerce to Shopify: B2B and ERP integration

Answer to your refined scope. Prepared by Vadym Shevchenko, 18 November 2026.

Based on your message and Shopify's documentation. Every claim about Shopify links to its page. Where I tested something in my own test store, I say so. Where I need information from you, it is in the questions at the end.

1. The main points

  • The Advanced limit of 3 catalog assignments counts per market. One catalog used in the US B2B market and in the Canada B2B market already takes 2 of the 3. A catalog for a single company is Plus only. Shopify B2B features by plan. So catalogs on Advanced can carry the base dealer prices per country, but not per-dealer prices.
  • Dealer pricing can be built on segments and discounts instead, on Advanced. I tested the key parts in my own test store. Details and limits in answer 2.
  • Historical orders are imported with their buyer and their company location, so a dealer's past orders show in each buyer's history and in the company and location history. Answer 5.
  • Net payment terms, PO numbers and manual payment methods work on Advanced. Different payment methods for dealers and retail need a third-party app without Plus. Answer 6.
  • Plus is needed only if dealer pricing turns out to be individual for many dealers and you do not want a third-party app or your own App Store app built by me. Answer 2.
  • Estimate: under two months full time, 203 to 278 hours for everything needed to launch. Section 4.

2. Your requirements, one by one

Where each line of your scope lands. "Native" is Shopify out of the box, "App" a third-party app, "My build" code I write, "Info" means I need something from you first.

RequirementNativeAppMy buildInfoSee
1. Migration and store configuration
Migrate and consolidate products, variants, collections, customers, selected orders✓✓A4, A5
Shopify Markets for US and Canada✓A2
Storefront and theme, SEO, redirects, data validation✓✓2.1
Shipping zones, carrier-calculated rates, tax settings, payment methods✓✓2.2, A6
2. B2B and dealers
Dealer registration, approval and management✓✓2.3
Companies with multiple buyers and locations✓2.3
Dealer-specific pricing, discounts, negotiated price lists✓✓✓A2
Special pricing for larger accounts✓✓✓A2
Dealer checkout: payment options, PO references, net terms✓✓✓A6
Advanced vs Plus, structure of markets, catalogs, companies✓A2
3. Custom ERP integration
Product and SKU sync, inventory, product prices, dealer prices✓✓A3, A7
API and webhook handling, errors, retries, logging, monitoring✓A3
Embedded admin dashboard for sync status and errors✓A7
4. Other integrations
Shipping and carrier integrations, custom shipping logic✓✓✓✓2.2
Tax calculation and exemptions✓2.2
Existing promotions, cart upsells, storefront functionality✓✓✓2.1
Performance, testing, security, deployment✓A3, A7, 4
Timeline and engagement
Contribution to technical planning, not isolated tasks✓5
Timeline, resources, level of effortA8, 4

2.1 Storefront and theme

  • Your message says little about the site itself. The catalog size is clear, but the size of the site is not: how many different page templates, custom features and BigCommerce apps it has. This can change the estimate a lot, so I would like to see both sites. I will analyse the current site and come with my own recommendations. If anything must stay untouched, tell me.
  • The store is built from scratch, so I build it properly from the start, not "move it as is and optimise later". While I replicate the current store I can improve UX, SEO and loading speed and fix small UI issues where I see room, without much extra time. I have done this a lot.
  • I am a developer, not a designer. Do not expect a new creative brand look from me. Expect a clean, even, well-structured site: misaligned blocks fixed, anything clearly broken or ugly cleaned up, and structure, navigation and content organised around data.
  • With a catalog this size, navigation can be restructured based on Google Search Console data, analytics if you have it on BigCommerce, and best sellers from the order history.
  • Example, the Kuroobiya migration (ZenCart to Shopify, done alone). The old site was old and the navigation did not match the product structure. I reorganised the same content: navigation built on how the business works, on Search Console data (how people search, which URLs are popular) and on best sellers from the order history. Links between pages and to the help pages, shipping information, measuring and size guides and contact. The FAQ rewritten from real customer questions I pulled from the order history of the old platform. A new Help Center, because the product needs careful preparation before ordering and staff spent most of their time agreeing order details. The goal was to answer those questions before the order. New store: kuroobiya-zc3wn1fu.myshopify.com (password: blackbelt).
  • Existing promotions: BigCommerce promotions and coupon codes can be read through its Promotions API and rebuilt as Shopify discounts. Cart upsells: with this much SKU overlap there is room for cross-sells, upsells, bundles and custom recommendations. BigCommerce has no ready "frequently bought together" data, so I would calculate pairs and best sellers from the order history. I propose options once I know the catalog.

2.2 Shipping and tax

  • Carrier-calculated rates (UPS, FedEx, USPS, Canada Post and others) are included on Advanced. If a carrier has a ready app, it is setup work. If not, I can build a rate service with the CarrierService API, available on Advanced, and that is separate work.
  • Custom shipping logic is limited by what Shopify allows. I either use what the platform offers, or simplify the logic to fit it. Hiding, renaming or sorting delivery options at checkout uses a Delivery Customization Function, which without Plus has to come from an App Store app. The estimate includes the base shipping setup. Please tell me what custom logic you have in mind.
  • Tax: each company location has its own tax ID and a setting to collect tax, not collect it, or collect it unless exemptions apply. The exemption list covers US state reseller exemptions and Canadian ones such as provincial PST. Company location exemptions work on all plans with B2B. Shopify does not store or check exemption certificates, so they stay in the ERP or in metafields. Shopify Tax covers the US and Canada, and Shopify does not file or remit Canadian taxes. Exemptions are set during the dealer import.

2.3 Dealer registration and companies

  • Shopify has a basic company account request form through the free Shopify Forms app. It creates a company, a location and a customer, and staff approve it by hand or with Shopify Flow. It does not assign a pricing segment and cannot add a person to an existing company.
  • Buyers cannot manage their company in their Shopify account: adding buyers, locations or changing permissions is "displayed, but can't be changed".
  • I built dealer registration on amplock.com: one form creates the customer and the company, links them and assigns one of three pricing segments, so dealers get their prices with no manual approval. For you the same, with approval by hand or by rules as you prefer, plus a page in the dealer's account where a company admin adds locations and buyers. The storefront sends the request to the app, and the app makes the change through the Admin API. No Plus needed.
  • Companies are unlimited, with up to 10,000 locations and 10,000 customers per company and 50 customers per location, on all plans with B2B. Creating companies.

3. Answers to your questions

A1. Relevant experience

  • Migrations: ZenCart to Shopify (Kuroobiya, alone, 14,004 orders imported and checked against the old system, 99.8% match), Magento to Shopify as lead developer (identical look, every feature and integration rebuilt), LightSpeed to Shopify.
  • I have not done a BigCommerce migration. I checked its export. Products export to CSV. Customers export with Company, customer group, several addresses each with its own company field, and form fields (BigCommerce customer export). Orders, customer groups, price lists, promotions and redirects come through its API. Passwords cannot be exported anywhere, and on Shopify customers sign in with a one-time email code, so no reset campaign. The Shopify side of the import I have done three times.
  • B2B: amplock.com (registration, companies, three pricing segments), b2b.deuxpardeux.com (a separate wholesale store next to the retail one), an outdoor wholesaler (dealer approval, minimum order value, bulk ordering across variants).
  • Custom apps: many, of different size, including B2B.
  • ERP and integrations, honestly: I have not built a full integration with a proprietary ERP. What I have done: product data and inventory sync with a third-party ERP for a Canadian cosmetics retailer with physical shops. For a warehouse that had no API at all, an automation over CSV files on FTP. Orders went out as CSV in the warehouse's format and mapping, fulfilments came back as CSV in another folder, and the app parsed them, matched them to Shopify orders and set fulfilment status and tracking links. Even with no API and a manual system, it ran on its own. Your ERP has developers who can describe its API, which is the easier case.

A2. Shopify Advanced and B2B architecture

Catalogs on Advanced: 3 active assignments across B2B markets, counted per market, and no catalogs for single companies (B2B catalogs). So I recommend:

  • Markets: a regional market for the US and Canada for retail, and a B2B market per country for dealers.
  • Catalogs: one base dealer catalog per country B2B market if US and Canadian dealer prices differ. That uses 2 of the 3.
  • Standard percentage discounts: one segment per pricing level, and one automatic discount per segment (Amount off products, percentage). The segment level is stored in a customer metafield on each buyer of the company, and the app keeps it the same for all buyers of one company. A customer can belong to only one company. Discounts in B2B can be limited to customer segments, and segments can filter by company, tag and metafield (segment filters).
  • Negotiated SKU prices for select dealers: an Amount off products discount on those variants, limited to that dealer's company segment. If the price is 100, the dealer's level gives 10% (90), and the negotiated price is 80, the discount is 20 off each item. On one line Shopify applies only "the best discount for the customer's cart", so the negotiated price wins over the level discount and they never stack.
  • Tested in my own test store: a discount for a segment and for a specific customer applies at B2B checkout when the buyer orders for the company. Of two product discounts on one line, the bigger one wins and they do not stack. A fixed amount applies per item. A new tag puts the buyer in the segment in under two minutes.
  • Showing dealer prices: discounts appear only in the cart. The theme can read the buyer's company, location and customer metafields, so it shows the dealer price on product pages, product cards and collections the same way the cart will calculate it. In my test store the product page already showed the catalog price for the signed-in dealer, and the discount appeared only in the cart, as expected.

The limits that decide how far this goes:

So the right way depends on how many pricing levels and negotiated prices you have:

  • A few levels and a limited number of negotiated prices: native discounts, managed from the app. Levels as automatic discounts. Negotiated prices as discount codes that the app creates per company, grouped by value, and shares between companies with the same price on the same products. The codes are saved on the customer and the theme applies them to the cart automatically, so dealers never type a code. Applying them happens in the cart, before checkout, because a checkout extension in your own app would need Plus. The app shows every dealer with all their discounts and links to each one in Shopify, so prices are managed in one place.
  • Individual prices for most dealers: this needs a Discount Function, one discount that reads each dealer's prices and prices every cart line. A custom app with Functions runs only on Plus. Public apps from the Shopify App Store with Functions run on any plan.

Without Plus there are two ways for the features Shopify keeps for Plus. I am not a fan of third-party apps, they are an extra dependency. But Shopify makes some non-Plus features available through paid App Store apps, and that is how it supports its ecosystem of app developers.

  1. A third-party App Store app. Fast, but the prices then live in that app as well, so it has to be convenient for your team, or prices end up in several places.
  2. Your own app, built by me and published on the App Store with limited visibility: not listed in search, installed by link. No dependency on someone else's app, but it goes through the full App Store review. Shopify does not state how long that takes, and in my experience it is not quick or easy, so it is a risk for the timeline.

Plus or Advanced for this project

  • What Plus unlocks here: unlimited catalogs and catalogs per company, your own Functions in a custom app (pricing, payment and delivery rules), deposits and partial payments, abandoned checkouts and gift cards for B2B, checkout extensions on the information, shipping and payment steps, separate US and Canadian business entities in one store, a 5 times higher API limit. B2B by plan, Markets by plan, API limits. Plus is 2,500 USD a month on a 1-year term, 2,300 USD on 3 years.
  • Where the plan makes no difference, the work and the hours are the same: companies, locations, permissions, B2B markets, catalogs with percentage and fixed prices, volume pricing, net terms, PO numbers, draft orders and invoices, Markets with USD and CAD, tax exemptions, the migration, the ERP integration and the dashboard.
  • What Advanced cannot do, and the workaround:
    • More than 3 catalog price lists: segments and discounts as above.
    • Own Functions: an App Store app, third-party, or your own app with limited visibility.
    • Deposits and partial payments: draft orders with payment terms, or invoicing through the ERP.
    • Separate US and Canadian legal entities: one entity selling in USD and CAD, with payouts in a second currency on Advanced, or two stores.

A3. ERP integration reliability

  • Shopify says webhook delivery isn't always guaranteed, order isn't guaranteed, duplicates happen, and after 8 failed attempts in 4 hours a subscription is removed (deliveries). Its own advice is reconciliation jobs. So events are the fast path, and scheduled reconciliation is the safety net.
  • Shopify's new Events (generally available since API 2026-10) trigger on specific fields, for example only an inventory quantity, which cuts noise. They use the same delivery as webhooks, so reconciliation stays. I would use them where they cover the resource.
  • How it works: incoming events go into a queue and are processed with retries. Every record keeps the other system's ID. Processing is idempotent, so a repeat never creates a duplicate. An order is never sent twice. Each field has one source of truth, agreed with your ERP developers, for example stock and prices from the ERP, orders from Shopify.
  • Reconciliation by schedule and by how much a gap costs: stock every 5 to 15 minutes, prices and products hourly, a full comparison of products, stock and orders daily. Retries run only for real gaps that reconciliation finds. The dashboard counts what went through normally, what failed and how each failure was handled.
  • Stock writes: from API 2026-04 Shopify requires an idempotency key and the expected previous quantity, and rejects a write if the stock changed meanwhile. That protects a fresh value from being overwritten by an old one.
  • Checks that the sync is healthy: daily control totals on both sides (number of SKUs, total stock, order count and totals per day), random SKU spot checks, and an alert when a flow goes quiet longer than usual.
  • Challenges I expect: whether the ERP can send events or has to be polled, and its API limits. Shared stock for retail and dealers, since Shopify cannot allocate stock by customer type. Orders edited after they reach the ERP. Mass price updates within the Advanced API limit of 200 points a second.

A4. Dealer companies: identify, deduplicate, map

  • The data to group by exists in BigCommerce: the Company field and customer group on each customer, several addresses with their own company field, billing and shipping company on orders. If B2B Edition is installed, it has a company entity of its own. One sample dealer record from you would settle how to group.
  • Matching keys: normalised company name (no Inc, Ltd, case or punctuation), email domain (not gmail and similar), phone, address, tax ID if present. Location addresses come from the customers' addresses and the shipping addresses used in recent orders.
  • Process, all by script: import a sample of 10 to 50 companies to a development store, check the data, fix the logic, look for duplicates, and repeat until it is clean. Then one full run, then a final check for duplicates and a short manual cleanup. Every record keeps its BigCommerce ID, so a rerun updates instead of duplicating. Doubtful matches are not merged automatically. They go to a list for your team to confirm. The pricing segment comes from the BigCommerce customer group.
  • Order of the import: products, customers, then companies with locations, with existing customers attached as contacts (companyAssignCustomerAsContact) and given permission on their locations (companyContactAssignRole), then orders. To buy for a company, a customer must be a contact of the company and have a permission on a location (company contacts).

A5. Historical orders and companies

  • A B2B order stores its company on the order (purchasingEntity), and the import takes the company location, the PO number and the original date. So each historical order is imported with its buyer and their company location. Then it shows in the buyer's history and in the company and location history. The only thing to make sure of is that all buyers of one dealer in BigCommerce end up in one company in Shopify.
  • Companies are created first and orders after, because the company location is set when the order is created. Moving an existing order to a company later is possible only in the admin, as the customer's full history into one location (migrating customers).
  • Migrating only part of the history: no Shopify page sets a limit on the number of imported orders. Imported orders send no emails to customers and do not touch stock. Staff "new order" notifications are turned off before the import, or every order sends one (Shopify migration guide). Orders older than 60 days need the read_all_orders scope. If only recent orders move and a buyer's older orders are needed later, they can still be added.
  • Order numbers: imported orders keep their BigCommerce number as the order name. Continuing the BigCommerce numbering for new Shopify orders is tricky, because Shopify does not let you change the starting number, but a workaround is possible. Tell me if it matters.
  • Pulling 100,000 orders from BigCommerce runs in the background, roughly 5 to 17 hours depending on your BigCommerce plan (its API limits). That is my estimate, not a BigCommerce figure.

A6. B2B checkout and payments

  • Native on Advanced: net terms of 7 to 90 days or due on fulfilment, manual payment methods such as bank transfer, invoices from draft orders, checkout submitted as a draft for review, saved cards per location, ACH in the US (features by plan). Manual methods show only when the order is paid at once (payment methods).
  • PO numbers: the dealer's buyer types their own internal purchase order number into an optional field in the B2B checkout, and it is saved on the order (B2B checkout). Draft orders created by your staff have it too. It is the dealer's reference, so their accounting can match your invoice to their purchase. Nothing to build beyond passing it to the ERP and the invoice.
  • Plus only: deposits, partial payments, payment requests per fulfilment.
  • Not available for B2B: Shop Pay, Apple Pay, Google Pay and other accelerated checkouts, and on Advanced gift cards and abandoned checkouts for B2B (B2B considerations).
  • Different payment methods for dealers and retail: Shopify has nothing native for this. It is done with a Payment Customization Function. Shopify has its own app for this, Checkout Blocks. It is built by Shopify and free for any store, but what it can do depends on the plan. On Plus it covers a lot: content blocks and custom fields on the checkout steps, hiding, renaming and reordering payment and shipping methods, custom discounts with detailed conditions. On Advanced it only adds content blocks to the Thank you and Order status pages. Shopify's words: "All other features of Checkout Blocks are available only to Shopify Plus." So without Plus it is a third-party App Store app. I tested one in my own test store on a non-Plus plan (Payfy, from 3.99 USD a month): a payment method was hidden for the signed-in dealer and shown to a retail guest. Other apps of this kind work the same way. Or your own app with limited visibility, as in A2.
  • Only the store owner can activate and change Shopify Payments, so that step is yours. I help with the rest of the payment setup. Which payment methods do dealers and retail need?

A7. Technology and architecture

  • Sync service: Node.js and TypeScript on Cloudflare Workers, with a queue, scheduled jobs and a database. Cheap and reliable, and Shopify's own CDN runs on Cloudflare (Cloudflare case study). Bulk work, such as the import and full reconciliation, uses Shopify bulk operations.
  • Admin dashboard: an embedded app in the Shopify admin. The screen itself is hosted by Shopify (App Home UI extensions), with the data coming from the sync service.
  • What the dashboard shows: the status of each flow (products, prices, stock, orders, customers, companies), the time of the last successful sync, how many events went through normally, how many failed and how each was handled (retry, reconciliation, manual), a list of errors with a retry button, reconciliation results and gaps, and a warning when a flow is quiet longer than normal. Dealers, their segments and their discounts are managed from the same app.
  • From 20 November 2026 a custom app installed on a store of another organization must have an IP allowlist. Cloudflare supports it, so I plan for it.

A8. Responsibilities and team

  • I am comfortable taking all of it: data migration, B2B setup, dealer pricing and registration, the ERP integration and dashboard, the storefront with improvements on the way, testing and launch. For the ERP side I need your ERP developers for the API and the data structure. The rest is mapping the data and a sync that closes its own gaps.
  • I work independently. I have two developers I work with, but I would not hand any of this project to them. I am free now, with no other active projects, and would work on yours full time. Agreeing every detail with a team would take time, and doing it myself makes it easier to control quality and to answer for the result.

A9. Timeline and costs

Under two months full time. The estimate, assumptions and add-ons are in section 4.

4. Estimate

Hour ranges include testing and fixing, at 60 USD an hour. Third-party app faults are separate hours, and I tell you before I start.

Area: needed to launchHoursUSD
Store setup: Markets, shipping, tax, payments, B2B checkout settings, onboarding13 to 19780 to 1,140
Data migration: merged catalog, customers, orders, redirects30 to 401,800 to 2,400
Storefront rebuild with UX, SEO and speed improvements (about one full-time week, depends on the size of the site and the improvements)35 to 402,100 to 2,400
Dealer companies: import, deduplication, mapping15 to 22900 to 1,320
Dealer registration and company self-service18 to 261,080 to 1,560
Dealer pricing: segments, discounts, prices on the storefront15 to 24900 to 1,440
ERP integration: products, stock, prices, orders, retries, reconciliation. Includes dense testing, edge cases, mass import tests and simulated failures of Shopify and its webhooks30 to 401,800 to 2,400
Admin dashboard18 to 261,080 to 1,560
Testing, cutover with a final delta run, launch fixes25 to 351,500 to 2,100
Documentation and AI agent setup4 to 6240 to 360
Total203 to 27812,180 to 16,680

Everything in this table is delivered as a complete, launch-ready first version, not an MVP. If something comes up after launch, I diagnose, monitor and fix it, tracked as extra hours. That is a matter of hours, not days or weeks.

Add-ons, not needed for launch. I estimate them once the scope is clear:

  • Cross-sells, upsells and recommendations from the order history.
  • Help Center and FAQ rebuilt from real customer questions.
  • Dealer pricing through a Discount Function in your own app with limited visibility, if many dealers have individual prices (plus the App Store review time).
  • A custom carrier rate service or custom shipping logic.
  • Business process automation after launch.

Assumptions

  • About Shopify: checked on Shopify's pages above, and the key pricing and checkout behaviour tested in my own test store.
  • About your requirements: a limited number of pricing levels and negotiated prices, the storefront replicated with improvements rather than redesigned, carriers available through existing apps, and an ERP with a usable API and a test environment. The questions below can move the estimate up or down.

5. How I work

  • Development on Shopify is first of all business: how easy the store is to run for the owner and the team, how easy it is for the buyer, and working with data. Code is a small part. Automating and simplifying how the business runs, and the recommendations I can bring, interest me even more.
  • I look at the project as someone who runs the business and the site, and I try to automate and simplify its management as much as possible. I do not wait for tasks. I think about the buyer and about the people who manage the store.
  • Once I have access, and if you want it, I will bring many recommendations for the site, the admin processes and the routine work that can be automated, based on data, analytics and online store marketing.
  • At the end you get infrastructure for an AI agent connected to the Shopify store, so your team can run many processes through it, and detailed documentation of how everything works. All code belongs to you. The project can be handed to another developer with everything described.
  • Communication is intensive in the first phase, while the data, the ERP and the pricing rules are agreed.
  • I am interested in long-term work. After launch I stay available to support the store. And if your agency has other Shopify projects, I am open to working on them once this one is finished successfully.

6. Questions

  1. The addresses of both stores. Should the design stay as it is, or is there room to improve? If the data shows the navigation can be improved, are you open to reworking it?
  2. How many pricing levels do you have, how many dealers have negotiated prices and on roughly how many SKUs, are they percentages or fixed prices, and where are they kept today? This decides the pricing approach and whether Advanced is enough.
  3. Do dealer base prices differ between the US and Canada?
  4. Which payment methods do dealers and retail customers need?
  5. What custom shipping logic do you have in mind?
  6. One sample dealer record from BigCommerce, and is B2B Edition installed on either store?
  7. How many years of order history move, and when can I see the ERP API documentation and a test environment?