Summary

  • Q2 revenue recovered to $5.149 million and gross margin reached 57%, but revenue was still 13.4% below the prior year and gross-profit dollars were almost unchanged.
  • Bookings of $4.9 million were below shipments, backlog fell to $2.1 million and deferred revenue stood at $1.1 million; the forward ledger did not expand with the sequential headline.
  • Cash rose after a $9 million private placement. Neither the proposed semiconductor-handling acquisition nor the intended IAR security-asset purchase had entered the reported operating perimeter.

The clean comparison contains two clocks

The sequential comparison is strong. Data I/O's revenue rose from about $3.3 million in Q1 to $5.149 million in Q2. The annual comparison points the other way: Q2 revenue was down from $5.948 million, while first-half revenue fell 30.7% to $8.399 million.

Both statements are true because they answer different questions. Sequential growth measures escape from a weak quarter. Year-on-year growth tests whether the business has recovered the scale it produced under a comparable season. Calling Q2 an inflection is reasonable only if later orders replenish what the company has just shipped.

The product ledger also resists a simple transformation story. Platform sales were $2.282 million, adapter sales $1.759 million, and software and services $1.108 million. Software and services grew 3.2% year on year in the quarter but were down 0.9% for the first half. Consumable adapters and services together supplied 55% of Q2 revenue, yet the filing does not provide service ARR, retention or a clean recurring-revenue bridge.

Margin percentage improved more than gross-profit dollars

Gross margin rose to 57% from 49.5% in Q1 and 49.8% a year earlier. Management cited favourable mix, stricter discounting, overhead absorption and production efficiency. Those are useful operating levers.

The dollar result is more restrained. Gross profit was $2.935 million, against $2.960 million a year earlier. A lower revenue base produced almost the same gross profit, which is better economics than the sales decline alone suggests. It is not yet gross-profit growth.

Operating loss was $724,000. R&D fell 17% year on year, and the company linked most of that reduction to realignments in Germany and Redmond. The Redmond action itself generated about $345,000 of employee-related cost. Margin therefore reflects mix, pricing, production absorption and a changing cost base. Later quarters must show which gains survive after restructuring effects pass.

Orders, backlog and deferred revenue are separate records

Second-quarter bookings rose to $4.9 million from $4.2 million sequentially, but remained below $5.8 million a year earlier. They were also below Q2 revenue. Backlog consequently declined from $2.6 million to $2.1 million. Deferred revenue fell from $1.5 million at year-end to $1.1 million.

This does not prove demand is collapsing. Customer decisions had been delayed by tariff uncertainty, and sales processes were resuming after a ransomware incident. The public filing does not quantify either effect. The narrower conclusion is that execution consumed more scheduled work than new orders replaced during the quarter.

For a small manufacturer, that gap matters quickly. A large shipment can lift revenue and factory absorption while leaving the next quarter more dependent on late bookings. Backlog is not a perfect demand measure and excludes work that converts rapidly. It is nevertheless the most visible bridge between a recovery already shipped and revenue still waiting to be earned.

Financing cash is not operating proof

Cash increased from $5.7 million at March 31 to $10.8 million at June 30. The decisive event was a $9 million private placement comprising common shares, convertible securities and warrants. That strengthened liquidity and can support a transaction. It should not be presented as cash generated by the Q2 rebound.

The distinction becomes more important because two acquisition narratives sit beside the organic figures. The proposed semiconductor-handling transaction was still under exclusivity, subject to definitive documentation, financing, approvals and diligence. Data I/O also announced an intent to acquire embedded-security software and related assets from IAR. Intent is not control, and anticipated consolidation is not reported revenue.

Until closing, the existing operation should be judged on its own shipments, bookings, backlog, margins and cash use. After closing, investors need a perimeter bridge showing purchase consideration, acquired revenue, deferred revenue, working capital, integration cost and the legacy business without the target. Otherwise an enlarged revenue line could conceal whether Data I/O's own order engine strengthened.

Sources