Define the nutrition fields that appear on every SKU — from the 6 built-in defaults to fully custom fields with your own label and unit. Changes here flow through the SKU form, the consumer QR page, and CSV exports.
6 min read
All plan tiers
Settings → Nutritional Settings
What you'll need
Access level
Settings or admin role — read-only users see fields but cannot add, edit, or delete.
Entity context
Nutrition fields are scoped per entity. Switch entity at the top of the dashboard to manage a different one.
Who can manage
Tenant Admins have full access. Managers can be granted granular create/update/delete permission.
Navigate to Nutritional Settings
1
Open your dashboard
Sign in to your Meiver account. You will land on the main dashboard home page.
2
Expand the Settings section
In the left sidebar, click Settings to expand the section. Sub-items will appear beneath it.
If you do not see a Settings item, your account does not have the required permissions. Contact your Tenant Admin.
3
Click Nutritional Settings
Under Settings, click Nutritional Settings. Full path: Dashboard → Settings → Nutritional Settings.
Default nutrition fields
Meiver ships with 6 default fields that are always present for every entity. They cannot be deleted, but their label and unit can be edited at any time. Each is marked with a default badge in the table.
Field key
Default label
Default unit
Description
protein
Protein
g
Total protein per serving
carbs
Carbs
g
Total carbohydrates per serving
fat
Fat
g
Total fat per serving
sugar
Sugar
g
Total sugars per serving
sodium
Sodium
mg
Sodium content per serving
energy
Energy
kcal
Caloric value per serving
Default fields cannot be deleted. This protects existing SKU data and prevents broken CSV exports. You can rename their label or change their unit at any time.
Add a custom nutrition field
Custom fields appear alongside the defaults in every SKU nutrition form. They are fully configurable — you set the label, unit, and a key is auto-generated from the label.
1
Locate the Add field form
At the top of the Nutritional Settings page you will find a form with two inputs: Field label (max 40 chars) and Unit (max 10 chars, e.g. g, mg, kcal, %).
2
Enter a label and unit
Type a descriptive label such as Fibre and its unit g. The system automatically generates a unique field key from your label (e.g. fibre). A preview of the key appears below the label input.
The key is derived by lowercasing the label and replacing special characters with hyphens. Duplicate keys are rejected — choose a unique label.
3
Click Add field
Click the green Add field button. The new field immediately appears in the table and becomes available in all SKU nutrition forms for this entity.
Changes are entity-scoped. If your account has multiple entities, switch entity context using the entity selector at the top of the dashboard to manage each one independently.
Edit a field
Both default and custom fields support inline editing of the label and unit. The underlying key never changes, so all existing SKU data remains intact.
1
Click the edit icon on any row
In the field table, click the Edit (pencil) icon on the right side of any row. The row expands into an inline edit form with pre-filled label and unit inputs.
2
Update the label and/or unit
Modify the label or unit text as needed. Label is limited to 40 characters and unit to 10. The field key shown below the label is read-only and will not change.
Changing a field's unit label (e.g. from 'g' to 'grams') is cosmetic only — it does not convert any stored numerical values.
3
Click Save
Click the Save button. The row returns to read-only view and the updated label and unit appear across all SKU forms immediately.
Delete a custom field
Only custom fields (those you added) can be deleted. Default fields do not show a delete button.
1
Click the delete icon
On a custom-field row, click the Trash icon. A confirmation modal will appear.
2
Confirm deletion
Read the warning in the modal, then click Delete to proceed, or Cancel to abort.
Deleting a field removes it from the Nutritional Settings table and from all future SKU forms. Previously saved SKU nutrition values for this key are preserved in the database but will no longer be displayed or exported.
Where nutrition data appears
Every field you configure flows through three places in Meiver:
SKU nutrition form
When editing a SKU, a Nutrition section shows all active fields. Staff enter a value per field and set a reference quantity (e.g. per 100 g).
Consumer QR page
If a SKU has nutrition values saved, they appear in a formatted nutrition panel on the public-facing consumer QR landing page.
CSV export
Each field appears as a column named nutrition.{key} (e.g. nutrition.protein). Reference quantity exports as nutrition_ref_qty.
Nutrition data only appears on the consumer QR page if at least one nutrition value has been saved for that SKU. Fields with no value entered are hidden from the public panel.
Permissions reference
Access is controlled by the settings_nutrition module. Tenant Admins have full access automatically.
Permission
What it allows
read
View the list of nutrition fields (default and custom)
create
Add new custom nutrition fields
update
Edit label and unit of any field (including defaults)
delete
Delete custom fields (default fields cannot be deleted)
export
Export SKU nutrition data to CSV
manage
Full access — equivalent to all permissions above
Troubleshooting & FAQs
I can't see the Nutritional Settings menu item.+
Your user account does not have read permission on settings_nutrition. Ask your Tenant Admin to grant you at least the 'read' permission for this module.
The Add field button is disabled / not visible.+
You have read-only access. A Tenant Admin needs to grant you 'create' permission on the settings_nutrition module.
My custom field isn't appearing in the SKU nutrition form.+
Make sure you are viewing the same entity as the one where the field was created. Nutrition fields are entity-scoped — switch entity context using the selector at the top of the dashboard.
Why does deleting a field not remove old SKU nutrition values?+
Meiver preserves historical data by design. The stored values remain in the database but are no longer shown in the UI or exported. This prevents data loss for already-processed SKUs.
I changed a field's unit but the SKU form still shows the old unit.+
Try a hard refresh (Ctrl/Cmd+Shift+R). If the issue persists, the SKU form may be cached — log out and back in to force a full reload.
Can I reorder the nutrition fields?+
Not currently. Default fields always appear first in the order listed (Protein, Carbs, Fat, Sugar, Sodium, Energy), followed by custom fields in the order they were added.
Can I duplicate a field definition?+
No. Each field key must be unique within an entity. If you try to add a field whose generated key already exists, the system will reject it with a duplicate key error.
Ready to configure your nutrition fields?
Head to Nutritional Settings and customise the fields that appear on every SKU.