Dentreat

In health tourism a patient does not choose a clinic — they choose a treatment package: the procedure, the clinic, accommodation, transfer, and follow-up are one decision. Off-the-shelf commerce themes cannot carry that shape, because a product is modelled as one seller with one price.

What I needed was a structure where the same treatment can be offered by different clinics at different prices and with different content, and where adding clinics grows the data rather than the code.

I took Shopify’s Taste theme as a base and built an entirely custom component family on top of it. Clinic and treatment pages are not hardcoded into the theme; they are driven by Shopify metaobjects. Adding a clinic means adding a record, not opening a Liquid file.

The operational side of the platform has too many steps to track by hand: enquiry, pre-assessment, clinic routing, appointment, reminder. I wired these end to end with Shopify Flow and Make.

To make content operations independent of the admin panel, I also wrote scripts against the Shopify Admin API — pages, products, and metaobject records can be created and updated in bulk.

Alongside the technical work I built the supply side. I ran partnership discussions with 20+ clinics and designed an onboarding process covering the application form, document collection, and Drive automation. Two partner clinics were integrated into the platform.

Because the project is a team of one, not losing the decision history mattered. The repository holds documentation alongside code: component pages, architecture decision records, and a chronological work log. Why a decision was made six months ago can still be read from the repo.