What's New In V5?

GoPlanogram Version 5 is our largest update ever. Virtually every part of GoPlanogram has been updated and improved -- without taking away the features our customers have enjoyed for years.

Below enumerates many of the changes. Use the sidebar to navigate to any section that is most of interest.

Aisles, Bays, and Racks

GoPlanogram 4 Racks required each Bay to be uniform -- the same dimensions, type (slatwall, pegboard), color, etc. Additionally, this required users doing math to determined each Rack's number of bays -- having to ensure the Width of a Rack was a multiple of its Standards Spacing property.

Top-level Racks (Bays) in GoPlanogram 5 are now organized in curtains_closed Aisles -- each Aisle may have any number of shelves Bays, and each Bay may have its own completely independent specification.

An Aisle may optionally include a Base Deck -- a special crop_16_9 Shelf affixed to the bottom of each bay.

Additionally, bays can easily be added, removed, detached, or swapped with other bays, both via selection adornment buttons, or the Rack context menu

Product Positions

Merch Styles

An item may support multiple pallet Merchandising Styles -- useful when a product can be displayed in different ways, though the item for purchase is the same (this is not the same as selling a single vs. a 6-pack of soda, for example)

If you are a catalog Admin and want to learn how to add merchandising styles for items, click here.

Nested Positions

Product positions may be Nested, such as bowls that stack into one another.

Layered Groups

Occassionally, it is useful for have multiple different products to share a position. This is when creating a Layered Group is useful.

A Layered Group arranges its positions either Front to Back or Top to Bottom

Common examples include:

• Multiple items sharing the same peghook, such as differently sized gift bags (Front to Back)
• Different items stacked on top of each other (Top to Bottom)

Below is an example of a Front to Back Layered Group:

Below is an example of a Top to Bottom Layered Group:

POG Comparisons

A Plan may be compared to any other saved Plan, automatically highlighting SKU changes, adds, and deletes.

This comparison report may be downloaded as a PDF or XLSX file.

Shelves and Containers

Shelves now default to the Left Aligning layout, and their dropzone is not visible by default. Both these settings can be reverted in File > Settings if desired.

Slanted Shelves

A Shelf can be specified as Slanted, by setting its Slant Height property. This will be reflected in 2D and 3D.

Shelf and Container Fences

Shelves and Containers both support Fences -- structures in front of product Positions often used to prevent products from sliding off

Containers

Nearly every dimension of a container is now customizable (sides, base, back), to allow for more arbitrary configuration, especially for the use case of Containers as dividers (often on Shelves, to represent cubbies)

Containers now support the same auto-layouts as Shelves, as well as a Container-specific Center-Align option

Topdown Plan View

In addition to the standard  Plan View, one may also view the fixtures of a planogram in  Topdown View or 3d_rotation 3D View.

Topdown View is most often useful when creating planograms for mid-sized spaces of related fixtures -- for example, a clothing rack wall with a few complementary tables in front of it. For larger spaces, it is recommended to instead arrange entire  Plan files within a  Store Plan file.

Revamped Filesystem

The Filesystem has been iterated upon to more easily allow users to find what they're looking for.

The distinction between File > Import and File > Open is gone. Now, everyone uses File > Open, whether they are opening a file they own, or another user created.

To aid with this, navigating the Filesystem (both choosing a top level drive or drilling deeper into a folder structure) has been remade.

Additionally, the default view (Anywhere) show all files a user has at least READ access for. We anticipate most users will simply use the Anywhere view, perhaps in conjunction with a search (or more advanced) filters.

Access Control

Much more fine-grained access control mechanisms exist now, both for Filesystem entities ( Plans, group_work Projects, analytics Store Data Sets,  Components, shopping_basket Assortments...) and customizations (Heatmaps, Report Property Sets, Labels, etc...)

Projects

A new Filesystem type, group_work Project, has been added.

A Project is a collection of  Plans. When a Project is open, one can easily swap between its Plans via a UI panel.

