How it worksFeaturesPricingBlogSign in
Enterprise

Stage Templates

Stage Templates let Enterprise tenants define multiple named sets of lifecycle stages — each with its own fields — and assign them to specific SKU categories. Instead of every batch following one entity-wide lifecycle, different product categories can follow entirely different stage flows.

9 min read
Enterprise plan
Settings → Stage Templates

What you'll need

Enterprise plan
Stage Templates is an Enterprise-only feature. On Free or Pro plans, all batches use the entity-wide Stage Settings instead.
Access level
read, update, or manage permission on the stages module. Read-only users can view templates but cannot create, edit, or assign them.
Who can manage
Tenant Admins have full access. Managers can be granted update or manage permission on the stages module.

Templates vs. Stage Settings

Stage Settings defines a single, entity-wide lifecycle that every batch follows. Stage Templates builds on top of that by letting you define multiple named lifecycles and assign each one to a different SKU category.

Stage SettingsStage Templates
Plan availabilityAll plansEnterprise only
ScopeOne lifecycle for the whole entityMany named lifecycles, one per SKU category
Applies toEvery batch by defaultBatches whose SKU category has an active template assignment
FallbackCategories without an assignment fall back to Stage Settings

Create a template

Each template is a self-contained named set of stages, built with the same field editor used in Stage Settings.

1

Click + New Template

On the Stage Templates page, click + New Template. A new template card opens with an empty name field and no stages yet.
2

Name the template

Give the template a clear, descriptive name — for example, Frozen Seafood Lifecycle or Dietary Supplements. The name is shown wherever the template is referenced, including the category assignment list.
Use a name that describes the product line or process it covers, not the categories it's assigned to — assignments can change over time.
3

Click Save to create the template

Click Save to persist the new (initially empty) template. You can now add stages to it.

Define stages in a template

Stages inside a template use the exact same shape as entity-wide stages — a name and an ordered list of data-capture fields.

1

Click + Add stage on the template

Inside the template card, click + Add stage. A new stage row is added with an auto-generated name like stage-1 that you can rename.
2

Add fields to the stage

Click + Add field inside the stage. For each field, set a Label, a Type (text, number, date, select, boolean, image, image with geo, or document), and whether it's Required. Select fields take a comma-separated options list.
3

Reorder or remove stages as needed

Use the position controls on each stage row to change the order batches will move through, or remove a stage entirely before saving.
4

Click Save

Click Save on the template card to persist all stage and field changes in one operation.
Each template's stages are independent of every other template and of entity-wide Stage Settings. Editing one never affects the others.

Assign SKU categories

A template only takes effect once one or more SKU categories are assigned to it. Each category can point to exactly one template at a time.

1

Open the category assignment panel

On the Stage Templates page, find the Category Assignments section below the template list.
2

Pick a category

Use the category combobox to search existing SKU categories, or type a category name that doesn't exist yet. Suggestions are drawn from categories already used across your SKUs.
3

Pick the template to assign

Choose which template this category should use from the dropdown. Click Assign to save the mapping.
Assigning a category to a new template does not retroactively change batches that already exist — see How resolution works below.
4

Remove an assignment

Click the remove icon next to any assignment row to unlink that category. Once removed, the category falls back to entity-wide Stage Settings.

Edit a template

All editing happens inline on the template card — rename the template, add or remove stages and fields, and reorder stages, then click Save.

Edits to a template's stages are not retroactive. Batches already created under that template keep the stage schema that was active when they were created — only new batches pick up the change.

Delete a template

1

Click Delete on the template card

Click the red Delete button on the template you want to remove. A confirmation prompt explains that any categories currently assigned to it will fall back to Stage Settings.
2

Confirm

Confirm the deletion. The template and its stage definitions are removed, and any category assignments pointing to it are cleared automatically.
Existing batches created under the deleted template are unaffected — their stage data and schema snapshot are preserved for traceability.

How resolution works

When a new batch is created, Meiver resolves exactly one stage configuration for it using this order:

1. Active template
If the batch's SKU category is assigned to an active template and the tenant is on Enterprise, that template's stages are used.
2. Stage Settings
Otherwise — no assignment, an inactive template, or a non-Enterprise plan — the entity-wide Stage Settings are used.
3. Frozen at creation
Whichever configuration is resolved is snapshotted onto the batch at creation time. Later template or assignment changes never alter existing batches.
A category always resolves to exactly one configuration — never both a template and Stage Settings at the same time.

Permissions reference

Access is controlled by the same stages module used by Stage Settings. Tenant Admins always have full access.

PermissionWhat it allows
readView templates, their stages, and category assignments (read-only, no edits)
updateCreate, edit, and delete templates; assign and remove category mappings
manageFull access — equivalent to update for the stages module

Troubleshooting & FAQs

I don't see Stage Templates in the sidebar.+
Stage Templates is an Enterprise-only feature. If your tenant is on Free or Pro, the page redirects to the dashboard overview. Confirm your plan with your Tenant Admin, or contact connect@meiver.io to upgrade.
I assigned a category to a template but existing batches didn't change.+
Resolution happens once, at batch creation time. The new template only applies to batches created after the assignment was saved — existing batches keep whatever schema was resolved when they were created.
Two categories need the exact same stages — do I need two templates?+
No. You can assign multiple categories to the same template. There's no limit on how many categories point at one template.
What happens to a category if I delete its assigned template?+
The category's assignment is cleared automatically and it falls back to using the entity-wide Stage Settings for all new batches.
Can a category have no template and just use Stage Settings?+
Yes — that's the default. Categories only deviate from Stage Settings once you explicitly assign them to a template.
I'm on Enterprise but my batch still used Stage Settings instead of my template.+
Check that the batch's SKU category exactly matches an assigned category, and that the assignment was saved before the batch was created. Category matching is case-sensitive based on how it's stored on the SKU.

Ready to run multiple stage lifecycles?

Head to Stage Templates and build a tailored lifecycle for each product category.

Go to Stage Templates →

Was this article helpful?