Inside a modern Australian distribution centre

Warehouse operations

I need AI help for my warehouse. Where should we start?

Last updated

Most mid-sized and multi-site warehouses should start with AI in the ERP and document layer before robotics. That means goods receipts, packing slips, supplier invoices and purchase orders read into the ERP, stock discrepancies and demand forecasts drawn from ERP and warehouse history, exception alerts, and admin and reporting agents. Measure one use case against a baseline, then expand.

Who this is for

This page is for operations, warehouse, supply chain and ERP managers at wholesalers, distributors, 3PLs, logistics operators, manufacturers and mining suppliers that run one or more warehouses. Stock, orders and receipts usually sit in Business Central, NetSuite, SAP, Pronto Xi or Microsoft Dynamics 365, sometimes with a separate warehouse management system and Power BI on top. Solve8 delivers in fixed-fee phases: discover one process at one site with a measured baseline, prove it in shadow mode beside your team, build it into your systems on your infrastructure in Australia, then support it or hand it over. We are based in Brisbane and work on site in Sydney, Melbourne, Perth and across Australia and New Zealand.

Robots, shuttles and automated storage solve physical throughput and need capital and site works. Most stock accuracy, receiving and admin problems come from data and paperwork moving between people and systems, which is where AI software can help without changing the floor.

Where AI helps in a warehouse

Where AI helps in a warehouse
AreaWhat AI doesWho stays in control
Document captureReads goods receipts, packing slips, supplier invoices and purchase orders and prepares the entry in the ERP or warehouse systemReceiving or accounts staff approve
Receiving discrepanciesCompares what arrived with the purchase order: short, over, substituted or damaged linesPurchasing decides on the supplier claim
Stock accuracyFlags locations and SKUs with repeated cycle count variances, negative stock or adjustments outside the usual patternInventory controller chooses what to recount
Demand and replenishmentBuilds a baseline forecast from sales and stock history and suggests reorder quantitiesA planner or buyer approves every order
Slotting and pick pathsSuggests moving fast sellers and items picked together closer, based on order historyWarehouse manager approves moves
Customer enquiriesDrafts replies to order status, availability and delivery questions from ERP and tracking dataCustomer service sends
Freight and carrier chargesChecks carrier invoices against consignments and rate cardsLogistics or finance approves payment
Equipment maintenanceReads forklift, conveyor and dock equipment logs and pre-start checks to spot repeat faultsMaintenance lead raises the work order

Where AI will not help yet

  • Poor master data

    Duplicate SKUs, wrong units of measure and missing pack sizes make every forecast and match unreliable. Fix these first.

  • No scanning discipline

    If stock moves without a barcode scan or a location update, the system never matches the shelf and AI only reports the gap.

  • Physical throughput limits

    Congested docks and aisles or labour shortages at peak need layout changes or automation with capital and site works.

  • Decisions with no history

    New products, one-off projects and new sites have little data to learn from, so a person sets the plan.

What to fix before AI

  • Item master

    One SKU per product, correct units of measure, pack and carton quantities, weights and dimensions.

  • Location master

    Every bin and location set up in the system and labelled on the floor, with no informal overflow areas.

  • Scan every movement

    Receipts, putaway, transfers, picks and adjustments each recorded at the time they happen.

  • One definition of accuracy

    All sites measure stock accuracy and pick errors the same way, so results can be compared.

How to choose the first use case

How to choose the first use case
TestWhat to measureGood sign
VolumeDocuments, lines or enquiries per weekHundreds of similar items, every week
ErrorsCount variances, mispicks, receiving disputes, credit notesErrors you can count and trace to a cause
HoursStaff time spent keying, checking or chasingSkilled people doing repetitive checks
DataHistory in the ERP or warehouse systemAt least a year of clean transactions
OwnerOne manager accountable for the resultSomeone who will review exceptions daily

