Store Data
analytics Store Data files allow you to specify data properties for items on a per-planogram basis, in addition to the fields specified globally in the Catalog data.
Store data is fully customizable, and you can include any number of fields in your Store Data set. Common examples include weekly sales metrics, inventory, sale items, and more.
Uploading Store Data
To create a new analytics Store Data file, navigate to File → New → Store Data. Store Data is saved into the Filesystem in the same way as Planograms or other files.
When you create a new analytics Store Data set, the dialog below will appear, which allows you to set the file's name and description. Here you can also modify and preview the data fields.
analytics Store Data files are updated via a spreadsheet or CSV file, which is uploaded via the Replace Store Data input. The format of this spreadsheet is simple:
- item_id must be the first column
- Each subsequent column must have as its header a Store Data field name, which must start with !.
- Empty or unspecified values for a field will default to 0.
Below is a screenshot of an example analytics Store Data file with a few items. You can download this sample file here.
Once a Store Data set is populated, you can preview its contents with the visibility View Current Data button:
Using Store Data
To link a analytics Store Data set to a Planogram, simply open it via File → Open while you currently have a planogram open. The selected store data set will now appear in the Store Data panel on the right:
The next time you save your work, the Store Data will be linked to your planogram, and will remain linked the next time you open that planogram.
- The visibility button allows you to preview the currently selected Store Data.
- The folder button allows you to choose a different Store Data set to link to this planogram.
- The button allows you to edit the current Store Data set.
- The button unlinks the current Store Data file.
Once a Store Data set is linked to a planogram, its fields become available for site customizations. This allows for more in-depth, specific, display analysis, often through the use of various customizations like local_fire_department Heatmaps, newspaper Reports, insights Insights, assignment Template Rules and more.
Below is an example of a custom Product Label and a custom Heatmap, both tied to the !WeeklySales data field we uploaded.
Store Data via API
If you have GoPlanogram API access, you can programatically upload, attach, and access analytics Store Data via an API endpoint.
See the API documentation for more details.