B2B Portal Development in Australia: Simplify Wholesale Ordering and Account Management
Planning a B2B ordering portal in Australia: account pricing, GST and tax invoices, Peppol, bulk orders, approvals, ERP and freight integration, and MVP scope.
What should an Australian B2B portal do?
A B2B portal should let each trade customer see their own catalogue and prices, order in bulk or repeat past orders, route orders through their approvals, track delivery and access correct tax invoices and statements, with orders flowing straight into your ERP or accounting system. In Australia that also means clear GST treatment, invoices that meet ATO requirements, optional Peppol eInvoicing, freight options that reach regional customers and trade terms that survive unfair contract terms rules.
This guide is an Australian decision page for wholesalers, manufacturers and distributors. It covers account-specific pricing, catalogues and bulk orders, approvals, ERP and inventory integration, customer-specific terms, reordering and tracking, permissions and reporting, and MVP scope. For depth on each area, it links into our generic B2B guides, starting with wholesale ecommerce websites.
If your customers mostly need service self-service rather than ordering, read customer portal development. Nothing here is tax or legal advice.
Key takeaways
- Start from how your best customers order today: email, phone, spreadsheet or rep visits.
- Account-specific catalogues and prices are the core feature; get the data model right first.
- Make GST treatment explicit everywhere, and ensure invoices meet ATO tax invoice requirements.
- Treat the ERP as the source of truth for prices, stock and invoices. Confirm its integration capabilities before promising portal features.
- Design for approvals and multiple users per customer from the start.
- Plan freight for metro and regional delivery, including carrier integration where you have contracts.
- Review standard trade terms for unfair contract terms risk with small business customers.
Account-specific pricing and catalogues
Most wholesale complexity lives in pricing: price lists by customer group, contract prices for key accounts, quantity breaks, promotional pricing and customer-specific product ranges. The portal must show each signed-in buyer exactly their prices and products, calculated the same way as your ERP, or trust collapses quickly.
Decide where pricing rules are calculated. Usually the ERP is the source of truth and the portal either syncs price lists or asks the ERP for prices in real time. Each approach has trade-offs in speed and accuracy. Our guides to B2B pricing display and customer-specific catalogues cover patterns in depth.
Pro tip
Our recommendation: before any design work, export ten real customers' price lists from your ERP and have someone recreate their prices by hand from the rules. If that is hard, the portal will be too. Simplify pricing rules first where you can.
GST, tax invoices and Peppol
GST display. Trade buyers usually expect prices excluding GST, but the basis must be obvious on product pages, in the cart and at checkout, and totals must match the tax invoice to the cent. Check how your ERP rounds GST (per line or per invoice) and make the portal match.
Tax invoices. The ATO's tax invoice requirements include that the document is intended to be a tax invoice, the seller's identity and ABN, the issue date, a description with quantity and price, the GST amount or a statement that the total includes GST, and the extent each sale is taxable; for sales of $1,000 or more, the buyer's identity or ABN must also be shown. If a customer asks for a tax invoice, you must provide one within 28 days, unless the sale is $82.50 or less including GST (ATO). Generate invoices from the ERP or accounting system so the portal shows the same document your books hold.
Peppol eInvoicing. Peppol uses the ABN as the business identifier in Australia, and businesses connect through an accredited access point provider (ATO). Many accounting platforms support it. It is voluntary for business-to-business trade, but useful for customers who prefer it and for government customers, where Commonwealth agencies apply faster payment terms to Peppol invoices.
Bulk ordering and reordering
Trade buyers know what they want. Speed matters more than browsing.
- Quick order: enter SKUs and quantities, or paste a list. See quick order design.
- CSV or spreadsheet upload for large orders, with clear error handling.
- Order pads and saved lists per site or season.
- Reorder from order history in one step. See B2B reordering.
- Pack sizes, minimums and multiples enforced at entry, not after submission.
- Stock visibility by warehouse, with expected restock dates where available.
- Split deliveries by site or date where your operations support it.
Approval workflows and permissions
Larger customers often need purchase approvals: a site manager builds an order, a manager approves it over a threshold, and finance controls payment terms. Model organisations, sites, users and roles from day one, and let customer administrators manage their own users.
Keep approvals fast: notifications with one-step approve or reject, delegation when approvers are away and visibility of where an order is waiting. See B2B approval workflows and account, user and role management.
ERP and inventory integration
The portal is only as reliable as its integration. Typical flows are products, customer price lists, stock levels, customers and contacts, orders, order status, invoices, statements and credit limits.
| Data | Usual source of truth | Sync pattern to consider |
|---|---|---|
| Products and pack sizes | ERP or PIM | Scheduled sync plus change events |
| Customer prices | ERP | Price list sync, or real-time price lookup for complex rules |
| Stock | ERP or WMS | Frequent sync; real-time check at checkout for scarce items |
| Orders | Portal creates, ERP owns | Push immediately with retries and confirmation |
| Invoices and statements | ERP or accounting system | Fetch on demand or sync after posting |
| Credit limits and terms | ERP | Check at checkout |
Worth noting
Do not promise portal features until the ERP's integration capability is confirmed. Check which version you run, which APIs or connectors it supports, rate limits and costs, and whether your ERP partner must be involved. Older systems may only support file exchange or need middleware. Our B2B ERP integration guide and API integration for Australian businesses cover patterns and failure handling.
Customer-specific terms, credit and payment
Trade customers often buy on account with payment terms and credit limits, while new or small customers may pay by card. Support both: show terms and available credit, block or flag orders over the limit, and offer card payment where appropriate. Card surcharges on eftpos, Visa and Mastercard were removed from 1 October 2026 under the RBA's decision, so build card costs into prices or terms.
Unfair contract terms. If trade terms are standard form and some customers are small businesses, the unfair contract terms regime applies, and since 9 November 2023 unfair terms can attract penalties (ACCC). Review terms such as unilateral variation, broad indemnities and automatic renewals with a lawyer before customers accept them through the portal.
Order tracking and freight across Australia
Distance shapes B2B commerce in Australia. Show realistic delivery estimates by location, including regional and remote areas, and make freight costs clear before checkout. Integrate with your carriers for labels and tracking where you have accounts: Australia Post's shipping and tracking APIs, for example, are available to businesses with eParcel or StarTrack contracts (Australia Post). Offer pick-up from your warehouse where customers prefer it.
After the order, show status from the ERP or warehouse system, tracking links per consignment, and proof of delivery where available. See order tracking for patterns.
Reporting for customers and for you
Give customers simple reports: spend by site and period, frequently ordered items and outstanding invoices. For your team, track portal adoption by account, share of orders through the portal, order errors, average order processing time and reorder frequency. Our guide to business intelligence dashboards covers definitions and permissions.
Platform choice
| Option | Fits when | Watch for |
|---|---|---|
| Ecommerce platform with B2B features (for example Shopify's B2B capabilities on eligible plans) | Catalogue, account pricing, terms and reorders are the main needs | Plan requirements; ERP connector quality; limits on complex pricing |
| Dedicated B2B commerce platform | Complex catalogues, quoting, procurement integration | Cost and implementation effort |
| Custom portal or layer | Unusual ordering rules, configuration, or heavy ERP logic | Ongoing maintenance and security ownership |
MVP scope
| Release | Scope |
|---|---|
| MVP | Sign-in for invited accounts, customer-specific catalogue and prices, quick order and reorder, order submission to ERP, order history and status, invoices and statements |
| Next | Multiple users and roles, approvals, credit limits at checkout, saved lists, carrier tracking |
| Later | CSV upload, quotes, punchout to procurement systems, customer reporting, Peppol-related improvements in partnership with your accounting platform |
Hypothetical example: a food service distributor
This example is hypothetical. A Queensland food service distributor takes most orders from cafés and restaurants by phone and text late at night, then re-keys them into its ERP each morning. Prices vary by customer group, and some customers have contract prices.
Technical discovery confirms the ERP exposes APIs for products, stock, customer price lists and orders, but not real-time price calculation. The portal therefore syncs price lists nightly and checks stock at checkout. The MVP offers reorder from history and order pads, enforces case quantities and delivery cut-off times, and pushes orders straight to the ERP. Prices are shown excluding GST with GST totals at checkout, and tax invoices are generated by the ERP. Regional customers see delivery days for their area.
Common mistakes
- Designing the portal before confirming what the ERP can actually expose.
- Recreating pricing logic in the portal so it drifts from the ERP.
- Ambiguous GST display, so totals do not match invoices.
- Single-user accounts for customers with teams and approvals.
- Treating the portal as a B2C store with a login.
- Launching without onboarding customers and reps, so phone orders continue.
B2B ecommerce site, logged-in portal or hybrid store?
'B2B ecommerce' covers several different builds. Decide which you need before choosing a platform, because the requirements, SEO approach and integrations differ.
- Public catalogue pages can earn search traffic; logged-in prices and catalogues cannot, so decide what to show publicly.
- Hybrid stores need careful GST display: consumer prices including GST, trade prices often excluding it, never mixed on the same page without labels.
- Account applications need approval workflows, credit checks and ABN validation.
- Platform choice depends on the model: see B2B ecommerce website development and Shopify development in Australia.
- Whichever model you choose, the ERP integration, pricing rules and tax invoice requirements in this guide still apply.
| Model | What it is | Fits when |
|---|---|---|
| Public B2B catalogue site | Products and specifications visible to all, with quote requests or account applications | New customer acquisition matters; search visibility for product and category pages helps |
| Logged-in ordering portal | Account-specific catalogue, prices and terms for approved trade customers | Most revenue comes from existing accounts that reorder |
| Hybrid B2B and B2C store | One storefront with retail prices for consumers and trade prices after sign-in | You sell to both, and catalogue and fulfilment are shared |
Sources
Tax and invoicing: ATO, tax invoices; ATO, Peppol.
Consumer law and payments: ACCC, businesses urged to remove unfair contract terms; RBA, surcharging conclusions.
Freight: Australia Post developer centre.
ATO and ACCC points were confirmed via search summaries where those sites blocked our fetcher. The pricing exercise, release plan and example are ours. Nothing here is tax or legal advice or ZSpace client data.
Conclusion
A B2B portal in Australia succeeds when trade customers can order faster than by phone, at prices and on invoices that match your books exactly. Get pricing and GST right, confirm what your ERP can expose, design for teams and approvals, make freight realistic for regional customers and review your trade terms. Then onboard customers deliberately, because adoption is the measure that matters. For getting new trade customers set up, see B2B customer onboarding automation.
Moving trade orders online?
ZSpace Labs is an India-based, remote-first technology studio working with Australian and international businesses on Shopify and B2B commerce, custom portals and ERP integrations and ordering UX. If it would help to test your pricing and integration assumptions, we are happy to talk it through.
Common questions.
A B2B portal is a signed-in website or app where trade customers order from you and manage their account: they see their own catalogue and prices, place bulk or repeat orders, route orders for approval, track deliveries, and view invoices and statements. It replaces orders by email, phone and spreadsheet with structured orders that flow into your ERP or accounting system.