Company: CALX
Filing Date: 2025-02-21
Form Type: 10-K
Source: 0001406666-25-000008
Chunk: 127

Company: CALIX, INC
Filing Date: 2025-02-21
Form: 10-K
Item: Item 7
Chunk 127
---
 prepared in accordance with U.S. generally accepted accounting principles. These accounting principles require us to make certain estimates and judgments that can affect the reported amounts of assets and liabilities as of the date of the financial statements, as well as the reported amounts of revenue, costs and expenses during the periods presented. We base our estimates, assumptions and judgments on historical experience and on various other factors that are believed to be reasonable under the circumstances. To the extent there are material differences between these estimates and 

27

Table of Contents

actual results, our financial statements may be affected. We evaluate our estimates, assumptions and judgments on an ongoing basis.

We believe the following critical accounting policies affect our significant judgments and estimates used in the preparation of our financial statements. 

Revenue Recognition

Revenue is recognized when a performance obligation is satisfied, which occurs when control of the promised goods or services is transferred to the customer, in an amount that reflects the consideration we expect to be entitled to in exchange for those goods or services. Revenue from sales of access and premises systems is recognized when control is transferred to the customer, which is generally when the products are shipped. Revenue from software platform licenses, which provides the customer with a right to use the software as it exists, is generally recognized upfront when the license is made available to the customer. Revenue from cloud-based software subscriptions, customer support, maintenance, extended warranty subscriptions and managed services is generally recognized ratably over the contract term. Revenue from professional services and training is recognized as the services are delivered.

A performance obligation is a promise in a contract to transfer a distinct good or service to the customer and is the unit of account. A contract’s transaction price is allocated to each distinct performance obligation and recognized as revenue when, or as, the performance obligation is satisfied. Our hardware products contain both software and non-software components that function together to deliver the products’ essential functionality and therefore constitutes a single performance obligation as the promise to transfer the individual software and non-software components is not separately identifiable and, therefore, not distinct. Cloud-based software subscriptions can include multi-year agreements with a fixed annual fee for a minimum committed usage level. To the extent that minimum committed usage level each year varies, we have concluded that each year represents a distinct stand-ready performance obligation and the transaction price allocated to each performance obligation is recognized as revenue ratably over each annual period.

Our contracts generally include multiple performance obligations. For such arrangements, we allocate the contract’s transaction price to each performance obligation using the relative stand-alone selling price of each distinct good or service