Skip to content
English
Log into Green Check
  • There are no suggestions because the search field is empty.

Understanding Data Ingestions

How the platform collects, recovers, and reconciles sales data from POS integrations. For financial institution compliance and audit teams.

Data Ingestions Reference Guide

Each time the Green Check ingestion system runs, it looks up the most recent sale record on file for the CRB and requests everything from that point forward from the POS system.

This means ingestions are always incremental: they pick up where the last successful pull left off rather than re-pulling the full history each time.

If an ingestion fails, the next successful run automatically goes back to that same last-known sale record and collects any data that was missed.

The Ingestions tab in the Green Check platform's Monitoring Review shows a log of every attempt the system made to retrieve sales data from a Cannabis Related Business's (CRB's) point-of-sale (POS) system during the review period. Each row represents one API call, whether it succeeded or not.

Ingestions Tab vs. Data Summary Tab

The Ingestions tab is a diagnostic log showing when the system tried to collect data and what each run retrieved.

The Data Summary tab is the authoritative source. It always shows the complete, reconciled totals for the review period. Direct auditors to the Data Summary tab.

Three questions come up most often when reviewing the Ingestions tab:

  • What is the difference between a Failed status and a Successful - $0 status?
  • Why does the ingestion dollar amount sometimes not match actual sales for that day or month?
  • How does the system automatically recover data from days when an ingestion failed?
Section 1: Failed vs. Successful - $0

The status reflects whether the system's API call to the POS connected, not whether sales data was present.

Think of it like making a phone call:

Failed

Busy signal. The call never went through. The POS system or network was unavailable.

Common cause: CRB internet outage, POS vendor server downtime.

Data impact: No data collected. Automatic recovery happens on the next successful ingestion.

Action: None. System retries automatically.

Successful - $0

Call connected, no new data. The system reached the POS but there was nothing new to collect.

Common cause: There were no new sales to bring into the system.

Data impact: No data is missing. Sales were already captured.

Action: None. Data is complete.

Real-World Example: Blaze Cannabis (April)

Two ingestion records appeared for April 4th: one showing "Successful - $0" and a second with a dollar amount.

The first run connected to the POS but found no data yet. A later run on the same day retrieved the April 4th sales.

Both records remain in the log; the second contains the actual data reflected in the Data Summary totals.

Section 2: Why Ingestion Amounts May Not Match Actual Sales

The dollar amount on an ingestion row shows how much sales data was collected during that specific run, not the sales that occurred on that calendar date.

Three factors can create a discrepancy:

1. Catch-up from prior failures

When an ingestion fails, no data is collected that day.

The next successful ingestion runs the automatic adjuster, which looks back and pulls all sales missed during the failure window.

A single row may contain two or more days' worth of sales, making the amount appear higher than that day's actual sales alone.

2. Timezone differences

If a CRB operates in a timezone that differs from the system's processing timezone, a sale made late in the evening may not appear in the POS until the following calendar day and will be captured in the next day's ingestion.

3. Manual corrections and re-ingestions

If Green Check support corrects data, for example, fixing missing gram weights by deleting and re-ingesting sales records, the corrected data appears in a subsequent ingestion row.

That row's total may be higher than the day's new sales since it includes previously corrected records.

For Auditors: Where to Find Correct Totals

The Ingestions tab is a diagnostic tool, not a final ledger.

For accurate, reconciled sales totals, use the Data Summary tab. It reflects the complete data for the review period, regardless of how or when it was ingested.

If the Data Summary tab shows all days accounted for and totals match expectations, any failed or $0 rows in the Ingestions tab require no further action.

Real-World Example: Top Shelf (June)

Ingestions on June 2nd and June 10th both show "Failed" because the BioTrack POS was offline.

The June 11th ingestion shows $1,744, higher than June 11th's actual sales of $775.40.

This is because the June 11th run automatically recovered the missed sales from June 10th, plus a small carry-over from June 9th due to timezone handling.

The Data Summary tab correctly reflects all 30 days of June activity.

Section 3: Automatic Data Recovery from Failed Ingestions

Green Check uses an automatic adjuster that runs as part of every successful ingestion, ensuring no sales are lost due to prior connectivity failures.

  1. A scheduled ingestion runs and fails because the CRB's POS is offline or unreachable.
  2. The system logs the failure and automatically queues a retry.
  3. When the next successful ingestion runs, the adjuster checks whether any recent days have missing data.
  4. If gaps are found, the adjuster pulls the missing sales for those days alongside the current day's data.
  5. All recovered data rolls into the platform's totals. The Data Summary tab reflects the corrected, complete dataset.
  6. The original failed rows remain visible in the Ingestions tab as a permanent historical record and are not removed or modified.
What This Means in Practice

A "Failed" row is not evidence of missing data. It records that the system encountered a connectivity issue on that day.

The presence of failed rows alongside correct Data Summary totals confirms the recovery process worked as intended.

Re-ingesting data manually after the system has already recovered it is not necessary and may create duplicate records.

Contact Green Check support before initiating any manual re-ingestion.

Quick Reference: Common Questions

I see "Failed" rows. Is data missing?
Not necessarily. Check the Data Summary tab. If totals are complete, the data was recovered automatically.

I see "Successful - $0" rows. Is something wrong?
No. The API call connected but found no new data. This is normal and requires no action.

The ingestion amount is higher than that day's sales. Why?
The ingestion likely recovered missed sales from one or more prior failed days in addition to the current day.

The ingestion amount is lower than that day's sales. Why?
Some sales may have been captured in an earlier run that same day, or a small portion may carry over to the next day due to timezone handling.

Where do I look for correct totals for an audit?
The Data Summary tab. It always reflects the complete, reconciled data for the review period.

Do I need to manually re-ingest after a failure?
No. The system recovers missed data automatically. Contact Green Check support before initiating any manual re-ingestion.

Green Check | Internal & Financial Institution Use
Questions? support@greencheckverified.com