Magento · Accessibility
61WCAG 2.2 findings in the audit, 15 of them critical
An accessibility audit, fixed one finding at a time
The search box trapped keyboard users, the checkout left screen readers on the previous step, and the basket quantity buttons did nothing from a keyboard. Every finding was fixed and released on its own with the auditor’s reference on it, so the retest could trace each result to a single change. 48 passed at the first retest.
Magento · Analytics
3 of 11orders that reached Google Analytics on the day we measured
Purchases dropped before the page knew the customer had consented
The tracking was installed and the cookie banner worked. The purchase event just fired before the page had told Google whether the customer had said yes, so returning customers were counted as unknown for the first moment of the page. We set the consent state before the tag manager loads and read the saved answer straight away.
Hyvä · Migration
5 weeksfrom first commit to a Hyvä storefront taking orders
A Hyvä storefront, live in five weeks
A Hyvä migration replaces the entire front end, and a lot was attached to the old one. We reviewed all 44 of the store’s custom modules and decided for each whether to port it, reinstall it or drop it, then fixed what a fast new theme quietly breaks: site search, address lookup at checkout, visitor counting and the marketing pixels.
Magento · Security
5 stores, 1 dayAdobe’s October security patch, applied and released
One security patch, five stores, one day
Every Adobe patch is tested on our own copy of each store first. September’s emergency patch went on within the week. When one store’s build later failed because a patch had been applied twice, we replaced the patching script with one that applies each patch exactly once, put it on every other store, and October’s patch went on five stores in a day.
Magento · Upgrade
1,619SEO redirect rules carried through a two-version upgrade
Two Magento versions up, with 1,619 redirects intact
Upgrading two Magento versions changes how Magento sends mail, so the SMTP module and the form builder had to be replaced or patched, a payment module moved to a managed package, and one store sent every email twice until we found why. The 1,619 redirect rules that protect the store’s search rankings came through unchanged.
Hyvä · Checkout
Charged, no orderwhat a missed tick box used to cost the customer
The card was charged. The order never existed.
The card step and the rest of the checkout’s checks ran at the same moment. A customer who had missed the terms box still got the bank’s prompt, approved it, and then watched the order fail on the box they had missed. The card step now waits until everything else on the page is valid.
WooCommerce · Takeover
Updatable againevery live-site edit moved into a child theme under version control
A WooCommerce theme that could be updated again
Over the years, changes had been made straight into the theme’s files on the live site: header details, styling, a tracking tag. Any theme update would have wiped them, so nobody updated, and the store fell behind on security fixes. We moved every change into a child theme and put the whole site under version control.
Magento · Development task
One screento set what customers pay per size, across the catalogue
Prices for every size, on one screen
A store selling prints by size had to edit prices product by product, option by option. We added two admin screens: Size Prices, where the team types the price per size, sees before and after, and saves, and Extra Prices, one price per optional extra across all products. Two reports went in alongside so the team can see which sizes sell and which are abandoned.
Magento · Workflow
One threadper order, with every proof revision and reply in it
Every design proof in one conversation
Orders that need a design proof used to be a loose set of emails and statuses. We rebuilt the module so each order has numbered proof revisions and a single conversation, visible to staff in the admin and to the customer in their account. Staff get a morning digest of what is waiting, and a reconciler catches orders that fell out of step.
Magento · Reviews
4.9Google rating from 79 reviews, with the store asking only customers whose order arrived on time
Review requests that only go to customers whose order arrived on time
Asking every customer for a review also asks the ones whose order was late. We built review requests into the store with rules: paid in full, dispatched within five working days, a week after dispatch, never a disputed order, sent at 11:30 on Tuesdays and Wednesdays with a daily summary for the team. Customers who had a bad week are left alone, and the ones who are asked say yes: the store stands at 4.9 on Google from 79 reviews.
Is your store doing one of these?
Send the store URL and one line about what is going on. A senior developer reads every message and replies within one working day.