A buyer signs into the dealer portal, sees the correct products and submits an order. The warehouse receives it immediately. Only later does finance notice that the order used another branch's terms, bypassed an account hold or selected an address nobody had approved. The login worked; the business authorisation did not.
For a Toronto wholesaler commissioning a B2B portal, the important integration is between identity, commercial rules and order release. A customer organisation can have several locations, contacts and purchasing arrangements. The portal needs to represent those distinctions without asking employees to untangle them after goods have already been picked.
Start with the branch that is buying
Shopify's CompanyLocation API documentation describes location-specific purchasing context, including catalogues, pricing and checkout settings. Its B2B application guide explains the relationship between companies, locations and contacts. These are useful primitives if Shopify is part of the proposed solution; verify the features available in the merchant's actual plan and configuration.
Your ERP may use a different hierarchy. A parent organisation could map to several customer accounts, ship-to codes and billing relationships. Write that mapping down before developing the login screen. Otherwise the team may build an attractive portal whose definition of “customer” cannot express how the business trades.
Keep purchasing location visible during browsing, checkout and order history. If a person switches branches, re-evaluate prices, permitted addresses and relevant permissions. Do not leave an old basket implicitly carrying authority from the previous branch.
Separate permission from commercial approval
There are at least three different questions. Is this person allowed to act for this location? Is this requested order within their purchasing authority? Is the business willing to release the order under the account's present commercial conditions?
The first belongs to identity and membership. The second may depend on an internal buyer approval process. The third might involve credit policy, overdue balances, restricted products or a manual finance decision. Combining all three in a single enabled-account checkbox creates exceptions that staff will eventually manage outside the system.
Use explicit states such as draft, submitted, awaiting buyer approval, awaiting account review, accepted and released. Choose names the operations team understands. Preserve the reason an order is waiting and the role responsible for moving it forward. A customer should see a useful status without seeing confidential internal finance notes.
Decide who owns the current answer
If finance manages account holds in the ERP, the portal should not maintain a conflicting editable copy. It can display the latest known status with a freshness indicator, but release decisions need an agreed policy for source availability and timing.
For an illustrative distributor, imagine that a branch submits an order just as finance changes its account status. Define which event wins and when the decision becomes binding. A workflow that checks status only when the customer logs in may be using an answer from hours earlier when fulfilment begins.
Record the commercial decision applied to each order, the relevant rule version and the source response used. This makes later investigation possible without pretending that today's customer record proves yesterday's approval was valid.
Keep terms, payment and release distinct
Shopify's payment-terms guidance shows that terms can be configured for company locations and draft orders. Terms describe an arrangement for payment; they do not automatically implement your credit policy or every approval your warehouse requires.
The integration should say when it creates an ERP order, reserves stock, captures a payment or authorises fulfilment. Decide which actions are reversible and who handles a failure after another system has already acted. Repeating a submission after a timeout must not create a second sales order.
If one item requires review, decide whether the whole order waits or whether a split is permitted. Show the resulting delivery and payment implications to the buyer. Silent splits create a new support problem even when the systems remain technically consistent.
Give buyers an explanation they can use
A rejected checkout that merely says “contact support” transfers every exception to a person. Where appropriate, offer a clear next action: request an approved delivery address, ask the company's approver to review the order, or wait for an account review already in progress.
Preserve the basket and its revision while the issue is resolved. If prices or availability change before approval, show what changed and obtain any required reconfirmation. An approval should refer to a defined order revision, not an editable basket that can be altered afterwards.
The customer portal also needs a dependable handoff to staff. Include the order reference, company location and outstanding decision in the support view. Avoid asking the customer to repeat information that the software already has, while ensuring staff see only the accounts their role permits.
Buy a complete order path before a catalogue redesign
Scope an initial delivery around one customer hierarchy and a representative set of orders. Include a buyer with access to two branches, an account put on hold mid-process, an unavailable ERP and an approved order changed before fulfilment. Test that an unauthorised branch cannot retrieve another branch's documents through a direct URL.
Ask for evidence that every submitted portal order can be reconciled to its downstream counterpart or an owned exception. Require a documented procedure for restarting a failed integration without duplicating orders. Include source-system administrators and finance in acceptance, because developers cannot invent the commercial policy.
Success can mean fewer orders rekeyed, fewer unowned account exceptions and faster resolution of purchasing questions. Establish the baseline first. The goal is a portal that makes a valid purchase easier and an invalid purchase understandable, not a promise that every order will pass automatically.
Use our customer portal security brief and CRM/ERP integration scope guide to prepare supplier discussions. Our custom software development service connects commerce with business operations. Discuss your B2B order workflow with your customer hierarchy and the order exception your team handles most often.