Customer Account

v2.26.0 Updated Sep 15, 2026

Customer Account

Refonte de l'espace client Magento : un menu latéral groupé et piloté depuis l'admin, et un tableau de bord en tuiles qui expose enfin toutes les fonctions du….
Hyvä Compatible Magento 2.4.4 Magento 2.4.5 Magento 2.4.6 Magento 2.4.7 Mage-OS 2.0 Mage-OS 2.1
€99.00
Try the live demo
  • Updates and support included for 12 months
  • License key delivered immediately by email
  • 30-day money-back guarantee
  • Full documentation included
  • Compatible with Hyvä themes
  • Composer-ready installation

Customer Account

Magento's account area has not changed in years: a flat list of ten to fourteen text links that every installed extension adds to, a dashboard showing two blocks, and an order history that is a bare table. It is the page repeat customers see most often, and the one nobody redesigns.

This module rebuilds it end to end. A grouped, icon-driven side menu configured from the admin. An order history of cards with search and status filters, where a row opens in place to show what was in the order and lets the customer reorder any line. A dashboard carrying the order in progress, a buy-again panel built from what has actually been bought twice, a stats strip and a recent-activity feed. A product alerts screen Magento never shipped. Address cards, a restyled order detail page, and a site-wide banner for a parcel waiting at a pickup point.

Who it is for

  • Merchants whose account menu has grown one extension at a time and lost any readable order
  • B2B and spare-parts stores where customers come back often to reorder, and to fetch documents
  • Agencies wanting the same polished account area across a portfolio, without rebuilding it per site
  • Multi-store-view shops needing a different arrangement, wording and colours per scope

Key benefits

  • A grouped menu, not a list — fourteen links become four blocks of three, under your own
  • headings, with an icon and a label on every entry. Never the icon alone.

  • No link is ever lost — links are matched on their route, not their block name, so one added
  • by an extension installed later still appears, in the fallback group. A page never quietly becomes unreachable.

  • Reorder where the customer already is — open an order row, see its lines with images and unit
  • prices, and add any of them to the cart without leaving the page.

  • A buy-again panel built on evidence — by default a product has to have been ordered in two
  • separate orders. On a catalogue where nobody reorders, the panel simply does not appear; there is no per-project decision to make.

  • Search and filters on the order history — over order numbers, product names and SKUs, applied
  • to the collection rather than to the rendered page, so the pager and the counts stay honest.

  • The screen Magento forgot — customers can finally see and cancel the price-drop and
  • back-in-stock alerts they subscribed to. All the alert logic stays Magento's.

  • Managed from two admin listings — groups and link mapping are real entities with search,
  • sorting and column control, scoped per store view, and they can be exported and imported from the CLI so staging and production stop drifting apart.

  • Reversible — one switch and the page is exactly Magento's again. No native block is removed
  • from the theme; every removal runs through configuration, and Magento's own blocks are kept and restyled rather than replaced.

  • Full page cache friendly — the personal parts arrive through private content, so the account
  • pages Magento ships cacheable stay cacheable.

  • Accessible — labelled nav landmark, current link announced, group titles wired to their
  • lists, visible keyboard focus, 44px touch targets, and a mobile menu that folds behind a bar of its own.

Compatibility

  • Magento 2.4.x / Mage-OS equivalents
  • PHP 8.1, 8.2, 8.3
  • Requires wimakeit/module-core (^3.0)
  • Luma, Magento/blank and bespoke root themes; Hyvä through the companion module
  • wimakeit/module-customer-account-hyva

  • In-page delivery tracking through wimakeit/module-customer-account-delivery-tracking (optional,
  • 1.2 or later)

  • Works with themes that rebuild the account menu inside their own wrapper

Install this module via Composer. Make sure your auth.json is configured with your Wimakeit credentials.

Terminal
$ composer require wimakeit/module-customer-account:^2.26.0
$ bin/magento setup:upgrade
$ bin/magento setup:di:compile

Installation

composer require wimakeit/module-customer-account
bin/magento module:enable Wimakeit_CustomerAccount
bin/magento setup:upgrade
bin/magento setup:di:compile
bin/magento cache:flush

Dependencies

PackageMinimum
magento/framework^103.0
wimakeit/module-core^3.0
PHP8.1 (tested up to 8.3)

Also required: magento/module-catalog and magento/module-product-alert, both part of every Community Edition install — Composer resolves them without anything to do on your side.

Optional companions

PackageWhat it addsWhen to install
wimakeit/module-customer-account-hyvaTailwind styling and Alpine templatesThe store runs a Hyvä theme
wimakeit/module-customer-account-delivery-trackingIn-page delivery timeline on the order cardwimakeit/module-delivery-tracking is installed — 1.2 or later, earlier versions are refused by a conflict rule

