Register → Lightning Layouts uses the exact LayoutGrid icon. Any signed-in user can view assigned/visible layout cards and star personal favorites, but only owners or users with Manage Lightning Layouts can create, edit, assign, or delete. Layouts reference existing catalog records and are filtered again in Sell by active product, location/register availability, and availability rules. Saving a layout spans metadata, folder/item upserts/deletes, and register-assignment writes rather than one transaction; test the exact register after every structural change.
Step by step
- Go to Register → Lightning Layouts, identified by the LayoutGrid icon. A user without management permission sees the list/favorite controls and the message about starring favorites; opening an editor URL shows Access denied.
- Search layouts matches layout name in the already loaded list. The register filter matches a layout when it is assigned to any selected register. Its register list is loaded from all tenant locations for this list view; selecting multiple registers uses any-match, not “assigned to every selected register.”
- Each card shows name, grid columns × rows, assigned-register count, and distinct location names, or Unassigned. Star is personal to the current user and orders Favorites first in the Sell switcher; it does not assign a register, change another user, or establish a default.
- Choose New Layout only when authorized. Enter a nonblank name and Create. The new record starts as a 3×3 layout with no register assignment, folders, or product cells, then opens in the editor. Creation does not make it available on Sell until the appropriate assignment is saved.
- The card trash control is manager-only but issues layout deletion immediately with no confirmation dialog. Dependent folders, items, assignments, and favorites can be removed by database relationships. Audit register use and obtain approval before choosing it; there is no visible undo.
- In the editor, change the layout name, Columns, and Rows. Grid size controls the visible cell matrix at each folder level. Before shrinking it, move or remove content that would sit outside the new boundary; verify all levels after Save rather than assuming off-grid cells were automatically reorganized.
- Assign Registers from the editor. Owners/admin-equivalent location scope can load active locations across the tenant; other users receive only their scoped location IDs. The query returns registers at those locations and does not add an explicit active-register condition. Select only registers whose teams and screen sizes have been tested.
- Choose Add Product and search by parent product name or SKU; the candidate list is capped at the first 50 filtered products. For a variable product, choose Entire product or a specific supported variant when prompted. A product cell stores product ID and optional variant ID; it does not copy price, stock, tax, or availability into the layout.
- Use Rename/Edit Product Cell for an optional button label and color/size controls supported by the editor. A custom label changes only this layout cell, not product/variant identity. Confirm the Sell tile still resolves the expected catalog record.
- Create a manual Folder with required name and color. It can hold product cells and nested manual folders. Use the breadcrumb/Main layout navigation to edit each level. A dynamic folder is filter-driven and does not behave like a manual container for placed children.
- Drag a product or folder to an empty cell to move it. Drop a product/folder onto a manual folder to place it at that folder’s next available position. Dropping a product onto another product offers a new folder containing both. Review destination level and occupied cells before releasing.
- Dynamic Folder criteria can include exact products, variants, brands, categories, suppliers, tags, variant attribute values, and optional target price with range, depending on the dialog entry point. It queries a capped option set (up to 500 active products and 1,000 variants in the shared dialog); absent options are not proof the catalog has none.
- At Sell time, dynamic-folder brand/category/supplier/tag/variant-value and price criteria are passed into the same ranked product/variant selection logic with active location, register, and availability rules. Contents can change as catalog metadata, price, availability, or stock context changes; it is not a frozen snapshot. Exact productIds/variantIds saved by some shared-dialog paths are not included in the Sell grid’s current folderFilters object, so verify those criteria in the target register rather than trusting the chip alone.
- Delete a cell or folder only after inspecting the current level and descendants. Removing a layout item does not delete its catalog product. Removing a folder removes that organizational record and can remove/cascade contained layout records according to database relationships; Save is the persistence point for editor removals.
- Choose Save once. The save operation first updates layout name/grid size without checking that update’s returned error, reads existing records, upserts current folders/items, deletes removed items/folders, then adds/removes register assignments. It is sequential, not atomic; later failure can leave earlier metadata/content changes saved. Reopen and compare every level and assignment after an error.
- Unsaved Changes protects the editor Back action, browser history/popstate, and tab close/reload differently. Discard clears dirty state and leaves. Save & Exit calls the caught-error save handler and then navigates even if that handler displayed Failed to save lightning layout, so do not assume remaining on the page is the success test. Reopen and verify after Save & Exit.
- Go to Register → Sell in an assigned register and enter Lightning Layout Mode. If more than one available layout exists, the switcher appears; favorites are grouped first, other layouts second, active has a check, and Default labels the layout returned as the active/default register layout. The Lightning Layout editor itself has no Set default control.
- Open every manual and dynamic folder and test representative standard/variant cells. Static cells are suppressed when the linked product is missing or disallowed at the active location/register. Dynamic results are likewise re-ranked/filtered. A tile can therefore exist in the editor but not appear or add in Sell.
- Choose a static product with variants carefully: a product-level cell can invoke variant selection, while a variant-specific cell should resolve that variant. Confirm price, tax, fulfillment, availability, and stock behavior in the resulting cart; the layout never bypasses those workflows.
- Verify desktop and target touch devices. Grid positions, spans, scroll state per folder, breadcrumbs, names, and dynamic result density can behave differently by viewport. Do not solve a layout-density issue by changing catalog availability or product data.
- For troubleshooting record tenant, user permission/location scope, layout ID/name/grid, folder/item IDs and parent/positions/spans, dynamic criteria, register assignments, active location/register, favorite/default/active IDs, missing catalog ID, availability rules, Save toast/error, and exact Sell result.
- No screenshot is published for this guide. The real Amelia Grant Harbor & Hearth `/register/lightning-layouts` route ended at Could not load Lightning Layouts, so the rejected error capture is not shown as a valid layout and no different screen is substituted.
Screen and contract reference
| Control or area | What it means |
|---|---|
| LayoutGrid icon | Exact Register navigation and empty-state icon for Lightning Layouts. |
| Manage Lightning Layouts | Permission required to create/edit/assign/delete; owners also qualify. |
| Search layouts | Client-side name match across loaded layouts. |
| Register filter | Any selected assigned register match. |
| Layout card | Name, grid dimensions, assignment count/locations, personal star, and manager delete. |
| Favorite | Current-user preference and Sell switcher grouping only. |
| New Layout | Creates unassigned empty 3×3 layout. |
| Immediate card deletion | No confirmation or visible undo. |
| Columns / Rows | Per-level visible grid boundary. |
| Assign Registers | Scoped register availability; not default selection. |
| Product cell | Product ID plus optional variant ID and layout-only presentation. |
| 50-product add search | First 50 name/SKU matches in editor. |
| Manual folder | Placed/nested layout container. |
| Dynamic folder | Live filter criteria evaluated against current Sell catalog/context. |
| Dynamic option caps | Shared dialog loads up to 500 active products and 1,000 variants. |
| Exact-ID criteria caveat | Sell grid currently forwards attribute/price criteria but not saved productIds/variantIds in its folderFilters object. |
| Drag/drop | Move to cell/folder or merge product-on-product into a new folder. |
| Save boundary | Unchecked metadata update, then sequential content and assignment operations. |
| Unsaved Changes | Discard or Save & Exit; Save & Exit can navigate after a caught save failure. |
| Layout switcher | Shown only with more than one available layout; active/check, favorite grouping, and Default label. |
| No editor Set default | Default comes from active register-layout resolution, not a control on this screen. |
| Sell revalidation | Product/variant and dynamic results remain subject to active catalog/location/register availability. |
| No public screenshot | Rejected real error-state capture; no substituted or fabricated image. |
Expected result
The exact layout name/grid, every folder/item identity and position/span, manual hierarchy, dynamic criteria, scoped register assignments, and current-user favorite state are reopened after save; the target register’s active/default/switcher behavior is understood; representative standard and variant tiles remain correctly filtered by catalog/location/register availability; and any partial sequential save or Save & Exit failure is reconciled before further edits.
Troubleshooting
- Confirm whether you are editing a product, variant, shared master record, or location-specific value.
- Search for an existing product, SKU, UPC, attribute, or tag before creating a duplicate.
- Preview labels, pricing, and availability in the intended location before broad publication.
CentriPOS API explorer · API Center administration