---
sourceDocument: Brazil Sales Customer Relationship Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/order-management

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Sales Customer Relationship Management

ft:clusterId :

    - omgmt

bundleId :

    - omgmt

workflow :

    - Customer and Industry


---

# Layouts

# Layouts {#ariaid-title1}

Release version: Brazil  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Layouts

Layouts in ServiceNow CPQ define the visual presentation of your product configuration experience.
They control the arrangement of fields, grouping of steps, and display of the product list (shopping cart), transforming blueprint logic and data into an intuitive, guided user interface.
Layouts operate at the presentation layer, focusing exclusively on how elements appear without altering underlying configuration rules or data structures.
Show full answer Show less  

## Key Features

* **Blueprint-Specific Layouts:** Each blueprint can have multiple layouts, enabling different user personas, channels, or demo scenarios without duplicating logic. Users can switch between layouts via the configurator UI.
* **Structural Tiers:** Layouts are built from nested structural elements called tiers, such as pages (with progress navigation), tabs, accordions, expandable sections, and basic containers, allowing flexible multi-level organization of configuration steps and content.
* **Authoring Tools:** Layouts are created and maintained through CSV files and in-product tools:
  * **CSV Upload:** The primary format that provides full control over tiers, fields, product lists, and component properties.
  * **Layout Wizard:** Generates initial layouts visually from blueprint fields, serving as a starting point for further refinement.
  * **Layout Editor:** Enables direct editing of layouts within the Admin UI, including arranging tiers, adjusting labels, and modifying display properties with visual and shortcut support.
* **Sets and Repeatable Content:** Layouts define how sets of products or options are presented---as tables, lists, or repeaters---with configurable behaviors like expand direction, sizing, messaging, and inline controls.
* **Product List Presentation:** Controls how the shopping cart appears, specifying which product attributes show as columns, their labels, alignment, and whether the list is inline or in a separate window. Product list columns are configured in the layout CSV and linked to product rules.

## Key Outcomes

By effectively leveraging layouts, ServiceNow CPQ customers can deliver tailored, user-friendly configuration interfaces that guide buyers through complex product selections clearly and efficiently. Layouts provide flexibility to adapt presentation without changing business logic, supporting multiple user scenarios and improving the overall purchasing experience. The combination of CSV-driven definitions and visual tools ensures layouts are maintainable, versionable, and easy to evolve alongside your product offerings.  
Layouts define how the configuration experience looks and feels for your users. They control where fields appear, how steps are grouped, and how the product list (shopping cart) is presented---turning a blueprint's logic and data
into an intuitive, guided UI in ServiceNow CPQ.
A layout is the presentation layer of a configuration experience. Where a blueprint brings together fields, rules, layouts, and configurable products, the layout focuses on how those elements are displayed:

* Which fields appear on each page or tab
* How sections are grouped and labeled
* How sets, product pickers, and messages are arranged
* How the product list is rendered alongside the configuration

{#layouts__ul_e2h_qr4_hhc}

Layouts are defined per blueprint. A single blueprint can have one or more layouts, giving you flexibility to support different personas, channels, or demo experiences without duplicating configuration logic.

When a blueprint has multiple layouts, end users can rotate through them using the alternate layout control in the upper-right corner of the configurator UI.

## How layouts fit into the configuration model {#layouts__section_zj1_vr4_hhc}

Layouts are placed at the presentation layer of the ServiceNow CPQ configuration stack:

* Fields collect and display data.
* Rules control behavior (visibility, messaging, calculations, product inclusion, and more).
* Blueprints tie fields, rules, layouts, and configurable products into a single configuration experience.
* Layouts define the buyside interface---pages, tabs, sections, and product list---without changing the underlying logic.

{#layouts__ul_n4b_wr4_hhc}

Because layouts reference field variable names and product list parameters, you can safely iterate in the layout (for example, reorganizing tiers or changing display types) without modifying rules or data structures.

## Layout building blocks {#layouts__section_obs_xr4_hhc}

Layouts are composed of reusable structural and visual elements that you define in a layout CSV file and refine in the Layout Wizard or the layout editor.  
Tiers: pages, tabs, and sections: Tiers define the major structural areas of the configuration experience. Each tier has a tierDef that describes how it behaves:

* Pages (PagesWithLabels): Break the configuration into discrete steps with progress navigation.
* Tabs (VerticalTab): Group related content horizontally or vertically for quick switching.
* Accordion (AccordionWithNavigation): Show one expanded section at a time for long or complex content.
* ExpandableSection: Allow users to expand or collapse content as needed.
* BasicContainer: Provide an unstyled container for simple grouping.
{#layouts__ul_ysy_zr4_hhc}

You can nest tiers to build multilevel layouts---for example, pages that contain tabs, or tabs that contain expandable sections.

## Layout definition and tools {#layouts__section_tp4_2s4_hhc}

Layouts are authored and maintained using a combination of CSV files and in-product tools:

* CSV layout upload
  * Primary definition format for layouts
  * Built in a spreadsheet tool and exported to a CSV file
  * Supports full control over tiers, column sets, fields, product list, and component properties
  {#layouts__ul_ilg_fs4_hhc}
* Layout Wizard
  * Helps you quickly generate an initial layout from a blueprint's fields
  * Provides a visual preview of tiers and major groupings
  * Acts as a starting point; fine-tuning is done via CSV file or the layout editor
  {#layouts__ul_jlg_fs4_hhc}
* Layout editor
  * Allows you to edit an existing layout directly in the Admin UI
  * Supports arranging tiers and column sets, editing labels, adjusting display types, and updating extended properties
  * Provides keyboard shortcuts and visual cues for missing or partially supported elements
  {#layouts__ul_klg_fs4_hhc}

{#layouts__ul_hlg_fs4_hhc}

Regardless of which tool you use, the layout is ultimately stored as a structured definition that can be exported, versioned, and replaced as your configuration experience evolves.

## Sets and repeatable content {#layouts__section_hpx_3s4_hhc}

Layouts also control how sets are presented:

* As tables (rows and columns with headers)
* As lists (card-style rows with optional selection and search behavior)
* In repeaters that focus the user on one set index at a time

{#layouts__ul_m5d_ks4_hhc}

Set-specific layout properties---such as expand direction, size controls, message indicators, inline add/remove controls, and upload/download behavior---are configured in the layout via extended properties and raw value JSON.

The product list section of a layout defines how the shopping cart is displayed:

* Which product list parameters appear as columns (for example, name, quantity, price, extended attributes)
* How columns are labeled and aligned
* Whether the product list is inline or in a window

{#layouts__ul_vpn_ns4_hhc}

Product list columns are driven by the layout CSV file using the `productlist` and `productlistcolumn` types and by referencing `ProductList.<param>` values defined in the product rules
and underlying tables.
**Related concepts**   

* [Set up layouts](https://servicenow-prod.fluidtopics.net/LYjp9BqJPJlNdbxg12S2WA "Layouts in ServiceNow CPQ define the structure and appearance of the configuration interface. They organize fields into pages, tabs, and sections, shaping how users interact with configurations and view shopping cart details.")
* [Layout Wizard](https://servicenow-prod.fluidtopics.net/jqaC_8UNIIZKVRe4GRAkHg "Watch a video about how to generate a layout.")
* [Layout: a deeper dive](https://servicenow-prod.fluidtopics.net/c9UOr8IVP17gRp0nBaPT8A "Learn advanced layout concepts in ServiceNow CPQ, including tiers, column sets, and product list layouts. Understand how to structure pages, tabs, and sections in CSV files to create dynamic, responsive configuration interfaces with organized and intuitive user experiences.")