A phased approach for warehouses

  1. Discover

    Pick one process at one warehouse, such as receiving or cycle counts, and measure today's volume, errors and hours.

  2. Prove

    AI runs in shadow mode on live work while your team works as normal. You set the accuracy bar and we compare results.

  3. Build

    Connected to your ERP and warehouse system with approvals, logs and role permissions, on your infrastructure in Australia.

  4. Run

    We support it, or hand over code, documentation and training. Then repeat at the next site or process.

Three warehouses with stock accuracy and picking errors

When several sites all report poor stock accuracy, the cause is usually different at each one. Start by comparing count variances, adjustments and mispicks by site, location and SKU from the ERP and warehouse system. AI is useful here for sorting thousands of variances into patterns: one supplier's units of measure, one zone with no scanning, one shift, or items with similar codes picked in error.

Fix the cause at the worst site, measure again, then roll the same checks to the other sites. A single governed report across all warehouses, described in our answer on one version of the numbers across sites, keeps the sites honest once the fixes are in.

Systems involved

  • Business Central

    The Sales and Inventory Forecast extension predicts sales from item ledger history and suggests replenishment. Microsoft notes it forecasts across all locations combined, so multi-site warehouses need to split the forecast by location afterwards.

  • Microsoft Dynamics 365 Supply Chain Management

    Demand forecasting generates a statistical baseline from history, and manual adjustments must be authorised before planning uses them. Item names and units of measure must match across data sources.

  • NetSuite, SAP and Pronto Xi

    Stock, receipts and purchase orders are read and written through each ERP's APIs, with the same approval rules staff follow today.

  • Warehouse management system

    Location, scan and pick data often sits in a separate warehouse system. We read it alongside the ERP and leave it in place.

  • Xero and Power BI

    Xero holds the finance side where inventory runs elsewhere. Power BI gives one view of stock accuracy, receiving and pick errors across sites.

Sources

Microsoft Learn, Using the Sales and Inventory Forecast extension to manage inventory, Business Central: https://learn.microsoft.com/en-us/dynamics365/business-central/ui-extensions-sales-forecast

Microsoft Learn, Demand forecasting overview, Dynamics 365 Supply Chain Management: https://learn.microsoft.com/en-us/dynamics365/supply-chain/master-planning/introduction-demand-forecasting

Questions

Do we need a warehouse management system before using AI?

No. Many mid-sized warehouses run stock and locations inside the ERP, and AI can work from that data. What matters is that receipts, transfers and picks are scanned and recorded at the time they happen. A separate warehouse system helps with directed picking and putaway, and AI can read from it once it exists.

Can AI fix stock accuracy problems across several warehouses?

AI can find the patterns behind poor stock accuracy, such as locations with repeated count variances, suppliers whose units of measure cause receiving errors, or SKUs that get picked in place of each other. People still fix the causes: labelling, scanning and master data. AI then watches for the problem returning at each site.

Will AI demand forecasting replace our planners or buyers?

No. AI produces a baseline forecast and suggested order quantities from history, and a planner or buyer reviews and approves them. Planners add what the history cannot show, such as promotions, new customers, supplier changes or a site opening. Dynamics 365 Supply Chain Management requires manual adjustments to be authorised before planning uses them.

Should we invest in warehouse robotics or AI software first?

For most mid-sized and multi-site warehouses, AI software in the ERP and document layer comes first because it needs no site works and fixes data that robotics also depends on. Robotics makes sense when physical throughput is the constraint and stock, location and order data is already accurate.

How long does a warehouse AI pilot take to show results?

It depends on volume and data quality. A pilot starts with a measured baseline at one site, then AI runs in shadow mode on live work for several weeks so results can be compared against your own team. Only once the agreed accuracy bar is met does it connect to the ERP with approvals.

Can an AI consultancy support warehouses in several states?

Yes. Discovery and the shadow mode trial are usually done on site at the first warehouse, with workshops for the people doing the work. Later sites reuse the same build with local testing. Solve8 is based in Brisbane and works in Sydney, Melbourne, Perth and across Australia and New Zealand.

Running more than one warehouse?

A 30-minute review with a senior consultant. You leave with a written one-page summary you can share internally.

Fixed-fee phases, agreed before we start. Stop after any phase.