B2B company locations workflow connecting branch buyers, approval rules, ship-to addresses and warehouse routing

B2B Company Locations: Route Branch Orders Cleanly

In September 2026, the most useful B2B portal question is no longer “can buyers log in and order?” It is “does the portal know which branch the buyer is ordering for before it promises price, stock and delivery?” Shopify’s own B2B documentation describes companies as parent organisations with one or more company locations, and says buyers with access to more than one location are prompted to choose the location they want to purchase for when logging in. That small login decision carries a large operational load.

For wholesalers, distributors and brands, B2B company locations are where portal convenience becomes warehouse execution. A national retail chain might have one parent account, 42 ship-to branches, three buyer groups, different order cut-offs by region and special assortments for only a subset of stores. If that structure is flattened into one “customer”, the portal looks modern but the back office still corrects prices, delivery addresses, PO references and stock promises by hand.

25
catalogs per location
Shopify Help Center notes this cap for company locations.
3
catalogs on non-Plus
Basic, Grow and Advanced B2B markets have tighter catalog limits.
1
branch = one operational promise
Price, stock, address and release rules must match the selected location.
Why company locations are the missing layer in B2B portals

Most ranking B2B ecommerce articles cover the visible features: customer-specific pricing, catalogs, order history, invoice downloads, quick reorder and payment terms. Those are important, but they miss the operational question that decides whether the warehouse receives clean work. A company location is the point where buyer identity meets sellable stock, allowed assortment, delivery address and release rules.

That matters because B2B buying rarely happens as one person placing one parcel order. A buyer can order for several branches. A finance user may need invoice access without purchasing rights. A store manager may reorder fast movers but not approve a high-value purchase. A sales rep may enter an order on behalf of a branch. The portal has to identify the correct location early enough to apply the right catalog, price list, tax settings, credit controls and fulfillment path.

The common mistake

A B2B company location is not just a delivery address. It is the rule bundle that decides what the buyer can see, which price applies, who can approve, which VAT and payment terms are valid, and how the warehouse should release the order.

What competitors say — and what they often leave out

Competitor content around B2B portals is increasingly specific. OrderEase talks about customer-specific products, pricing, pack sizes, minimums and terms. BigCommerce explains that company accounts can support buyer roles and a Buyer Portal. Shopify’s B2B help pages describe catalogs that can be assigned to company locations, with Shopify Plus allowing unlimited catalogs and direct assignment to specific company locations while lower plans have tighter active-catalog limits through B2B markets.

The gap is that most articles stop at “set up companies, catalogs and roles”. They rarely explain the branch-level failure modes that ecommerce operations teams see after launch: a buyer chooses the wrong location, a discontinued SKU is still visible for one branch, a catalog is right but the warehouse route is wrong, a branch exceeds credit but the order is still released, or the finance contact cannot match a shipment because the PO number was captured at parent-account level instead of branch level.

ChannelDock’s angle is warehouse-first. A portal should not simply create a prettier ordering screen. It should send cleaner orders into order processing, reserve stock consistently through inventory controls and connect with the broader integration layer that already handles marketplaces, webshops, carriers and ERP/WMS data.

The operational model: parent account, location, user and order line

A reliable B2B location setup has four separate records. The parent account stores the commercial relationship: legal entity, contract, payment risk and sales ownership. The location stores the branch reality: ship-to address, delivery window, local tax details, preferred carrier route, branch cut-off time and allowed fulfillment warehouse. The user stores what a person may do: browse, build a cart, approve, download documents or manage colleagues. The order line stores whether each SKU is valid for that location right now.

This separation prevents the classic portal trap: solving buyer login while leaving order execution ambiguous. If a buyer is attached to the parent account only, they can accidentally order for the wrong branch. If catalogs are attached to the wrong level, a branch sees products it cannot receive. If shipping rules are stored as sales notes, the warehouse learns about branch constraints too late. If credit and approval are checked after picking, the team can reserve stock for an order that finance later blocks.

  1. 1
    Map the customer hierarchy before portal setup
    List the parent account, every branch, every ship-to address, finance contacts, buyers, approvers and sales reps. Do this before importing users or assigning catalogs.
  2. 2
    Separate commercial rules from fulfillment rules
    Catalog, price, credit and payment terms belong to the commercial layer. Warehouse, carrier, cut-off and partial-shipment rules belong to the execution layer. The portal order needs both.
  3. 3
    Make location selection explicit at login
    If a buyer can purchase for multiple branches, force a branch choice before showing prices or availability. Otherwise the cart can inherit the wrong catalog or ship-to promise.
  4. 4
    Validate every line before warehouse release
    Check SKU visibility, pack multiple, MOQ, stock allocation, credit status, PO reference, ship-to address and cut-off time before the order becomes pickable.
  5. 5
    Keep one order queue for portal, EDI and manual orders
    A branch order should land in the same operational queue as marketplace, webshop and sales-rep orders so stock reservations and picking priorities stay consistent.
Catalog assignment is only half the promise

Shopify’s B2B catalog model is useful because it separates product visibility and price context from the public store. The documentation notes that catalogs can control pricing and product availability for B2B customers and can be assigned to companies, markets or company locations depending on plan and setup. For many wholesalers, that is the right starting point. But catalog assignment alone does not decide whether an order can be picked tomorrow.

