Distribution ERP Consultant, Australia

Distribution across a continent: where should stock sit?

Most Australian distributors I meet started in one capital city and grew interstate. At some point they faced the same question: keep everything in one warehouse and ship long distances, or hold stock in several states and manage the transfers. Both work, but each needs a different ERP design.

With a single warehouse, the focus is on order cut-offs that match linehaul departures, freight cost per order and reliable delivery promises for customers a long way off. With several sites, the focus moves to replenishment: which site buys from suppliers, which is topped up by interstate transfer, how much safety stock each state carries, and how stock riding on a truck or train is valued and kept visible.

The process map I draw covers supplier receipt -> placement decision -> interstate transfer -> local putaway -> order capture -> sourcing -> pick and dispatch -> metro run or carrier -> proof of delivery -> invoice -> collection. Placement and sourcing carry the most business judgment, so I write them down with your operations and finance leads before configuration starts. If a 3PL runs one of your states, its warehouse system joins the integration scope, with receipts, dispatches and stock positions exchanged on an agreed schedule.

Metro runs, country runs and freight that protects margin

Metropolitan and regional delivery behave like two different businesses. In the city, your own trucks run dense routes with many drops, and the questions are about sequencing, delivery windows and capacity. In the country, deliveries may go weekly on a fixed schedule or through a transport company that charges by zone, weight and cubic volume, and one small order can cost more to deliver than it earns.

I document the freight model in enough detail for the ERP to reflect it:

• postcode or zone groupings and the delivery days for each
• which runs use your own fleet and which use carriers, lane by lane
• how carrier charges are captured against the consignment and the order
• minimum order values, remote area surcharges and freight-free rules by customer group
• cut-off times tied to truck departures from each site

With that model in place, reports show margin after freight by customer and region, and sales teams can see which accounts are profitable to serve. Many distributors discover that pricing for remote customers was set long ago and never revisited. That finding often matters more than any software feature, and it comes from business analysis rather than configuration.

Cold chain, expiry and supplying the major retailers

Food, beverage, pharmacy and rural supply distributors need temperature and expiry control throughout the network. The ERP has to know which locations are chilled or frozen, track batches and best-before dates, pick the earliest expiry first, and record goods rejected on delivery for temperature or damage. When stock travels interstate the shelf-life clock keeps running, so a long transfer can leave little life for the receiving state. I build that into replenishment rules instead of leaving it to a supervisor's judgment on the day.

Supplying the major supermarket chains and national retail groups adds another layer. Orders and invoices usually flow through EDI or supplier portals, deliveries go to distribution centers within booked windows, and labeling and pallet rules are strict. Promotional programs and trading terms bring deductions that must be matched against agreements. I capture each retail customer's rules as a checklist before selection so the integration effort is known in advance.

GST applies to most sales, while some food lines are treated differently, so tax codes must sit on the item and flow cleanly into BAS reporting. Your accountant confirms the treatment for each product group; the ERP design makes sure it is applied without manual correction.

Systems Australian distributors move from, and how to choose

Common starting points are Xero or MYOB with an inventory app, an older on-premise wholesale package, or a mix of both after an acquisition. The tipping point tends to be a second state, a supermarket contract, or a recall that took days to trace by hand. The Australian ERP consultant page covers the broader triggers I see across industries.

For selection I build a scripted demo around an interstate day: stock received in one state, transferred to another, sold to a regional customer through a carrier, with a short-dated batch and a retailer EDI order landing at the same time. Vendors that handle it cleanly earn a place on the shortlist; those that need a workaround at each step show you the future support burden.

Migration priorities are open orders with promised dates, stock by site with batches and expiry, customer freight zones and delivery days, current price agreements and retail trading terms. Product-level notes sit on Odoo Inventory in Australia and Zoho Inventory in Australia.

My work with Australian firms is remote, and I book live calls in the window when all of your states are at their desks. The Australia hub and my distribution ERP guide add wider context.