Seller Profit Guard

Break-even ROAS formula, inputs, and assumptions

Last updated: 2026-07-31

Written and reviewed by Seller Profit Guard Editorial Team.

Break-even ROAS equals the declared advertising conversion value divided by retained contribution before ads. Target ROAS divides the same value by contribution before ads minus the seller's post-ad contribution reserve. Revenue, value, costs, attribution, refunds, and conversion delay must describe one comparable cohort.

Freeze the cohort grain

Bind one product, market, objective, traffic scenario, attribution convention, value definition, currency, closed period, and retained-order cohort. Add the result to the ROAS calculation specification with its cohort alias, source version, evidence date, owner, currency, window, denominator, scope, and affected output. This makes a reproducible break-even and target-safe ROAS boundary reproducible instead of dependent on memory or an unversioned dashboard.

Mixed cohorts make the value numerator and spend denominator incomparable. Review point 1 must distinguish observed data, explicit assumptions, unresolved evidence, and decisions outside the calculator. Keep retained revenue, reported conversion value, spend, variable costs, attribution, refunds, delay, target, and maturity separate.

Define retained revenue

Use revenue retained under one discount, refund, cancellation, tax, and shipping convention. Add the result to the ROAS calculation specification with its cohort alias, source version, evidence date, owner, currency, window, denominator, scope, and affected output. This makes a reproducible break-even and target-safe ROAS boundary reproducible instead of dependent on memory or an unversioned dashboard.

Gross catalog value and uncollected or reversed value do not silently become retained revenue. Review point 2 must distinguish observed data, explicit assumptions, unresolved evidence, and decisions outside the calculator. Keep retained revenue, reported conversion value, spend, variable costs, attribution, refunds, delay, target, and maturity separate.

Define conversion value

Record the exact conversion actions, value rule, window, duplicate treatment, and reporting source. Add the result to the ROAS calculation specification with its cohort alias, source version, evidence date, owner, currency, window, denominator, scope, and affected output. This makes a reproducible break-even and target-safe ROAS boundary reproducible instead of dependent on memory or an unversioned dashboard.

Platform value may differ from seller revenue and must remain a separate field. Review point 3 must distinguish observed data, explicit assumptions, unresolved evidence, and decisions outside the calculator. Keep retained revenue, reported conversion value, spend, variable costs, attribution, refunds, delay, target, and maturity separate.

Build pre-ad variable cost

Add product, packaging, fulfillment, percentage and fixed fees, expected adverse-order loss, and other order-caused cost. Add the result to the ROAS calculation specification with its cohort alias, source version, evidence date, owner, currency, window, denominator, scope, and affected output. This makes a reproducible break-even and target-safe ROAS boundary reproducible instead of dependent on memory or an unversioned dashboard.

Every layer appears once and uses the same product and cohort. Review point 4 must distinguish observed data, explicit assumptions, unresolved evidence, and decisions outside the calculator. Keep retained revenue, reported conversion value, spend, variable costs, attribution, refunds, delay, target, and maturity separate.

Calculate contribution before ads

Subtract the full pre-ad variable-cost packet from retained revenue. Add the result to the ROAS calculation specification with its cohort alias, source version, evidence date, owner, currency, window, denominator, scope, and affected output. This makes a reproducible break-even and target-safe ROAS boundary reproducible instead of dependent on memory or an unversioned dashboard.

This is an operating contribution boundary, not accounting profit. Review point 5 must distinguish observed data, explicit assumptions, unresolved evidence, and decisions outside the calculator. Keep retained revenue, reported conversion value, spend, variable costs, attribution, refunds, delay, target, and maturity separate.

Derive the two spend ceilings

Use positive contribution before ads for break-even and subtract the target contribution reserve for target-safe spend. Add the result to the ROAS calculation specification with its cohort alias, source version, evidence date, owner, currency, window, denominator, scope, and affected output. This makes a reproducible break-even and target-safe ROAS boundary reproducible instead of dependent on memory or an unversioned dashboard.

A nonpositive ceiling means no paid-acquisition room under the packet. Review point 6 must distinguish observed data, explicit assumptions, unresolved evidence, and decisions outside the calculator. Keep retained revenue, reported conversion value, spend, variable costs, attribution, refunds, delay, target, and maturity separate.

Convert ceilings to ROAS

Divide the same reported conversion value by each positive spend ceiling. Add the result to the ROAS calculation specification with its cohort alias, source version, evidence date, owner, currency, window, denominator, scope, and affected output. This makes a reproducible break-even and target-safe ROAS boundary reproducible instead of dependent on memory or an unversioned dashboard.

Do not invert the ratio or change numerator between break-even and target calculations. Review point 7 must distinguish observed data, explicit assumptions, unresolved evidence, and decisions outside the calculator. Keep retained revenue, reported conversion value, spend, variable costs, attribution, refunds, delay, target, and maturity separate.

Protect advertising and customer data

Use aggregate cohort values, product-profile aliases, synthetic examples, and redacted evidence pointers. Keep buyer names, emails, addresses, messages, order IDs, click identifiers, audience membership, payments, refunds, raw exports, credentials, tokens, and OAuth material in authorized systems with access and retention controls.

