The admin assistant: ask the store instead of hunting through menus
A panel on every admin page reads the store with the same tools as the API, prepares changes that wait for a confirmation, and can run as a scheduled task.
The new Maho features in detail: what they do, where they live and what changes in the daily work. Releases link here for the deep dive.
A panel on every admin page reads the store with the same tools as the API, prepares changes that wait for a confirmation, and can run as a scheduled task.
CMS pages, CMS blocks and blog posts come together by dropping blocks, with the unsaved content previewed next to the editor and the theme classes ready to use.
Media, customer uploads, downloads, sitemaps and feeds go through named mounts: local.xml points one at a bucket and several web nodes work with no shared disk.
Since 26.9 Maho can be used by AI agents (MCP server, 201 tools, OAuth login) and read by them with robots.txt, llms.txt and markdown.
Since 26.9 layered navigation accepts several values on the same attribute: OR inside a filter, AND across filters, off by default.
Maho emits structured data since 26.7, and since 26.9 the product markup is complete: reviews, price, shipping, returns and variants.
Since 19 June 2026 directive 2023/2673 asks for a withdrawal button. Maho ships one since 26.7.0: configuration, widget and admin work.
Since 26.7 a switch per store view attaches the invoice, shipping document and credit memo PDF to the email announcing it.
Since 26.3 ShippingBridge sends cart and address to a JSON endpoint and shows the methods that come back, with no module to write.
Since 26.1 Maho runs on MySQL, PostgreSQL and SQLite. When PostgreSQL pays off, when SQLite is enough, and what to check before moving.
Since 25.9 customers are grouped by behaviour rules, and since 25.11 those rules send email sequences with generated coupons.
The Maho blog is in the core since 25.9.0, not bolted on: posts, categories, SEO, sitemap, search suggestions, a widget and an API.