Notes from the operating record.
Numbered notes from the engineers, architects and operators who write the source. A regular editorial series, two notes per week. Not content marketing.
The Record is an operating archive. Earlier issues are being released progressively, so issue numbers begin partway through the sequence. Archive refs (REF 058, REPL/048) are internal serials, not publication numbers.
Read by the problem you're trying to solve.
Notes are catalogued by category, but the more useful entry point is the brief on your desk. Pick a challenge to filter the feed below.
How to budget a Magento to Adobe Commerce migration in 2026
Budgeting an Adobe Commerce migration on the old Magento spreadsheet is the single most reliable way to underprice it. Here is the model that actually survives contact with the build.
A 200ms search budget for storefronts: how we hit it on Adobe Commerce
Hitting a 200ms search budget on Adobe Commerce is an architecture problem, not a hardware problem. The choices that get you there, in the order they matter.
Adobe Commerce vs Shopify Plus when the deciding factor is trade-account credit
For trade-led businesses, the platform decision is a credit and reconciliation decision. We look at where Adobe Commerce and Shopify Plus actually break under that load.
How to plan a replatform off Magento 2 without a four-week release freeze
A long pre-launch freeze concentrates risk rather than reducing it. A continuous-migration approach keeps the business shipping and turns launch into the smallest event of the project.
Why Magento support retainers fail when there is no roadmap
Magento support retainers often fail without a clear roadmap, turning into reactive cost centres that hinder strategic progress and stability.
Magento 2 end-of-life: the migration paths that survive contact with reality
Magento 2 EOL is not a single deadline. It is a sequence of architectural decisions that have to survive ERP, trade accounts and a finance team that is no longer interested in heroics.
How to make Adobe Commerce easier to maintain
Maintaining an Adobe Commerce platform effectively requires strategic development and operational practices. We cover technical debt, performance, and stability.
Magento support for B2B merchants: what to prioritise
Effective support for B2B merchants on Adobe Commerce requires strategic prioritisation to ensure operational continuity, functional evolution, and cost efficiency.
Adobe Commerce support: what good looks like after launch
Post-launch Adobe Commerce support is critical for ongoing stability and growth, shifting from reactive fixes to proactive maintenance and strategic evolution.
The difference between custom and careless
Customisation is a powerful tool in Adobe Commerce, but without clear governance, it can lead to technical debt and operational burden. Careful planning is needed.
Why "headless" is not a strategy
Headless architecture is a technical choice, not a strategy. We examine when it applies to B2B and complex retail, considering technical debt and long-term goals.
Accessible faceted search on Adobe Commerce: keyboard, screen reader and the patterns that pass audit
Accessible faceted search on Adobe Commerce is critical. We examine ARIA patterns, keyboard navigation, and WCAG compliance to ensure audit success.
INP on Adobe Commerce: the four interventions that moved it below 200ms
Four critical interventions for improving INP on Adobe Commerce: focus on third-party script optimisation, main thread work, JavaScript execution, and server response time.
Peak readiness on Adobe Commerce: the rehearsal checklist we actually use
Preparing an Adobe Commerce platform for peak trading requires a structured approach. We detail our rehearsal checklist for pre-event, live monitoring, and post-event phases.