Custom fields
Attach structured values to menu items for custom theme layouts.
Custom fields attach typed data to menu links. They do not appear automatically in your theme. A developer reads the published values using the app’s generated Liquid examples.
Create and populate a field
- Open the menu and select Custom fields.
- Add a field with a name and type. Review its generated key.
- Configure choices, validation, list mode, a default or required status where supported.
- Select each menu item and enter its value.
- Save, resolve validation messages and publish the menu.
- Open Developer integration to copy the matching Liquid reference.
Field keys and types remain fixed after creation. Names and supported settings can be edited. Use a new field if you need a different type, and update your theme integration accordingly.
Field types
| Type | Example use |
|---|---|
| Single-line text | A short description or eyebrow label |
| Multi-line text | A longer navigation description |
| Number | A numeric value used by your custom layout |
| True or false | A flag that your theme tests conditionally |
| Choice | One value from a defined set of options |
| URL | An additional destination |
| Colour | A colour used in your custom design |
| Metaobject reference | A selected entry from a Shopify metaobject type |
| File | An uploaded image URL |
Lists and validation
List fields hold multiple values of the same type. Add or remove rows in the item editor and loop over the published values in Liquid.
Supported validation includes text length bounds, numeric bounds and list item-count bounds. Choice fields accept the configured options. Correct invalid values before saving or publishing.
Defaults and required values
A default provides a fallback for items without an explicit saved value. It does not overwrite a saved per-item value. Supported defaults also participate in published data and required-field validation.
Require a value for every menu link applies across the menu. Publishing reports missing fields and affected items so you can complete them together. A valid configured default can satisfy a required field. Metaobject-reference fields do not offer the ordinary default-value input.
Defaults can make multiple menu items count as customised. Review plan allowances before applying a default widely.
Editing and deleting definitions
You can reorder fields and edit their supported settings. Deleting a definition deletes its saved values from every menu link. Changing a field’s metaobject type clears its existing reference values after confirmation.
Update any theme code that reads a removed field, and publish to update the storefront data. See Files and metaobjects and Liquid integration.