Neither is required. Without the Hyvä companion the module styles itself with plain CSS; without the tracking bridge the order card simply shows the order status on its own.

Hyvä

composer require wimakeit/module-customer-account-hyva
bin/magento module:enable Wimakeit_CustomerAccountHyva
bin/magento setup:upgrade
bin/magento hyva:config:generate
# then, in the active Hyvä theme:
npm run build-prod

hyva:config:generate registers both this module and the base one in app/etc/hyva-themes.json, so Tailwind keeps the classes the templates use.

First steps after installing

1. Go to Stores → Configuration → Wimakeit → Customer Account. 2. Set General → Enable to Yes. The module ships switched off, so nothing changes until you do. 3. Go to Wimakeit → Customer Account → Navigation Groups. Four groups are seeded: purchases, profile, preferences, help. Rename them to your customers' language before anything else — these headings are what they read. Labels print exactly as typed and are never passed through the translation layer; to translate one, add a row carrying the store view. 4. Go to Wimakeit → Customer Account → Navigation Links. Fifteen routes are already mapped, covering what Magento, PayPal, Vault, Wishlist, Reviews, Newsletter, Downloadable, Mage-OS RMA, Mollie and the Wimakeit range ship. Anything not listed still appears, in the fallback group. 5. Open /customer/account as a logged-in customer and check the fallback group: whatever landed there is a link this store has and the seed did not know about. Map it, or leave it. 6. Review the feature switches. The dashboard tiles, the product alerts page, the greeting and the site-wide alert banner are off by default; the side menu, the order card, the order history restyle, the stats strip, the activity feed and the buy-again panel are on. 7. Adjust Styling to your theme's accent colour.

Carrying the navigation between environments

Configure it once, then move it rather than retyping it:

bin/magento wimakeit:customer-account:nav:export -f navigation.json
bin/magento wimakeit:customer-account:nav:import navigation.json --dry-run
bin/magento wimakeit:customer-account:nav:import navigation.json

The round trip is idempotent, so importing the same file twice changes nothing. Rows the target has and the file does not are kept — the target legitimately carries links from modules installed only there — unless you pass --prune.

A third command, bin/magento wimakeit:customer-account:doctor, reports what the module sees on this installation when something does not appear where you expect it.

Upgrading from 1.x

The group and link mapping moved out of core_config_data into two tables in 2.0.0. A data patch carries an existing mapping across on setup:upgrade; it does nothing if the tables already hold rows, so an upgrade is the standard flow with no manual step. The old configuration rows are left in place, inert.

Version
v2.26.0
Support
12 months
Last updated
Sep 15, 2026
Magento
Magento 2.4.4 Magento 2.4.5 Magento 2.4.6 Magento 2.4.7 Mage-OS 2.0 Mage-OS 2.1
PHP
PHP 8.1 PHP 8.2 PHP 8.3
Hyvä
Compatible
Package
wimakeit/module-customer-account

Compatibility checker

Pick your stack to see if this module fits.

Changelog — Customer Account

Categories: Security, Feature, Fix, Perf, Admin, Deps.

2.26.0

  • Feature — The account menu folds behind a bar of its own on mobile, showing the current page
  • next to its name. Stacked layouts put the menu above the content, so it was a screenful of links before the order the customer came for. New setting, on by default.

  • Fix — The menu had no heading at all on mobile: the stylesheet stepped aside for a theme bar
  • that Luma-family themes render empty and hidden.

  • Fix — Group headings could not be hit with a thumb. Headings and entries now stand 44px tall
  • below 768px, Apple's touch-target floor.

  • Fix — The column stayed frozen in place once stacked, overlapping the content beneath it.
  • Fixaria-expanded and the navigation landmark's accessible name were both wrong on one
  • side of the breakpoint or the other.

2.25.4

  • Admin — The colour fields in the Styling section showed a white swatch instead of the
  • configured colour.

2.25.3

  • Fix — The column heading and the page title now sit on the same line, with their rules facing
  • each other, whatever the size gap between the two texts.

2.25.2

  • Fix — The navigation column slid under a theme's sticky header when scrolling. The offset is a
  • CSS custom property a theme sets once instead of a percentage that only matched by accident.

  • Feature — The navigation is drawn as a card whose entries are rows, replacing the pill
  • treatment: fewer outlines for one column, and an entry now has a surface at rest.

2.25.1

  • Fix — The navigation column sat bare on the page ground with nothing behind it.

