What it means
A manufacturer has twenty open sales orders, with some placed yesterday and others waiting a month beyond their promised date. Backlog aging shows how long unresolved demand has remained open and where action is overdue.
Sage documentation describes aged orders grouped by age periods and Aptean describes backlog in units and value and distinguishes backorders, but the business still needs its own definition of open, late and partially fulfilled. Define an eligible order: accepted sales orders with undelivered quantities may count, while quotes and cancelled orders should be separate.
Select the age start, since order creation, customer acceptance and promised date serve different purposes, and show both elapsed age and lateness where useful. Set the reporting date, because a snapshot must state when it was taken and orders can be fulfilled after the report is generated.
Work at line level, since one order might contain five fulfilled lines and one delayed line and header-level aging can exaggerate outstanding value. Measure remaining quantity as ordered units minus confirmed fulfilled units, adjusted for valid cancellations and returns, and use value cautiously because remaining order value may exclude tax or freight and can change with approved amendments.
Handle partial shipments by reducing outstanding units only when delivery or shipment meets the measure, and do not mark the whole line complete after one carton. Group into bands: zero to seven, eight to thirty and over thirty days are illustrative, so choose bands that reflect lead times and customer expectations.
Separate overdue from old, since a custom machine ordered two months ago may still be on schedule while a standard part due yesterday may be late. Preserve promises by storing original and agreed revised dates, because editing a promised date should not erase the history of delays.
Classify blockers, since stock shortage, quality hold, missing customer approval and carrier capacity need different fixes, and identify an owner who can advance the next action or update the customer for each open line. Check duplicates, because a replacement order can be created after a damaged shipment and should be linked so backlog is not counted twice without explanation.
Avoid gaming, as cancelling and recreating old orders can make the queue look younger, so retain linkage and original request dates and keep the agreed revision of any legitimate buyer change. Look at demand concentration, track movement between bands over weeks, and review the oldest cases, because a stable total can hide new orders replacing unresolved older ones and averages can look healthy while one critical customer waits.
A backlog can be normal when the business sells made-to-order products, so age alone does not prove process failure, and an order backlog is not recognised revenue or guaranteed cash. Check fulfilment evidence, since a warehouse picked status does not prove an order shipped or arrived, reconcile the order feed with warehouse completion, communicate material delays to customers through the agreed channel and investigate recurring bottlenecks, because for owners backlog aging is a map of unfinished promises.
In practice
Real-world examples.
Example
A custom order is sixty days old but still within its agreed schedule, so it sits in an older age band without being counted as late. The planner compares age with the promised date before escalating. The customer has not been let down.
Example
One delayed line remains open after the rest of an order ships. The report shows only that line's remaining quantity and value, with the blocker recorded as a missing component. The account owner tells the customer a revised date.
Example
A critical overdue spare part receives an assigned recovery owner. The owner confirms the supplier date, arranges expedited transport and updates the customer. The order moves out of the oldest band within the week.
Formula
Calculation
Illustrative line age = report date minus accepted order date. Lateness = report date minus promised date for an open line; positive days indicate overdue under this convention.
Worked example. A fictional line was accepted on 1 August and promised for 15 September. On a 30 September report, its age is 60 days (31 - 1 + 30) and its lateness is 15 days (30 - 15). Now look at value. An order worth $20,000 has five of six lines shipped, and the open line is worth $2,500. Line-level backlog is $2,500, while header-level aging would wrongly show $20,000 as outstanding, overstating the backlog by $17,500.Case study
Seen in the real world.
This entirely fictional example follows Ridge Manufacturing. Its dashboard aged entire orders even after most lines shipped. The team shifted to remaining line quantities and added original promise and blocker fields.
After the change, the reported backlog value fell by about a third because shipped lines no longer counted, and the oldest genuinely late lines became visible for the first time. The team then assigned an owner to each of them. The case does not equate backlog value with future revenue.
Watch out
Common mistakes.
- Treating order age as identical to lateness.
- Counting fully shipped lines as outstanding backlog.
- Resetting age by cancelling and recreating an old order.
Questions
People also ask.
What belongs in backlog?
Accepted orders or lines with defined remaining fulfilment.
Is an old order always late?
No. Compare it with the agreed promise.
Is backlog revenue?
No. It is unfulfilled demand subject to terms and execution.
From the founder's library
Take it further with the book.
Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.
25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.
View the book and save 25%