Step 2: Enrich with Store Metadata
Raw POS transactions begin with a store_id. The reference adds authored region, format, and location fields before delivery. Review those values against an authoritative store registry in a real implementation.
Store Lookup Table
The canonical reference owns the inline store lookup and derived analytics fields, including average-item-price rounding. A deployed implementation needs a reviewed file or API contract.
Inspect the sample input and enriched output in the Explorer.
Why Enrich at the Edge?
- One enrichment, many consumers: MotherDuck, dashboards, fraud systems all get enriched data
- No warehouse compute wasted: JOINs on store metadata happen at the edge for free
- Consistent dimensions: Every system sees the same region/format/city — no drift
Next Step
Enriched data is great, but bad data is worse than no data. Next, we'll validate transactions and flag anomalies.
