Preorders and Backorders: Capturing Demand Without Breaking a Promise
When an item runs out, most Australian businesses simply stop selling it. The demand does not disappear, it moves to a competitor, and the stock arrives three weeks later to a quiet website. Selling ahead of arrival recovers that revenue, and it also converts every optimistic date into a commitment you are legally and commercially on the hook for.
The difference between a preorder programme that builds trust and one that generates refunds is not the button on the product page. It is whether your available to promise number is real, whether allocation is fair when the shipment lands short, whether payment is taken at the right time, and whether the customer hears from you before they have to ask.
Realistic ROI
Four Things That Have to Be True Before You Sell Ahead
Preorders fail on arithmetic and communication far more often than on technology.
An available to promise number that is honest
What you can safely sell is not what is on the shelf. It is stock on hand, less what is already allocated to unfulfilled orders, less a safety buffer, plus confirmed inbound quantities that will land inside the horizon you are prepared to promise. Every one of those terms comes from a different system, which is exactly why so many businesses fall back on selling only what they can physically see.
A rule for who gets the stock when it lands short
A container arrives with sixty units against ninety orders. Who is filled: the earliest orders, the highest value ones, the customers who paid a deposit, the retail channel or the wholesale accounts. Deciding this in advance and applying it consistently is what keeps allocation from becoming an argument, and it should be written down before the first preorder is taken, not after the shortfall.
A decision about when money changes hands
Full payment on order, a deposit with the balance on despatch, or an authorisation captured when the goods ship. Each has different consequences for cash flow, for card authorisation expiry, for refunds if the date slips, and for when GST is attributable. This is a conversation to have with your accountant and then encode in the systems, rather than a setting to leave at whatever the platform defaults to.
Communication that arrives before the customer chases
A preorder customer will tolerate a delay and will not tolerate silence. The design needs proactive messages at the points that matter: order confirmed with a date, date changed with the new one and the reason, in transit, allocated, despatched. Most of the operational cost of a bad preorder programme is inbound enquiries that a well timed automated message would have prevented.
What the Integration Has to Handle
Six mechanisms sit between an order taken early and a parcel that arrives when you said it would.
Inbound visibility
Purchase orders, supplier confirmations and shipment milestones flow from the ERP or supplier feeds so the store knows what is coming and roughly when. Confirmed inbound quantities are what make a preorder date defensible. Unconfirmed intentions are not, and treating them the same is where most programmes go wrong.
Available to promise
A calculated figure per item and per location: on hand less allocated less buffer, plus inbound arriving inside the promise horizon. It recalculates when stock moves, when an order is placed, and when a supplier date changes, and it is published to every channel that can sell the item rather than kept in one system.
Allocation on arrival
When a shipment is receipted, waiting orders are filled according to the agreed rule, reserved against the specific order, and released to the warehouse or store for picking. Anything unfilled keeps its place in the queue with a revised date. This should be an automated run with a reviewable output, not a person working through a spreadsheet at the receiving dock.
Partial and split decisions
An order with three lines where one is available raises a question with a cost attached: ship now and pay freight twice, or hold and delay the customer. A threshold based rule, adjustable by customer type and order value, settles it consistently. Wholesale accounts often prefer consolidated despatch while retail customers usually prefer the available item now.
Payment timing and capture
Deposits taken at order, balances requested before despatch, or authorisations captured at fulfilment, with handling for the authorisation that expires before the goods land and the card that fails on capture. Failed payment on a long awaited item needs a defined retry and hold process, because cancelling silently loses both the sale and the customer.
Notification and status
Order status that reflects the real state, from awaiting stock through allocated to despatched, published to the customer account and to the service team so nobody has to guess. Date change messages go out when the date changes, not in a weekly batch, and they say what the new date is rather than apologising vaguely.
Situations That Decide Whether This Works
| Task | Traditional | Managed Properly | Notes |
|---|---|---|---|
| Popular line sells out on Friday | Product hidden until restock | Sold against confirmed inbound | Only where the supplier date is reliable. Unconfirmed stock should not carry a public date. |
| Container lands 40% short | First to complain gets filled | Allocation rule applied automatically | Consistency matters more than which rule you pick, and the rule should be visible internally. |
| Supplier pushes the date out a month | Customer finds out by asking | Automatic message with the new date | Also the point at which a customer should be offered a straightforward cancellation. |
| Order with one available line | Whole order waits | Split by value and customer type | Freight cost is the deciding factor. Set a threshold rather than deciding order by order. |
| Card authorisation expires | Payment fails at despatch | Re-authorisation requested before pick | Long lead preorders need a payment approach that survives the wait. |
| Wholesale account wants everything at once | Split shipments and complaints | Consolidation flag on the account | Account level despatch preferences are cheap to implement and quietly valuable. |
| Item is cancelled by the supplier | Sits in backorder for months | Flagged, refunded, customer told | Aging reports should force the decision rather than letting it drift indefinitely. |
| Marketplace channel | Preorders listed the same way | Excluded or handled separately | Marketplace despatch deadlines rarely tolerate long lead times. Check the rules per channel. |
Where Selling Ahead Goes Wrong
Publishing a date you were merely given
A supplier estimate is not a delivery date. It has to survive production, freight, customs, receipting and put away before the item can leave your warehouse, and each of those adds variance. Publish a date that sits behind the date you were given, with your own handling time included, and update it the moment the underlying estimate moves. It is better to beat a conservative date than to explain an optimistic one.
Treating Australian Consumer Law obligations as fine print
When you accept payment for goods, the law expects supply within the time you specified or, if none was specified, within a reasonable time. Delivery timeframes shown at checkout are representations, and continuing to take orders for stock you know will not arrive risks being misleading. If a date slips materially, tell the customer, offer a genuine choice including cancellation and refund, and keep records of what was promised and when it changed. This is general information, not legal advice, and it is worth a conversation with your own adviser.
Overselling because two channels both sold the inbound
The available to promise figure has to be shared across the website, the shops, marketplaces and wholesale ordering, or each will happily sell the same incoming container. That means one system owning the calculation and publishing it, with allocations recorded against orders as they are taken rather than at despatch. Where a channel cannot consume a live figure, cap what it may sell instead of hoping.
Deposits treated as revenue and spent
Money taken against goods not yet supplied has accounting and tax consequences, and it is also the customer’s money in a practical sense until the item ships. Agree the treatment with your accountant, including when GST is attributable and how deposits are recorded in the ledger, and make sure the integration posts them accordingly rather than as ordinary sales. A refund wave against revenue you have already recognised is an unpleasant way to learn this.
Backorders that age quietly forever
Without an aging report and a rule, backorders accumulate: discontinued lines, cancelled shipments, orders the customer has long forgotten. Run a weekly report by age, force a decision at agreed thresholds, and give service staff the authority to cancel and refund with a message. The measure of a healthy backorder book is not its size, it is how quickly items leave it in one direction or the other.
No allocation trail when someone complains
The customer who waited nine weeks and sees the item back in stock for someone else will ask what happened, and so will your own team. Every allocation decision should be logged with the rule that produced it, the quantity and the timestamp, so the answer is a record rather than a reconstruction. This is also what lets you defend the fairness of the process to a wholesale account that believes it was skipped.
How Yes AI Approaches Preorder and Backorder Work
We check whether your dates are reliable first
Before designing anything, we look at how accurate your supplier confirmations have actually been over the last year. If inbound dates move by weeks routinely, the honest answer is a shorter promise horizon or a waitlist rather than a public preorder date, and we will say so.
One available to promise calculation, published everywhere
We build the figure once from the systems that own each term, then publish it to every channel that sells. That single decision removes most of the overselling risk, and it makes the numbers explainable when someone asks why the website is showing what it is showing.
Allocation and notification automated together
Flows run on a managed cloud automation layer we operate: receipting triggers allocation, allocation triggers customer messages and warehouse tasks, and every step is logged at record level so the trail exists when it is needed.
Backorder aging that forces decisions
A weekly report by age, value and customer, with thresholds that prompt action rather than observation. It is usually the report that tells you which supplier relationship is quietly costing you customers.
From Hidden Products to Managed Demand
Five steps. A first category is typically live in four to six weeks.
Assess date reliability and demand lost
How often items go unavailable, how much demand that turns away, and how accurate your inbound dates have been. That establishes both the opportunity and the safe promise horizon.
Define the rules with the business
Allocation order, split shipment thresholds, payment timing, which categories may be sold ahead and which never should, and the cancellation policy when a date slips materially.
Build the available to promise calculation
On hand, allocations, buffers and confirmed inbound combined into one published figure per item and location, refreshed as stock and supplier dates change.
Automate allocation and messages
Receipting drives allocation, allocation drives picking and customer notification, and date changes generate proactive updates. Every decision logged against the order.
Report, review, extend
Backorder aging, fill rate and date accuracy reviewed monthly, rules tuned against real behaviour, and the programme extended to further categories or channels once it is holding.
Related Reading
SaaS Integration Explained
The patterns behind any system to system connection.
Multichannel Inventory Sync
One stock pool, and the buffers that protect it.
Supplier Feed and Dropship
Selling stock held by someone else entirely.
Purchase Order Automation
Where confirmed inbound dates come from.
B2B Ecommerce Integration
Trade accounts, credit and contract pricing.
Ship From Store
Filling demand from stock already in the network.
FAQ
Stop Turning Away Demand You Could Fill
Book a call. We will quantify the demand your out of stock lines are losing, test whether your inbound dates are reliable enough to promise on, and give you a design and a priced plan. The assessment is yours either way.
All discussions held in confidence. Australian-based consultants.