An open format for planograms
Free your shelf data.
You shouldn’t have to pay a software vendor to use your planograms.
Vazen TOML puts you back in control of your planogram data, with one open format that lets any new tool, partner or AI use your plans correctly from day one. It works with your legacy systems too.
A complete shelf plan in a few lines
Two cereal products share one shelf, with three facings each and four packs deep. This is the complete spec file that describes the plan.
Example shelfvazen/spec · 0.3.0
schema = "vazen/spec"
schema_version = "0.3.0"
name = "Example shelf"
[[products]]
name = "Oat cereal"
[[products]]
name = "Cocoa cereal"
[[fixtures]]
[[fixtures.equipment]]
type = "shelf"
[[fixtures.equipment.sites]]
product = { name = "Oat cereal" }
facings = { wide = 3, deep = 4 }
[[fixtures.equipment.sites]]
product = { name = "Cocoa cereal" }
facings = { wide = 3, deep = 4 }A spec describes the products and facings, leaving exact positions and dimensions open. The illustration shows one possible layout.Read the example
Why Vazen TOML?
Tools that work together
Retailers and brands should be able to choose their software without starting again with their shelf data.
A shared format gives planning, analysis, simulation and AI tools a common model to read and write.
The case for an open format- Choose your tools
- Read and analyse plans outside the application that created them. Share the data with the partners and software you choose.
- Share the integration work
- Build against one published structure for products, equipment and placements. Each tool can use the same description of the shelf.
- Keep the detail retail needs
- Represent product variants, nested equipment and your own attributes in the same file. Add information without inventing another format.
- AI you can check
- Every plan follows a published specification with defined units and meanings, so you can check what an agent reads and writes before anyone acts on it.
Build with Vazen TOML
Start with a file and a standard TOML parser. The docs include a working Python example, and the specification defines the data.
Current schema: 0.3.0. Schema and package versions
JavaScript / TypeScript
Install from npm:
npm install @vazen/tomlThe npm package reads and writes Vazen TOML, JSON and PSA files. A Python package is planned.
Building a tool or considering adoption? Share an idea, propose an extension or help shape the specification.
Contribute your ideas