Data discrepancies
Numbers in DataHawk don't match Seller Central, Vendor Central, your BI tool, or your accounting system. Find the most common causes and fixes.
Numbers in DataHawk look different from another source you trust? This is the most common issue category and usually has a known explanation. Most discrepancies fall into one of eight categories below. Find yours and follow the checks.
Run these four checks first
Most "discrepancy" cases are actually mismatched filters between the two reports you're comparing.
- Same date range?: Including / excluding today matters. Try expanding by one day on each side.
- Same time zone?: Amazon reports are typically UTC. Your local timezone in the DataHawk app might be different.
- Same currency?: DataHawk converts to your workspace's display currency. Native amounts in source reports differ.
- Same marketplace + account scope?: Multi-account customers sometimes compare "All accounts" in DataHawk against a single account in Seller Central.
Find your discrepancy
Specific problems
If you have a more specific scenario, jump directly to the article:
Why are fees under No SKU?
Why Amazon Seller fees can appear without a product or brand, and what to check.
Ads data appearing under the wrong account type
When ad data shows up under your Vendor account but should be under Seller, or vice versa.
I can't see data in Manufacturing views, but I see it in Sourcing
The Sourcing vs Manufacturing data difference for Vendor accounts; explained.
Still stuck?
Before contacting support, gather:
- Your workspace ID
- The exact two reports being compared (DataHawk table/dashboard name + the source-of-truth report name)
- Date range, marketplace, account, and currency for both
- The two numbers with the exact difference
- Screenshots of both sides (cropped to show filters and totals)
This information cuts our investigation time by ~80%. Send to [email protected] with "Discrepancy" in the subject.
For active production reports: If a customer-facing dashboard is showing wrong numbers right now, add "production issue" to your email subject for priority handling.