03 · Shopify & eCommerce
The engineering behind the storefront.
Themes are not usually the bottleneck. The bottleneck is the catalog that drifts out of sync with the ERP, the attribution that loses half the journey, and the search box that returns nothing for a part number.
The problem
Where Shopify stops.
Shopify is excellent at being a storefront and indifferent about everything behind it. Once a business has real inventory, real B2B pricing or a real back office, the gaps show: catalogs drift, orders need enrichment, and reporting disagrees with itself.
Attribution is the most common complaint. A customer arrives on mobile from an ad, returns on desktop days later, and converts — and the ad platform, GA4 and Shopify each tell a different story about what happened.
The other is discovery. Default search fails on part numbers, fractions and synonyms, which is exactly the vocabulary technical catalogs are made of.
What we build
Apps, sync and signal.
- Custom Shopify apps, including embedded admin tools
- Product and catalog sync with back-office and ERP systems
- Cross-device attribution with identity stitching across sessions
- Typesense-backed product and collection search
- Conversion workflows across the funnel — cart, quote and follow-up events
- Automation through Shopify Flow and n8n
Architecture
Storefront to back office.
- 01captureA lightweight script records journey and cart events with device signals
- 02stitchSessions are joined into one identity across devices where evidence supports it
- 03syncCatalog, price and inventory changes move both ways on a schedule and on webhook
- 04indexProduct changes are pushed into the search index as they happen
- 05attributeOrders are matched back to first and last touch, with gaps flagged not guessed
- 06reportOne reporting surface the marketing and ops teams both trust
Stack
- Shopify
- Laravel
- JavaScript
- MongoDB
- GA4
- Typesense
- Shopify Flow
- n8n
Questions
Asked most often.
Will this slow the storefront down?
The tracking layer is deliberately small and asynchronous. Performance is part of the acceptance criteria, not something we check afterwards.
Do we have to leave our theme?
No. Most of this work sits behind or alongside the theme rather than replacing it.
Can attribution survive cookie restrictions?
Partly, and we are honest about the limits. Server-side capture and identity stitching recover a large share of journeys; anything unresolved is reported as unknown rather than attributed to the last thing we happened to see.
Can you integrate our ERP or accounting system?
Commonly Zoho, Xero and Google Sheets, through n8n or direct API work.
Next step