Templates and Custom Attributes
As mentioned in our Config Settings guide the Config tab in Limio contains the Templates which are core to how Limio Catalog works.
A template defines the set of attributes available for the Offers, Products, Segments and Tags.
Config hierarchy — two levels to know:
Config > [Object] (e.g. Config > Products) — where you define any attributes for that object type.
Config > [Object] > [Template name] (e.g. Config > Products > Default) — a template. This controls which attributes appear on objects using that template.
Changes not showing? After saving config or template changes, do a hard refresh to clear the cached layout: Mac Cmd+Shift+R · Windows/Linux Ctrl+Shift+R
You can add new templates in the config section of the catalog using the add icon under specific hierarchy. Make sure to select default in the dropdown while saving the new template as this is the baseTemplate.

Screenshot: Adding an offer template.

Screenshot: Adding the name and saving the new template.
How to display an Attribute on a Template
You can then select the attributes that you want on the template by clicking on the checkboxes next to the attributes and save the changes. These selected attributes will be visible on the template configured.

Screenshot: Selecting the attributes for the template.
How to create new Custom Attributes
These changes are self-service — you don't need to contact support to add or modify attributes.
To modify a Template, go to Config and click a folder such as Offer. Scroll to the bottom and press the (+) button. You can then create a new field with:
A name (see warning below)
A label (editable)
A type (editable): String, Numeric, Boolean, Picklist, Status, Chevron, Price, Date, Colour, Hidden, Rich Text and Multi-Picklist
The attribute Name is permanent — it cannot be changed after saving. Choose it carefully. The Label can be edited at any time.
These fields are now available for any templates to use.
For Picklist and Multi-Picklist attributes, you also need to configure the available options after creating the attribute. See How to manage picklist options below.

Attribute validation with JSON Schema
From Release 116, if an attribute definition includes a JSON Schema, Limio validates values against that schema whenever a catalog item is saved — whether the save comes from the Limio app, the API, or an AI tool connected through the Limio MCP. Invalid values are rejected with an error describing what is wrong.
This matters most for catalog changes made outside the app UI: the UI's field-level guardrails (dropdowns, inline validation, custom editors) don't apply to API or MCP edits, so the attribute schema is what enforces the correct data shape there.
Attributes without a schema keep the existing basic type validation, so nothing changes for your current templates unless you add schemas to them.
How to manage picklist options
Picklist and Multi-Picklist attributes have a separate set of options (values) that users can select. These are managed at the top-level config (e.g. Config > Products), not inside a template.
How to hide Custom Attributes in Limio for Salesforce
It is possible to hide custom attributes in Limio for Salesforce so that they are not visible to agents assisting customers. To do this, slide the "Hide in Limio for Salesforce" toggle.
By default custom attributes are not hidden in Limio for Salesforce.
Named attributes cannot be hidden in Limio for Salesforce.

How to select a Template on an object
Go to the object (e.g. offer) and press 'Select Template' to see a dropdown of your available templates.

Removing an attribute from a template hides it in the Limio UI but does not delete the existing data on objects that previously had a value for it. If you re-add the attribute to the template, the old values will reappear. The data travels with the object, not the template.
How to create Sections for a Template
You can now define sections for offer templates under the "Sections" tab. Here is an example:

You can then assign attributes to the different sections here:

This will then be displayed on the actual offer (that has an OfferBase template in this case) like this:

How to define Default Values for a Template
For the attribute default, you are able to set the default value per attribute when you click on the Edit Default Value button for each attribute.

What this means is that for example if we create a new offer from scratch and we select the OfferBase template, it will automatically fill in all attributes based on the default values that we set up in the template.

Does it only work for newly created objects?
Yes, it will only on creation of new objects.
Is the default applied when duplicating objects?
No, duplicating an object will retain the value of the initial object.
If a default value is updated, does it update existing objects?
No, the default value is only applied upon creation of an object.
Any questions? Ping us an email at support@limio.com and we'll be happy to help.
Last updated
Was this helpful?

