All Plans
Stage Settings
Stages are the lifecycle checkpoints that every batch moves through — from raw material procurement to final delivery. Each stage carries a custom set of data-capture fields that staff fill in as the batch progresses. Configure them once here and they automatically apply to every new batch you create.
10 min read
All plan tiers
Settings → Stage Settings
What you'll need
Access level
update or manage permission on the stages module. Read-only users can view stages but cannot create, edit, reorder, or delete.
Entity context
Stages are configured per entity. Switch entity at the top of the dashboard to manage a different entity's stages.
Who can manage
Tenant Admins have full access. Managers can be granted update or manage permission on the stages module.
Default stages
When you open Stage Settings for the first time, Meiver automatically seeds 5 default stages aligned to FSMA 204 Key Data Elements (KDEs). Each comes pre-loaded with relevant fields so you can start capturing data immediately.
| Stage | Purpose | Key fields included |
|---|---|---|
| 📦 Procurement | Raw material intake & supplier records | Supplier Name, PO/Reference, Material Lot, Country of Origin, Quantity, Received Date |
| ⚙️ Processing | Manufacturing & transformation details | Process Type, Start/End Time, Temperature, Yield (%), Operator, QC Status |
| 🗃️ Packing | Packaging, lot code & labelling | Packaging Type, Pack Date, Lot/Batch Code, Net Weight, Units per Case, Label Version |
| 🏭 Storage | Warehouse conditions & location | Storage Location, Storage Type, Temperature, Humidity, In/Out Dates, Rack/Bay |
| 🚚 Delivery | Dispatch & distribution records | Carrier, Vehicle No., Dispatch Date, AWB/LR No., Destination, Receiver Contact |
Default stages can be renamed, edited, reordered, and even deleted (if no batch data has been captured against them yet). They are a starting point, not a locked-in requirement.
Create a stage
There are three ways to add a new stage. All three methods add the stage to your local editor — click Save when you are ready to persist all changes.
+ From template
Choose from 8 pre-configured templates (Procurement, Processing, Packing, Storage, Delivery, QC Inspection, Customs Clearance, Cold Chain). Each template ships with a full set of relevant fields.
+ Blank
Start with an empty stage. Enter the stage name and then add fields manually one by one.
Import CSV
Upload a .csv file to bulk-create stages and fields. Columns: Stage Name | Field Label | Field Type | Required | Options.
1
Choose a creation method
Click + From template to pick from 8 pre-built options, or click + Blank to start fresh. Both open a new collapsible stage card at the bottom of the list.
2
Enter the stage name
Type a name in the stage name field (max 120 characters). The name is auto-normalized to lowercase kebab-case — for example, QC Checkpoint becomes
qc-checkpoint. Duplicate names are rejected.The normalized name is used as a unique key. Choose a name that clearly identifies the lifecycle step — you can always update the display label later.
3
Add fields to the stage
Click + Add field inside the stage card to add data-capture fields. For each field, provide: a Label, a Type (see Field types below), and check Required if staff must fill it in before moving on. For Select fields, add comma-separated options.
4
Click Save
All changes in the editor are local until you click the green Save button at the top of the page. A single Save persists all staged changes — new stages, edits, reorders, and deletions — in one operation.
You can add multiple stages, reorder them, and edit existing ones all before clicking Save. Everything is batched into a single save operation.
Field types reference
Every field in a stage has a type that controls what input staff see when filling in batch data.
| Type | What it collects | Notes |
|---|---|---|
| Text | Free-form text input | Suitable for names, notes, IDs |
| Number | Numeric value | Suitable for quantities, temperatures, weights |
| Date | Date picker | Stored as ISO date string |
| Select | Dropdown with predefined options | Add comma-separated options in the field definition |
| Yes / No | Boolean toggle (Yes or No) | Suitable for pass/fail checks |
| Image upload | Photo upload (PNG, JPEG, WEBP — max 5 MB) | Stored in your entity's document storage |
| Image upload (Geo tagged) | Photo upload with GPS coordinates captured | Useful for FSMA location proofs |
| Document upload | File upload (PDF, DOCX, XLSX — max 20 MB) | Suitable for certificates, inspection reports |
Edit a stage
All editing is done inline — there are no separate modals. Changes are held locally until you click Save.
1
Expand the stage card
Click on a stage card header to expand it. The first stage is expanded by default. Inside, you will see the stage name input and a list of all its fields.
2
Edit the stage name or fields
- Stage name — Edit the text input in the card header. The name is re-normalized on save.
- Field label — Click directly on any field label to edit it.
- Field type — Change the type dropdown. Note: changing type does not migrate existing batch data for that field.
- Required — Toggle the Required checkbox on any field.
- Options — For Select fields, edit the comma-separated options list.
- Add / remove fields — Click + Add field to add a new field, or the red delete button on any field row to remove it.
Removing a field from a stage definition does not delete data already captured in existing batches. However, that field will no longer appear in new batches created after the save.
3
Click Save
Click the green Save button at the top of the page to persist all edits, additions, and deletions in one operation.
Reorder stages
The order of stages here determines the order they appear in every batch's lifecycle. Use the arrow buttons in each stage card's action bar to adjust the sequence.
1
Use the Up ↑ / Down ↓ arrows
In the action bar of any stage card, click the ↑ Up arrow to move the stage one position up, or the ↓ Down arrow to move it one position down. The Up arrow is disabled when the stage is already first; the Down arrow is disabled when it is last.
Stage order only affects new batches. Batches already created retain the stage order that was active at the time they were created.
2
Click Save
Once you are happy with the order, click Save. The new sort order is persisted and applied to all subsequently created batches.
Delete a stage
Meiver handles deletion intelligently depending on whether the stage has existing batch data.
1
Click Remove on the stage card
In the stage card's action bar, click the red Remove button. A confirmation modal appears with the message: “The stage will be removed from the lifecycle. Existing batch data won't be deleted.”
2
Confirm and Save
Click Confirm in the modal. The stage is removed from the editor. Click Save to persist the change.
How deletion actually works
✓ Not in use
Stage has no batch data — permanently deleted from the database.
⚠ In use (has batch data)
Stage is archived instead — hidden from new batches but existing batch data is fully preserved.
CSV import
If you have many stages or are migrating from another system, the CSV import lets you bulk-load stage definitions without clicking through the UI.
1
Prepare your CSV file
Your file must be a .csv (not .xlsx) with the following columns in order:
| Column | Description | Example |
|---|---|---|
| Stage Name | Name of the stage (groups rows into stages) | Procurement |
| Field Label | Label shown to staff when capturing data | Supplier Name |
| Field Type | text | number | date | select | boolean | image | image_geo | document | text |
| Required | yes / true / 1 / required — case-insensitive | yes |
| Options | Comma-separated list (for select fields only) | Air,Sea,Road |
All rows sharing the same Stage Name are grouped into one stage. The Stage Name row ordering determines sort order.
2
Click Import CSV and upload your file
Click the Import CSV button on the Stage Settings page. Select your .csv file. The system parses the file and merges the imported stages into your local editor — they are not saved yet.
The import merges data into your current editor state. Review the imported stages carefully before clicking Save.
3
Review and Save
Inspect the imported stages and their fields. Make any adjustments needed, then click Save to persist everything.
Where stages are used
Stage definitions configured here power two key parts of the batch workflow:
Batch creation
Every time a new batch is created, Meiver automatically instantiates all currently visible stages for that entity. The stage schema is snapshotted at creation time, so later edits to definitions do not alter existing batches.
Stage data entry
Staff fill in stage fields at Dashboard → Batches → [Batch] → Stages as the batch progresses through the supply chain. Each stage shows exactly the fields defined here.
Traceability snapshots
Stage names and schemas are frozen on each batch at creation time. This ensures full traceability even if you later rename or restructure stages.
Stage definitions are not retrospective. Changes you make here only apply to batches created after you save. Existing batches always use the schema that was active at their creation time.
Permissions reference
Access is controlled by the stages module. Tenant Admins always have full access.
| Permission | What it allows |
|---|---|
read | View stage definitions in the Stage Settings page (read-only, no edits) |
update | Create, edit, reorder, and delete stage definitions; import CSV; save changes |
manage | Full access — equivalent to update for the stages module |
Users with only
read permission see a 👁 View-only mode banner at the top of the Stage Settings page and all edit controls are hidden.Troubleshooting & FAQs
Ready to configure your batch lifecycle?
Head to Stage Settings and define the checkpoints that every batch will pass through.
Was this article helpful?