¶ Cache - refreshing data in the store and admin panel

Cache in Hummerce temporarily stores frequently used data - database query results, generated page fragments, URL rules and language messages - so the store and admin panel run faster and put less load on the server. Most cache clears itself automatically after data changes, and store staff can force a manual refresh from the panel or with a command to the AI assistant if needed.

Last updated: core platform feature, available in all current versions, updated 2026-09-29.

¶ Benefits and use cases

Faster store and admin panel - fewer database queries and less server work when regenerating the same page fragments (e.g. menu, header, item lists in a category).
Automatic refresh after changes - editing an item, price, price list or category usually clears the related cache on its own; store staff usually don't need to do anything manually.
Quick response when a change isn't visible yet - manually clear the selected cache from the panel, without waiting for a developer or for the cache to expire.
Refresh with a command to the AI assistant - the most commonly needed clearing (database, category tree, admin panel permissions) can be requested without logging into the panel.

¶ How it works

¶ What is stored in cache

The panel groups cache for manual clearing into three groups (Status -> Cache):

Basic - language messages, URL rules (friendly URLs), page content fragments (canvases), database query cache, the list of parcel lockers available in the cart, data source reloads, selected Allegro integration data.
Prices - matches of price list rules to customers, views and items, and price calculator matches - speeds up price calculation in a store with many rules and price lists (Price list rules).
System - the category tree, admin panel authorization, change history entries, cache of basic statistics on the panel's home page.

¶ Automatic clearing

Updating an object in the panel (item, price list, category and similar) usually clears its related cache on its own - store staff don't need to do anything.
Exceptions are changes that appear with a delay due to another mechanism, not cache itself - e.g. banner visibility refreshes roughly every 5 minutes (Banners), and a full search index rebuild happens once a day (Items suddenly missing from the store).

¶ Manual clearing in the panel

Status -> Cache - a list of groups and individual caches; clicking a group clears every cache in it, clicking a single cache clears only that one.
Useful when a change (e.g. in price list rules or admin permissions) isn't visible yet and you don't want to wait for the cache to expire.

¶ Refreshing with a command to the AI assistant

The AI assistant (MCP) can clear the most commonly needed set of caches with a single command: the database query cache, the category tree, and the admin panel authorization cache, and it also tries to refresh the store-side (front-end) database cache - that's a separate application with its own cache.
The command does not clear caches of modules that react to an event requiring a full request and response from the browser (e.g. coupons, delivery deadlines, item filters) - those need the button in the panel (AI assistant - MCP server).

¶ Disabling cache

The cache module can be disabled in Configuration -> Settings, group Cache module - disabling it is only acceptable for testing purposes, since it significantly slows down a production store.
Page content cache (canvases) has its own retention setting in the Canvases group - shortest, short, medium or long.

¶ Version

Cache is a core platform mechanism - it works in all current store versions.
Manual clearing from the panel (Status -> Cache) and a separate retention setting for page content cache (canvases) - since version 2.18.
Refreshing with a command to the AI assistant - requires a deployed MCP server (AI assistant - MCP server).

¶ Dependencies

The cache module is part of the standard platform configuration.
Refreshing with a command to the AI assistant requires a deployed MCP server and admin permissions on the account the assistant connects with.

¶ Implementation

Cache works right after an update - it's part of the platform and doesn't require implementation.

¶ Limitations

Manual clearing from the panel covers more caches than the AI assistant command - some modules (e.g. coupons, delivery deadlines, item filters) only clear via the button in the panel.
The store (front end) and the admin panel are separate applications with their own cache - refreshing in the panel tries to refresh the store's cache too, but if that fails, the store may show unrefreshed data for a few more minutes, until its own cache expires.
Disabling cache is only acceptable for testing - in a production store, cache should always stay enabled.
We do not review the configuration for legal compliance.

¶ Future development

Extending the AI assistant command to clear the full set of caches, including modules that today only clear via the button in the panel.
Clearer indication in the panel of which changes require manual cache clearing and which refresh on their own.

¶ Frequently asked questions

Do we need to manually clear cache after changing data in the store?
Usually not. Updating an object in the panel usually clears its related cache on its own.

Can clearing cache be requested from the AI assistant?
Yes, for the most commonly needed set - database, category tree and panel permissions. Coupons, delivery deadlines and item filters must be cleared with the button in the panel.

Is disabling cache safe on a production store?
No. Disabling it is only acceptable for testing purposes - it significantly slows down a production store.

How long does implementing the cache mechanism take?
Cache works right after an update - it's a core platform feature and doesn't require separate implementation.

Is clearing cache in the panel visible in the store immediately?
Usually yes, but not always right away - the store (front end) has its own cache and in rare cases may show unrefreshed data for a few more minutes.

Banners - an example of a change visible with a delay for a reason other than cache.
Items suddenly missing from the store - a delay in item visibility during a search index rebuild.
AI assistant - MCP server - commands available to the AI assistant, including refreshing cache.
Price list rules - an example of data sped up by the "Prices" cache group.
On hummerce.com: AI assistant - MCP (in Polish).

Want to check how refreshing data works in your store? Contact the Hummerce team (in Polish).

¶ Configuration details

¶ Access in the admin panel

Manual clearing: Status -> Cache - a list of groups (Basic, Prices, System) and individual caches within each group.
Module configuration: Configuration -> Settings, group Cache module - settings Enabled (yes by default), Maximum number of entries.
Page fragment cache (canvases): Configuration -> Settings, group Canvases - settings Store content in cache (yes by default) and Cache retention period (shortest/short/medium/long).

¶ REST API and MCP

The standard REST API does not expose a separate resource for clearing cache - it's only available from the panel and via the AI assistant.
MCP (AI assistant - MCP server): ec2_cache_clear - clears the database query cache, the category tree and the panel authorization cache, and tries to refresh the store-side (front-end) database cache. It does not clear caches of modules that react to an event requiring a full HTTP request/response (e.g. coupons, delivery deadlines, item filters) - use the button in the panel for that. Requires admin permissions.