Skip to main content
Talk to an expert
Issue 045PositionGovernanceRef 158

Ecommerce technical discovery: what should be checked early

Early technical discovery for an ecommerce project identifies critical system limitations, integration complexities, and potential architectural misalignments. Establishing these factors upfront mitigates significant risks and avoids costly rework during later project phases.

Neil Boughton· Technical Director
3 min readReviewed March 2026
"Thorough technical discovery is not just an optional first step; it is a vital risk mitigation strategy that underpins the entire project's success."
Written by
Neil Boughton, Technical Director at iWeb
Neil Boughton
Technical Director
29 years at iWeb

Neil leads platform architecture and integration strategy at iWeb. He has designed ERP and commerce integration patterns across manufacturing, wholesale and retail, and writes about operational resilience, release governance, observability, and the infrastructure decisions that determine whether large programmes stay stable under pressure. Bias toward durable, measurable systems over architectural theatre.

Next in this thread

Operational notes worth reading next.

All notes in The Record →
Issue 048Briefing · Governance

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.

Ian··5 min read
Issue 046Benchmark · Governance

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.

Neil··4 min read
Issue 044Field Note · Governance

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.

Tom··5 min read
The briefing · regular

A regular round-up of new notes.
No content marketing.

Sent on the last Thursday of the month. The most useful five notes from the previous four weeks, written by the operators, architects, engineers and commercial leads running the work.
Next step

Take this conversation private.

If this note matches the brief on your desk, the version we'd write for your platform, sector and trade-account model is the work itself. Send a short brief and a senior lead replies inside 48 hours.
Talk to an expertBack to The Record →