Cloning VM Briefs
Last updated February 11, 2026
Cloning is a useful way to save time and maintain consistency when creating new VM briefs based on existing layouts and plans.
Cloning a VM guide allows you to:
- Reuse existing floor plans and fixture setups
- Maintain consistency across stores or seasons
- Save time by avoiding repetitive setup tasks
- Ensure product placement and directive consistency from previous rollouts
What gets cloned into the new VM brief?
When you create a new VM guide by cloning a previous one, several components from the original guide are automatically copied over:
VM Guide Properties
- Fixtures: All fixtures that existed on all stores in the original guide will be included in the new one. This means you don’t have to start by adding and positioning fixtures onto floor plans for each store again.
Store Properties
- Fixture location: The position of each fixture on the floor plan is retained.
- Fixture dimension: The size and rotation of fixtures is preserved for each store.
Fixture Properties
- Fixture notes: The merchandising directive linked to the fixture.
- Fixture color swatches: Visual indicators representing the color story or palette used.
- Example images and captions: Visual references for how the fixture should appear and its description.
- Fixture rows and row names: Structure of how products are arranged.
- Products and product captions: The specific products assigned to each row and its description.
What does NOT get cloned into the new VM brief?
While the cloning process captures much of the original setup, some elements are intentionally left behind to prevent outdated data from being carried over.
Store Properties
- Resources: Files uploaded specifically for the original store setup.
Fixture Properties
- Fixture statuses: Progress status indicators for execution (e.g. “Approved”, “Revision Required”) are reset.
- Fixture due dates: Due dates for each fixtures are reset.
- Execution images: VM execution photos uploaded by store teams are not carried over.
- Execution comments: Comments added by the team during VM brief execution or review.
Was this article helpful?