Public content needs only declared model fields, non-sensitive scenario labels, validation state, and aggregate outputs. Do not place private evidence in URLs, screenshots, image metadata, schema, console output, analytics dimensions, issue reports, generators, or downloadable examples.

Keep reporting states separate

Track planned, configured, served, clicked, viewed, attributed, converted, charged, paid, cancelled, refunded, returned, recovered, adjusted, billed, reconciled, and closed as distinct states. A later state can change value or retained revenue, so never backfill it into an earlier snapshot without a dated correction.

Tie value, spend, fees, refunds, reimbursements, and expected loss to source state and maturity. Pending, estimated, approved, posted, settled, failed, reversed, disputed, waived, and expired values are not interchangeable.

Correct defects without erasing history

When source evidence or logic changes, identify the defect, affected cohort versions, pages, fixtures, outputs, decisions, and downstream owners. Preserve the earlier packet, enter the corrected source and reason, rerun calculations and tests, and record reviewer, timestamp, release decision, and authorized remediation.

Distinguish tracking correction, late conversion, refund adjustment, cost correction, formula defect, content defect, display defect, platform-rule change, attribution change, and target change because each has a different repair and rollback path.

Test numerator consistency

Recompute when reported value differs from retained revenue and preserve the reconciliation gap. Deep review 1 stores the tested input, source state, numeric delta, authority boundary, reviewer, expiry, correction condition, and next action in the ROAS calculation specification. Retain counterexamples even when they do not support the preferred campaign decision.

Compare the result with a reproducible break-even and target-safe ROAS boundary, not a generic benchmark or another cohort at a different grain. Explain which single driver moved, which fields stayed constant, what remains unknown, and whether the response is collect, reconcile, stress, review, observe, correct, pause, release, or restore.

Test fee-base sensitivity

Change only the variable-fee convention and identify the threshold movement. Deep review 2 stores the tested input, source state, numeric delta, authority boundary, reviewer, expiry, correction condition, and next action in the ROAS calculation specification. Retain counterexamples even when they do not support the preferred campaign decision.

Compare the result with a reproducible break-even and target-safe ROAS boundary, not a generic benchmark or another cohort at a different grain. Explain which single driver moved, which fields stayed constant, what remains unknown, and whether the response is collect, reconcile, stress, review, observe, correct, pause, release, or restore.

Test return-loss maturity

Replace an expected value with a mature comparable cohort without rewriting history. Deep review 3 stores the tested input, source state, numeric delta, authority boundary, reviewer, expiry, correction condition, and next action in the ROAS calculation specification. Retain counterexamples even when they do not support the preferred campaign decision.

Compare the result with a reproducible break-even and target-safe ROAS boundary, not a generic benchmark or another cohort at a different grain. Explain which single driver moved, which fields stayed constant, what remains unknown, and whether the response is collect, reconcile, stress, review, observe, correct, pause, release, or restore.

Test zero contribution

Raise costs until the calculator reports no spend room. Deep review 4 stores the tested input, source state, numeric delta, authority boundary, reviewer, expiry, correction condition, and next action in the ROAS calculation specification. Retain counterexamples even when they do not support the preferred campaign decision.

Compare the result with a reproducible break-even and target-safe ROAS boundary, not a generic benchmark or another cohort at a different grain. Explain which single driver moved, which fields stayed constant, what remains unknown, and whether the response is collect, reconcile, stress, review, observe, correct, pause, release, or restore.

Test currency alignment

Block value and cost amounts that do not share one declared currency. Deep review 5 stores the tested input, source state, numeric delta, authority boundary, reviewer, expiry, correction condition, and next action in the ROAS calculation specification. Retain counterexamples even when they do not support the preferred campaign decision.

Compare the result with a reproducible break-even and target-safe ROAS boundary, not a generic benchmark or another cohort at a different grain. Explain which single driver moved, which fields stayed constant, what remains unknown, and whether the response is collect, reconcile, stress, review, observe, correct, pause, release, or restore.

Freeze the cohort grain: verification drill

Recreate “Freeze the cohort grain” from a clean synthetic cohort instead of copying the primary example. Bind one product, market, objective, traffic scenario, attribution convention, value definition, currency, closed period, and retained-order cohort. Change one driver, retain all other fields, calculate the before-and-after difference, and attach source state and expected output to the ROAS calculation specification.

Mixed cohorts make the value numerator and spend denominator incomparable. Drill 1 includes a supported case, broken case, late-evidence case, and correction case. Explain why each path produces Block, Review, Ready, no spend room, changed headroom, or a revised threshold for this specific a reproducible break-even and target-safe ROAS boundary.

Define retained revenue: verification drill

Recreate “Define retained revenue” from a clean synthetic cohort instead of copying the primary example. Use revenue retained under one discount, refund, cancellation, tax, and shipping convention. Change one driver, retain all other fields, calculate the before-and-after difference, and attach source state and expected output to the ROAS calculation specification.

