Skip to content
Order Management · for Wholesale

OpsUI's Order Management module is built for ANZ wholesalers running per-customer pricing, credit limits, and payment terms. Multi-channel order intake (email, phone, EDI, B2B portal, sales-rep app) flows into one order book; dispatch routes per retailer.

Wholesale distribution has three order-management headaches that generic OMS tools fix badly: per-customer pricing lookups, credit-limit enforcement, and multi-channel intake. OpsUI handles all three as first-class concepts so the order desk stops looking things up before they can quote.

Built for wholesale distribution

What this module brings to wholesale distribution operations.

Per-customer price lists

Each customer carries their own price list with volume tiers, contract overrides, and promotional pricing windows. Price calculation runs at order entry, not lookup-time.

Credit limit enforcement

Orders that would breach a customer's credit limit are flagged and held for approval. Stop-credit customers cannot place new orders until cleared. The rule lives in OpsUI, not in someone's head.

Payment-terms profiles

Each customer has their own payment terms (7-day, 14-day, 30-day, EOM, COD). Terms drive AR aging in the connected accounting system (Xero or MYOB) without manual re-keying.

EDI-ready order intake

Common ANZ EDI formats (Foodstuffs, Woolworths NZ/AU, Mitre 10) can be wired during rollout. Email, phone, B2B portal, and sales-rep app are first-party channels.

Dispatch routing per retailer

Different retailers have different delivery windows, dock booking requirements, and pallet/carton standards. OpsUI routes dispatch per retailer with the right carrier service tier.

Customer management built in (CRM-light)

Each trade customer record carries its price list, credit limit, payment terms, full order history, and contact notes, on the same record Order Management works from. The customer-management layer wholesale ops teams actually use, without a separate CRM licence.

Common questions

Does OpsUI include a CRM?
OpsUI is CRM-light: customer records, order history, pricing, credit and contact notes live inside Order Management rather than as a separately-licensed CRM module. For deep marketing automation or sequence-driven outbound, a dedicated CRM like HubSpot or Salesforce can run alongside. OpsUI integrates via REST API.
Does this handle chain-retailer EDI?
Yes. Scope during rollout. Common ANZ retailers (Foodstuffs, Woolworths NZ, Woolworths AU, Coles, Mitre 10, Bunnings) all have EDI integration patterns OpsUI can wire against. EDI is partner-quoted because every retailer's format and onboarding process is different.
Can I run trade pricing alongside a B2B portal?
Yes. Trade customers log into a B2B portal that shows their negotiated pricing automatically. They place orders that flow into OpsUI alongside email and phone orders. The same per-customer price list drives the portal display.
How does this connect to Xero or MYOB for AR?
Bidirectional sync via the Finance & Accounting module wired during rollout. Invoices generated on order fulfilment flow into Xero or MYOB AR automatically. Payment events flow back, updating order status and credit availability in OpsUI.
Module detail
Order Management

Order capture, status, priorities and pick-task generation in one module

Solution detail
Wholesale Distribution

For wholesalers and B2B distributors who need credit terms, price lists, and dispatch routing across multiple retailers.

Ready to see this in production?

Book a consultation and we will scope the Order Management module against your wholesale distribution operation specifically: your order volume, your channels, your team.

Book a consultationRun the recommender quiz