TL;DR
- What this guide covers: A practical, step-by-step process for designing B2B ecommerce workflows that support customers with multi-location and multi-department purchasing requirements.
- Who it’s for: eCommerce Managers and Ops Directors at B2B distribution and manufacturing companies.
- Platform covered: Adobe Commerce, integrated with NetSuite, SAP Business One, or Dynamics 365.
- What you’ll be able to do: Build a repeatable, structured approach to configuring enterprise account hierarchies, approval chains, location-specific catalogs, and budget controls inside your B2B storefront.
- Proof it works: Duke Industrial Equipment scaled multi-location self-service ordering to 35% of all orders and improved customer repeat rate from 58% to 72% with structured account access.
Enterprise buyers with five warehouses, three departments, and a dozen purchasers don’t fit neatly into a single customer account. When your B2B ecommerce platform treats them like one flat entity, you get misrouted orders, blown budgets, and frustrated ops teams fielding calls that should never have happened. This guide gives you a concrete process for designing B2B ecommerce workflows that handle multi-department buying and multi-location purchasing inside Adobe Commerce, connected to ERPs like NetSuite, SAP Business One, or Dynamics 365. By the end, you’ll have a clear blueprint for building a company account hierarchy in Adobe Commerce B2B that mirrors how your largest customers actually buy.
Why eCommerce Manager / Ops Directors Get This Wrong
Most teams start by replicating their offline ordering process in the ecommerce platform without rethinking the underlying account structure. The typical mistake is creating one company account per customer, then manually managing location-specific pricing, shipping addresses, and approval rules through workarounds: spreadsheets for budget tracking, email threads for approvals, custom code to restrict catalog visibility. This approach breaks the moment a customer adds a new location or reorganizes their purchasing team. The manual overhead compounds quickly, and the data in your ERP starts drifting from what’s happening on the storefront. Orders get shipped to the wrong warehouse. Pricing discrepancies trigger disputes. Your inside sales team spends more time fixing portal issues than closing new business.
The downstream cost is real. A distributor running 500+ B2B accounts with an average of three locations each can easily see order accuracy drop below 90% when account structures are flat. That translates to returns, re-ships, and credit memos that eat directly into margin. Labor waste is another factor: customer service reps handling “where’s my order” and “why was I charged this price” tickets instead of supporting high-value accounts.
Research shows that companies with well-structured digital commerce experiences see a 25% increase in customer satisfaction and a 20% boost in repeat purchases.
The gap between a well-designed multi-site B2B purchasing workflow and a cobbled-together one isn’t just operational: it’s a revenue problem. Duke Industrial Equipment faced exactly this. Multi-location self-service ordering scaled to 35% of all orders and customer repeat rate improved from 58% to 72% with structured account access after fixing it.
What You Need Before You Start
Before you touch Adobe Commerce configuration, make sure these prerequisites are in place. Missing any one of them will stall your workflow design mid-project.
- ERP data export of your customer hierarchy: Pull a complete list of parent companies, child locations, and department groupings from NetSuite, SAP Business One, or Dynamics 365. You need account IDs, billing/shipping addresses per location, contract pricing tiers, and credit terms. If this data is scattered across multiple systems, consolidate it first.
- Adobe Commerce B2B module enabled with admin access: Confirm you have the B2B module active (not just the base Commerce install) and that your admin user has permissions to create company accounts, configure approval rules, and manage shared catalogs.
- Stakeholder alignment on purchasing rules: Sit down with your eCommerce Manager, Ops Director, and at least one key customer’s procurement lead. Document the actual approval chains, budget limits, and catalog restrictions each department or location needs. Don’t assume: ask.
- Mapped approval workflows on paper: Before configuring anything, sketch out each approval path. Who can submit orders? Who approves? What dollar thresholds trigger escalation? This becomes your configuration blueprint.
- Integration middleware or connector in place: If you’re syncing account structures, pricing, and inventory between Adobe Commerce and your ERP, confirm your integration layer (whether that’s a middleware platform, custom API, or pre-built connector) is functional and tested.
- Catalog segmentation plan: Decide which products each location or department should see. This determines whether you need shared catalogs, category-level permissions, or both.
How To Design B2B Ecommerce Workflows for Customers With Multi-Location and Multi-Department Purchasing: Step-by-Step
Step 1: Audit Your Customer Account Data in the ERP
Start in your ERP, not in Adobe Commerce. Export your customer master data from NetSuite, SAP Business One, or Dynamics 365 and map every parent-child relationship. Identify which customers operate across multiple locations, which locations have independent purchasing authority, and which share a single billing entity. This audit often reveals inconsistencies: duplicate accounts, locations listed as separate customers, or departments with no clear hierarchy. Cleaning this data before import prevents cascading errors in your B2B ecommerce enterprise account structure. Flag any accounts where contract pricing, credit limits, or payment terms vary by location, because those differences will drive your configuration decisions in the next steps.
Step 2: Define Your Company Account Hierarchy in Adobe Commerce
Adobe Commerce B2B supports a parent-child company account structure out of the box. Use this to mirror your ERP’s customer hierarchy. Create a top-level company account for each parent organization, then add child accounts for each location or division. Assign a company administrator at the parent level who can manage users, and designate location-level admins who control purchasing for their site. The company account hierarchy in Adobe Commerce B2B is where you establish the organizational backbone: get this wrong, and every downstream workflow (approvals, catalogs, budgets) inherits the problem. A common pitfall is making the hierarchy too flat or too deep. Match the real org chart, not an idealized version of it.
Step 3: Configure Role-Based Permissions and User Access
Within each company account, create roles that reflect actual purchasing behavior. A typical setup includes a Purchaser role (can add to cart and submit for approval), an Approver role (can approve or reject orders up to a defined threshold), and a Company Admin role (full account management). Adobe Commerce lets you assign these roles at the company or division level, which means a regional warehouse manager can approve orders for their location without seeing another location’s activity. This is where B2B ecommerce multi-department buying becomes practical rather than theoretical. Map each role to specific permissions: catalog access, order history visibility, credit usage, and approval authority. Test with real user scenarios before going live.
Step 4: Set Up Approval Rules and Budget Controls
Approval workflows prevent unauthorized spending and keep procurement aligned with internal policies. In Adobe Commerce, configure approval rules that trigger based on order value, product category, or user role. For example, any order over $5,000 from a branch purchaser might require regional manager approval, while orders under that threshold auto-approve. If your ERP manages budget allocations by department or cost center, sync those limits into Adobe Commerce so buyers see their remaining budget before checkout. This two-way sync between your ERP and storefront is critical: without it, approvals happen in a vacuum, disconnected from actual financial controls. HumCommerce has seen quote turnaround times drop from 3-5 days to just hours when approval logic is automated and tied directly to ERP rules rather than handled through email chains.
Step 5: Assign Shared Catalogs and Location-Specific Pricing
Not every location needs access to every product. A manufacturing customer’s East Coast facility might order raw materials, while their West Coast plant orders packaging supplies. Use Adobe Commerce’s shared catalog feature to create catalog segments tied to specific company accounts or divisions. Layer in customer-specific pricing by connecting your ERP’s contract rates and volume tiers to each shared catalog. This ensures that when a buyer at Location A logs in, they see only the products and prices relevant to them. Custom pricing rules integration has been shown to deliver the highest conversion lift at 37% among all B2B portal capabilities: it’s not a nice-to-have, it’s a revenue driver.
Step 6: Integrate ERP Sync for Orders, Inventory, and Account Updates
Your multi-site B2B purchasing workflow only works if the data flowing between Adobe Commerce and your ERP stays current. Configure real-time or near-real-time sync for order placement (so the ERP processes orders immediately), inventory levels (so buyers see accurate stock by warehouse location), and account updates (so new locations or changed credit terms propagate automatically). In NetSuite, this typically runs through SuiteCloud connectors or middleware. SAP Business One and Dynamics 365 integrations often use pre-built connectors or custom API endpoints. The ERP is the single source of truth for contract pricing, credit limits, and product master data: your ecommerce platform should read from it, not override it.
Step 7: Test With a Pilot Customer and Iterate
Pick one multi-location customer and run the full workflow end to end. Have their purchasers log in, verify they see the correct catalog and pricing, submit orders, and route them through approvals. Check that the ERP receives the order with the correct ship-to address, pricing, and cost center allocation. Document every friction point. Common issues at this stage include approval notifications not reaching the right person, inventory counts lagging behind real-time, and child accounts inheriting permissions they shouldn’t have. Fix these before rolling out to your full customer base. A structured pilot with one account saves you from fielding hundreds of support tickets after a broad launch.
3 Mistakes to Avoid
Mistake 1: Building a Flat Account Structure for Complex Customers
Treating a multi-location enterprise buyer as a single account forces you into manual workarounds for everything: shipping addresses, pricing, approvals, catalog access. This creates order errors and frustrates buyers who can’t self-serve. Instead, invest the time upfront to build a proper parent-child hierarchy in Adobe Commerce that mirrors your customer’s actual organizational structure.
Mistake 2: Disconnecting Approval Logic From ERP Financial Data
Setting up approval rules in Adobe Commerce without syncing budget limits and credit terms from your ERP means approvals happen without financial context. Orders get approved that shouldn’t, or buyers hit checkout only to discover their credit is maxed: both outcomes erode trust. Connect your approval workflows to real-time ERP data so every approval decision is grounded in actual financial standing.
Mistake 3: Giving Every Location Access to the Full Catalog
A blanket catalog approach overwhelms buyers with irrelevant products and increases the risk of incorrect orders. When a maintenance team at one facility can order components meant for a different plant’s production line, you’re inviting returns and re-ships. Use shared catalogs and category permissions to restrict visibility by location or department from day one.
Real Example: Duke Industrial Equipment
Duke Industrial Equipment, a multi-branch industrial distributor, struggled with fragmented ordering across locations: buyers at different branches were placing orders through email, phone, and an outdated portal that treated every location as the same account, making multi-location B2B ecommerce purchasing chaotic and error-prone.
After getting this right:
- Multi-location self-service ordering scaled to 35% of all orders
- Customer repeat rate improved from 58% to 72% with structured account access
The specific changes centered on restructuring their Adobe Commerce B2B instance with a proper company account hierarchy: each branch became a child account under the parent company, with its own catalog visibility, approval chain, and shipping configuration. Their ERP integration was reconfigured so that contract pricing and inventory availability synced per warehouse location rather than at a global level. Branch managers gained the ability to approve orders for their teams without escalating to corporate procurement, which removed a bottleneck that had been adding 1-2 days to every order cycle.
The result wasn’t just operational efficiency: buyers actually preferred using the portal because it finally reflected how they worked.
Need Help Implementing This?
Designing B2B ecommerce workflows for customers with multi-location and multi-department purchasing is straightforward in concept but genuinely complex to configure correctly. The interplay between Adobe Commerce’s B2B module, your ERP’s customer and pricing data, and the real-world purchasing behavior of enterprise buyers creates dozens of configuration decisions that compound on each other. Getting one wrong can break the experience for your highest-value accounts.
HumCommerce specializes in exactly this type of implementation for B2B distributors and manufacturers running Adobe Commerce with NetSuite, SAP Business One, or Dynamics 365. We’ve built these workflows for companies with 50 locations and companies with 5, and the process is different every time because the buying complexity is different every time. Our approach is ERP-first: we design the storefront to behave like part of your operations, not as a disconnected frontend.
Talk to a HumCommerce consultant about your multi-location B2B ecommerce purchasing setup.
