Yes. Shopify can support a combined B2B and DTC ecommerce model, including B2B companies, catalogs, pricing, payment terms, delivery options, and integrations with ERP systems such as NetSuite. The harder part is usually not building the storefront. It is translating the commercial rules behind the storefront into an architecture that Shopify, NetSuite, and the integration layer can handle consistently.
The Easilocks implementation is a good example. The project involved more than moving products and customers to Shopify. The implementation had to account for B2B catalogs and pricing, DTC pricing, customer-specific discounts, VAT rules, payment methods, delivery methods, shipping prices, customer migration, approval workflows, and NetSuite integration.
That is an important distinction for enterprise ecommerce projects. A store can look simple to a customer while a large number of rules are evaluated behind the scenes before an order is completed.
Key Considerations
- B2B and DTC pricing: B2B customers can have catalogs and pricing that differ from the standard DTC experience.
- Customer-specific discounts: A trade customer may need an additional commercial discount beyond the standard catalog price, which needs to be designed separately from DTC promotions.
- Delivery methods and shipping prices: B2B and DTC customers may need different delivery options or shipping charges based on customer type, location, order conditions, and business rules.
- Payment methods and payment terms: Trade customers may use different payment methods or net terms from DTC customers. Shopify now provides native B2B payment-term capabilities, while more specific checkout rules can be implemented with Shopify Functions.
- VAT and tax rules: Tax treatment may depend on customer type, VAT registration, destination, and the merchant’s tax registrations. This needs to be validated against the actual tax requirements and ERP setup.
- Customer migration: B2B migration requires more than a CSV import. Existing customers, companies, addresses, VAT information, duplicate records, and customer communication all need to be handled carefully.
- ERP ownership and synchronization: The architecture should define which system owns products, inventory, pricing, customers, orders, tax mapping, and fulfillment information.
What Shopify Supports
Shopify has native B2B capabilities that can cover a substantial part of an enterprise wholesale workflow. Shopify B2B uses companies and company locations to manage business buyers, and company locations can have their own pricing, payment terms, tax settings, addresses, and contacts.
Shopify also supports B2B catalogs, quantity rules, and volume pricing. On plans that support B2B, the available catalog functionality depends on the plan, with Shopify Plus providing more extensive catalog assignment capabilities.
B2B Companies and Company Locations
B2B customers are represented through companies and company locations. This is important because the company location can carry business-specific settings such as pricing, payment terms, tax information, and delivery details.
B2B Catalogs and Pricing
B2B catalogs determine which products a business customer can access and what prices they see. Shopify supports fixed prices, overall catalog adjustments, quantity rules, and volume pricing.
Shopify’s current documentation also allows multiple catalogs to be assigned to a company or company location in supported configurations. This means catalog strategy should be designed around the actual pricing model rather than assuming that every customer must have exactly one catalog.
Quantity Rules and Volume Pricing
Shopify supports minimum, maximum, and increment quantity rules, as well as volume pricing for B2B purchases. This can be useful for wholesale businesses where products are sold in cartons, packs, or other required quantities.
Payment Terms and Delivery Options
Shopify B2B supports payment terms and company-level checkout configuration. Shopify also provides Payment Customization Functions that can hide or reorder payment methods and apply payment terms based on conditions such as buyer identity.
Similarly, Delivery Customization Functions can rename, reorder, or hide delivery options based on checkout information such as buyer identity, products, and delivery address.
ERP Integration
Shopify supports integration with external ERP systems, including NetSuite. Shopify’s ERP documentation describes synchronization patterns for products, inventory, orders, customers, pricing, and fulfillment, while the exact ownership and synchronization model depends on the business architecture.
What Usually Requires Custom Development or Additional Architecture
Native Shopify B2B functionality can handle many requirements. Custom development is usually needed when business rules go beyond standard configuration, when several rules need to interact, or when Shopify and the ERP have different data models.
Customer-Specific Discounts on Top of Catalog Pricing
One of the important requirements in the Easilocks implementation was the distinction between the standard B2B catalog price and the final commercial price offered to an individual customer.
A B2B customer may receive a catalog price and then have an additional customer-specific commercial agreement. The implementation therefore needed to treat the base catalog price, additional discount rules, and DTC promotional pricing as separate concerns.
Shopify now supports B2B discounts and Discount Functions, but the exact implementation depends on how customer-specific agreements are stored and how they should interact with catalog and volume pricing.
Different Delivery Methods and Shipping Prices
Shipping was another area where the requirements became more detailed during implementation.
The business needed to consider different delivery methods and shipping prices for B2B and DTC customers. Instead of treating shipping as one global rule, the implementation needed to consider customer identity and the conditions under which a particular delivery option should be shown.
Shopify’s Delivery Customization Function API provides a current platform mechanism for hiding, renaming, or reordering delivery options using checkout information such as buyer identity and delivery address.
Different Payment Methods and Net Payment Terms
Payment requirements also differed between customer types.
The project included requirements around Stripe, Shopify Payments, and customers using net payment terms. The team also needed to distinguish between a payment method and a customer’s commercial payment terms. They are related, but they are not the same thing.
Shopify’s current Payment Customization Function API can customize payment methods and set payment terms, including net, fixed, and event-based terms. This provides a platform-level mechanism for implementing rules that depend on buyer identity or other checkout conditions.
VAT and Tax Configuration
VAT was one of the areas that required the most investigation during the project.
The requirements included different treatment for B2B and DTC customers, VAT-registered versus non-VAT-registered customers, and different regions, including the UK, Northern Ireland, Ireland, the EU, and international destinations.
During the project, the team tested Shopify’s registration-based tax behavior and found that Shopify could automatically apply country-specific rates in many cases. The business requirement for a fixed rate across all EU countries did not match that country-specific calculation model.
The broader lesson is that tax automation and business requirements are not always the same thing. Shopify can automate tax calculation based on its tax configuration, but the merchant remains responsible for determining where it needs to collect tax and whether its configuration matches its tax obligations.
For an enterprise Shopify and NetSuite implementation, tax rules should therefore be validated end-to-end with the client’s tax advisor or relevant tax authorities and then mapped consistently into Shopify and NetSuite.
B2B Sign-Up and Approval
The existing B2B process included an approval step. The Shopify implementation therefore needed to determine how a prospective trade customer submits a request, how the business approves the customer, and when the customer becomes a B2B company or company location.
Shopify supports B2B customer access workflows, but businesses with an existing approval process should document the exact workflow before implementation so that approval, account creation, and company assignment happen in the correct order.
ERP-Specific Payload and Order Requirements
NetSuite also introduced requirements around identifying B2B and B2C customers in integration data and handling order information.
This is where enterprise integration design becomes important. Not every desired field can simply be added to a standard Shopify API response. Where Shopify’s data model differs from the ERP’s requirements, the solution may need field mapping, custom integration logic, metafields, Functions, or another integration mechanism.
Folio3 Experience: Where the Real Complexity Appeared
The Easilocks project shows why enterprise ecommerce migrations are better treated as business-process projects rather than simple platform migrations.
The original work involved moving an established ecommerce operation to Shopify and connecting it with NetSuite. As the implementation progressed, the team had to work through requirements that affected pricing, checkout, tax, payments, shipping, customer onboarding, and integration.
For example, a B2B customer could not simply be given access to a B2B catalog and considered finished. The business also needed to consider whether that customer had an additional discount, which payment method they could use, what payment terms applied, which delivery methods were available, what shipping price should be charged, and how VAT should be handled.
This is the kind of detail that can significantly change an ecommerce architecture, even when the storefront itself looks relatively simple.
Customer Migration
Customer migration was another area where the implementation required careful controls.
- Existing Shopify customers should not be duplicated.
- A company should not be created when the corresponding customer already exists in Shopify.
- Customer addresses from the source platform need to be mapped correctly into Shopify’s address structure.
- The migration should not unintentionally send emails to live customers.
- Migration scripts should provide logging so failed customer records can be identified and reviewed.
- Currency and exchange-rate considerations should be finalized before migrating B2B customers where those values affect order calculations.
Recommended Architecture
For an enterprise Shopify and NetSuite implementation, a useful way to think about the architecture is to give each platform a clear responsibility.
| Layer | Typical Responsibility |
| Customer | B2B or DTC buyer |
| Shopify | Storefront, catalog presentation, checkout, B2B commerce, and customer-facing commerce configuration |
| Custom Shopify logic | Customer-specific pricing, discount, shipping, and payment rules that require additional logic |
| Integration layer | Data mapping, synchronization, transformation, logging, and error handling |
| NetSuite | ERP processes, operational data, and business processes that remain in the ERP |
Before development starts, the implementation team should be able to answer:
- Which system owns product data?
- Which system owns inventory?
- Where is the standard B2B price maintained?
- Where are customer-specific discounts maintained?
- How are DTC promotions calculated?
- Which system determines payment terms?
- How are shipping methods and prices determined?
- Which system is responsible for VAT calculation and tax mapping?
- How are B2B customers identified in orders?
- What happens when a synchronization fails?
When Shopify May Not Be the Right Fit
Shopify is not automatically the right answer for every enterprise ecommerce business. The platform should be evaluated against the client’s actual commercial and operational requirements.
A different architecture may need to be considered when the business has highly specialized pricing, procurement, tax, checkout, or ERP-driven workflows that cannot reasonably be implemented within Shopify’s platform model.
The better question is not “Can Shopify do everything?” It is “Which parts of the commerce process should Shopify own, which should remain in NetSuite, and what integration and custom logic are needed between them?”
What We Learned From the Easilocks Project
The biggest lesson from the Easilocks implementation is that enterprise ecommerce complexity is often hidden behind a simple storefront.
A customer may see a product, add it to the cart, and complete checkout. Behind that experience, however, the system may need to decide which catalog applies, which price the customer should see, whether an additional customer discount applies, which payment methods are available, which delivery methods are available, how much shipping should cost, and which VAT rules should be applied.
Those decisions become even more important when Shopify needs to work alongside an ERP such as NetSuite.
For businesses considering a Shopify migration, the practical takeaway is to document these rules before development begins. The more clearly the team defines customer types, pricing ownership, tax ownership, payment terms, shipping logic, and ERP responsibilities, the less likely the project is to discover major architectural changes late in the implementation.
Frequently Asked Questions
Can Shopify support both B2B and DTC customers on the same store?
Yes. Shopify supports B2B and DTC selling in the same blended store. B2B customers can be managed through companies and company locations, with B2B-specific catalogs, pricing, payment terms, and delivery configuration.
Can Shopify integrate with NetSuite?
Yes. Shopify supports NetSuite integration through Shopify’s ERP ecosystem and APIs. The important implementation decision is how products, customers, pricing, inventory, orders, fulfillment, and financial data are divided between the two systems.
Can B2B customers have different prices from DTC customers?
Yes. Shopify B2B catalogs can provide B2B-specific product availability and pricing. Additional customer-specific discounts can be handled through B2B discount capabilities or custom logic, depending on the commercial rules.
Can Shopify support customer-specific B2B discounts?
Yes, but the exact approach depends on how the discount is defined and how it needs to interact with catalog pricing, volume pricing, and other discounts. Shopify provides B2B discounts and Discount Functions for more granular rules.
Can B2B customers have different shipping methods from DTC customers?
Yes. Shopify B2B supports company-level delivery configuration, and Shopify Functions can customize which delivery options are shown during checkout based on available checkout information.
Can B2B and DTC customers use different payment methods?
Yes. Shopify supports B2B payment configuration, and Payment Customization Functions can hide, reorder, or otherwise customize payment methods based on checkout conditions.
Can Shopify support net payment terms for B2B customers?
Yes. Shopify supports B2B payment terms, and Shopify’s Payment Customization Function API can set payment terms based on buyer identity and other conditions.
Can Shopify apply different VAT rules to B2B and DTC customers?
Tax behavior depends on the merchant’s registrations, customer and transaction details, destination, and Shopify’s tax configuration. A business should validate the required tax treatment before relying on automated tax calculation.
How can a Shopify store identify B2B orders?
In the Easilocks implementation, the company relationship was used as the practical distinction: customers associated with a company were treated as B2B, while customers without a company relationship were treated as DTC.
What should be decided before integrating Shopify with NetSuite?
Define data ownership and synchronization rules for products, inventory, pricing, customers, companies, orders, payments, tax, fulfillment, and errors before development begins.
Planning a Shopify B2B or NetSuite Migration?
Enterprise ecommerce projects become difficult when pricing, customer-specific discounts, VAT, payment terms, shipping rules, and ERP processes all have to work together. If you’re evaluating Shopify for B2B, DTC, or a combined commerce model, our team can help map the requirements, define system ownership, and design the integration architecture before development begins.
Talk to our ecommerce team about your Shopify and NetSuite requirements.
People Also Ask
- Can Shopify handle both wholesale and direct-to-consumer customers on the same store?
- How do you integrate Shopify with NetSuite for B2B ecommerce without losing pricing and tax rules?
- Which agencies have experience migrating enterprise B2B ecommerce to Shopify Plus with ERP integration?
- Can Shopify support customer-specific pricing, payment terms, and VAT rules for trade customers?
- How do you handle B2B customer approval workflows and account setup in Shopify?
