1const n=`<script module lang="ts">\r 2 export const seoTitle = 'Planogram Glossary: Fixture and Data Terms';\r 3<\/script>\r 4\r 5<script lang="ts">\r 6 import IconFileType from '$lib/components/IconFileType.svelte';\r 7 import {\r 8 EDocLink,\r 9 EFilesystemTypes,\r 10 EIconNames,\r 11 getDocLink\r 12 } from '@my/shared';\r 13 import Icon from '@my/shared/components/Icon.svelte';\r 14 import { setContext } from 'svelte';\r 15 import { writable } from 'svelte/store';\r 16 import GlossaryItem from './_components/GlossaryItem.svelte';\r 17\r 18 const glossarySearch = writable('');\r 19 setContext('glossarySearch', glossarySearch);\r 20<\/script>\r 21\r 22<h1>Glossary</h1>\r 23\r 24<input\r 25 type="text"\r 26 bind:value={$glossarySearch}\r 27 placeholder="Filter by term..."\r 28 class="w-full max-w-md px-3 py-2 mb-4 border border-border rounded-md focus:outline-hidden focus:ring-2 focus:ring-gop-secondary focus:border-transparent"\r 29/>\r 30\r 31<h3>Planogram Parts</h3>\r 32<p>\r 33 Things that appear in <IconFileType fileType={EFilesystemTypes.PLAN} /> Plan files\r 34</p>\r 35\r 36<h4>Fixtures</h4>\r 37<GlossaryItem\r 38 iconName={EIconNames.AISLE}\r 39 term="Aisle"\r 40 relatedLinks={[getDocLink(EDocLink.RACKS)]}\r 41>\r 42 A horizontal grouping of <Icon iconName={EIconNames.BAY} /> Bays that can be combined,\r 43 reordered, or have Bays added and removed.\r 44</GlossaryItem>\r 45<GlossaryItem\r 46 iconName={EIconNames.BAY}\r 47 term="Rack"\r 48 relatedLinks={[getDocLink(EDocLink.RACKS)]}\r 49>\r 50 The most common fixture type representing a Pegboard, Slatwall, or Shelving\r 51 Only section that can hold pegged <Icon iconName={EIconNames.PRODUCT} /><a\r 52 href={getDocLink(EDocLink.POSITIONS)}>Product Positions</a\r 53 >\r 54 or other fixtures like <Icon iconName={EIconNames.SHELF} /><a\r 55 href={getDocLink(EDocLink.SHELVES)}>Shelves</a\r 56 >\r 57 and <Icon iconName={EIconNames.HANGING_BAR} /><a\r 58 href={getDocLink(EDocLink.BARS)}>Bars</a\r 59 >.\r 60</GlossaryItem>\r 61<GlossaryItem\r 62 iconName={EIconNames.BAY}\r 63 term="Bay"\r 64 relatedLinks={[getDocLink(EDocLink.RACKS)]}\r 65>\r 66 A top-level Rack arranged horizontally within an <Icon\r 67 iconName={EIconNames.AISLE}\r 68 /> Aisle, which can hold <Icon iconName={EIconNames.PRODUCT} /><a\r 69 href={getDocLink(EDocLink.POSITIONS)}>Product Positions</a\r 70 > and other fixtures.\r 71</GlossaryItem>\r 72<GlossaryItem\r 73 iconName={EIconNames.SUBRACK}\r 74 term="Sub-Rack"\r 75 relatedLinks={[getDocLink(EDocLink.RACKS)]}\r 76>\r 77 A nested Rack within another fixture, such as a Pegboard section inside a\r 78 Shelving Only Bay or on a <Icon iconName={EIconNames.HANGING_BAR} /><a\r 79 href={getDocLink(EDocLink.BARS)}>Bar</a\r 80 >.\r 81</GlossaryItem>\r 82\r 83<GlossaryItem\r 84 iconName={EIconNames.SHELF}\r 85 term="Shelf"\r 86 relatedLinks={[getDocLink(EDocLink.SHELVES)]}\r 87>\r 88 A fixture that attaches to <Icon iconName={EIconNames.BAY} /><a\r 89 href={getDocLink(EDocLink.RACKS)}>Racks</a\r 90 >\r 91 to hold <Icon iconName={EIconNames.PRODUCT} /><a\r 92 href={getDocLink(EDocLink.POSITIONS)}>Product Positions</a\r 93 >, <Icon iconName={EIconNames.CONTAINER} /><a\r 94 href={getDocLink(EDocLink.CONTAINERS)}>Containers</a\r 95 >, or <Icon iconName={EIconNames.GROUPS} /><a\r 96 href={getDocLink(EDocLink.GROUPS)}>Groups</a\r 97 >.\r 98</GlossaryItem>\r 99<GlossaryItem\r 100 iconName={EIconNames.CONTAINER}\r 101 term="Container"\r 102 relatedLinks={[getDocLink(EDocLink.CONTAINERS)]}\r 103>\r 104 A fixture that attaches to <Icon iconName={EIconNames.BAY} /><a\r 105 href={getDocLink(EDocLink.RACKS)}>Racks</a\r 106 >, <Icon iconName={EIconNames.SHELF} /><a href={getDocLink(EDocLink.SHELVES)}\r 107 >Shelves</a\r 108 >, or <Icon iconName={EIconNames.HANGING_BAR} /><a\r 109 href={getDocLink(EDocLink.BARS)}>Bars</a\r 110 >\r 111 to hold <Icon iconName={EIconNames.PRODUCT} /><a\r 112 href={getDocLink(EDocLink.POSITIONS)}>Product Positions</a\r 113 >, with optional resize layout to fit items uniformly.\r 114</GlossaryItem>\r 115<GlossaryItem\r 116 iconName={EIconNames.HANGING_BAR}\r 117 term="Bar"\r 118 relatedLinks={[getDocLink(EDocLink.BARS)]}\r 119>\r 120 A fixture that attaches to <Icon iconName={EIconNames.BAY} /><a\r 121 href={getDocLink(EDocLink.RACKS)}>Racks</a\r 122 >\r 123 to hold <Icon iconName={EIconNames.PRODUCT} /><a\r 124 href={getDocLink(EDocLink.POSITIONS)}>Product Positions</a\r 125 >\r 126 or sub-fixtures like <Icon iconName={EIconNames.CONTAINER} /><a\r 127 href={getDocLink(EDocLink.CONTAINERS)}>Containers</a\r 128 >\r 129 and <Icon iconName={EIconNames.SUBRACK} /> Sub-Racks.\r 130</GlossaryItem>\r 131<GlossaryItem\r 132 iconName={EIconNames.SURFACE}\r 133 term="Surface"\r 134 relatedLinks={[getDocLink(EDocLink.SURFACES)]}\r 135>\r 136 A fixture used when <Icon iconName={EIconNames.PRODUCT} /><a\r 137 href={getDocLink(EDocLink.POSITIONS)}>Product Positions</a\r 138 > require depthwise placement, such as arranging folded clothes on a table or frozen\r 139 food in a coffin case.\r 140</GlossaryItem>\r 141<GlossaryItem\r 142 iconName={EIconNames.HOOK}\r 143 term="Peghook"\r 144 relatedLinks={[getDocLink(EDocLink.HOOKS)]}\r 145>\r 146 A defined hook type used by <Icon iconName={EIconNames.PRODUCT} /><a\r 147 href={getDocLink(EDocLink.POSITIONS)}>Product Positions</a\r 148 >\r 149 when affixed to Pegboard or Slatwall <Icon iconName={EIconNames.BAY} /><a\r 150 href={getDocLink(EDocLink.RACKS)}>Racks</a\r 151 >\r 152 or <Icon iconName={EIconNames.HANGING_BAR} /><a\r 153 href={getDocLink(EDocLink.BARS)}>Bars</a\r 154 >, with properties like length, slant, and prong count.\r 155</GlossaryItem>\r 156\r 157<h4>Planogram Content</h4>\r 158<GlossaryItem\r 159 iconName={EIconNames.PRODUCT}\r 160 term="Product Position"\r 161 relatedLinks={[getDocLink(EDocLink.POSITIONS)]}\r 162>\r 163 One or more facings of a product arranged in rows and columns, placed on\r 164 fixtures like <Icon iconName={EIconNames.BAY} /><a\r 165 href={getDocLink(EDocLink.RACKS)}>Racks</a\r 166 >\r 167 or <Icon iconName={EIconNames.SHELF} /><a href={getDocLink(EDocLink.SHELVES)}\r 168 >Shelves</a\r 169 >.\r 170</GlossaryItem>\r 171<GlossaryItem iconName={EIconNames.SIGN} term="Sign">\r 172 An merchandising POP image element placed on the planogram, often attached to\r 173 a fixture.\r 174</GlossaryItem>\r 175<GlossaryItem iconName={EIconNames.HEADER_SIGN} term="Header Sign">\r 176 A sign that attaches to the top of a <Icon iconName={EIconNames.BAY} /><a\r 177 href={getDocLink(EDocLink.RACKS)}>Rack</a\r 178 >\r 179 or <Icon iconName={EIconNames.AISLE} /> Aisle, typically used for category or section\r 180 identification.\r 181</GlossaryItem>\r 182<GlossaryItem\r 183 iconName={EIconNames.GROUPS}\r 184 term="Group"\r 185 relatedLinks={[getDocLink(EDocLink.GROUPS)]}\r 186>\r 187 A collection of items (Positions, fixtures, etc.) that move, copy, and paste\r 188 together as one unit; can be saved as a reusable <IconFileType\r 189 fileType={EFilesystemTypes.COMPONENT}\r 190 /> Component.\r 191</GlossaryItem>\r 192\r 193<h3>Filesystem Types</h3>\r 194<p>\r 195 Files saved and managed in the GoPlanogram <a\r 196 href={getDocLink(EDocLink.INTRO_FILESYSTEM)}>Filesystem</a\r 197 >\r 198</p>\r 199\r 200<GlossaryItem\r 201 fileType={EFilesystemTypes.PLAN}\r 202 term="Plan"\r 203 relatedLinks={[getDocLink(EDocLink.INTRO_FILESYSTEM)]}\r 204>\r 205 The primary file type containing fixtures like <Icon\r 206 iconName={EIconNames.BAY}\r 207 /><a href={getDocLink(EDocLink.RACKS)}>Racks</a> and <Icon\r 208 iconName={EIconNames.SHELF}\r 209 /><a href={getDocLink(EDocLink.SHELVES)}>Shelves</a>, along with <Icon\r 210 iconName={EIconNames.PRODUCT}\r 211 /><a href={getDocLink(EDocLink.POSITIONS)}>Product Positions</a>.\r 212</GlossaryItem>\r 213<GlossaryItem\r 214 fileType={EFilesystemTypes.PROJECT}\r 215 term="Project"\r 216 relatedLinks={[getDocLink(EDocLink.FS_PROJECTS)]}\r 217>\r 218 A collection of <IconFileType fileType={EFilesystemTypes.PLAN} /> Plans for bulk\r 219 operations, <a href={getDocLink(EDocLink.SKU_REPLACE)}>item replacements</a>,\r 220 cross-plan reporting, and easy navigation between related planograms.\r 221</GlossaryItem>\r 222<!-- Store Plan guide is not published yet; restore relatedLinks when it is:\r 223 relatedLinks={[getDocLink(EDocLink.SP_INTRO)]} -->\r 224<GlossaryItem fileType={EFilesystemTypes.STOREPLAN} term="Store Plan">\r 225 A floor layout that positions multiple <IconFileType\r 226 fileType={EFilesystemTypes.PLAN}\r 227 /> Plans with location and angle information to represent a full store.\r 228</GlossaryItem>\r 229<GlossaryItem\r 230 fileType={EFilesystemTypes.STOREDATA}\r 231 term="Store Data"\r 232 relatedLinks={[getDocLink(EDocLink.STORE_DATA)]}\r 233>\r
234 A data set (sales, inventory, etc.) that can be bound to <IconFileType\r 235 fileType={EFilesystemTypes.PLAN}\r 236 /> Plans for analysis, heatmaps, and reporting calculations.\r 237</GlossaryItem>\r 238<GlossaryItem fileType={EFilesystemTypes.ASSORTMENT} term="Assortment">\r 239 A saved set of catalog items with customizable filters or item lists, used to\r 240 filter the catalog or populate <IconFileType\r 241 fileType={EFilesystemTypes.TEMPLATE}\r 242 /> Templates.\r 243</GlossaryItem>\r 244<GlossaryItem\r 245 fileType={EFilesystemTypes.TEMPLATE}\r 246 term="Template"\r 247 relatedLinks={[getDocLink(EDocLink.AUTOFILL)]}\r 248>\r 249 A rule-based file that automatically generates planogram content by placing\r 250 items from <IconFileType fileType={EFilesystemTypes.ASSORTMENT} /> Assortments into\r 251 defined regions.\r 252</GlossaryItem>\r 253<GlossaryItem\r 254 fileType={EFilesystemTypes.COMPONENT}\r 255 term="Component"\r 256 relatedLinks={[getDocLink(EDocLink.GROUPS)]}\r 257>\r 258 A reusable <Icon iconName={EIconNames.GROUPS} /> Group of products, fixtures, or\r 259 other elements saved to the Filesystem; can be shared and used across multiple\r 260 <IconFileType fileType={EFilesystemTypes.PLAN} /> Plans.\r 261</GlossaryItem>\r 262\r 263<h3>Catalog</h3>\r 264<GlossaryItem\r 265 iconName={EIconNames.CATALOG}\r 266 term="Catalog"\r 267 relatedLinks={[getDocLink(EDocLink.CATALOG_USERGUIDE)]}\r 268>\r 269 A list of items, which site admins manage. Users see these items as a\r 270 searchable palette of products, POP elements, and other items that can be\r 271 dragged onto the canvas to build <IconFileType\r 272 fileType={EFilesystemTypes.PLAN}\r 273 /> Plans.\r 274</GlossaryItem>\r 275\r 276<h3>Customizations</h3>\r 277<p>\r 278 Configurable bindings that connect your data to GoPlanogram features for\r 279 analysis, reporting, and usability.\r 280</p>\r 281\r 282<GlossaryItem\r 283 iconName={EIconNames.CUSTOMIZE}\r 284 term="Customization"\r 285 relatedLinks={[getDocLink(EDocLink.INTRO_CUSTOMIZATION)]}\r 286>\r 287 A user-defined binding that maps data or <Icon\r 288 iconName={EIconNames.CUSTOM_CALCULATION}\r 289 /> Calculations to GoPlanogram features like <Icon\r 290 iconName={EIconNames.HEATMAP}\r 291 /> Heatmaps,\r 292 <Icon iconName={EIconNames.LABELS} /> Labels, or <Icon\r 293 iconName={EIconNames.REPORT}\r 294 />\r 295 Reports.\r 296</GlossaryItem>\r 297<GlossaryItem\r 298 iconName={EIconNames.CUSTOM_CALCULATION}\r 299 term="Calculation"\r 300 relatedLinks={[getDocLink(EDocLink.CALCULATIONS)]}\r 301>\r 302 An Excel-like expression combining data properties, operators, and functions\r 303 to derive computed values for use in Customizations.\r 304</GlossaryItem>\r 305<GlossaryItem term="1-1 Mapping">\r 306 A simple Customization type that directly maps a single data property (catalog\r 307 field, custom data, store data, or Dynamic Field) without any calculation.\r 308</GlossaryItem>\r 309<GlossaryItem\r 310 term="Aggregate Calculation"\r 311 relatedLinks={[getDocLink(EDocLink.CALCULATIONS, 'aggregate_functions')]}\r 312>\r 313 A <Icon iconName={EIconNames.CUSTOM_CALCULATION} /> Calculation using functions\r 314 like <code translate="no">Sum()</code> or <code translate="no">Avg()</code>\r 315 that operate across all <Icon iconName={EIconNames.PRODUCT} /> Positions in a display;\r 316 used in <Icon iconName={EIconNames.REPORT} /> Report Property Sets for totals and\r 317 averages.\r 318</GlossaryItem>\r 319<GlossaryItem\r 320 term="Dynamic Field"\r 321 relatedLinks={[getDocLink(EDocLink.DYN_FIELDS)]}\r 322>\r 323 A built-in property whose value is calculated by GoPlanogram based on\r 324 planogram state, such as <code translate="no">LocationID</code>,\r 325 <code translate="no">Bay</code>, or\r 326 <code translate="no">FacingsTotal</code>.\r 327</GlossaryItem>\r 328\r 329<h4>Customization Types</h4>\r 330<GlossaryItem\r 331 iconName={EIconNames.REPORT}\r 332 term="Report Property Set"\r 333 relatedLinks={[getDocLink(EDocLink.REPORT_PROPERTY_SETS)]}\r 334>\r 335 A named collection of Properties, Aggregates, and Breakdowns that define what\r 336 data appears in <Icon iconName={EIconNames.REPORT} /> Reports and <Icon\r 337 iconName={EIconNames.INSIGHTS}\r 338 /> Live Insights.\r 339</GlossaryItem>\r 340<GlossaryItem\r 341 iconName={EIconNames.HEATMAP}\r 342 term="Heatmap"\r 343 relatedLinks={[getDocLink(EDocLink.HEATMAPS)]}\r 344>\r 345 A color visualization (typically green to yellow to red) that displays\r 346 numerical data for <Icon iconName={EIconNames.PRODUCT} /> Positions, useful for\r 347 identifying performance thresholds or data patterns.\r 348</GlossaryItem>\r 349<GlossaryItem\r 350 iconName={EIconNames.LABELS}\r 351 term="Label"\r 352 relatedLinks={[getDocLink(EDocLink.LABELS)]}\r 353>\r 354 Text displayed over each <Icon iconName={EIconNames.PRODUCT} /> Product Position\r 355 showing data or calculated values; multiple labels can be active simultaneously.\r 356</GlossaryItem>\r
357<GlossaryItem term="Catalog Filter">\r 358 A Customization that filters the <Icon iconName={EIconNames.CATALOG} /> Catalog\r 359 to show only items matching specified criteria, helping narrow down the assortment.\r 360</GlossaryItem>\r 361<GlossaryItem term="Catalog Sorter">\r 362 A Customization that determines the order in which items appear in the <Icon\r 363 iconName={EIconNames.CATALOG}\r 364 /> Catalog, based on a data property or calculation.</GlossaryItem\r 365>\r 366`;export{n as default};
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.