Visible assumptions. Reviewable calculations.
SellerHub is decision-support software. This page explains how inputs become results, what an audit flag means, and where seller verification is still required.
Methodology last reviewed
Inputs and report handling
Report tools read the file selected by the user inside the active browser. Parsers normalize column names, common punctuation differences, and supported number formats before calculating results. A tool should stop with a clear error when required fields cannot be identified rather than silently treating missing data as zero.
Manual calculators start with editable examples. These values demonstrate the workflow; they are not current quotes for a specific seller, SKU, category, marketplace, or shipping plan.
Core formulas
The exact cost components vary by tool, but the following definitions are used consistently where the required inputs are available.
- ACoS
- Advertising spend ÷ attributed advertising sales × 100
- ROAS
- Attributed advertising sales ÷ advertising spend
- TACOS
- Advertising spend ÷ total account sales × 100
- Contribution profit
- Revenue − product costs − Amazon fees − advertising − refunds − other included costs
- Net margin
- Net profit ÷ revenue × 100
- ROI on cost
- Net profit ÷ included landed cost × 100
- Days of cover
- Available units ÷ adjusted average daily unit sales
- Reorder point
- Expected lead-time demand + safety stock
Zero denominators are handled explicitly. When a percentage or ratio cannot be calculated responsibly, the interface should show that it is unavailable instead of displaying infinity or a misleading zero.
What an audit signal means
Audit tools compare seller-supplied records with visible rules, totals, thresholds, or relationships. A flag means “review this evidence,” not “Amazon made an error.” Reimbursements, inventory events, payment differences, catalog relationships, and advertising routes can have legitimate explanations outside the uploaded report.
When a tool suggests an action, the underlying rows and calculation should remain available for review and export.
Fees, policies, and changing marketplace rules
Amazon fees and requirements depend on marketplace, category, dimensions, weight, storage period, program eligibility, and effective date. SellerHub labels editable fee assumptions and date-sensitive examples. Always confirm the exact SKU in Seller Central, Amazon’s Revenue Calculator, Fee Preview, current rate cards, or the shipment workflow presented to your account.
Published schedules may change after a tool is reviewed. The changelog records material updates, while the support page provides a way to report a suspected outdated rule.
Quality controls
- Required columns and invalid files produce visible errors.
- Calculations use seller-visible inputs and configurable thresholds.
- Exports retain source evidence or explain how a summary was produced.
- Edge cases such as empty data, negative values, missing dates, and zero sales are handled deliberately.
- Production builds are linted, type-checked, statically rendered, and browser-tested before release.
Limits and seller responsibility
SellerHub does not connect to Amazon, submit claims, change listings, adjust campaigns, file taxes, or verify the completeness of an export. Results do not replace Seller Central records, Amazon policy, accounting advice, tax advice, legal advice, or professional operational judgment.
Before acting, confirm report scope and date range, marketplace, currency, tax treatment, attribution window, SKU mapping, fee schedule, and any rows excluded from the source export.