XML 19 R8.htm IDEA: XBRL DOCUMENT
v3.26.1

BASIS OF PRESENTATION | 3 Months Ended
--- | ---
Mar. 28, 2026
Organization, Consolidation and Presentation of Financial Statements [Abstract] |
BASIS OF PRESENTATION | 1. BASIS OF PRESENTATION The condensed consolidated financial statements of Kopin Corporation as of March 28, 2026 and for the three month periods ended March 28, 2026 and March 29, 2025 are unaudited and include all normal recurring adjustments that, in the opinion of management, are necessary to present fairly the results of operations for the periods then ended. These condensed consolidated financial statements should be read in conjunction with the Company’s financial statements and notes thereto, included in the Company’s Annual Report on Form 10-K for the fiscal year ended December 27, 2025, as amended. The results of the Company’s operations for any interim period are not necessarily indicative of the results of the Company’s operations for any other interim period or for a full fiscal year. As used in this report, the terms “we”, “us”, “our”, “Kopin” and the “Company” mean Kopin Corporation and its subsidiaries, unless the context indicates another meaning. Principles of Consolidation The condensed consolidated financial statements for the three-month periods ended March 28, 2026 and March 29, 2025 include the accounts of Kopin Corporation and its wholly owned subsidiaries. All intercompany transactions and balances have been eliminated. As of October 16, 2025, the Company no longer has a controlling financial interest in Kopin Europe Ltd. and the assets and liabilities and operations of Kopin Europe Ltd. were deconsolidated (“Deconsolidation”). The assets and liabilities of Kopin Europe Ltd. are no longer included within the Company’s December 27, 2025 consolidated balance sheet. Any discussions related to results, operations, and accounting policies associated with Kopin Europe Ltd. are referring to the periods prior to Deconsolidation. Subsequent to Deconsolidation, the Company accounted for our equity ownership interest in Kopin Europe Ltd. under the equity method of accounting using the fair value option under ASC 825, Financial Instruments (“ASC 825”), (See Note 3, “Strategic Investment from Theon”). Liquidity The accompanying condensed consolidated financial statements have been prepared on a going concern basis, which contemplates the realization of assets and the satisfaction of liabilities in the normal course of business. The Company incurred a net loss of $3.8 million and net cash outflows from operations of $0.8 million for the three months ended March, 28, 2026. The Company’s net cash outflows from operations were partially a result of funding its ongoing investments in research and development, which management believes will continue, and production inefficiencies. As of December 28, 2024, the Company had $24.7 million accrued related to a jury verdict in the matter of Blue Radios Inc. v. Kopin Corporation (see Note 16 Litigation). On September 5, 2025, a post-trial order for $19.7 million was awarded. As a result, the Company reduced the accrual to $19.7 million and recognized a benefit of $5.1 million in the consolidated Statements of Operations for the fiscal year ended December 27, 2025. On October 2, 2025, the Company posted a supersedeas bond for $23.0 million which consisted of the $19.7 million judgement, legal expenses, and interest that would accrue over the expected term of the Company’s appeal to the verdict. To post the bond, the Company deposited $24.2 million in the bank, which consists of $23.0 million plus judgement, fees, and interest and $1.15 million in additional fees. The bank then issued a letter of credit to a surety company who then issued the bond to the court. While the Company has appealed the verdict, the bond is available to satisfy the payment of the judgment, interest, and fees should the Company’s appeal be unsuccessful. Moreover, the Company raised approximately $51.2 million during the fiscal year ended December 27, 2025, through the issuance of common stock, pre-funded warrants and preferred stock. As of March 28, 2026, the Company had $34.1 million of cash and cash equivalents (excluding restricted cash), which the Company believes is sufficient to support its operations and satisfy its obligations for at least the next twelve months from the issuance of these financial statements. Nonetheless, we monitor the capital markets on an ongoing basis and may consider raising capital if favorable market conditions develop. If our actual results are less than projected or we need to raise capital for additional liquidity, we may be required to do additional equity financings, reduce expenses or enter into a strategic transaction. However, we can make no assurance that we will be able to raise additional capital, reduce expenses sufficiently, or enter into a strategic transaction on terms acceptable to us, or at all. Revenue Recognition Substantially all the Company’s product and license and other revenues are derived from the sales of components and subassemblies and the license of intellectual property for use in defense and industrial applications. The Company also has development contracts for the design, manufacture and or modification of products for the U.S. Government or prime contractors for the U.S. Government and for customers that expect to sell into the defense markets. The Company may offer technologies developed under these defense research and development contracts in products sold to industrial, medical and consumer markets. The Company’s contracts with the U.S. Government are typically subject to the Federal Acquisition Regulations (“FAR”) and are priced based on estimated or actual costs of producing goods. The FAR provides guidance on the types of costs that are allowable in establishing prices for goods provided under U.S. Government contracts. The pricing for non-U.S. Government contracts is based on the specific negotiations with each customer. In accordance with ASC 606 Revenue from Contracts with Customers (“ASC 606”), revenue is recognized when a customer obtains control of promised products, and the amount of revenue recognized reflects the consideration to which the Company expects to be entitled to receive in exchange for these products and excludes taxes collected from customers which are subsequently remitted to government authorities. Pursuant to the contract terms, shipping and handling activities occur prior to the transfer of control of the Company’s products to customers and are therefore accounted for as fulfillment costs rather than as a separate performance obligation. The Company applies the following five steps to guide revenue recognition:
| 1) | Identify the contract(s) with a customer—A contract with a customer exists when (i) the Company enters into an enforceable contract with a customer that defines each party’s rights regarding the products to be transferred and identifies the payment terms related to those products, (ii) the contract has commercial substance and (iii) the Company determines that collection of substantially all consideration for products that are transferred is probable based on the customer’s intent and ability to pay the promised consideration. The Company’s contracts are typically in the form of a purchase order. For certain large customers, the Company may also enter into master service agreements that define general terms but are not customer commitments to purchase until coupled with a purchase order. The Company applies judgment in determining the customer’s ability and intention to pay, which is based on a variety of factors including the customer’s historical payment experience or published credit and financial information pertaining to the customer.
| 2) | Identify the performance obligations in the contract—Performance obligations promised in a contract are identified based on the products and services that will be transferred. A product or service is distinct if both a) the customer can benefit from the product or service either on its own or together with other resources that are readily available from third parties or from the Company, and b) is separately identifiable from other promises in the contract. To the extent a contract includes multiple promised products or services, the Company must apply judgment to determine whether the products or services meet the criteria to be distinct. If these criteria are not met the promised products or services are accounted for as a combined performance obligation.
| 3) | Determine the transaction price—The transaction price is determined based on the consideration to which the Company will be entitled in exchange for transferring products to the customer. The Company historically does not have contracts with variable consideration but to the extent the transaction price includes variable consideration, the Company estimates the amount of variable consideration that should be included in the transaction price utilizing either the expected value method or the most likely amount method depending on the nature of the variable consideration. Variable consideration is included in the transaction price if, in the Company’s judgment, it is probable that a significant future reversal of cumulative revenue under the contract will not occur.
| 4) | Allocate the transaction price to the performance obligations in the contract—If the contract contains a single performance obligation, the entire transaction price is allocated to the single performance obligation. The Company’s contracts do not typically contain multiple performance obligations that require an allocation of the transaction price to each performance obligation on a relative Stand-alone Sales Price (“SSP”).
| 5) | Recognize revenue when (or as) the Company satisfies a performance obligation—The Company satisfies performance obligations either over time or at a point in time as discussed in further detail below. Revenue is recognized at the time the related performance obligation is satisfied by transferring a promised product or service to a customer.
Product Revenues For certain contracts with prime contractors for the U.S. Government, the Company recognizes product revenue over time as the Company performs because of continuous transfer of control to the customer and the lack of an alternative use for the product. The continuous transfer of control to the customer is supported by liability clauses in the contract that allow the U.S. Government to unilaterally terminate the contract for convenience, pay the Company for costs incurred plus a reasonable profit and take control of any work in process and finished goods. In situations where control transfers over time, product revenue is recognized based on the extent of progress towards completion of the performance obligation. The Company uses the cost-to-cost input method to measure the extent of progress towards completion of the performance obligation for its contracts because the Company believes it best depicts the transfer of assets to the customer. Under the cost-to-cost input method, the extent of progress towards completion is measured based on the ratio of costs incurred to date to the total estimated costs at completion of the performance obligation which includes the expected yield which is a significant judgment. Revenues are recorded proportionally as costs are incurred. For certain contracts with prime contractors for the U.S. Government and commercial customers, while the contract may have a similar liability clause, the Company’s products historically have an alternative use and thus, revenue is recognized at a point in time upon transfer of control. Provisions for product returns and allowances are reductions in the transaction price and are recorded in the same period as the related revenues. The Company analyzes historical returns, current economic trends and changes in customer demand when evaluating the adequacy of sales returns and other allowances. Research & Development Contracts For most of the Company’s development contracts and contracts with the U.S. Government, the customer contracts with the Company to provide a significant service of integrating a set of components into a single unit. Since these components are not capable of being distinct or distinct within the context of the contract, the entire contract is accounted for as one performance obligation. If there is a follow-on production contract it is assessed whether it is a contract modification or a new contract. In situations where control transfers over time, revenue is recognized based on the extent of progress towards completion of the performance obligation. The Company generally uses an input method using the cost-to-cost approach to measure the extent of progress towards completion of the performance obligation for its contracts because the Company believes it best depicts the transfer of assets to the customer. Under the cost-to-cost measure approach, the extent of progress towards completion is measured based on the ratio of costs incurred to date to the total estimated costs, including material, labor and overhead. at completion of the performance obligation which requires management to use significant assumptions and judgements. Revenues are recorded proportionally as costs are incurred. The Company recognizes revenue at a point in time for certain contracts because the related performance obligations are satisfied upon delivery and transfer of control to the customer. The Company’s fixed-price contracts with the U.S. Government or other customers may result in revenue recognized in excess of amounts currently billed. The Company discloses the excess of revenues over amounts actually billed as Contract assets and unbilled receivables on the consolidated balance sheets. Amounts billed and due from the Company’s customers are classified as Accounts receivable on the consolidated balance sheets. In some instances, the U.S. Government may retain a small portion of the contract price until completion of the contract. For contracts with the U.S. Government and some commercial customers, the Company typically receives payments either as work progresses or by achieving certain milestones or based on a schedule in the contract. The Company recognizes a liability for these advance payments in excess of revenue recognized and present it as Contract liabilities and billings in excess of revenue earned on the consolidated balance sheets. Advanced payments typically are not considered a significant financing component because it is used to meet working capital demands that can be higher in the early stages of a contract and to protect the Company from the other party failing to adequately complete some or all of its obligations under the contract. For industrial and consumer purchase orders, the Company typically receives payments within 30 to 60 days of shipment of the product, although for some purchase orders, the Company may require an advanced payment prior to shipment of the product. License and other revenues The rights and benefits to the Company’s intellectual property are conveyed to certain customers through royalty-bearing technology license agreements. These sales-based royalties are recognized when they are earned. Revenues from sales-based royalties under license agreements are shown under License and other revenues on the Company’s consolidated statements of operations. Contract Assets Contract assets include unbilled amounts typically resulting from sales under contracts when the cost-to-cost method of revenue recognition is utilized and revenue recognized from customer arrangements, including licensing, exceeds the amount billed to the customer, and right to payment is not just subject to the passage of time. Amounts may not exceed their net realizable value. Contract assets are generally classified as current. The Company classifies the noncurrent portion of contract assets under Other assets in its consolidated balance sheets. Contract Liabilities Contract liabilities consist of advance payments and billings in excess of revenue recognized for the contract. Performance Obligations The Company’s revenue recognition related to performance obligations that were satisfied at a point in time and over time for our contracts accounted for in accordance with ASC 606 were as follows: SCHEDULE OF SATISFACTION OF PERFORMANCE OBLIGATIONS
Fiscal year ended |  | Three months ended March 28, 2026 |  |  | Three months ended March 29, 2025 |
Point in time |  |  | 8 | % |  |  | 13 | %
Over time |  |  | 92 | % |  |  | 87 | %
The value of remaining performance obligations represents the transaction price of orders for which work has not been performed and excludes unexercised contract options and potential orders under ordering-type contracts. As of March 28, 2026, the aggregate amount of the transaction price allocated to remaining performance obligations was $12.2 million, which the Company expects to recognize revenue over the next 12 months. The remaining performance obligations expected to be recognized beyond 12 months of $7.2 million represent amounts to be earned under government contracts, which are subject to cancellation. Government Grants The Company accounts for government grants which are not considered exchange transactions in accordance with ASC 832, Government Assistance (“ASC 832”). These grants generally provide the Company with payments for certain types of expenditures in return for research and development activities. The Company recognizes the government grant as grant revenue in the consolidated statement of operations, as the grants relate to improving the design of an already existing product that the Company regularly sells to other customers. Such amounts are recognized on a systematic basis in proportion with the related qualifying costs incurred, applying judgment to determine when grant conditions are met and when grant proceeds are no longer subject to clawback or performance uncertainty. Proceeds received before recognition of the related grant revenues are recorded as deferred grant income within Other current liabilities in the consolidated balance sheet. Grant contract assets include unbilled amounts resulting from recognized grant revenues in excess of billings. Grant contract assets are generally classified as current assets in the consolidated balance sheet. Costs associated with such grants are recorded as a component of funded research and development expenses in the consolidated statements of operations. Collaborative Arrangements At the inception of an agreement, the Company evaluates if an agreement is a collaborative arrangement within the scope of ASC 808, Collaborative Arrangements (“ASC 808”). For collaborative arrangements that fall within the scope of ASC 808, the Company first determines which elements of the collaboration are deemed to be a performance obligation with a customer within the scope of ASC 606. For elements of collaboration arrangements that are accounted for pursuant to ASC 808 and are subject to the guidance in ASC 606, the Company applies the revenue recognition model under ASC 606 or other guidance, as deemed appropriate. The Company generally recognizes proceeds under collaborative arrangements within the scope of ASC 808 using a cost-to-cost methodology consistent with the underlying project economics within Collaboration revenues in the consolidated statements of operations. Proceeds received before recognition of the related collaboration revenues are recorded as deferred collaboration income within Other current liabilities in the consolidated balance sheet. Costs associated with such arrangements are recorded as a component of funded research and development expenses in the consolidated statements of operations.

X
- Definition The entire disclosure for the basis of accounting, or basis of presentation, used to prepare the financial statements (for example, US Generally Accepted Accounting Principles, Other Comprehensive Basis of Accounting, IFRS). + References Reference 1: http://www.xbrl.org/2009/role/commonPracticeRef -Topic 235 -SubTopic 10 -Name Accounting Standards Codification -Section 50 -Paragraph 4 -Subparagraph (a) -Publisher FASB -URI https://asc.fasb.org/1943274/2147483426/235-10-50-4 + Details
Name: | us-gaap_BasisOfAccounting
Namespace Prefix: | us-gaap_
Data Type: | dtr-types:textBlockItemType
Balance Type: | na
Period Type: | duration

X
- References No definition available. + Details
Name: | us-gaap_OrganizationConsolidationAndPresentationOfFinancialStatementsAbstract
Namespace Prefix: | us-gaap_
Data Type: | xbrli:stringItemType
Balance Type: | na
Period Type: | duration