Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.retailgrid.io/llms.txt

Use this file to discover all available pages before exploring further.

The Datasets page is where you manage all the data you’ve loaded into Retailgrid — product master data, transaction history, competitor prices, and product-store-level data — in one place. Open it from the Datasets icon in the left sidebar.
Datasets page

What you’ll see

Each row is one loaded dataset. The columns:
ColumnWhat it shows
DatasetThe dataset type — Products, Transactions, or Competitors.
StatusReady once the file has finished parsing and validating.
Last updatedWhen the file was last replaced or refreshed.
Uploaded byThe team member who uploaded the current version.
RowsRow count after parsing.
Source fileThe original filename of the uploaded CSV or XLSX.
OriginHow the data got in — currently CSV / File for files uploaded through the UI.

Upload a new dataset

Click Upload data in the top-right corner. The Upload Data modal opens; pick the dataset type (Products, Transactions, Competitors) and select your file. For the field requirements per dataset, see: You can also load Products and Transactions data programmatically via the public Retailgrid REST API.

Replace, download, or delete a dataset

Use the three-dot menu at the right of any dataset row to:
  • Replace the file — upload a fresh CSV or XLSX without changing the dataset’s role. The new file replaces the previous version’s rows and the row count updates accordingly.
  • Download the current file — useful for reviewing what’s currently loaded or sharing with a colleague.
  • Delete the dataset.
Replacing a dataset preserves its role (Products stays the Products dataset) and refreshes the data available to your existing grids and agents.
Deleting a dataset removes its rows from Retailgrid. Grids that depended on those rows will become empty or partial. Replace rather than delete when you only want to refresh the data.

Status values

StatusMeaning
ReadyParsed, validated, and available for use in grids and agents.
ProcessingUpload is being parsed. Appears briefly after a fresh upload.
FailedParsing or validation failed. Open the row to see the error, then fix the source file before re-uploading.

When to upload vs replace

  • First time a dataset type is loaded — use Upload data and pick the type.
  • Refreshing data you already loaded (e.g. monthly product master refresh, daily competitor price feed) — use Replace on the existing row. This keeps grid bindings intact. Replaced datasets are picked up by the nightly grid refresh; existing grids show the new rows the next morning without any further action.
  • Switching to a totally different schema — delete and re-upload, then expect to remap fields.