Saving and Copying
A Store Plan references Plans rather than containing them, which changes what saving, copying and sharing mean. This page covers the file operations that behave differently for Store Plans, and the safeguards GoPlanogram puts around them.
Saving a Store Plan
A Store Plan is saved with File > save Save, or with Ctrl + S, exactly as a Plan is. What gets written is the list of sections and their positions and angles, the schematic settings, and any photo_camera Cameras. The contents of the referenced Plans are not copied into the Store Plan -- they are read from those files each time it opens.
history Previous Versions
Every save of a Store Plan archives the version that came before it, so an earlier layout can always be recovered. Archived versions are reached the same way as for Plans, through Previous Versions in the Filesystem, and are kept for 30 days by default. See the Filesystem overview.
Plans Used in Store Plans
Because one Plan may be positioned in many Store Plans, saving a Plan can change layouts you are not looking at. GoPlanogram therefore warns you: if the Plan you are saving is used anywhere, a Save will Affect Derived Works dialog lists how many Store Plans use it and names several of them before the save proceeds.
If those changes are not meant to propagate, cancel and use save_as Save As instead: the new file is not attached to any Store Plan, leaving the original -- and every layout that uses it -- untouched. The dialog can be suppressed for good with its don't-show-again option.
The relationship can also be inspected before you edit anything: with a Plan open, the Plan Inspector lists the Store Plans that use it, and each entry can be opened directly.
Copying a Store Plan
Copying a Store Plan from the Filesystem asks for a destination folder and then asks a second question: how to copy it. The two answers behave very differently.
Shallow Copy
Creates a new Store Plan that references the same underlying Plans. The layout is duplicated; the planograms are shared. Later changes to those Plans appear in both the original and the copy.
Use this for a variant of the same store -- a seasonal reset, an alternative floor layout, a what-if -- where the merchandising should stay in sync.
Deep Copy
Creates a new Store Plan and copies every Plan and nested Store Plan it references, placing the copies in the destination folder. The result is completely independent: nothing you do to it affects the original, and nothing done to the original affects it.
Use this to hand a store layout to another team, to branch a format for a different region, or to experiment without any risk to live files.
Deep copies of large stores can take a while; a progress dialog is shown while the files are created. See Teams and Access for how READ and WRITE access are granted.
Locking and Read-Only
Like other files, a Store Plan is locked while someone has it open for editing. Opening a locked Store Plan offers to open it read-only: you can view the layout, walk it in 3d_rotation 3D and report on it, but not move sections or save.
The same applies one level down. If you open a Store Plan you have READ access to but not WRITE, and then open one of its Plans, that Plan opens read-only as well -- so a store layout can be shared widely for review without exposing the planograms to accidental edits.
Store Plans in Projects
group_work Projects may include Store Plans alongside Plans. Adding a Store Plan to a Project brings all of its planograms into the Project's newspaper reporting and insights Insights, which is the usual way to analyse several stores together rather than one at a time.
