Trace · LOC-000019
Source — POS Store
Derived chronology · 5 stages · technical time- Source
POS Store BOOTSTRAP · Bootstrap control store · status INACTIVE
- Connector
Incremental sync · extract version POS_STORE_V1
Open the POS Store connector - Landed
13 Sep 2026, 18:18 IST · recorded
source updated 13 Sep 2026, 18:18 IST · recorded
Raw payload as it landed (10 fields)
- country_code
- IN
- created_at
- 2026-09-13T12:48:06.250712+00:00
- ownership_type
- COMPANY_OWNED
- record_version
- 1
- status
- INACTIVE
- store_code
- BOOTSTRAP
- store_id
- 1
- store_name
- Bootstrap control store
- timezone
- Asia/Kolkata
- updated_at
- 2026-09-13T12:48:06.250712+00:00
payload sha256 b055c0103ff8394764a9f6cdaed890fc441e6bdb5e7e56042ffc97b9852936f9
- Mapping
MAP-LOC-POS v1 · Normalize
- Resolution
Exact business identifier match · confidence 1.00000 · RES-LOC-POS-STORE v1
This is a view over the records, not a second source of truth. The landed time is technical time — when the payload arrived — not the business time of the record, which its own dates carry.
Field lineage
| Canonical field | Canonical value | Source | From | Contribution | Mapping · survivorship |
|---|---|---|---|---|---|
| country_code | India (IN) | POS Store BOOTSTRAP | ← country_code= IN | Direct | MAP-LOC-POS |
| display_name | Bootstrap control store | POS Store BOOTSTRAP | ← store_name= Bootstrap control store | Direct | MAP-LOC-POS |
| location_type | Store | POS Store BOOTSTRAP | ← constant STORE | Constant | MAP-LOC-POS |
Entity resolution
Open entity resolution
- POS Store BOOTSTRAP · Exact business identifier match · confidence 1.00000 · RESOLVED · RES-LOC-POS-STORE v1
Resolution says records represent the same enterprise thing. It is not an operational integration link.