2.25.0

  • Feature — "Since your last visit" on the activity feed: what is new, not only what happened.
  • Feature — A note on an order, written by the customer, readable by support from the admin
  • order view.

  • Feature — A thumbnail on every line of an order, and bundle and configurable options rendered
  • in line rather than stacked.

  • Feature — The order detail page is brought in line with the rest of the account: a way back,
  • panels that match, and order information dressed like every other block.

2.24.2

  • Fix — The order search field had no border on themes that reset it.

2.24.1

  • Fix — "My account" was written twice on the dashboard, as page title and as column heading.

2.24.0

  • Admin — The navigation can be carried between environments: three CLI commands export, import
  • and diagnose the group and link mapping, so staging and production stop drifting apart.

  • Fix — The export/import round trip is idempotent, verified by running it.

2.23.0

  • Feature — A page background for the account area, panel headings on a tint, and a dependency
  • free lightbox for product pictures. Thirteen new glyphs in the closed icon set.

  • Feature — A navigation group may carry no title, so one entry can sit above the first heading.
  • Feature — The alert can be drawn inside the page, under its title, instead of pinned above the
  • header.

  • Fix — The account navigation was unreachable on a phone on themes positioning the collapsible
  • block off-screen.

  • Fix — Entries the customer had already opened came out in the theme's visited colour, so the
  • menu looked like it held two kinds of link.

  • Fix — An empty group label rendered as the group's machine code.
  • Fix — The alert banner never appeared for a returning customer, a configurable product showed
  • a zero price in the reorder panel, and the stats strip left a hole when a figure was empty.

  • Fix — The save button on Account Information was cut in half on a phone.

2.22.0

  • Feature — One shared empty state across every list, instead of a grey box where a pictogram
  • belongs.

  • Fix — Account forms lay out on a grid rather than a fixed 48% column.

2.21.0

  • Fix — A store's house "no picture" image is now treated as no image, so placeholder squares
  • stop appearing in the reorder panel and the order lines.

2.20.0

  • Feature — Order lines show the whole calculation: quantity, unit price and line total, on the
  • tax basis the order was placed with.

2.19.0 – 2.19.3

  • Admin — A separate corner radius for cards, so cards are no longer stuck at the value chosen
  • for buttons.

  • Feature — Neighbouring account pages are dressed to match, and line quantities and prices sit
  • in their own right-aligned columns.

2.18.0 – 2.18.1

  • Feature — A "recent orders" card on the dashboard, with product images. How many and which
  • store scope are configurable.

  • Fix — Magento's own recent-orders table no longer renders a second time underneath.

2.17.0 – 2.17.1

  • Feature — The order history is a list of cards rather than a table, which is what fits a phone.
  • Fix — The search field clipped its own placeholder, and the item counter read "1 articles".

2.16.0

  • Fix — The two native dashboard blocks were unstyled, and the reorder panel was the height of a
  • phone.

  • Feature — Icons on the address cards: an invoice on billing, a truck on shipping.

2.15.0 – 2.15.1

  • Feature — Search on the order history, over order numbers as well as product names and SKUs.
  • Feature — Product images in the activity feed, and "last bought 4 months ago" on the reorder
  • panel.

  • Fix — The reorder panel had never returned anything. A search with no result no longer tells
  • the customer they have never ordered.

2.14.0

  • Fix — A customer with nineteen orders could be told they had none, and the activity feed
  • reached back seven years.

  • Feature — What was in the order, shown as images on the dashboard card.
  • Admin — The dashboard tiles are off by default: with a side menu on every account page, they
  • repeated it entry for entry.

2.13.0

  • Feature — An order row opens in place, showing its products, quantities and line totals, with
  • a reorder button on every line. Quantities are carried over.

2.12.0 – 2.12.1

  • Feature — Product images on the order rows: two queries for the whole page, never one per row.
  • Fix — Products with no image no longer draw blank squares.

2.11.0 – 2.11.1

  • Feature — The stats strip moved into the side column, and the menu background is one of four
  • treatments chosen per store.

  • Fix — This module silently removed order cancellation from the history page.

2.10.0 – 2.10.1

  • Feature — The dashboard is two columns on wide screens, with the default shipping address as a
  • card rendered through Magento's own address format.

  • Fix — Links this module could not map rendered as bare blue anchors beside the styled ones,
  • and unmapped links had no icon.

2.9.0

  • Feature — The native blocks in the account area are styled, so the pages this module does not
  • own stop looking like a different site.

2.8.0

  • Feature — Counts beside the navigation entries. Sources register themselves; an entry with
  • nothing to count shows no badge rather than a zero, and a count may mark itself as needing action.

  • Admin — The greeting is off by default.

