I count a backlog only once it turns into sales and cash. Until then it’s a list of orders that can still move. One canceled order rarely hurts much. The bigger risk is a downturn, when lots of customers push their orders out at once.
What a backlog is
A backlog is work a customer has ordered and the company hasn’t delivered yet. ASML, the Dutch company that makes the machines that print chips, had €38.8 billion of it at the end of 2025. That’s more than its €32.7 billion of sales for the whole year. It isn’t revenue yet, though. ASML’s own annual report says a weak economy could make customers decrease, cancel or delay their orders. Its contracts usually carry cancellation penalties. Those don’t help much when a lot of orders get pushed out at once.
Why I wait for the cash
Google Cloud’s backlog came up in another Reddit thread. Alphabet reported $513.9 billion of cloud backlog at the end of June 2026. In that same quarter it spent more on servers and data centers than the business brought in. Free cash flow came out at minus $5.9 billion. The backlog tells you customers want the capacity. The cash flow tells you how much Alphabet has to spend before it gets paid for it.
So I haircut any backlog until it’s billed, more so when a few customers make up a big part of it. Lose one of them and the number changes overnight. Delays don’t keep me up at night, because I never counted those orders as cash in the first place.
Where this breaks
For some businesses the backlog is the best forward data there is. A shipbuilder or a defense contractor can have years of work booked, on contracts that are hard to walk away from. I’d still read it next to the cash flow statement.