Electreon: How Much of Backlog Is Truly Near Revenue, and How Much Still Depends on Milestones
Electreon's backlog is real, but it is not the same thing as near-term revenue or available cash. Most of it still depends on milestones, customer approvals, budgets, and in some cases on completing the contractual setup itself.
The main article argued that Electreon's central friction is not whether backlog exists, but what kind of backlog it is. This follow-up isolates that exact point: how much of the disclosed backlog already sits on a plausible path to revenue, and how much is still one layer earlier, stuck between milestones, customer approvals, schedules, budgets, and sometimes the completion of the binding contractual setup itself.
The key document here is not the 130 million NIS headline in the presentation. It is the combination of the backlog section and Note 13 on revenue recognition. The backlog section provides a timing view. Note 13 explains why that timing view is inherently fragile: in multi-stage projects, the group recognizes revenue only when a defined milestone is completed, or when the customer approves the milestone. For system sales, recognition is even tighter, only when the system is installed at the customer site and the customer confirms that it operates as specified in the contract. In other words, signed backlog is not a clean revenue queue. It is a stock of obligations that still has to be converted into approved milestones.
The numbers already do most of the filtering. As of December 31, 2025, the company showed 80.1 million NIS of backlog that had not yet been recognized as revenue. Near the publication date of the annual report, that figure rose to 111.2 million NIS. That is a meaningful increase, but more than 58% of the backlog at both snapshots still sits in 2027 and later. So even after the increase, most of the backlog remains relatively far from the near-term revenue line.
That is the core of the story. The portion scheduled for 2026 increased from 33.6 million NIS to 46.3 million NIS, and that is the bucket that really matters if the reader wants proof of commercialization. But even that bucket is not hard. The company says explicitly that the timing of recognition, and even the actual execution of the orders, depends among other things on project start dates, customers' flexibility to change schedules, and the availability of budget sources. The right way to read this is therefore in two layers: yes, there is backlog, but no, the recognition path still does not behave like a clean management spreadsheet.
Where backlog is relatively closer to revenue
The Avnat terminal project is the stronger example of relatively mature backlog. In 2025, the company had already recognized about 0.5 million NIS from the planning stage. On March 29, 2026, it signed the construction stage for about 7.8 million NIS plus VAT. That is still not immediate cash, because payment is tied to milestones, but it is a project that has already moved from planning into construction. From a backlog-quality perspective, that is much closer to revenue than an early-stage award or a funding framework that still needs another chain of conditions.
The DENSO agreement also looks more mature than some of the other additions. The company disclosed an agreement for up to 9 million dollars, up to 29 million NIS, over three years for development services. That matters because it shows the backlog is not only a list of one-off experiments. At the same time, this is exactly why the reader should not treat it as near-term revenue in one block: it is a multi-year development-services framework, so recognition should be spread across delivery milestones rather than arriving all at once.
Where backlog is still farther from revenue
The story is less comfortable here. The Buffalo project, which also appears in the presentation as part of the backlog added since December 2025, rests on a funding agreement for about 1 million dollars, around 3.2 million NIS, to be transferred over two years and only against defined milestones. Beyond that, actual execution and timing are subject to a dedicated agreement with NFTA, supplemental agreements with additional partners, and other conditions precedent. That does not make the project weak. It does mean it is farther from near-term revenue than one unified backlog headline may imply.
Pennsylvania is an even sharper case. The presentation includes the project at roughly 3 million NIS inside the signed-project backlog added since the end of 2025. But in the immediate filing from January 21, 2026, the award notice is described explicitly as an intent to contract and not as a binding agreement. The next steps were contingent on formal contracting, a final agreement, preconditions, and an official notice to proceed. That is not a footnote. It is a textbook example of the gap between a meaningful commercial achievement and revenue that is actually close.
This is where readers tend to make the wrong move with Electreon: they put all backlog components into the same bucket. They do not belong in the same bucket. There is a project that already generated planning-stage revenue and moved into construction. There is a signed multi-year development-services agreement. And there are awards or funding arrangements that still need to move through conditions, partners, and approvals before turning into revenue. The backlog headline is real, but the maturity of its components is not uniform.
| Item | Disclosed amount | What brings it closer to revenue | What is still open |
|---|---|---|---|
| Avnat, construction stage | About 7.8 million NIS plus VAT | The planning stage already generated about 0.5 million NIS of revenue in 2025, and the construction stage is signed | Consideration is milestone-based, not upfront |
| DENSO, development services | Up to 29 million NIS over 3 years | Signed multi-year framework with a defined work envelope | Recognition should be spread across service delivery and execution |
| Buffalo | About 1 million dollars, about 3.2 million NIS | There is a signed funding agreement with NYSERDA | A dedicated NFTA agreement, supplemental agreements, conditions precedent, and two years of milestones are still required |
| Pennsylvania | About 800 thousand dollars in the first year, and about 3 million NIS in the presentation | There is an award and real commercial progress in the US | At the time of the filing the award was not yet a binding agreement, and a final contract plus a notice to proceed were still needed |
The slide that turns backlog into cash
The cash slide in the presentation matters because it shows how management wants the market to connect backlog and liquidity. The company takes 105.1 million NIS of cash and cash from investing activity, adds 46.3 million NIS of signed pipeline for 2026 and another 64.9 million NIS of signed pipeline for 2027 and later, and reaches 216.3 million NIS of projected cash.
The issue is not that the slide is false. The issue is what it combines. The slide itself flags two important caveats: it is a possible and non-binding scenario, and it does not deduct procurement and operating expenses. That means this is not a full cash-flexibility view, meaning cash left after actual cash uses. It is a gross illustration of possible inflows. Once procurement, installation, subcontractors, operations, and other execution costs are brought back into the picture, 111.2 million NIS of backlog stops being equivalent to 111.2 million NIS of cash that can be relied on.
That distinction matters especially in Electreon, because backlog quality is the thesis. If the reader substitutes signed backlog for available cash, the company looks as if it has already crossed the proof threshold. But the annual report and the immediate filings say something more conservative: there is real improvement in the number of contracts and in the size of the backlog, yet the conversion into revenue and cash still depends on execution, customer approvals, budgets, and the company’s ability to close the full contracting chain.
Bottom line
The right way to read Electreon's order backlog is in three layers. The first layer is projects that have already crossed a planning or contractual step and are beginning to move toward revenue, such as Avnat. The second layer is well-signed multi-year frameworks that should support the commercial base but will be recognized over time, such as DENSO. The third layer is awards and funding arrangements that still depend on conditions, partners, or supplemental agreements, such as Buffalo and Pennsylvania.
So a 130 million NIS backlog headline should not be read as proof of near-term revenue, and certainly not as proof of available cash. The right test for the next 2 to 4 quarters is simpler: how much of the 46.3 million NIS marked for 2026 actually converts into approved milestones, invoices, and cash receipts, and how much gets pushed further out. Until the company shows that conversion consistently, the backlog remains more a stock of signed opportunities than a proven revenue run-rate.
Disclosure: Deep TASE analyses are general informational, research, and commentary content only. They do not constitute investment advice, investment marketing, a recommendation, or an offer to buy, sell, or hold any security, and are not tailored to any reader's personal circumstances.
The author, site owner, or related parties may hold, buy, sell, or otherwise trade securities or financial instruments related to the companies discussed, before or after publication, without prior notice and without any obligation to update the analysis. Publication of an analysis should not be read as a statement that any position does or does not exist.
The analysis may contain errors, omissions, or information that changes after publication. Readers should review official filings and primary sources before making decisions.