Change history in Hummerce records who changed what and when in the store - from orders and items to settings and admin accounts. Support staff and implementers have a full change trail in one place, useful for explaining mistakes, controlling operator work, and security audits.
As of Hummerce 2.32-2.35, updated 2026-09-29.
¶ Benefits and use cases
- Explaining mistakes - check who changed a price, order status or customer data, and when.
- Controlling operator work - review the changes made by a specific admin.
- A trail of AI assistant changes - changes made via MCP are marked in the history as remote, see AI assistant - MCP server.
- Smaller database and a faster panel thanks to optional archiving of older entries to Google BigQuery, see Reports - BigQuery and Looker Studio.
- Filtering by data type and change type - quickly reach the entries you need without browsing the entire store history.
¶ Objects and entry types
- Since version 2.32, history is split by data type - two filters are available: Object and Entry type.
- Object determines what kind of data the entry concerns - among others Order, Item, Customer, Category, Coupon, Warehouse, Price list, Cart promotion, View, Set, Complaint, Admin, and dozens of others. The MCP tool
ec2_history_vocabulary shows the full, current list for a given store.
- Entry type filters further within the selected Object - most often Creation, Update, Deletion; the list of types is matched individually to each Object.
- Since version 2.35, history can be browsed for all objects, including those previously available only as a bulk "Uncategorized" group.
- Since version 2.35, a history entry shows directly which object the change concerns - this makes the list easier to read when browsing without a selected Object.
- Since version 2.34, a change to the assigned manufacturer, customer group or item group is recorded more clearly - an empty value is shown as "(none)", and the change arrow is always visible, so you can see whether a value was added, removed or changed.
Passwords and tokens saved as a parameter value are masked already at the moment they're written to history - the entries never show their real value, regardless of whether the history is viewed in the panel, via the REST API, or via the AI assistant. Described in more detail on AI assistant - MCP server.
- Change history is a core platform feature - available in all current store versions.
- Split into Objects and Entry types - since version 2.32.
- Archiving older entries to Google BigQuery and a built-in Looker Studio report to view them - since version 2.34, see Reports - BigQuery and Looker Studio.
- Automatic cleanup of old entries from the store database - since version 2.33.169.
- Clearer recording of manufacturer, customer group and item group changes - since version 2.34.
- History for all objects and information about the modified object in each entry - since version 2.35.
- Works right after an update - history is recorded automatically, without configuration.
- Work is only needed for: archiving to BigQuery (see Reports - BigQuery and Looker Studio) and enabling automatic cleanup of old entries, if the store wants to limit the size of its own database.
- Minimum estimated time: enabling and configuring cleanup of old entries (retention period, any additional tables) - from 1 h.
- Cleanup of old entries from the store database is disabled by default - it must be knowingly enabled in settings, otherwise the history grows without limit.
- Deleted history entries disappear from the store database permanently, unless they were already archived to BigQuery.
- The list of entry types depends on the selected Object - you can't filter by Entry type without selecting an Object.
- We do not review the configuration for legal compliance (e.g. the retention period of personal data in the history) - the period is set by the store.
- More information about the context of a change directly in the history list, without expanding each entry separately.
Can you see who made a specific change in the store?
Yes. Every history entry shows the operator (or a remote-change marker, when the AI assistant made it), the date, and the scope of the change.
Are passwords and other sensitive data visible in the history?
No. Sensitive values are masked already when the entry is written, regardless of where the history is viewed.
Does the store history grow indefinitely?
Only if cleanup of old entries hasn't been enabled - the mechanism is disabled by default. Once enabled, it removes entries older than a set period (730 days by default), optionally after first archiving them to BigQuery.
Can history be browsed via the AI assistant?
Yes, with the ec2_history_list and ec2_history_search tools - available to accounts with the change history permission.
How long does it take to set up cleanup of old history entries?
From 1 h - setting the retention period and enabling the task in the panel.
Want to check how change history and its archiving could work in your store? Contact the Hummerce team (in Polish).
- Browsing history: admin panel, Status -> History - filters Object and Entry type, search with the Search button.
- History of a single object: the Change history tab in an object's details (e.g. an order, item or customer).
- Cleanup of old entries (configuration group History management): Run history cleanup task (disabled by default), a list of additional table names to clean up (the table name must contain the word "HISTORY" - a safeguard against mistakes).
- Archiving to BigQuery: module configuration described in Reports - BigQuery and Looker Studio.
¶ REST API and MCP
- No dedicated REST API operations - history is only available in the panel and via MCP.
- MCP (AI assistant - MCP server), admin accounts only:
ec2_history_list - the history of one object: who changed what and when, with a date and entry type filter,ec2_history_search - search the history by operator, entry type, changed field or property, and date range,ec2_history_vocabulary - a list of entry types, operators and object kinds actually present in a given store's history (before filtering by type or who in ec2_history_search).- Changes made by the AI assistant are recorded in the history marked as having come in remotely.
The history screen has no messages of its own visible to store customers - it applies only to the admin panel.
History is not a separate object with its own parameters - it records changes to the parameters and fields of other store objects.