🧭 Overview
This guide shows how to turn MYOB sales history into a repeatable demand forecasting workflow: export the right data, build drivers that explain demand, and convert assumptions into scenarios your team can act on. It’s built for operators, finance teams, and commercial leaders who need a reliable demand forecast without relying on guesswork or brittle spreadsheets. You’ll finish with a structured model that supports seasonality, promotions, pipeline shifts, and “what-if” decision-making. If you’re mapping out the broader MYOB planning ecosystem first, start with MYOB budgeting and forecasting.
🔗 How Model Reef + MYOB Fit Together
MYOB is excellent at recording actual sales and financial outcomes, but it isn’t designed to run planning scenarios: it won’t naturally help you test assumptions like “What if conversion drops?” or “What if we add a new channel?” Model Reef sits on top of your exported actuals so your team can translate sales history into drivers and scenarios – then refresh the forecast as new information arrives. In practice, MYOB remains the ledger and reporting engine, while Model Reef becomes the modelling layer for business forecasting: the place where you formalise assumptions, compare scenarios, and publish decision-ready outputs. If you want clarity on why this separation matters (and where each tool shines), see Model Reef vs MYOB. This pairing is best when you need scenario planning and driver transparency without disrupting how accounting closes and reports.
✅ Before You Begin
To build demand forecasting that your team actually trusts, align on these prerequisites:
- Access: permission to export relevant sales history from MYOB (by month, product, customer, and channel where possible).
- Data scope: confirm which demand signal is “truth” (invoices shipped, orders placed, bookings, or cash received).
- Granularity: pick the planning level that matches decisions (product family vs SKU, region vs store).
- Time horizon: decide the planning window (e.g., next 13 weeks for ops, next 12 months for finance).
- Seasonality decision: define whether you’ll use last year’s pattern, a rolling average, or a driver-based seasonal curve.
- Ownership: assign who owns export quality, who owns the driver assumptions, and who approves scenario changes.
- Integration path: decide whether you’ll start manual exports or formalise an integration workflow via Integrations].
You’re ready if you can produce a consistent sales export, you know what “demand” means operationally, and you’ve defined who signs off on the forecast.
Step-by-Step Instructions
Step 1: Define the workflow and success criteria.
Begin with clarity: what decisions must your demand forecasting support? Common answers include inventory buys, staffing rosters, marketing spend, and cash planning. Define the forecast horizon and cadence, then choose success metrics: forecast accuracy tolerance, cycle time to update, and whether you need “best/worst case” every refresh. Next, define the core drivers you believe explain demand: traffic/leads, conversion, average order value, churn/retention, repeat purchase rate, and price. If you skip this step, your demand forecast becomes a rear-view projection that fails the moment conditions change. The aim is to agree on the “few things that move demand,” so the forecast is easy to challenge and quick to update.
Step 2: Extract/connect the data cleanly.
Export sales history from MYOB using a consistent reporting method and time grain (weekly or monthly). Validate totals so the export matches the financial view leaders trust. Then establish a repeatable data pipeline: a standard file format, naming convention, and refresh owner. If your business needs frequent refreshes or multi-entity scaling, consider moving beyond manual imports with Deep Integrations. This reduces operational drag and keeps the forecasting conversation focused on drivers and actions. The quality bar here is consistency, not perfection – a forecast is only useful if it can be updated without rework. Clean any category drift early (new products, renamed accounts, merged customers) so your model structure remains stable over time.
Step 3: Map and reconcile (lock the source of truth).
Mapping is where you turn history into a usable planning structure. Decide how sales lines roll up into planning segments (product families, channels, regions, customer tiers). Then reconcile definitions: what counts as “new demand” vs “repeat,” what counts as “promo,” and how returns/refunds are treated. This is also where how to forecast sales becomes practical – forecasting isn’t a single number; it’s a structured set of assumptions applied consistently. Keep the model explainable: if leaders can’t understand the segments, they won’t trust the numbers. Lock a small number of segments that match decisions, and document mapping rules so your demand model doesn’t break when the business evolves.
Step 4: Build the model logic + outputs.
Build your demand logic around a driver chain: inputs (traffic/leads), conversion, average order value, and mix. Use scenarios to reflect real uncertainty: promo lift, churn changes, supply constraints, or channel expansion. This is where many teams discover they don’t need more spreadsheets – they need better sales forecasting software style workflows: standard drivers, consistent outputs, and version control. If your demand forecast feeds revenue targets, align the model with your top-line planning so sales assumptions and finance assumptions don’t drift. The revenue driver approach in the MYOB revenue forecasting guide is the clean complement here. Produce outputs that teams can act on: a demand plan by segment, a scenario comparison, and a short driver narrative.
Step 5: Operationalise: cadence + governance.
Operationalise your business forecasting with a clear cadence and governance rules. Create a recurring cycle: refresh data, update drivers, run scenarios, review changes, publish outputs. Assign ownership: one person responsible for exports, one responsible for driver assumptions, and one approving scenario changes. Keep a changelog of major driver edits so stakeholders understand what changed and why. Over time, you’ll build institutional memory: which drivers matter, how demand reacts to promotions, and where variance consistently comes from. The “win” is a forecast that becomes a management system – not a monthly fire drill.
🧪 Example
A multi-location retailer exports MYOB sales history monthly, then models demand weekly using drivers: foot traffic, conversion rate, and promo uplift. When marketing plans a campaign, they run scenarios: baseline demand, promo lift, and supply-constrained demand. The operations team uses the scenario outputs to adjust staffing and reorder points, while finance uses the same demand drivers to update revenue outlook. Within two cycles, the business stops debating “whose spreadsheet is right” and starts debating actions: whether to pull forward inventory, extend promo duration, or shift spend to the highest-converting channel. If you want the direct inventory and working-capital layer that sits beside demand, the MYOB inventory forecasting guide is a strong companion.
🚀 Next Steps
You now have a clean how to path for building demand forecasting from MYOB history with drivers that leaders can challenge and scenarios that teams can act on. Your next move is to pick a single segment structure, run a baseline, and publish one scenario comparison to stakeholders. If you want to see a full workflow end-to-end, See it in action.
Back