操作指南 · B2B 门户

如何在 B2B 门户中配置批发买家权限

Wholesale customers rarely have one buyer. A dealer may have a junior buyer who builds carts, a purchasing manager who approves them, a finance user who only sees invoices and a branch manager who should order only for one location. This guide shows how to configure buyer roles, approver permissions and account-level guardrails in ChannelDock’s B2B Portal before orders reach fulfillment.

Map
account users and branches
Limit
catalog, prices and order actions
Approve
exceptions before pick-pack
Buyer permission mapControlled access
Account adminManage userscan invite buyers and assign roles
BuyerCreate orderscan submit carts for approval
ApproverRelease ordercan approve threshold exceptions
FinanceView invoicesno catalog or checkout access

Why this matters: BigCommerce documents separate permissions for submitting shopping lists for approval and approving them; Adobe Commerce requires company roles before purchase-order rules work; Shopify community threads show merchants still asking for finer B2B company-location permissions. The operational gap is not “can a customer log in?” — it is “can the right person do the right action without exposing every order, price list or warehouse queue?”

4 role typesadmin, buyer, approver, finance
Branch-levellocations and departments
Least accessonly what each user needs
Clean releaseapproved orders only

Before you start: model the customer account

Buyer permissions are easier to configure when you first draw the customer’s real purchasing structure. A B2B portal should mirror how the customer buys, but it should not copy every messy exception from email.

Company and location list

List each wholesale account, branch, ship-to address, billing address, VAT number and buyer group. If one customer has several stores or departments, decide whether users see only their own location or the full company.

Role and approval policy

Define who can browse, create orders, approve carts, manage users, view invoices and change delivery addresses. Tie this to your existing B2B order approval workflow.

Operational release rules

Decide when an order can move from portal submission to order management, stock reservation, pick lists and shipping labels. Permission design fails if unapproved orders still reach the warehouse.

Practical rule: start with fewer roles than you think you need. Four clear roles are safer than twelve nearly identical roles that sales, support and customers cannot explain six months later.

Step-by-step workflow to configure buyer permissions

Use this sequence when wholesale customers need self-service ordering, but your team still needs control over prices, approval thresholds, invoices and fulfillment release.

Inventory every customer-side user type

For each account, write down who actually participates in buying: owner, procurement manager, junior buyer, store manager, finance contact, receiving clerk and external sales rep. Capture what each person needs to see and what they must never change.

Common mistake: treating the first person who requests portal access as the account admin without checking whether they are allowed to invite colleagues or approve spend.

Create a minimum role set

Start with Account admin, Buyer, Approver and Finance. The account admin manages users. The buyer builds carts and submits orders. The approver releases carts above thresholds or outside normal rules. Finance sees invoices, open balances and order history without catalog-editing rights.

Common mistake: giving everyone full account access because it avoids setup work. That creates price exposure, duplicate orders and unclear responsibility.

Decide visibility by company, branch and user

A head-office buyer may need every branch order; a store manager may only need one shipping location. Set whether users can view company-wide orders, only their own orders, or orders for specific locations. This is especially important for franchise networks, dealer groups and multi-branch retailers.

Common mistake: letting branch users see prices, order history or delivery addresses for other branches when the customer expects separation.

Separate cart creation from order approval

Let buyers build repeat orders quickly, but route carts to an approver when they exceed spend thresholds, include restricted SKUs, use a new ship-to address or conflict with account terms. BigCommerce and Adobe Commerce both document this split because it matches real procurement behavior.

Common mistake: assuming “can place order” and “can approve order” are the same permission.

Protect prices, terms and documents

Buyer roles should not expose internal margin notes, draft price lists or other customer accounts. Connect the permission map to customer-specific pricing, payment terms and documents so users only see the prices and references meant for their account.

Common mistake: hiding the catalog but forgetting that invoices, quotes or exports reveal the same sensitive pricing.

Test the portal as each role

Log in as a buyer, approver, account admin and finance user. Try to create an order, change a delivery address, view another branch, approve a cart, download an invoice and trigger a reorder. Document what should happen and what must be blocked.

Common mistake: testing only the happy path with an admin user, then discovering after launch that a junior buyer can approve their own order.

Connect approvals to warehouse release

The final test is operational: unapproved orders should not enter pick waves, reserve scarce marketplace stock, print packing slips or generate carrier labels. Once approved, the order should flow into the same ChannelDock pick, pack and shipping process as other clean orders.

Common mistake: building perfect portal permissions while the warehouse still receives every submitted order as if it were approved.

The permission flow at a glance

Good B2B permissions create a narrow bridge between customer self-service and warehouse execution. The portal should let the customer move faster without bypassing commercial controls.

The safest B2B portal does not ask “who can log in?” It asks “who can commit stock, spend budget and release warehouse work?”

RoleCreate cartApproveInvoicesManage users
Admin
Buyer
Approver
Finance

Common wholesale permission pitfalls

  • Letting a buyer approve the same order they created when company policy requires a second person.
  • Giving finance users full catalog access when they only need invoices, credit status and payment references.
  • Using one shared login for a whole dealer account, which removes accountability and makes audit trails useless.
  • Forgetting branch restrictions, so a store manager can view another branch’s orders or negotiated prices.
  • Allowing submitted carts to reserve stock before approval, creating stock-outs for marketplace and retail channels.

Manual permission handling vs. ChannelDock B2B Portal

Manual B2B access control usually starts with “just email sales.” That works for ten orders a month, then breaks when buyers, branches and approvers multiply.

Without ChannelDock

  • Customers share logins or email spreadsheets, so approval history is unclear.
  • Sales manually checks who may order, which price applies and whether finance must approve.
  • Warehouse teams see submitted orders before the correct buyer-side and seller-side checks are complete.

With ChannelDock

  • Wholesale customers order in a branded portal with clear buyer roles and approval gates.
  • Orders that need review stay out of fulfillment until released by the right person.
  • Approved B2B orders flow into ChannelDock inventory, order handling and warehouse workflows without duplicate entry.

Explore the B2B Portal →

Wholesale buyer permissions FAQ

Buyer permissions define what a customer-side user can see and do: browse the catalog, create carts, submit orders, approve orders, view invoices, manage addresses or invite other users.

Start with four roles: Account admin, Buyer, Approver and Finance. Add branch-specific or sales-rep roles only after the basic workflow is proven with real customers.

Usually no, unless the order is below a defined threshold and company policy allows auto-approval. For higher-value or exceptional orders, keep cart creation and approval as separate permissions.

Permissions should decide when an order is safe to release. Unapproved carts should not enter picking, reserve scarce stock or generate labels. Approved orders can then flow into normal fulfillment.

Yes. Multi-branch customers often need branch-level visibility: a local manager orders for one store, while head office sees company-wide orders, invoices and approval queues.

ChannelDock’s B2B Portal gives wholesale customers a controlled self-service ordering route while your team keeps approval, order handling and fulfillment release connected in one operational system.

Related workflows to improve next

After buyer permissions are clear, tighten the approval, pricing and reorder workflows around the same B2B portal.

Approval workflows

Route submitted carts before they become warehouse work.

Read the how-to

Customer pricing

Keep price lists aligned with account permissions.

Read the how-to

Repeat ordering

Let buyers reorder without rekeying SKUs or quantities.

Read the how-to

B2B Portal

Give wholesale customers a controlled self-service route.

Learn more

Let wholesale buyers self-serve without losing control

Use ChannelDock’s B2B Portal to configure buyer roles, approval gates and clean order release before fulfillment starts.