B2B trade portal vs e-commerce platform: what NZ food distributors actually need

When a food distributor or wholesaler starts looking for an online ordering system, the conversation usually lands in the same place: "Can we just use Shopify B2B?" or "What about BigCommerce?" These platforms have expanded their B2B feature sets significantly, and demos look compelling. But for most established NZ food distributors, a generic e-commerce platform and a purpose-built B2B trade portal are solving different problems — and choosing the wrong one creates operational work, not less of it.

This isn't an argument that generic platforms are bad. They're excellent at what they were built for. The question is whether what they were built for matches how your business actually operates.

What a generic B2B e-commerce platform does

Shopify B2B, BigCommerce B2B Edition, and similar platforms were designed to let consumer e-commerce merchants add a wholesale or trade-account layer to an existing storefront. They handle a separate trade login and customer-group pricing, basic order history and reorder, a product catalogue with wholesale price overrides, and payment via credit card or manual payment tagging.

For a business whose wholesale operation is straightforward — a fixed trade discount, no complex account relationships, payment in advance or by card — these platforms work well. They're faster to deploy than a custom build, well-supported, and have large app ecosystems.

The problem arises when your business operates the way most established NZ food distributors do.

Where generic platforms break for food distribution

1. Customer-specific contract pricing

Most food distributors don't run a single trade price list. They run contract prices — different rates for each customer, sometimes for each SKU within a customer, sometimes with volume breaks on top of that. A major grocery chain gets one price matrix; a single-site café gets another; your largest customer gets individually negotiated rates that live in your ERP.

Generic platforms offer customer-group pricing: all accounts in "Group A" get the same discount. They don't support true contract pricing where each account has its own per-SKU price sourced from whatever your ERP holds on record for that customer. Displaying the wrong price — even briefly, even to a single account — erodes trust fast.

2. Credit limits and account terms

Established food distribution runs on credit. Most trade customers order on account — Net 30, Net 60, or Net 90 — and their current balance and credit limit affect what they can order right now. A customer who is over their credit limit shouldn't be able to place an order that further extends their exposure; a customer with a clean account should be able to order without friction.

Generic e-commerce platforms handle checkout, not credit. They process transactions; they don't know what your AR ledger looks like at 9 am on a Tuesday. Replicating real-time credit limit checking on a generic platform requires custom middleware that almost always breaks when the ERP changes or the middleware falls behind.

3. Catch weight and variable-weight products

Meat, seafood, and fresh produce are priced by weight but sold in variable units. A carton of lamb shoulders might be ordered in units but invoiced at the actual weight packed. Standard e-commerce products have a fixed price per unit; they don't have an "invoice at catch weight" concept.

This is technically solvable with workarounds — unit price estimates with post-shipment adjustments, manual corrections — but workarounds mean your platform and your ERP disagree until someone reconciles them. In high-volume distribution, that's a daily accounting problem. See our guide on how catch weight inventory software actually works for a deeper look at the mechanics.

4. ERP integration depth

Every platform vendor will tell you they integrate with your ERP. The meaningful question is: which direction, how often, and what actually syncs?

For a food distributor, real operational integration means:

• Stock levels updating in near real-time so customers don't order product that isn't available
• Orders posting directly into the ERP and creating invoices in your accounting system — without re-keying
• Debtor records, payment terms, and credit balances flowing back from the ERP to the portal
• Price changes in the ERP reflecting in the portal immediately, not overnight

Most generic platform integrations sync inventory once or twice daily and treat orders as fulfilled by the platform. An order doesn't become an ERP invoice until someone manually pushes it across — the exact manual step a portal is supposed to eliminate. This is true even for platforms that advertise Xero or MYOB integration; the integration architecture for a distributor running Xero is more demanding than a simple accounting sync.

5. Rep and agent ordering workflows

Food distribution sales reps don't just support customers; they often place orders on their behalf — visiting a site, taking a verbal order, placing it in the system while they're still in the car park. Generic platforms are built around self-service customers, not reps acting on customer accounts. Adding rep impersonation, territory-based account visibility, and mobile-first rep workflows requires custom development or third-party apps that add cost and complexity without being purpose-built for the task.

6. Per-customer product catalogues

Some customers are authorised for your full catalogue; others see a restricted list — a hospitality account that only orders your foodservice range, a retailer that only buys specific product lines. Per-customer product visibility is different from product availability. It's about showing each account exactly what they're contracted to buy, nothing more and nothing less. Generic platforms handle product availability (in stock / out of stock); they don't natively handle contractual catalogue restrictions at the per-account level.

What a purpose-built B2B trade portal does differently

A trade portal built for food distribution starts from the commercial relationship rather than the checkout flow. Customer-specific pricing isn't a feature you configure on top of a retail price — it's pulled directly from what your ERP has on record for that account. Credit checking isn't middleware; it's a live balance check against your AR system before the order is confirmed. Rep workflows are first-class features, not afterthoughts. Catch-weight products invoice at actual weight, matching your ERP exactly.

The integration architecture is also different in character. Rather than syncing data on a schedule, a well-built trade portal reads directly from the ERP for time-sensitive data — stock, price, credit balance — and posts back to it for transactions: orders, invoices, payments. There is no parallel data set drifting out of sync overnight.

When is a generic platform good enough?

If your operation is genuinely straightforward — one price list per customer group, payment in advance or by card, a limited SKU count, no catch-weight products, and basic ERP integration needs — then a platform like Shopify B2B or BigCommerce B2B Edition may be a practical fit. They're faster to deploy and cheaper to maintain when your requirements match what they were built for.

The question to ask honestly: how much of the complexity described above does my business actually have? If the answer is most of it, a generic platform will eventually be patched into something that takes more work to maintain than a purpose-built system would have from the start.

Three questions to guide the decision

1. Do you run customer-specific contract pricing? If yes, a generic platform needs custom middleware to display correct prices. Evaluate whether that integration is cheaper long-term than a platform that handles it natively.
2. Do trade customers order on account? If yes, you need real-time credit limit checking at the point of order. Assess how your shortlisted platform handles this before signing anything.
3. How tightly does your ordering system and ERP need to stay in sync? If daily sync is acceptable and orders can be processed manually, a generic platform works. If you need orders to flow straight through to invoices and payments, check the integration architecture carefully — not just whether an integration exists, but how it actually moves data.

What this looks like in practice

Zeabyte's B2B platform was designed for the commercial relationships food distributors actually run on — customer-specific pricing sourced from the ERP, live credit limit checking, rep ordering via mobile, catch-weight invoicing, and deep integration with Accredo, Attaché, CSB-System, SAP, Xero and others. See our integrations list for the full range of systems we connect in production. It isn't a generic e-commerce platform with B2B add-ons; it's a trade portal designed around how established NZ and Australian distributors operate.

If you're evaluating ordering platforms and want a clear view of where a trade portal approach would add value for your operation, talk to us. We'll look at your current setup and give you an honest answer — including whether a generic platform would actually be the right fit.

For more context on the B2B portal decision, see our guide on what a B2B ordering portal costs in New Zealand .