Projects allow for easy in-app bulk reporting and SKU replacement. Additionally, the revamped Insights panel can produce real-time reports for all Plans in the currently open Project (or a chosen cross-section of Project Plans).

Catalogs and Assortments

A GoPlanogram site may have more than one catalog now. If this is the case, each Plan file declare which catalog(s) it uses.

Assortments are a new way to save a set of catalog items for later use. They are a GoPlanogram Filesystem type, and can be identified by the shopping_basket icon.

Assortments make use of the list_alt Item List and filter_altCustom Filters features to create a reusable, dynamic set of items.

An assortment can be chosen to filter the catalog by, or as selection criteria for POG template rules (for automatic regional generation).

Components

What was formerly known as Groups / Saved Fixtures in v4 has been generalized and made into a new Filesystem type called Components.

 Components are reusable groups of products, fixtures, and other elements that are saved to the Filesystem, brought in from the Components Catalog and can be used in multiple planograms.

As these are Filesystem items, they can be shared with other users, or restricted to particular person Users or diversity_2 Teams.

Common use cases for Components include:

• Creating a fixture library that can be used across planograms, by all your users
• Grouping products that are frequently used together, such as a set of complementary items.
• Designating a Plan section, such as a Shelf, whose contents will change whenever the root  Component changes

Reporting Changes

Bulk reporting is now possible (both in-app, and via API), largely through the use of group_work Projects (covered elsewhere on this page)

Scope

A reported Aggregate / Breakdown may now specify its Scope -- the type of collection of items the aggregate will be calculated against.

This is a somewhat advanced feature, so the default is for Scope to be unset.

Below is an example of setting the Total Cost aggregate's Scope to be Scoped against the whole Project (so it gives the total cost of all Plans in the project, rather than each Plan's total cost)

POG Generation

A new Filesystem type, assignment Templates, has been added.

Each Template has one or more Rules. A Rule dictates a set of items (dynamically or statically) to place on a POG, and what criteria to optimize for.

A user may then draw Regions for each rule over fixtures in the canvas. Each Region corresponds with a Template Rule.

At the user's discretion, they can then generate optimally selected product Positions in all drawn Regions, or a subsection of them.

API / Automation

Many API endpoints will be exposed with the release of GoPlanogram 5 including:

• Writing data directly to a GoPlanogram catalog
• Writing data directly to a GoPlanogram Store Data set
• Generating a report out of GoPlanogram (for any arbitrary set of Plans, using any RPS), in PDF, XLSX, or JSON format
• Automated SKU replacements
• Automatic POG generation via templates

Official documentation for these endpoints should be available in early 2026

Item Replacements

One may now easily replace items (product Positions and/or dynamic Components), within a single Plan, or across an entire Project of Plans.

This can be done both in-app and via API.

Store Planning

 Storeplans are a new Filesystem type.

They can be used to arrange pre-existing  Plan files in a topdown view. Optionally, a scaled schematic image of your space can be included to position fixtures accurately.

We plan to iterate and enhance this feature as feedback is received.

Peghooks

widgets Product Positions and dataset Layered Groups use phishing Peghooks when affixed to a Pegboard or Slatwall shelves Rack or dry_cleaning Bar.

Setting a hook may be useful for atypical product snapping (due to an offset or slant), or if one must output hook Capacity (inferred from explict hook length, or prongs)

The hook used obeys the following hierarchy:

1. Explicit: The hook used is explicitly set by the user
2. Catalog Default: The hook used by default for this item
3. Fixture Default: The hook used inferred by the item's parent fixture

Misc

Fully customizable UI

Freely switching between units (centimeters vs inches)

Product position capping

SSO for enterprise customers

Built-in tools for catalog image manipulation on upload (cropping, background removal)

When multiple fixtures of the same Type are selected, then you open the Properties dialog for one of them, one may now specify which property changes to propagate to all selected fixtures

Shelves and Bars of the same Alignment (Left Align, Even Align, etc) can be marked as Can Combine. If 2 or more such fixtures are vertically aligned, products placed upon them will treat the entire length of all fixtures as one, filling the contiguous fixtures in accordance with the shared alignment