Shopify B2B Buyer Self-Service vs Sales Rep Ordering: Build a Controlled Wholesale Workflow

Start with one question: who should create this order?

Do not begin by assigning software permissions. Begin by classifying orders. A routine monthly replenishment of the same 18 SKUs should usually be buyer-created because the buyer already knows the quantities and the company should not wait for a salesperson to retype them. A 300-unit request with a negotiated freight arrangement may be better handled by a rep. A large capital purchase might be buyer-created but still require internal approval before the merchant accepts it. Those are different routing decisions.

Write a short policy with three lanes: buyer self-service, rep-assisted, and exception. Buyer self-service covers repeatable orders that fit approved catalogs and commercial rules. Rep-assisted covers negotiated configuration, phone or email orders, and cases where the merchant is assembling the offer. Exception covers orders that breach an approval threshold, credit rule, overdue policy or another condition that requires a named reviewer.

This prevents the common failure mode where every buyer request becomes a sales ticket simply because a rep happens to own the account. Sales ownership and order authorship are not the same thing. A rep can remain responsible for the relationship while the customer handles predictable replenishment directly.

Use Shopify's native buyer path for ordinary B2B self-service

Shopify's current B2B plan documentation says companies, company locations, up to three B2B market catalogs on Basic, Grow and Advanced, net payment terms, quantity rules and self-serve ordering are available across the listed plans, with additional capabilities on higher plans. A company location gives the transaction its commercial context: the buyer can be associated with the correct location and the store can apply the relevant catalog, payment terms, addresses and checkout settings.

That native path is a strong default when the merchant does not need special procurement logic around the order. For example, a restaurant group can let an authorized location buyer reorder approved consumables under the location's normal terms. The buyer signs in, sees the B2B experience attached to that company location and creates the order without a salesperson rebuilding it.

Keep the permission model narrow. Shopify distinguishes customer-side location permissions from merchant staff permissions. The fact that a customer can order for a location does not make that customer an internal spending approver, and it does not give them merchant-admin rights. If your process needs requester-to-manager-to-finance approval inside the buying organization, that is a separate workflow question covered in ShopRadar's /blog/shopify-b2b-order-approval-workflow guide.

Use sales-rep access when the merchant needs to assemble or capture the order

Shopify documents a dedicated B2B sales-staff model. Merchants can create staff roles, assign sales staff to company locations, and restrict certain admin views to the company locations assigned to that user. Shopify specifically suggests Customers, Orders and Draft orders permissions when staff need to view accounts and take orders. Sales staff can then capture phone, email or in-person B2B requests as draft orders while using current product, pricing, customer and inventory data from the admin.

The restriction matters. Shopify notes that the assigned-company-location filter applies to Customers, Orders, Draft orders and Companies, while other admin pages are not filtered the same way. Its guidance even cautions merchants to think carefully before giving sales staff pages such as broad Analytics or Marketing access because those areas can expose data beyond the assigned accounts. A clean sales role is therefore not 'give the rep admin and hope they stay in their lane.'

Shopify currently allows up to 10 sales staff to be assigned to a company location, and sales-staff permissions are documented as available on all plans, although the number of staff accounts can depend on the merchant's Shopify plan. That makes native sales-assisted order capture useful even before adding a procurement app. The app decision begins when the order also needs buyer-side approval, company credit enforcement, structured repeat ordering, quote handling or commission logic.

Do not confuse a rep-created draft with buyer-side approval

A sales rep creating a draft order is a merchant-side action. Shopify can also require a company location's checkout orders to be submitted as drafts for merchant review. Neither fact, by itself, proves that the buyer's own organization approved the spend. A hotel purchasing coordinator may be allowed to prepare an order but still need a regional manager and CFO to authorize larger amounts before the supplier should treat the purchase as approved.

B2B Procurement OS is more explicit about that internal procurement pattern. Its current listing advertises multi-level approvals with conditional rules based on order amount and names Purchasing, Manager and CFO as the example chain. That is useful when self-service should continue for the buyer but spend authority changes with the size of the order.

Keep both sides visible in your policy. Buyer approval answers whether the customer's organization authorizes the purchase. Merchant review answers whether you accept the commercial transaction. A single order can legitimately require both, but they should not be represented as one vague status called 'approved.'

Put credit and net terms after approval, not inside the salesperson's memory

A rep may know that a customer is 'good for it,' but that is not a scalable credit policy. Shopify payment terms define when money is due. B2B Procurement OS's current listing adds a different control: per-company credit limits and net terms that can block over-limit or overdue orders. The distinction matters because an account can be within net-30 on every invoice and still create too much unpaid exposure with one more large order.

A safer sequence is: create or request the order, route required buyer approval, evaluate account credit policy, then let the merchant complete the order under the applicable terms. Sales can still advocate for an exception, but finance should be able to see that it is an exception rather than discovering it later in receivables.

For a detailed operating model, ShopRadar's /blog/shopify-b2b-net-terms-vs-credit-limits guide separates due-date policy from account exposure. The key point here is routing: neither a buyer nor a sales rep should be able to bypass the same account-level risk rule simply by using a different order-entry path.

