
A contractor applies for a trade account online. The request arrives in the sales inbox, but nobody knows whether the contractor is new, already buys through a branch, or should have access to the company’s negotiated prices. A salesperson creates another record to get the order moving. The buyer can now sign in, but the account history and terms are split across two records.
For Australian and New Zealand wholesalers and trade retailers, the decision is how much of B2B account onboarding to automate. The aim is to let eligible buyers place a correct first order while keeping existing accounts, confidential prices and payment terms under control. Start by deciding which applications are safe to process automatically and which need someone to resolve an exception.
Key Takeaways
- Separate identity checks, trade access and credit approval.
- Give existing buyers a route to their current account.
- Verify the first order against the intended ERP account.
Separate access, purchasing and credit
A trade account request can trigger three separate decisions. First, confirm the business and the applicant’s relationship to it. Second, assign the right buying location, permissions and prices. Third, decide how the business can pay. An applicant may qualify for trade purchasing and still need to pay upfront while finance reviews a request for credit.
Model these decisions explicitly in your workflow. An application can be received, waiting for a match, under review, or ready for a specific type of ordering. Staff should be able to see which decision is pending and who owns it. Give buyers an acknowledgement with a clear next step. Only send an invitation to order once the account is ready to do so under the approved policy.
Agree what an approved user can see before activating access. Some customers may need to browse their range and price list but should have no access to invoices, other branches or company administration. Check those boundaries in the storefront using test buyers. A screenshot of the correct catalogue from an administrator’s session cannot tell you whether a different buyer can see it.
Give existing buyers a route that avoids duplicate accounts

Design separate paths for a new business, a new buyer joining an existing business and a known customer who needs their first online login. These applicants can start from the same page, but they need different checks. The returning customer should not have to create a new company record simply to get online.
Ask account managers to list the clues they already use to match buyers. A trading name, a branch address, an existing account number and a known business contact may help. Use them as evidence with different levels of confidence. A similar name or matching email domain alone can be ambiguous, especially where several branches or franchisees share a brand.
New Zealand’s NZBN Primary Business Data guidance distinguishes legal business names from trading names and describes information available through the register. Use an identifier as an input to matching where appropriate. Establish a separate way to confirm that the applicant is authorised to purchase for that business and location.
If several candidates match, show staff enough context to choose the correct one. For a new buyer joining an established company, ask an authorised contact to confirm the relationship through a known channel. Avoid sending pricing or account history to an unverified address during that check. Give applicants who cannot supply a reliable identifier a manual path with a clear owner.
Decide which requests to automate
An invitation from a known account manager is often the easiest starting point. The relationship and account already exist, so the work is to verify the named buyer, attach the right location and confirm permissions. This can be an efficient pilot for a distributor whose existing customers already ask to order online.
A public application form works better when there is meaningful demand from new customers. Keep initial fields tied to the decision they support. A buyer’s name and contact details, business identity and intended location may be enough to route the request. Defer finance-specific questions to the credit process where they are needed. Ask sales to identify any form field they collect but never use before adding it to the launch scope.
Automated approval can suit a narrowly defined group with consistent access and upfront payment. Define the exact conditions and what a failed check does. For example, an unambiguous existing account match could route an invitation to a verified company administrator, while a conflicting branch record goes to manual review. Auto-approval carries more commercial risk if it also grants access to negotiated pricing, purchasing on account or a restricted assortment.
Keep a manual queue for cases that need judgement. A reviewer should see why a request was routed there, the records they can compare and the permissions they are being asked to approve. Set an internal response target and assign a backup owner. Review the queue before expanding automation. A frequent, well-understood exception may justify a better matching rule, while a rare exception may remain cheaper to handle manually.
Test the platform against each onboarding path
Shopify documents company account requests through Shopify Forms. A submission creates a company, location and customer for review, with ordering and B2B pricing unavailable by default until approval. The documented form does not add a buyer to an existing company. A store gated to approved B2B customers also needs another way for prospective buyers to reach a request form. Verify which options apply to your storefront and plan. OSE’s Shopify B2B guide for New Zealand trade retailers gives broader context for that platform decision.
Adobe Commerce documents company approval states for its B2B workflow. Storefront company requests await review, and administrators can approve or reject them. Adobe also describes company roles and storefront permissions that can support different buyer responsibilities. Demonstrate those controls on the intended deployment with your actual extensions and integration.
Evaluate both approaches with the same test script. Ask a provider to register a new account, add an authorised buyer to an existing branch and handle a duplicate application. Follow each case into the ERP and then back to the storefront. Request a demonstration of rejection, suspension and reinstatement as well. If a capability requires custom work, identify who will maintain it and how staff will handle a failure during trading hours.
Give each customer record a clear owner

