Theme & store build
Full storefronts from an empty admin, or precise edits to the theme you already run. Written directly in Liquid.
Shopify virtual assistant and store specialist for founders and small ecommerce teams. Two years inside Shopify's technical merchant support. Theme work, product data, daily orders, page speed and search, handled by one person who can read the code.
No pitch deck. You show me the store, I tell you what I would fix and what it costs. You keep the list either way.
Most of what I do to a store is invisible from the front end. It happens in the Theme code (Liquid)Shopify's templating language. Editing it directly is how you change a storefront without installing an app that charges monthly and slows the page down. rather than in an app, in the Structured product data (metafields)Extra fields on a product — brand, format, origin, use case — stored as data instead of typed into the description. Filters, cluster pages and search all depend on them existing. underneath the catalogue, and in whatever is quietly costing you Core Web VitalsGoogle's three loading and responsiveness measures: LCP, INP and CLS. They are measured on real visits from real phones, which is why a store can look fast on your laptop and still fail. on a mid-range phone.
If you have been told your store needs AEO — answer engine optimisationGetting cited by AI answers rather than only ranking in blue links. In practice it is structured data, clear headings and content that answers a question outright. or a Staging branchA copy of the theme where changes are made and checked before they reach customers. Without one, every edit is made live, in public, on a store that is taking money. and were not told what either means or whether you need it, that is the gap this page is trying to close. You should be able to read a proposal from me without a glossary.
How the notes work: each one is a native popover anchored to its term with CSS anchor-name — no tooltip library, no JavaScript. Both features sit behind an @supports check, and where they are missing the note prints in the margin instead of disappearing.
Everything is written into the theme rather than bolted on as another app, because every app you add is another thing that can slow the store down or break in an update.
Full storefronts from an empty admin, or precise edits to the theme you already run. Written directly in Liquid.
Bulk imports, variant clean-up and structured attributes, plus the collections and filters that sit on top of them.
Orders, inventory, refunds and the customer inbox. The unglamorous daily work that keeps a store trustworthy.
Find what is actually slowing the page down, then fix it in the theme rather than installing another app to compensate.
On-page SEO plus the structured data that makes a store the one AI Overviews, ChatGPT and Perplexity actually cite.
Shopify Flow for the repetitive work, gateways and checkout configured properly, apps wired together so they stop fighting.
Curated rather than exhaustive. Each one follows the same shape so you can compare them: what was broken, what I did, what came out of it.
A distributor carrying imported brand lines was running entirely brick-and-mortar. High overhead, reach limited to walk-ins, and no catalog structure to build anything on.
Selling online with a catalog structured to grow, bulk updates through Matrixify, and alerts running without anyone watching the admin.
Add the Taste Culinary Food quote here. Beside its own case study is where a testimonial does the most work.Client name, Owner · Taste Culinary Food
A growing catalogue and a storefront where every new section risked breaking the brand's typography and colour rules. Deploys went straight to live with no staging step.
New sections land inside the existing system rather than beside it, and every deploy traces back to a commit.
Add the Adahlia Boutique quote here.Client name, Founder · Adahlia Boutique
Stock counts and prices arrived as supplier spreadsheets in a different shape to the Shopify catalog. Reconciling them by eye was slow and produced quiet errors that surfaced as oversells.
A repeatable check the owner runs themselves, with the risky write step kept under human approval by design.
Add a quote about the tool here, or delete this block. Three strong case studies beat twelve weak ones.Client name · Taste Culinary Food
You show me the store and the thing that has been annoying you. I say honestly whether it is worth paying someone to fix.
A list ordered by what will actually move revenue, with a price against each item. Yours to keep and hand to anyone.
Work happens on a staging copy wherever possible. Progress ships as it lands, not a silent month then a surprise.
Documented and handed back, or I stay on monthly and keep running it. Your call, made at the end rather than the start.
From April 2024 to April 2026 I worked inside Shopify as technical merchant support, front line for merchants worldwide. Themes, apps, payments, checkout, DNS, domains, gateway failures. When something broke, it landed in my queue.
That job taught me where stores actually break, and it is almost never where the owner thinks it is. Now I do the fixing directly, freelance, for founders and small teams who need someone who can read Liquid and answer a customer email in the same afternoon.
Before Shopify: two years of high-volume data processing and a year coordinating patient care, which is where the catalog discipline comes from. Information Technology at Gordon College, Olongapo City, where I still work from.
Bring the store URL and the thing that has been annoying you. Worst case you leave with a straight answer and a written plan you could hand to anyone.
No retainer required to start. No lock-in if you stay. · +63 976 148 2996