Use buyer self-service for repeat orders and sales-assisted ordering for genuine exceptions

Consider an office-supply distributor serving 40 branch locations. The branches buy the same paper, cleaning products and break-room stock every month. Making a salesperson rebuild those baskets creates work without adding judgment. B2B Procurement OS advertises saved-list and CSV reordering, which is a stronger fit when buyers replenish from recurring lists or exported procurement sheets. ShopRadar's /blog/shopify-b2b-repeat-order-workflow guide goes deeper on native past-order duplication versus saved-list and CSV workflows.

Now consider the same account asking for 600 custom chairs with staged delivery. That is different. A rep may need to assemble the offer, coordinate a special price and confirm logistics. Shopify B2B draft orders support merchant-created orders and custom line-item pricing for negotiated cases. If the customer should initiate a volume-price request inside the portal, B2B Procurement OS also advertises volume quote requests priced from merchant data. The related /blog/shopify-b2b-quote-workflow guide explains when a published volume price, draft order or buyer-requested quote is cleaner.

The design principle is boring and powerful: automate the repeatable path, not the judgment-heavy exception. The salesperson should spend time where commercial judgment changes the outcome, not where the buyer is perfectly capable of reordering the same basket.

Treat commission attribution as a policy, not a side effect of who typed the order

B2B Procurement OS's current listing says merchants can assign sales reps and track commission from paid orders. That matters in a hybrid model because a buyer may place the order directly even though a salesperson owns the account relationship. If commission were based only on who manually created the order, self-service adoption could accidentally punish the sales team for moving customers onto a more efficient channel.

Before rollout, define attribution explicitly. Decide whether a rep owns a company, a company location, a specific order or only sales-assisted transactions. Decide how reassignment works when territories change. Decide how your business handles cancellations, refunds, partial payments and disputed orders. The public listing supports paid-order commission tracking, but it does not justify inventing automatic refund clawbacks or every commission rule your compensation plan might require. Verify those edge cases against the current product before depending on them.

A practical policy is to make account ownership independent from order-entry method. That lets the buyer self-serve without creating a channel conflict and keeps the rep focused on relationship management, quotes and exceptions. If your compensation model is more complex, document the gaps before migration rather than assuming 'commission tracking' means full incentive-compensation software.

Run five scenarios before expanding the workflow

Pilot with one representative company location and walk through the actual order paths. Scenario one is a normal buyer-created replenishment that fits catalog and terms. Scenario two is a phone or email request that a rep converts into a B2B draft order. Scenario three is a larger buyer-created order that should trigger internal approval. Scenario four is an account that is over its credit limit or already overdue. Scenario five is a negotiated quantity request that needs a quote before it becomes an order.

For every scenario, write down who creates the order, who can see it, who approves it, which account terms apply, whether the salesperson receives attribution, and what happens if the order changes before fulfillment. Do not call a pilot successful because the happy path reached checkout. The value of a procurement workflow is visible at the boundaries where ordinary ecommerce assumptions stop working.

As of September 15, 2026, B2B Procurement OS's official Shopify App Store listing shows Starter at $79 per month, Growth at $199 and Enterprise at $499, each with a 14-day free trial; annual prices are also listed with a 20% saving. B2B Procurement OS is available in English. If multi-level approvals, credit enforcement, self-service reordering, quote requests and paid-order rep commission belong in the same operating model, the Shopify App Store CTA below opens the authentic b2b-procurement-os listing in English through ShopRadar's shared locale helper.

• Default routine replenishment to buyer self-service.
• Use rep-created draft orders for genuinely assisted sales and negotiated exceptions.
• Keep buyer approval separate from merchant review.
• Apply the same credit policy regardless of who entered the order.
• Define rep attribution independently from order-entry method when that matches your compensation policy.
• Verify refunds, reassignment and other commission edge cases before relying on them operationally.

Apps mentioned in this guide

Frequently asked

Should every Shopify B2B order go through a sales rep?

Usually no. Routine replenishment is often a better self-service candidate, while negotiated, unusual or exception-heavy orders may benefit from sales assistance. The correct split depends on where human judgment actually changes the commercial decision.

Can Shopify restrict sales reps to assigned company locations?

Yes. Shopify documents staff roles that can restrict relevant Customers, Orders, Draft orders and Companies views to assigned company locations. Other admin areas are not necessarily filtered the same way, so build the role narrowly rather than granting broad access by default.

Is a sales-rep-created draft order the same as buyer approval?

No. A rep-created draft is a merchant-side order-entry method. Buyer-side approval answers whether the purchasing organization has internally authorized the spend. Some workflows need both layers.

Does B2B Procurement OS track sales-rep commission?

Its current Shopify App Store listing says merchants can assign sales reps and track commission from paid orders. Do not infer unlisted refund clawbacks, territory rules or other compensation logic without verifying those edge cases first.

Is B2B Procurement OS available in English?

Yes. B2B Procurement OS is available in English. ShopRadar routes the promotional CTA to the authentic b2b-procurement-os App Store slug with locale=en; that parameter selects the listing language and does not change installed-app language settings.