Decide which system owns the approved company identifier, branch relationships, catalogue eligibility and payment terms. An ERP may own the commercial account while the commerce platform owns storefront login and permissions. Write down which updates flow each way and which system can override a value. That decision matters whenever two teams change the same account on the same day.
Set a rule for when a request becomes an ERP customer. Sending every unreviewed submission downstream can create records that finance never needs. Waiting until a first purchase may leave the storefront without a reliable way to validate prices or send an order. Choose the earliest point at which a confirmed account is operationally useful, then test creation and matching for that point.
Use a stable company and location reference once they exist. A retry should resolve to the same request or approved record, even when the first integration attempt succeeded and the response never came back. Give staff a way to reconcile stalled approvals. If the ERP has accepted the account but the storefront lacks the pricing group, the buyer should receive an accurate status and staff should know which step to repair.
Keep credit separate in the integration. An approved buyer may still have prepaid terms or be limited to a particular location. Test what the storefront displays when finance changes terms after activation. The operating policy for holds and exceptions is a separate decision covered in OSE’s B2B credit limits and ERP guide.
Prove the first order works

Build acceptance cases with account managers, finance and customer service. Include a new prepaid buyer, a current customer requesting access for another branch, a duplicate submission, an applicant with an unresolved identity and a buyer removed from an existing company. Write the expected access, catalogue and payment options for each before the demonstration.
For an illustrative test, give a Wellington buyer permission to order for one branch on upfront payment. Leave the company’s other branch and account-payment terms inaccessible. Have the buyer attempt to switch branches, open a direct link to a restricted product and submit an order. The expected result is one order on the Wellington account at its approved price, with the other branch and account payment unavailable. Record who signs off each result.
Follow an approved request through to the first accepted ERP order. Compare the account number, location, price and payment method against the expected values. Check what staff and the buyer see if an account update is delayed. Run the rejection and suspension cases from a different user session so you can see whether permissions have been removed where intended.
Use a small pilot group whose transactions you can reconcile. Track the time from complete application to usable access, the share of requests needing manual review and the number of duplicate records or first orders requiring correction. Measure how long each step takes separately. Faster form submission will not solve a queue that waits for account matching or price assignment.
Agree what would stop the pilot, such as showing one branch’s prices to another or accepting account payment before finance authorises it. Decide who can pause invitations or disable an automated approval path. Expand only when staff can support both the normal flow and the exceptions. If you need help designing that flow, bring representative account records and a first-order test set to an OSE discovery discussion. Use the examples to define the acceptance criteria and who owns each handoff.
Frequently asked questions
Start with manual review where matching or permissions are uncertain. Automate well-understood cases with explicit conditions and a fallback queue. Check what an automatic approval grants before enabling it, particularly access to prices and payment on account.
Trade access gives a named buyer approved purchasing permissions and catalogue access. Credit approval governs whether orders can be charged on account and on what terms. A business can approve trade purchasing on upfront payment while a separate credit decision is pending.
Route the request to a matching check using the known business and branch records. Once the applicant’s authority is confirmed, attach the named buyer to the correct existing account. Where there are multiple matches, have staff resolve the conflict before sending an invitation.
The platform can manage relevant storefront roles and approval states, depending on configuration. If the ERP controls customer identifiers, terms or prices, verify those values through the integration. Demonstrate that the first order is accepted against the intended account before rolling out.
Measure time to usable access, manual reviews, duplicate records and corrections on first orders. Break results down by new and existing account paths. This shows whether to improve the form, the review process or the handoff between systems.