Data Collection Delays - Tesco SKUtrak service impacted

Missing data 6th to 8th November (Resolved)
The Tesco data for 6th, 7th and 8th November, which was previously missing, has now been collected and is available on the platform.

Store names (Resolved)
The issue where some Tesco store-level data was showing the store name as “Unknown” has now been resolved. Store names are displaying correctly again, and filtering by individual store is working as normal. No data was lost during this period.

Data timeliness (Monitoring)
Tesco data is flowing again following our reprocessing. Please note there is still a short lag in the most recent data being available while the platform catches up to its normal daily schedule.

Thank you for your patience. We will post a further update once Tesco data is fully back to its usual timeliness.

We are aware that Tesco data has not updated since 5 November. We have confirmed directly with Tesco that the underlying data is present and accurate at source, and we have triggered a fresh collection to bring the platform back up to date.

As a result of a separate issue over the weekend, some Tesco store-level data has come through with the store name showing as “Unknown”. We expect this to correct itself as part of the reprocessing now underway.

No data has been lost. Once the collection and reprocessing complete, Tesco data will return to its normal daily schedule and store names will display correctly. We will post a further update as soon as the refresh has landed.

The recent backlog has now cleared and Tesco data on SKUtrak is up to date, including the previously outstanding 22 October.

Tesco’s source reports are still being generated later and less consistently than usual, so you may occasionally see the most recent day’s Tesco data arrive late or read around a day behind. This corrects itself automatically once Tesco generate the report and we collect it the following day, so no data is lost in the process.

We are continuing to monitor this closely and are working on a longer-term improvement to capture the later files more reliably. We will post further updates here if anything changes.

The data for 23, 24 and 25 October has now been recovered and is available on SKUtrak, so the recent days have largely caught up.

One day, 22 October, remains outstanding. Tesco did not generate their report for that day at source, so there is nothing for us to collect for it yet. We have raised this with Tesco and will load the data as soon as they make it available.

As a reminder, affected days are corrected retrospectively once collected, so 22 October will backfill automatically once Tesco provide it. We will post further updates here as that resolves.

The most recent day currently available on SKUtrak is 21 October. There are two separate things affecting the days since:

23 to 25 October: this data is available from Tesco, and we are in the process of recovering it onto the platform. These days should appear shortly.

22 October: Tesco’s report for this day was not generated at their end, so it is not currently available to collect. We are following this up with Tesco.

What this means for you: recent Tesco days may be missing or incomplete until the above completes, and any metrics calculated from them (for example availability and week-on-week comparisons) may be affected. All data is corrected retrospectively as it lands.

We will post further updates here as the days are recovered.

The data for 18 and 19 October has now been processed and is available on SKUtrak, so the platform has caught up on those two days.

One day, 17 October, is still outstanding, as Tesco has not yet released that day’s report at source. We will collect and apply it as soon as it becomes available, at which point the affected week will reconcile to the full figure.

More broadly, Tesco’s daily reports are continuing to arrive later and less consistently than usual, so the most recent day’s data may still be delayed at times. We are continuing to monitor this and will post further updates here as the position changes.

We are continuing to see Tesco’s daily source reports released later and less consistently than usual. The current position (as of 20 October) is:

17 October: Tesco has not yet made this day’s report available at source, so it cannot be collected yet. We are retrying automatically and it will come through once the retailer releases it.

18 and 19 October: both of these reports have been received, but are not yet visible on SKUtrak. The most recent days are processed together, so these two are currently held behind the outstanding 17th. We are working to release them so they appear as soon as possible.

The latest Tesco day currently available on the platform is 16 October.

This issue is still ongoing. Tesco's source reports are continuing to be made available later and at less consistent times than usual, which can leave the most recent day's Tesco data arriving late or temporarily reading a day behind.

To help you plan around it: Tesco data normally finishes updating in SKUtrak by around midday (UK time), with collection typically completing between approximately 09:00 and 11:30. On affected days, a later collection runs into the early afternoon to pick up the delayed report. We'd therefore recommend relying on Tesco data up to the previous day, which is reliably available by around midday.

We're continuing to monitor this closely and adjust the timing of our collection so we pick up the reports as soon as they're released.

We'll update here again as the situation improves.

We're currently seeing intermittent delays in Tesco data updating in SKUtrak. The source Tesco reports are being made available later than usual and at inconsistent times, which can cause the most recent day's Tesco data to arrive late or temporarily read a day behind.

We're actively monitoring this and looking to adjust the timing of our data collection to pick the reports up as soon as they become available. In the meantime, we'd recommend referring to Tesco data up to the previous day. We'll update here as the situation improves.