External File Formats

In addition to exporting your work as reports and images, GoPlanogram also supports importing and exporting in the third-party JDA / Blue Yonder PSA file format.

Importing External Files

To import from a third-party file format, go to vertical_align_bottom File → Import → PSA File.

Dialog to import files from the .PSA format.

Choose one or more PSA files via the Choose Files input. A single PSA file can contain multiple planograms, and you can select several files at once, so the dialog lists every valid Plan it found:

Select one or more planograms to import.

Select the Plans you want to import (use Ctrl / Shift to select multiple, or Select All). The Import button then loads them.

search Previewing Products

Enable Show all products in this PSA to preview every unique product the file contains — including item ID, UPC, category, and dimensions — before importing. You can also press download Download XLSX to export this product list as an Excel spreadsheet.

Saving PSA Files

If Save imported files is selected, the selected planograms are saved into your Filesystem; you will be prompted to choose a location. If more than one Plan is selected, this option is always active. You can also attach label File Tags to the imported Plans at the same time.

receipt_long Saving Catalog Data

Most PSA files contain Catalog data about the items in their planograms. To save this data into one of your site's Catalogs, select Save Catalog Data. You have two options:

• Save to an existing catalog that you have WRITE access to.
• Save to a brand-new catalog, if your site is not currently at its max catalogs limit.

Choose an existing catalog to import PSA data.

Specify a new catalog to import PSA data to.

When saving to an existing catalog, enable Overwrite Existing Items to replace items that share the same item_id with the values from the PSA file. This affects every plan that uses the catalog and cannot be undone, so you will be asked to confirm before importing.

If you do not save a PSA's catalog data, and your existing site catalogs do not contain the items in the PSA, you can still view the PSA with temporary catalog data. However, this catalog will disappear on refresh, so some items may not have valid catalog data the next time you open the planogram.

analytics Importing Store Data (Performance)

Many PSA files carry Performance records — per-item metrics such as sales, movement, facings, days of supply, and dozens of other measures. When you enable Save Store Data, GoPlanogram converts these Performance records into a analytics Store Data set that is saved alongside your planogram and automatically linked to it.

The dialog lists only the Performance fields that actually contain values in your PSA file. Choose which ones to save — use the search search box to filter the list and Select All / Deselect All to toggle the currently shown fields:

• Each selected field becomes a Store Data property (prefixed with !), matched to items by their item_id.
• Enable Only items in this POG to limit the Store Data to items actually placed in the imported planogram. Performance records otherwise span the entire catalog.
• When importing multiple Plans, a separate Store Data set is generated and linked for each one.

Once imported, these fields behave exactly like any other Store Data — they become available for local_fire_department Heatmaps, edit_note Labels, newspaper Reports, and other customizations.

key Matching Products: ID vs. UPC

Every PSA file declares a primary key — the field GoPlanogram uses to match PSA products (and their Performance records) to catalog items. This is usually the product ID, but some files key on UPC instead, or on a composite of both.

Under Advanced Options → PSA Primary Key, you can override which field is used:

• Auto (from PSA file) — use the key the PSA file itself declares. This is the default and is correct for most files.
• ID — match on the product ID field.
• UPC — match on the UPC field. Useful when your catalog's item_id values are actually UPCs, even though the PSA declares ID as its key.
• Both (composite) — match on a combined ID-UPC key, for files where neither field is unique on its own.

Choosing the right key ensures PSA positions and Store Data line up with the correct receipt_long Catalog items on your site. When multiple catalogs contain the same item_id, GoPlanogram binds each position to the catalog whose product dimensions most closely match the PSA. The Show all products preview updates live as you change this setting, so you can confirm the match before importing.

group_work Creating a Project

Under Advanced Options, enable Create Project to gather the imported Plans into a single group_work Project. This option requires Save imported files to be active.

Exporting to External Files

To export to a third-party file format, go to upgrade File → Export → PSA File.

Dialog to export your current planogram to a .PSA file.

Press Export to generate a PSA file and download it to your local system.

Some GoPlanogram features, such as inventory_2 Containers and dataset Layered Groups, are not supported by the PSA file format. If your planogram contains any of these, the dialog will show you a warning.

If you have a group_work Project open, you will have the option to export your entire Project as a single PSA file, or as a ZIP file with one PSA file for each planogram.

PSA Export with Images

When exporting to PSA format, you have the option to include a ZIP file containing all used product images. This ensures that whoever receives your PSA file(s) will have images included when they open the planogram in their software.