When a consumer-tech company sells a device that comes with services attached — cloud storage, software updates, a bundled subscription, or platform features delivered after purchase — it does not earn the entire price the instant the box ships. Revenue-recognition rules require the company to identify the distinct promises in the contract and allocate the transaction price among them. The part of the price that pays for the hardware delivered at sale is recognized immediately. The part that pays for services delivered later is deferred: recorded as a liability called deferred revenue, then recognized as revenue over the period those services are provided. This is why a single device sale can show up partly as product revenue today and partly as services revenue spread across the months that follow.

Apple's fiscal 2025 Form 10-K, for the year ended September 27, 2025, describes the back end of this process directly in its discussion of services net sales.

Services net sales include amortization of the deferred value of services bundled in the sales price of certain products.— Apple Inc. Form 10-K (FY2025), source

Read carefully, that sentence describes a transfer across the income statement over time. When a product sells, some of its price is set aside as the "deferred value of services bundled in the sales price." That deferred value is not lost — it is amortized, meaning released gradually, and when released it lands in services net sales rather than product net sales. So a portion of what a buyer paid for hardware is reported, quarters later, as services revenue. On the balance sheet, the unreleased portion sits in deferred revenue, a liability that represents performance the company still owes.

Why this matters to the segment story

The bundling-and-deferral mechanism quietly shifts revenue from the product line to the services line, and the two lines carry very different margins. In the same fiscal 2025 filing, Apple reports a products gross margin of 36.8% and a services gross margin of 75.4%. Revenue that migrates from product recognition to services recognition therefore arrives in a much higher-margin bucket. For a reader trying to understand a device company's growth, this is a reason to treat the product/services split with care: part of the services line is, in economic substance, deferred hardware value being released over time, not purely a separate subscription business. It also means a company's reported services growth can be fed in part by the cadence of hardware sales in prior periods.

The five-step model behind it

The deferral is not discretionary; it follows the standard revenue-recognition model that governs all U.S. public companies. That model requires a company to identify the distinct performance obligations in a contract, determine the total transaction price, allocate that price across the obligations based on their relative standalone selling prices, and then recognize each obligation's revenue as it is satisfied. For a device sold with bundled services, the hardware is one obligation satisfied at delivery and each bundled service is a separate obligation satisfied over time. The allocation step is where judgment enters: the company must estimate what each component would sell for on its own to decide how much of the bundled price belongs to the deferred services. A company that allocates more price to the over-time services defers more revenue up front and recognizes more services revenue later; one that allocates less defers less. Because those standalone-selling-price estimates are judgments, they are an area auditors and regulators scrutinize, and a change in the allocation methodology can shift revenue between the product and services lines without any change in what was actually sold.

The cash-versus-revenue distinction is the other key to reading the line. When a customer pays the full price of a bundled device at purchase, the company has the cash immediately, but it cannot count the bundled-service portion as earned revenue yet. That gap between cash collected and revenue recognized is exactly what the deferred-revenue liability captures. Over the service period, the liability shrinks as revenue is recognized, with no further cash changing hands. This is why deferred revenue is sometimes described as a favorable kind of liability: it represents money already in hand against a service the company will deliver from infrastructure it largely already operates. Apple's framing — services net sales "include amortization of the deferred value of services bundled in the sales price of certain products" — is a compact statement that a portion of today's services revenue was funded by hardware sales recorded in earlier periods.

How to read the deferred-revenue line

Deferred revenue appears as a liability on the balance sheet, usually split between current (expected to be recognized within a year) and non-current. A growing deferred-revenue balance signals that a company is collecting cash ahead of delivering the associated services — a sign of bundled or subscription commitments building up. The balance is not debt in the borrowing sense; it is an obligation to perform, and it converts to revenue as performance occurs rather than being repaid in cash. Three things are worth checking. First, how a company allocates price between hardware and bundled services, which is a judgment that affects how much is deferred. Second, the recognition period, since longer service terms stretch the release schedule. Third, whether deferred revenue is growing faster or slower than reported revenue, which hints at whether future recognized revenue is being banked or drawn down. Apple's own description — services net sales "include amortization of the deferred value of services bundled in the sales price of certain products" — is the clearest statement that, in a bundled-hardware business, the timing of revenue and the timing of the sale are not the same thing.