The warehouse needs extra answers: which stock pool should this branch consume from, can the SKU be backordered, should a case pack be rounded up, does the branch accept partial shipments, which carrier service is allowed, and what happens after today’s cut-off? Those answers usually live outside the ecommerce catalog. They live in WMS, ERP, shipping rules, account notes and the practical knowledge of sales operations. The better portal design pulls those answers forward before the buyer submits the order.

Flat B2B account
  • One customer record for every branch
  • Sales reps fix addresses and prices manually
  • Warehouse sees notes instead of rules
  • Finance chases mismatched PO and invoice fields
Works only while order volume and buyer count are low.
Location-aware portalRecommended
  • Parent account with branch-level locations
  • Catalog, terms and ship-to rules assigned per location
  • Portal validates order lines before release
  • Warehouse receives pickable orders without spreadsheet context
Best for distributors, franchise networks and wholesalers serving multi-site customers.
A branch-aware routing checklist

Use a branch-aware checklist when testing a B2B sales portal. Start with three real customers: one simple single-location buyer, one multi-branch buyer and one high-touch buyer with special pricing or delivery rules. Build the same basket for each account and watch what changes before checkout. If nothing changes, the portal is probably hiding complexity instead of managing it.

  • Login context: can the buyer select the correct company location before seeing prices and availability?
  • Catalog context: are products, substitutes, discontinued SKUs and restricted items shown correctly by branch?
  • Price context: do contract prices, tier breaks and branch-level exceptions appear without sales-rep edits?
  • Quantity context: are MOQ, case pack, pallet and increment rules validated at line level?
  • Stock context: does the branch see sellable available-to-promise stock, not just global inventory?
  • Approval context: does the order route to the right approver by amount, category, buyer role or branch?
  • Fulfillment context: does the final order carry the warehouse, carrier, delivery window, partial-shipment rule and cut-off status?
  • Document context: are PO reference, VAT fields, invoice recipient and packing-slip requirements attached before release?

The best B2B portal is not the one with the longest feature list. It is the one that turns branch-specific buying rules into warehouse-ready orders without a Slack message, spreadsheet note or sales-rep correction.

Where this fits in ChannelDock

ChannelDock’s B2B Portal is strongest when the seller treats it as part of the order operation, not a separate storefront. A wholesale buyer places an order in a branded environment. ChannelDock then keeps the order connected to approval gates, stock visibility, document checks and fulfillment routing before the warehouse starts picking. That is especially useful for brands that already sell through marketplaces, a webshop, POS and B2B accounts at the same time.

The practical benefit is consistency. Portal orders should not compete with bol.com, Amazon, Shopify or manual orders in a hidden spreadsheet. They should join the same operational queue, with the same stock truth and the same exception handling. If one branch order needs approval, it waits. If another branch order is clean, it releases. If a SKU is unavailable, the buyer sees the issue before the warehouse team discovers it during picking.

For teams planning a rollout, start small: import the top 20 wholesale accounts, model their locations, validate the most common 200 SKUs and run two weeks of orders through both the old process and the portal. Measure manual edits per order, order-status questions, address corrections, credit holds after release and warehouse exceptions. Those numbers show whether the portal is actually reducing work.

What this means for B2B sellers
  • Treat each company location as a promise bundle: product access, price, address, payment terms, approval and fulfillment route.
  • Do not let buyers build carts before the portal knows which branch they are buying for.
  • Keep portal orders, EDI orders and manual sales-rep orders in one queue so stock reservations do not compete silently.
  • Measure exceptions by branch, not only by customer, because one weak location setup can create most of the rework.
FAQ
What is a B2B company location?
A B2B company location is a branch, ship-to unit or purchasing location under a parent wholesale account. In a good portal setup, the location controls catalog access, pricing context, delivery address, tax details, buyer permissions and fulfillment rules.
Why do company locations matter for wholesale order routing?
Because the same parent customer can have different branches with different products, prices, payment terms, delivery windows and warehouse routes. If the portal only stores one flat customer record, teams often fix those differences manually after checkout.
Should every branch have its own catalog?
Not always. Use shared catalogs for repeated product access rules and branch-specific overrides only where the agreement genuinely differs. Too many one-off catalogs become hard to maintain; too few create hidden order exceptions.
How should B2B portal orders connect to the warehouse?
The portal should release only validated orders into the warehouse queue: visible SKU, valid pack multiple, available stock, approved buyer, accepted payment terms, correct ship-to address and clear cut-off status.
Can ChannelDock help with this workflow?
Yes. ChannelDock's B2B Portal is built to move wholesale orders from buyer self-service into controlled order processing, inventory checks and fulfillment routing, so the portal does not become another disconnected inbox.
Conclusion

B2B company locations are the control layer that many wholesale portals under-design. They turn a parent customer into real operating units: branches, ship-to addresses, buyer permissions, catalog access, stock promises and fulfillment routes. Without that layer, ecommerce teams still need manual correction after checkout.

The winning setup is simple to describe and hard to fake: the portal knows the branch before it shows the promise, validates every line before release and sends the warehouse an order that is already priced, approved, documented and routable. That is the difference between a B2B portal that looks digital and one that actually removes work.