Standalone Selling Price: How Transaction Price Is Allocated

When a company sells multiple goods or services as a bundle but does not sell each component separately, standalone selling price allocation is the process of dividing the total transaction price among each performance obligation using estimated or observable market prices. The accounting standard (ASC 606) permits three estimation methods when standalone prices are not directly observable.

The bundle problem

A company often sells products or services in packages where the customer pays one lump sum for multiple deliverables. A software vendor might sell a license, implementation, and two years of support for $100,000. A manufacturer might bundle equipment, installation, and a maintenance contract. In each case, the company must allocate the $100,000 across its performance obligations so that revenue is recognized in the right period at the right amount.

If the company sold each component separately—the license for $60,000, implementation for $25,000, support for $15,000—the allocation is simple and observable. But often, the company does not sell components separately, or sells them only rarely, making direct observation impossible. That is where standalone selling price estimation enters.

Defining standalone selling price

The standalone selling price is the estimated price at which the company would sell the same good or service on its own, in a similar circumstance, to a similar customer. It is not the price the company charges in the bundle; it is what the component would cost if unbundled. Arriving at this estimate is the heart of ASC 606 revenue allocation.

The estimate must be reasonable and defensible. It should consider market conditions, customer profiles, the company’s own cost structure, and competitor pricing. A company cannot simply assign arbitrary percentages; the estimate must rest on evidence or plausible modeling.

Method 1: Adjusted market assessment

Under the adjusted market assessment approach, the company surveys what comparable products sell for in the market, then adjusts the observed price to reflect differences in the company’s offering.

Example: A SaaS company bundles a core product and advanced analytics for $50,000. The core product has an observable standalone price of $40,000 (it is sold separately). The company studies competitors and finds that similar advanced analytics modules sell for $12,000 to $15,000. The company adjusts this market range downward by 10% because its analytics are less comprehensive than the highest-end competitors, settling on $13,500 for the analytics component. The allocation is then $40,000 (core) and $13,500 (analytics), totaling $53,500. The actual transaction price of $50,000 is allocated proportionally: 75.9% to core ($37,950) and 24.1% to analytics ($12,050).

This method is most credible when markets are active and comparable offerings are abundant. It works well for commodities, standard software licenses, and services with published price lists.

Method 2: Expected cost plus margin

When market data is thin, the company estimates the standalone selling price by calculating its own cost to deliver the component, then adding a markup that reflects the margin the company typically earns on similar products.

Example: A consulting firm bundles strategy advice and custom software development. The firm’s cost for the software development is $20,000 in internal labor and external tools. The firm’s gross margin on software projects is 40%, so the standalone selling price of the software is $20,000 ÷ (1 − 0.40) = $33,333. Strategy advice costs $10,000 and carries a 50% margin, so its standalone price is $20,000. Total standalone price is $53,333. The bundled price is $45,000. The allocation is $45,000 × ($33,333 ÷ $53,333) = $28,125 to software, and $16,875 to strategy.

This method works well for bespoke services, custom manufacturing, and in-house products that are rarely sold separately. The key is that the markup must be consistent with the company’s own pricing history and industry norms. Using an inflated markup that the company has never actually charged risks overstating component revenue.

Method 3: Residual approach

The residual approach allocates the transaction price first to all components with observable standalone prices, then assigns the remainder to the component(s) with estimated prices.

Example: A company sells a hardware device, installation labor, and a three-year warranty. The device has an observable standalone price of $5,000 (sold separately). Installation labor is estimated at $2,000 using cost-plus-margin. The warranty has no observable market price. The bundled transaction price is $6,500. The residual is $6,500 − $5,000 − $2,000 = −$500.

In this case, the residual is negative, implying the customer receives a discount on the bundle. The company might allocate $5,000 to the device, $1,500 to installation, and $0 to the warranty (since the residual covers the entire warranty cost and part of installation).

The residual approach is practical when most components have observable prices and only a few do not. However, regulators and auditors scrutinize it closely because it can mask estimation error. If the estimated prices are significantly wrong, the residual component absorbs the full impact. For that reason, the residual method should be used only when the estimated component represents a minor portion of the total price, or when estimation is highly uncertain.

Common pitfalls

Circular allocation. A company cannot use the bundled transaction price to estimate the standalone price, then use that “estimate” to justify the allocation. The standalone price must be independent of what the customer actually paid.

Stale data. Market prices change. A company relying on competitor pricing from two years ago may be using outdated information. Standalone prices should be refreshed periodically to reflect current conditions.

Inconsistent margins. If a company claims different margins for different customers (or different bundles), the allocation must reflect those differences. Using a single “average” margin when margins vary materially across customer segments invites audit challenges.

Bundled discount misclassification. Sometimes the company deliberately discounts a bundle relative to the sum of standalone prices. The discount should be allocated proportionally to all components, not absorbed into one. Failing to do so overstates revenue for some obligations and understates others.

Documentation and audit considerations

ASC 606 requires companies to document their standalone price estimation method and the evidence supporting it. This means keeping records of market research, cost analyses, competitor pricing, and assumptions.

Auditors will challenge allocations that seem arbitrary or that change from period to period without justification. A company that allocated a bundled price 60-40 in 2023 cannot allocate it 70-30 in 2024 without explaining why customer circumstances, market conditions, or the company’s own cost structure changed.

When a company has material bundled contracts, the allocation method is often disclosed in the footnotes to the financial statements. Investors and lenders use this disclosure to assess whether revenue recognition is conservative or aggressive.

See also