Data Operations
The controlled path from grocer source systems into canonical records. Nothing reaches a financial result until it is received under contract, mapped, quality-checked, reconciled and released.
Every verified result in Nourishe is grounded in controlled source data, reconciled before use and traceable through every transformation.
Data is never blended across organizations. Every screen operates inside one grocer context.
Source coverage
Coverage answers one question before any number is calculated: do we have all the data we need, for the right entities, for the right period, from the right system of record? A missing or stale source is stated plainly rather than assumed away.
Coverage completeness
Datasets complete or complete with an approved exception for 2027-Q2.
Registered sources
2 authoritative · 2 corroborating
Measurement readiness
A financial result may only be produced from data that is complete for its declared scope, or explicitly partial with approval.
| Dataset | Source system | System-of-record class | Coverage · 2027-Q2 | What this means |
|---|---|---|---|---|
Processor settlement detail DS-0001 · Merchant account × processing date × tender type | SRC-0001 · Daily | Authoritative | Partial | Legal-entity alias GEL-MAYFAIR-LLC is not present in the approved effective-dated entity master. |
Processor fee detail DS-0002 · Merchant account × fiscal period × fee type | SRC-0001 · Daily | Authoritative | Complete | Received, reconciled and released. |
Daily POS tender summary DS-0003 · Store × business date × tender type | SRC-0002 · Daily | Corroborating | Complete with Approved Exception | Released with an approved, quantified coverage exclusion. |
Finance payment-acceptance expense DS-0004 · Legal entity × fiscal period × expense account | SRC-0003 · Monthly | Authoritative | Complete | Received, reconciled and released. |
Finance contribution-margin schedule DS-0005 · Legal entity × fiscal period × category | SRC-0003 · Monthly | Authoritative | Complete | Received, reconciled and released. |
Provider credit register DS-0006 · Provider × credit reference × fiscal period | SRC-0004 · Monthly | Corroborating | Blocked | Provider statement amount of $350,000 does not reconcile to the finance source. Neither posting nor receipt is confirmed. |
Merchant, legal-entity and store master DS-0007 · Entity / store / merchant account × effective period | SRC-0005 · Weekly | Reference Only | Missing | Expected delivery has not been received. |
Loyalty and e-commerce order summary DS-0008 · Channel × fiscal period | SRC-0006 · Monthly | Reference Only | Blocked | Prohibited field customer_email (Personal data) present in the delivered header. |
Approved baseline input DS-0009 · Legal entity × measurement period | SRC-0003 · Monthly | Authoritative | Complete | Received, reconciled and released. |
Approved solution-cost input DS-0010 · Legal entity × measurement period | SRC-0003 · Monthly | Authoritative | Complete | Received, reconciled and released. |
Connection profiles
| Dataset | Delivery mode | Credential | Last simulated test | Consecutive failures | |
|---|---|---|---|---|---|
| Processor settlement detail | Simulated SFTP feed Daily · 05:30–07:00 local | Simulated | Simulated Pass · 2027-07-01 | 0 | |
| Processor fee detail | Simulated SFTP feed Monthly · Working day 2 | Simulated | Simulated Pass · 2027-07-01 | 0 | |
| Daily POS tender summary | Simulated object-storage feed Daily · 04:00–05:30 local | Simulated | Simulated Pass · 2027-06-30 | 1 | |
| Finance payment-acceptance expense | Existing approved export uploaded manually Monthly · Working day 5 | Not Configured | Not tested | 0 | |
| Provider credit register | Simulated API feed Monthly · Working day 3 | Expired Simulation | Simulated Warning · 2027-07-04 | 3 |
Simulated integration environment. Source connections, files, records, credentials and reconciliation results are illustrative and do not connect to production systems.
Source precedence register
When two systems disagree, precedence decides which one is authoritative — and the disagreement is reconciled rather than averaged. A provider may never be the authoritative source for its own performance.
| Financial field | Authoritative | Corroborating | Approved fallback | Status |
|---|---|---|---|---|
Payment-acceptance cost Posted cost of accepting payments for the measurement period. | Finance Expense and Margin Extract (simulated) | Processor Settlement Platform (simulated) | Processor fee detail may be used as a Temporary Approved Fallback for up to one period with finance approval. | Active |
Presented card volume Card volume presented for settlement in the measurement period. | Processor Settlement Platform (simulated) | POS Tender Summary (simulated) | None approved. Defer measurement if the processor source is unavailable. | Active |
Provider credit Credits issued by a provider and proposed as recovered value. | Finance Expense and Margin Extract (simulated) | Provider Credit Register (simulated) | None. A provider may never approve its own performance data. | Pending Approval Proposed change from provider register to finance posting as the authoritative source for provider credits. Prospective only; historical releases preserved. |
Data contracts
A data contract states what a source must deliver, in what shape, at what frequency, and what happens when it does not. It is versioned, effective-dated and approved by both the data owner and finance.
| Dataset | Version | Effective | Cadence and deadline | Status | |
|---|---|---|---|---|---|
| Processor settlement detail | v2 | 2026-01-01 | Daily · Working day 5 after period end | Superseded | |
| Processor settlement detail | v3 | 2027-01-01 | Daily · Working day 5 after period end | Active | |
| Processor fee detail | v3 | 2027-01-01 | Monthly · Working day 5 after period end | Active | |
| Daily POS tender summary | v2 | 2027-01-01 | Daily · Working day 5 after period end | Active | |
| Finance payment-acceptance expense | v4 | 2027-01-01 | Monthly · Working day 5 after period end | Active | |
| Finance contribution-margin schedule | v4 | 2027-01-01 | Quarterly · Working day 5 after period end | Active | |
| Provider credit register | v2 | 2027-01-01 | Monthly · Working day 5 after period end | Active | |
| Merchant, legal-entity and store master | v1 | 2027-01-01 | Weekly · Working day 5 after period end | Active | |
| Loyalty and e-commerce order summary | v1 | 2027-01-01 | Monthly · Working day 5 after period end | Active | |
| Approved baseline input | v4 | 2027-01-01 | Per approved baseline version · Working day 5 after period end | Active | |
| Approved solution-cost input | v4 | 2027-01-01 | Quarterly · Working day 5 after period end | Active |