Gross catalog value and uncollected or reversed value do not silently become retained revenue. Drill 2 includes a supported case, broken case, late-evidence case, and correction case. Explain why each path produces Block, Review, Ready, no spend room, changed headroom, or a revised threshold for this specific a reproducible break-even and target-safe ROAS boundary.

Define conversion value: verification drill

Recreate “Define conversion value” from a clean synthetic cohort instead of copying the primary example. Record the exact conversion actions, value rule, window, duplicate treatment, and reporting source. Change one driver, retain all other fields, calculate the before-and-after difference, and attach source state and expected output to the ROAS calculation specification.

Platform value may differ from seller revenue and must remain a separate field. Drill 3 includes a supported case, broken case, late-evidence case, and correction case. Explain why each path produces Block, Review, Ready, no spend room, changed headroom, or a revised threshold for this specific a reproducible break-even and target-safe ROAS boundary.

Build pre-ad variable cost: verification drill

Recreate “Build pre-ad variable cost” from a clean synthetic cohort instead of copying the primary example. Add product, packaging, fulfillment, percentage and fixed fees, expected adverse-order loss, and other order-caused cost. Change one driver, retain all other fields, calculate the before-and-after difference, and attach source state and expected output to the ROAS calculation specification.

Every layer appears once and uses the same product and cohort. Drill 4 includes a supported case, broken case, late-evidence case, and correction case. Explain why each path produces Block, Review, Ready, no spend room, changed headroom, or a revised threshold for this specific a reproducible break-even and target-safe ROAS boundary.

Calculate contribution before ads: verification drill

Recreate “Calculate contribution before ads” from a clean synthetic cohort instead of copying the primary example. Subtract the full pre-ad variable-cost packet from retained revenue. Change one driver, retain all other fields, calculate the before-and-after difference, and attach source state and expected output to the ROAS calculation specification.

This is an operating contribution boundary, not accounting profit. Drill 5 includes a supported case, broken case, late-evidence case, and correction case. Explain why each path produces Block, Review, Ready, no spend room, changed headroom, or a revised threshold for this specific a reproducible break-even and target-safe ROAS boundary.

Sources and further reading

• Seller Profit Guard methodology: Contribution equations, evidence versions, privacy, correction, release, and rollback.
• Seller Profit Guard data privacy: Local-first boundaries for customer, order, advertising, payment, refund, audience, and raw-record data.
• Google Ads Help: Conversion value per cost definition: Official reporting formula: conversion value divided by cost.
• Google Ads Help: About Target ROAS bidding: Official definition of Target ROAS as an average conversion-value-per-cost objective and guidance on conversion-delay evaluation.
• Google Ads Help: About conversion values: Official context for conversion values, reporting, and value-based bidding.
• Google Ads Help: Data exclusions: Official limits for conversion-tracking data exclusions; exclusions apply to click periods and do not alter reporting.

Related Seller Profit Guard tools

• Break-Even ROAS Calculator: Run the browser-local retained-contribution and ROAS calculation.
• Break-Even ROAS and Return-Loss Guide: Review the existing nine-cost model and return-loss example.
• Etsy Ads Break-Even Calculator: Use the Etsy-specific fee and campaign model when that scope fits.
• Contribution Margin Calculator: Reconstruct retained contribution before advertising.
• Maximum Discount Calculator: Keep merchandise promotion headroom separate from paid-media headroom.
• Methodology: Review evidence, privacy, calculation, correction, release, and rollback.
• Data Privacy: Protect buyer, order, ad-platform, audience, payment, refund, and credential data.
• Break-Even ROAS Prospecting Example: Follow a USD 100 prospecting cohort through retained revenue, cost layers, contribution before ads, spend ceilings, ROAS thresholds, and headroom.
• Break-Even ROAS for Retargeting: Model a retargeting cohort without reusing prospecting attribution, audience, conversion value, product mix, or spend assumptions.
• Break-Even ROAS Calculation Mistakes: Fix numerator, denominator, attribution, fee, refund, return-loss, product-mix, timing, target, and false-profit errors before using ROAS.
• Break-Even ROAS Evidence Sources: Map every ROAS input to advertising reports, retained-order records, cost libraries, fee statements, return cohorts, target policy, and delay evidence.
• Set a Safe ROAS Decision Threshold: Separate break-even, target, stress, warning, and stop thresholds while preserving attribution uncertainty and seller governance.
• Prospecting vs Retargeting ROAS: Compare prospecting and retargeting at one economic grain while keeping audience, attribution, exposure, product mix, and incrementality questions separate.
• Weekly Break-Even ROAS Review Cycle: Run a repeatable ROAS review from source refresh and cohort closure through calculation, approval, observation, correction, and rollback.
• Interpret Break-Even ROAS Results: Read contribution, spend ceilings, break-even ROAS, target ROAS, planned ROAS, post-ad margin, and headroom without false precision.
• Break-Even ROAS Audit Checklist: Audit cohort scope, values, costs, attribution, delays, formulas, fixtures, privacy, release evidence, corrections, and rollback in one log.

Next step: Open Seller Profit Guard.

This is operational planning help, not tax, accounting, legal, financial, or platform-policy advice. Review the Terms and disclaimer, and verify current platform rules and fee assumptions before changing prices.