CMS

CMS in Fire spark is not a website builder. It is a way to define reusable content templates — the fields marketing needs (headlines, images, short copy) — and attach them to commercial objects like a brand or a store. Operations data (menus, prices, hours) still comes from your POS or RMS; CMS handles presentation and storytelling on top.

​

Templates and entities

Every CMS template belongs to exactly one entity type. That type tells you where the template can be assigned and where the content will appear in customer-facing channels. You create the template once (which fields exist and their type). Your team fills values per brand, store, menu, category, or product in the dashboard. Channels read that content through the API when a template is linked.

​

Field types (what marketers actually edit)

Fields can be required or optional and support localized labels so the same template works in more than one language.

​

How assignment works

1. Define a template for an entity type (for example “Store landing — summer”).
2. Link it to a record by setting cms_template_id on that brand, store, menu, category, or product.
3. Fill field values in the dashboard for each record.
4. Channels consume cms — when cms_template_id is set, APIs return a resolved cms object with the template structure and current values. When it is null, cms is also null.

Today, brands and stores expose this in the Storefront and Integrations APIs. Templates for menus, categories, and products follow the same model as those surfaces gain richer merchandising.

​

When CMS helps commercial teams

​

When you can start without CMS

If one brand, one look, and minimal copy on channels is enough, you can run on menus, stores, and channels alone. Add CMS when non-operational content becomes a bottleneck — when marketing asks for frequent copy or image changes that should not go through menu or POS updates.

​

Related concepts