E-commerce platforms
Building and extending online stores: catalogue and pricing, checkout and payments, order flow, fulfilment, and the integrations that keep inventory and data honest.
Senior web developer ยท E-commerce & internal business systems
I build the systems businesses actually run on
E-commerce platforms and internal business systems - designed, built, optimised and maintained. I care less about shipping code and more about whether the thing I shipped made the business measurably better
- End-to-end ownership
- Architecture, delivery and the years of maintenance that follow
- Business-first
- Requirements traced back to revenue, cost or risk before a line is written
- Built to last
- Systems that survive traffic spikes, staff changes and framework upgrades
About
Development that answers to the business
Most software problems turn out to be business problems wearing a technical costume. A checkout that loses orders, a warehouse process held together by spreadsheets, a platform nobody dares to deploy on a Friday. That is the work I take on.
I work across the whole stack and the whole lifetime of a system: shaping requirements with the people who will use it, choosing an architecture that fits the team maintaining it, building it carefully, then staying with it through the upgrades, the traffic peaks and the awkward integrations that arrive later.
The measure of a good build is not how clever it looks in review. It is how little it costs the business three years on.
Services
What I take on
Whole platforms or one stubborn problem inside an existing one.
Internal business systems
Admin panels, operational dashboards, reporting and automation that replace manual spreadsheet work and give teams one place to look.
Integrations and APIs
Connecting the systems a business already depends on - suppliers, payment providers, logistics, ERP and internal tools - with sync that fails loudly, not silently.
Performance and reliability
Profiling slow pages and slower queries, caching where it earns its keep, and monitoring that tells you about a problem before your customers do.
Technical SEO
Treating visibility as an engineering concern: crawlability, structured data, clean URL and redirect strategy, and Core Web Vitals that hold up on real devices.
Maintenance and support
Framework and dependency upgrades, security patching, backup and recovery you have actually tested. The unglamorous work that decides whether a platform ages well.
Expertise
The toolkit
Tools are means, not identity - but these are the ones I reach for most, and know well enough to know their sharp edges.
Backend
- PHP
- Laravel
- REST APIs
- Queues and scheduled jobs
- MySQL / MariaDB
- Redis
Frontend
- JavaScript
- TypeScript
- Tailwind CSS
- Vite
- Blade
- Responsive and accessible UI
Infrastructure
- Docker
- nginx
- Linux
- CI/CD pipelines
- Cloudflare
- Metrics and alerting
Practice
- Performance profiling
- Security hardening
- Automated testing
- Code review
- Documentation
- Technical SEO
Process
How the work goes
-
01
Understand
Before anything is estimated: who uses this, what does it cost them today, and what would make the difference measurable.
-
02
Design small
The smallest architecture that solves the problem and can grow. No speculative abstractions, no framework of the month.
-
03
Build properly
Readable code, tests where they earn their place, reviewed migrations, and deploys that are boring by design.
-
04
Measure and maintain
Watch it in production, tune what the numbers say to tune, and keep it patched and upgraded over the years.