Storepick Slot Availability Adapter

Overview

Primary objective of this integration is leveraging OSP slot availability APIs in order to provide slot availability data generated by customer slot searches so that this data can later be used for analytics and slot and routes configurations adjustments.

The approach would be to create a component that will poll the OSP API to retrieve the last 15 minutes view of live data in each poll. This is the maximum time frame available from the OSP APIs. Failing to read new data within 15 minutes cycle will result in gaps of live data. OSP does not store this data so there will be no option to recover it if the data is not read fully in real time during poll cycles.

Slot availability data will be pushed to GCP storage in the form of CSV to closely match existing interface of the Data Feed Adapter Task. The aim is to make the integration easy to transition to data feed approach if it will becomes available in the future. Note that currently there is no plans for such data feed on Ocado’s roadmap which is confirmed in this ticket . Therefore the CSV format will closely follow existing Ocado feeds format whereby each row represents slot request data element. Once the CSV is uploaded to GCP storage, appropriate data flow components would update BigQuery tables to store the data aggregated by searches and aggregated by availability.

  1. Slot Availability Adapter

  2. Dataflow Adapter