Deferred COGS (cost of goods sold) is delivery or fulfillment cost capitalized on the balance sheet and expensed in sync with related deferred revenue as performance obligations are satisfied.

How it works

Under ASC 606, when customers prepay for annual SaaS plus implementation, revenue may be recognized ratably while setup costs are deferred and amortized across the same period if they qualify as fulfillment costs tied to distinct performance obligations.

Example: A $120k annual contract with $12k of capitalizable onboarding labor. Cash arrives day one, but both revenue and associated COGS spread monthly — keeping gross margin stable instead of showing a loss in month one and inflated margins later.

Deferred COGS sits as an asset until expensed. It pairs with deferred revenue on the liability side — investors compare both when judging balance sheet health.

Hardware-plus-software bundles and professional services attachments often trigger deferred COGS more than pure self-serve SaaS.

Why it matters

• Founders: Work with accountants early on implementation economics. Misclassification makes cohort margins look better or worse than reality.
• Investors: Sudden spikes in deferred COGS may mean heavy services burden — a scalability warning even if ARR grows.

Common mistake

Expensing all implementation costs immediately while deferring subscription revenue — or the reverse — which breaks unit economics storytelling in board meetings.

Related ideas

See also deferred revenue, billings, ASC 606, and gross margin by cohort.