2026-04-03
Three checks before you blame the warehouse
Mismatched totals often begin at the emitter. These three field checks save days of warehouse archaeology.
When a dashboard under-counts purchases, the instinct is to inspect the warehouse model. Start earlier. First, confirm the client still emits the purchase event after the latest release—many “pipeline” incidents are silent removals in a feature flag.
Second, sample raw payloads for duplicate identifiers. Deduplication that keys on session id instead of transaction id will suppress legitimate repeats. Third, verify timezone handling at the emitter: an event stamped in device local time and later reinterpreted as KST shifts day boundaries for overnight orders.
Only after those three checks fail to explain the gap do we open warehouse jobs. That order keeps remediation close to the people who shipped the change, which is where most lasting fixes live.