Activity History gives your team a complete audit trail for every recipe in your Food Label Maker account. Every change is logged automatically, so you always know who made each edit, what was changed, and when. For teams managing multiple SKUs across several people, this cuts out the back-and-forth that slows down label approvals and gives your compliance team a verifiable record to hand over whenever a regulator or supplier asks.
This guide walks you through opening the log, reading it, and filtering it to find exactly what you need.
Step 1: Open Activity History
From your recipe, open the Manage Recipe menu and select Activity History. The log opens right over your recipe.
Step 2: Read the Log
Every change to the recipe is listed in order, across five columns:
Name: The team member who made the change.
Module: The part of the recipe that was affected, such as Recipe, Recipe Ingredient, or Tag.
Date: When the change was made.
Action: What was done, such as Created, Updated, or Deleted.
Description: A summary of exactly what changed.
If the log spans multiple pages, use the pagination controls at the bottom to move through older entries.
Step 3: Filter the Log
At the top of the log, three filter dropdowns let you narrow the view:
Name: See the edits made by one team member.
Module: Focus on a specific area, such as ingredients, recipe details, or tags.
Action: Show only what was created, updated, or deleted.
You can combine filters to find exactly what you need. For example, filtering by a team member and the Recipe Ingredient module shows every ingredient change that person made, making it easy to spot an allergen being added or removed, an ingredient being swapped, or a new tag being applied before the label ever reaches print.
Tips
Review Activity History before approving a label. A quick scan of recent changes helps quality teams catch ingredient swaps or allergen edits before printing.
Every entry is date-stamped, so the log serves as a verifiable trail for compliance reviews and supplier traceability requests.
Use the Module filter when investigating a specific issue. If an allergen statement looks off, filtering to the relevant module shows you every related change at once.
Watch the video tutorial here: