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.
B2B punchout for Coupa, Ariba and Jaggaer: where the implementations actually differ
While cXML and OCI provide a common language for B2B punchout, major e-procurement platforms like Coupa, Ariba, and Jaggaer speak very different dialects. Here is where the implementations really differ.
SEO for builders merchants: branch pages, product hubs and the site architecture that ranks
Standard SEO fails for builders merchants. To rank, your site architecture must prioritise hyper-local branch pages for local intent and product hubs for system-based searches.
Builders merchants on mobile: what site search has to do that nobody talks about
On-site search for a builders' merchant needs to act as a precision tool, not a discovery engine. It must parse complex trade vernacular to succeed, a challenge most platforms are not built for.
The real cost of a release freeze, calculated honestly
The release freeze is the most under-priced line item in most enterprise programmes. A practitioner method for putting a real number on it.
Why most rescue projects are actually replatforms in disguise
A rescue is a diagnosis, not a fix. The honest version of that diagnosis is often a replatform on a shorter timeline than the business expected.
The risk of rebuilding around edge cases
Rebuilding around edge cases in commerce development often diverts resources from core functionality, creating technical debt and project delays. Prioritise based on actual business value and user impact.
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.
How to spot a commerce project that is about to drift
Learn to identify early indicators of a drifting commerce project, from scope creep to communication breakdowns, to prevent delays and budget issues.
Why B2B ecommerce needs pricing logic in the room early
Ignoring pricing complexity until late in a B2B ecommerce project can lead to significant cost and delay. Early integration of pricing logic is critical.
How to plan an ecommerce MVP properly
A well-planned ecommerce MVP focuses on core functionality, technical feasibility, and measurable objectives, enabling strategic iteration and validated growth.
Why launch is not the finish line for commerce projects
Launching a commerce site is just the beginning. Ongoing maintenance, security, and optimisation are critical for sustained performance and growth.
The platform is rarely the first problem
When commerce operations falter, the platform is often blamed. We find the real problems are usually process, people, or data related, not the tech.
Why project ownership matters more than platform choice
Platform choice is secondary to dedicated project ownership. Effective internal teams, clear roadmaps, and strategic alignment drive commerce success.
In conversation with a head of ecommerce, twelve months after replatforming
A Head of Ecommerce discusses the operational realities and lessons learned a year after a significant Adobe Commerce replatforming project, offering practical insights.
Why the best ecommerce agencies say no earlier
Senior ecommerce agencies often decline prospective projects early. This practice ensures alignment, protects specialised teams, and prioritises long-term success over short-term gains.
What makes an ecommerce project supportable after launch
For an ecommerce project to be supportable, it requires clear documentation, established patterns, and a robust support framework. Supportability should be a core design principle.
Ecommerce requirements gathering without creating a monster
Striking the right balance in ecommerce requirements gathering prevents project scope creep and ensures deliverable, adaptable solutions, avoiding the "monster" outcome.
The ecommerce features that sound good but rarely pay back
Certain ecommerce features, despite sounding good on paper, frequently fail to deliver expected returns, misdirecting investment and effort. We explore common examples.
What a good commerce partner should challenge before taking the brief
A commercial partner's value isn't just in execution, but in pre-brief challenge. We highlight key areas where a partner should push back to ensure project success.
Ecommerce discovery: what should actually happen
Discovery is often misunderstood as a pre-sales phase. It is a critical project phase mapping business, technical, and strategic objectives.