Integrations and data pipelines
Booking APIs, product feeds, POS and ERP synchronisation, and conversion tracking that reports the truth.
Integration work is judged on what happens at 3am on a busy weekend, not on whether it demoed correctly. Most of it fails quietly, which is the worst way for it to fail.
The kinds of pipeline I build
- Booking and availability feeds from an external reservation system, kept in step with the site.
- Scheduled product imports at real scale — thousands of items, attribute mapping, category rules, search reindexing afterwards.
- Point of sale and stock synchronisation, including the awkward cases where two systems each believe they are authoritative.
- Product feeds and generated catalogue creatives for advertising channels.
- Google Ads, GTM and GA4 conversion tracking that reconciles against actual orders rather than reporting a comfortable fiction.
Built to be observable
Every pipeline gets logging, a failure path and a way to tell whether last night’s run worked, without you having to open the database. Silent success and silent failure should never look the same from outside.