2.7.0 – 2.7.5

  • Feature — Add to cart without leaving the page, from the reorder panel, with toasts announced
  • politely to screen readers. Without JavaScript everything falls back to a form post.

  • Feature — The two default addresses render as cards.
  • Fix — Blocks added since 2.3.0 rendered with no card, border or colour; the full-width setting
  • had no effect on Luma-derived themes; the order history page threw on every render; the pager was broken; a stat with no history drew a confident flat line.

2.6.0

  • Feature — The order history page is restyled, with status filters and a status pill per row.
  • Filtering is applied to the collection, so the pager and the count stay correct.

2.5.0

  • Feature — A stats strip at the top of the dashboard and a recent-activity feed below the order
  • card, both behind provider interfaces so a project can add its own sources.

  • Perf — Figures are cached for fifteen minutes by default.

2.4.0

  • Perf — The greeting no longer takes the account area out of the full page cache. It is filled
  • from private content instead of rendering a non-cacheable block on every account page.

  • Feature — Use the full page width, on by default: Magento centres the account pages in a column
  • sized for editorial text, which gives an order table a third of the screen.

  • Fix — The styling values reached the navigation and nothing else; they are now declared where
  • the whole stylesheet reads them.

2.3.0

  • Feature — A "buy again" panel on the dashboard, built from what the customer has actually
  • bought more than once rather than from a wishlist.

  • Perf — Only product ids are cached, tagged with the collections cache.

2.2.0

  • Feature — A page for the customer's product alerts. Magento ships the whole mechanism —
  • models, cron, e-mails — and no screen for the customer to see or cancel what they subscribed to.

  • Admin — Every admin help text is translated; eighteen had never been, in any locale.

2.1.0

  • Deps — Alert sources are wired through a composite, so several packages can contribute.
  • Requires wimakeit/module-customer-account-delivery-tracking 1.2.0 or later when installed.

2.0.0

  • Admin — The navigation moves out of the configuration section into two admin listings with
  • search, sorting, column control and an edit form each, scoped per store view.

  • Admin — Separate ACL resources for the two listings, distinct from the configuration section.
  • Feature — Group and link labels print as stored instead of passing through the translation
  • layer, so a merchant's own wording is no longer rewritten by a dictionary they do not control.

  • Perf — The mapping is cached and tagged with both entities; the link index covers the read
  • that runs on every account page.

  • Deps — Breaking: navigation/groups and navigation/links are removed from the configuration
  • section. An automatic data patch carries an existing mapping across; it does nothing if the tables already hold rows.

1.2.0

  • Feature — Site-wide alert banner for signed-in customers, announcing a parcel waiting at a
  • pickup point. Behind a provider interface with a null implementation, so no other module is required.

  • Admin — A native colour picker for the styling fields, replacing one that depended on a jQuery
  • plugin Magento no longer ships.

  • Fix — Group headings no longer shift on hover, and menu items no longer bleed outside the
  • sidebar block.

1.1.0

  • Fix — Deactivating a link in the mapping hides it everywhere, not only in the menu. A rule on
  • a path no longer deactivates everything beneath it.

  • Perf — The order lookup selects the columns it needs instead of loading whole objects, status
  • labels are cached, and invoice presence is read from a column rather than by loading invoices.

1.0.0

  • Feature — Grouped account navigation with icons, configured from the admin: groups, per-link
  • labels, ordering, and visibility in the menu and on the dashboard.

  • Feature — Fallback group. Links this module does not know about, including those added by
  • extensions installed later, are still rendered instead of disappearing.

  • Feature — Dashboard tiles generated from the same mapping as the navigation, so the menu and
  • the dashboard cannot drift apart.

  • Feature — "Order in progress" card: status, date, total, invoice and tracking actions.
  • Feature — In-page delivery timeline behind a provider interface, with a null implementation by
  • default so no tracking module is required.

  • Feature — Personalised greeting, with optional customer group.
  • Admin — Dynamic rows for groups and link mappings, with a closed icon picker.
  • Admin — Styling controls exposed as CSS custom properties.
  • Security — The link path field rejects absolute URLs and schemes; icons come from a closed
  • allow-list; the current order is resolved from the session and filtered by store.

  • Perf — The order lookup is a single indexed query capped at one row. The navigation mapping is
  • memoised per request, since Magento calls getLinks() several times per render.

Found a bug? Tell us about it.

A short form opens in a new tab — the module name and your language are already filled in. Share what you tried, what went wrong, and we will get back to you within one business day.

Report a bug for Customer Account
Module SKU: wimakeit-module-customer-account · Language: en_US

Need help?

Our team is available to assist with integration.

Contact us
Planifier un appel