Content templates
Content templates are reusable blocks of rich text that you write once and apply to many products, so your warranty, shipping and returns wording stays consistent. When you edit a template, every product using it is updated too.
Content templates need a plan that includes them (Growth or higher).
Where to find it
Go to Settings → Content Templates, or open /settings/templates.
The page has four sections: FAQ Templates, Warranty Templates, Shipping Information Templates and Returns Information Templates. FAQ templates are managed on their own page. Click Manage FAQ Templates to open it, or see FAQ templates.
Create a template
Each section works the same way:
- Click Add Template in the section.
- Fill in the form (see below).
- Click Create, or Update when you're editing.
Saved templates appear in a table in their section, with Edit and Delete actions and a Default badge on the default template.
Warranty templates
- Template Name — for example "12-Month Standard Warranty".
- Warranty Content — the rich-text body.
- Set as default template
Shipping information templates
- Template Name — for example "Standard Domestic Shipping".
- Section Title — the heading shown on the product page, for example "Shipping".
- Shipping Content — the rich-text body.
- Set as default template
Returns information templates
- Template Name — for example "30-Day Returns Policy".
- Section Title — the heading shown on the product page, for example "Returns".
- Returns Content — the rich-text body.
- Set as default template
The default template is marked (Default) in the template picker in the product editor, so your team knows which one to use.
Apply a template to a product
In the product editor, pick the template from the warranty, shipping or returns dropdown. The template's content is copied onto the product, and the product remembers which template it follows.
Edit a template
When you update a template, Fulify updates the content on every product that follows it. Products that were already synced are marked as pending, so the new wording goes out on their next sync.