Back to portfolioEXPERIENCE / COMMERCE ENGINEERING

Building practical
Shopify solutions.

My work brings together end-to-end project ownership, theme engineering, ecommerce operations, platform integrations, automation and behavioural analytics. I use data to frame problems, prioritise changes and evaluate outcomes. I collaborate with business owners, marketing teams and operational stakeholders to turn requirements into maintainable solutions.

Jomar Vallite working at a silver laptop in a studio setting
Working through technical problems, from implementation to verification
01 / WHAT I DO

Technical responsibilities

Storefront development and maintenance

Liquid components, responsive templates, landing pages, accessibility and performance troubleshooting. Work ranges from targeted bug fixes to structured theme improvements.

B2B commerce and operations

Weight-based purchasing workflows, catalogue configuration concepts, product data structures, sales-channel governance and promotional logic.

API integration and automation

Webhook handling, authentication patterns, fulfilment status synchronisation, Shopify Flow automation and operational reporting.

Measurement and optimisation

End-to-end project ownership and data-driven decisions using Shopify Analytics, Klaviyo, GA4, Microsoft Clarity and Hotjar. I investigate bounce and exit pages, conversion funnels, heatmaps and interaction points to prioritise UX, performance and tracking improvements.

02 / SELECTED WORK

Project examples

Wholesale eligibility architecture

Shopify B2B and Flow patterns for aggregate-weight ordering, with a fictional interactive demo in this public portfolio.

Explore simulator

Order and fulfilment integration

Connecting Shopify with warehouse operations through webhooks, status normalisation, automation and resilient event handling.

Workflow automation

Scheduled reporting, loyalty reward eligibility and gift-with-purchase automation patterns, documented without private client configurations.

Explore Flow case studies

Analytics and storefront quality

Investigating ecommerce reporting discrepancies, improving product metadata and maintaining responsive customer journeys.

CYBERSECURITY / PROFESSIONAL DEVELOPMENT

Cybersecurity: Foundation of CERT Operations

CERTIFICATE OF ATTENDANCE / 2023

Foundations of CERT Operations

Completed a 12-hour training programme held 5–6 December 2023 (08:00–17:00 on both days), documented by a signed certificate of attendance.

Organiser
Department of Information and Communications Technology (DICT), Region XII & Mainland BARMM, with the ICT Literacy and Competency Development Bureau (ILDB)
Training dates
5–6 December 2023
Document type
Certificate of Attendance, not a professional cybersecurity certification

The owner's original certificate names this course “Foundations of CERT Operations”; the portfolio heading uses “Cybersecurity: Foundation of CERT Operations” for context. This entry records attendance only, not a tested qualification, operational role or external accreditation. The signed PDF is not publicly distributed to protect its issuer's digital signature.

INDUSTRY CYBERSECURITY SESSION / EVENT ANNOUNCEMENT

No Fiber, No Cyber: Safeguarding the World's Undersea Cables

The U.S.–Philippines Joint Cybersecurity Working Group and digital consultancy APTelecom announced a session on securing global subsea cable connectivity and addressing maintenance and cybersecurity challenges. The event information places it in Ortigas, Philippines, on Thursday 16 November, from 2:00 p.m. to 4:00 p.m. Philippine Time; the invitation does not specify a year.

Organisers
U.S.–Philippines Joint Cybersecurity Working Group with APTelecom
Focus
Undersea cable resilience, infrastructure security, global connectivity and emerging submarine cable maintenance challenges
Speakers listed
Phillip Nervig, Economic Counselor, U.S. Embassy Manila; Eric Handa, CEO, APTelecom
Moderator listed
John Garrity, Chief of Party, USAID BEACON
Event information
Thursday 16 November, 2:00–4:00 p.m. Philippine Time, Ortigas, Philippines

This entry summarises an event invitation provided by the portfolio owner. It does not verify attendance, completion, registration or a certificate of participation. The original announcement did not identify its year.

EUROPEAN MARKETS / INTERNATIONAL COMMERCE

Eve Curls: international Shopify Markets architecture.

A multi-European-market experience structured within one Shopify ecosystem, spanning the UK, Switzerland, the Netherlands, Italy, France and Spain. The engineering challenge involved six connected Shopify Markets settings (Currency, Catalogs, Discounts, Online Store/Theme, Checkout and Accounts, and Domain/Language), while avoiding a separate store for every country.

PUBLISHED WORK / HOMEPAGE UI/UX

A custom Shopify homepage beyond the base theme

For a live Australian ecommerce storefront, I contributed to a bespoke homepage experience implemented as modular Shopify theme sections alongside an established theme. The published layout supports customers discovering products by occasion, exploring category ranges, seeing promotions, understanding delivery, and building brand trust.

Challenge & approach

A generic homepage did not provide the preferred content hierarchy for product discovery and brand storytelling. The design uses a prominent media hero, guided shopping entry points, featured ranges, promotional content and service reassurance to create a more intentional customer journey.

Implementation & maintainability

The live homepage is organised into independently configurable theme sections. This gives content editors flexibility to adjust modules without redesigning the entire page. The case study describes the architecture and UX principles, not proprietary Liquid or actual storefront settings.

Responsive commerce experience

Mobile-first review areas include hero readability, navigation clarity, product grouping, call-to-action hierarchy, image loading and spacing between content modules.

Publication & next measurements

The custom homepage has been published. Conversion, engagement, Core Web Vitals and navigation behaviour should be measured against a defined baseline before any uplift is claimed.

Responsive experience review

The comparison below documents interface goals and review checkpoints. It is not a measured before-and-after experiment.

DESKTOP / WIDE VIEW

Discovery and storytelling

A media-led hero presents the primary proposition, followed by guided shopping, collection exploration and reassurance sections. Review large-screen content hierarchy, CTA visibility, hero media rendering and spacing.

View published homepage
MOBILE / NARROW VIEW

Focused purchase journey

Prioritise legible hero text, touch-friendly actions, compact product discovery, image crops and section transitions. Validate these behaviours on physical devices before claiming visual outcomes.

Review live mobile layout

Measurements to validate

Baseline and post-publication measurements are not yet available for this case study. Evaluate mobile and desktop Core Web Vitals (LCP, INP, CLS), entry-page engagement, collection click-through, add-to-cart rate and purchase conversion for comparable periods. Segment by device and exclude anomalous traffic.

Screenshots are pending a successful capture of the actual published website; no mock-up is presented as a production screenshot.

Post-launch review, October 2026

After publication I reviewed the homepage code and loaded the public page in a headless browser at desktop and mobile sizes. The findings below are next steps. None of these fixes has been applied or measured yet, and single test runs are a guide, not field data. Before changing the live page, each finding should be confirmed with Microsoft Clarity and Hotjar heatmaps and session recordings from real visitors.

  • First screen on mobile. A marketing popup covered the hero within seconds, and on narrow screens the headline and main button sat below the first screen. Next step: delay or shrink the popup on mobile, and overlay the headline on the hero media.
  • Carousel and loading. Later slides were lazy-loaded, so when the carousel advanced the browser recorded a much later Largest Contentful Paint. Next step: load later slides at low priority, or fetch the next slide while the current one shows.
  • Returning visitors. Coming back from a product reset the page to the top, which is costly on a long mobile page. Next step: keep the visitor's scroll position.
  • Script weight. Animation libraries loaded on every page rather than only where they are used. Next step: load them per page, then review third-party app scripts.
  • Content. Several sections explained the same ranges, two products shared one photo, a “most popular” badge appeared twice, and one sentence ended mid-thought. Next step: merge overlapping sections and correct the copy.
  • What worked. Near-zero layout shift, a pause control for the moving hero, review data that updates live, and well-documented, editor-friendly sections.

Brand typography without a font app

The brand heading typeface was served by a font app that forced it onto every H1 and H2, and the theme's fluid heading scale produced inconsistent sizes. I moved the licensed font into Shopify Files and loaded it from a theme snippet, then removed the app.

  • Self-hosted. The WOFF2 is preloaded and declared with font-display: swap, so headings show in a fallback font at once and switch when the brand font arrives.
  • Sized for a Light-only face. The serif only exists in Light and read too large, so H1 moved from 32px to 24px and H2 from 24px to 20px, on a fixed 4/8px grid instead of fluid scaling.
  • Paired fonts. H3 uses the secondary sans at the same 20px as H2, so the levels differ by typeface and weight, not size.
  • Thickened, not faked. A 0.6px text stroke makes the Light serif read slightly heavier without a browser-generated bold. It is one variable, ready to remove if a heavier weight is added.
  • Readable everywhere. Headings the theme sizes down fall back to the sans, section titles show at the full brand H2, and testing was done on a computer without the font installed.

Licence confirmed for web use. The public code example uses a placeholder font name; no font files are published.

All descriptions are generalised from the published storefront structure. This portfolio does not mirror or license the client's production theme, brand assets or configuration.

03 / RESPONSIBILITIES & DELIVERABLES

How the work translates into results

These examples describe the type of work completed and the deliverables produced. They do not imply client-specific commercial results or independently audited performance improvements.

Shopify storefront maintenance

Responsibilities: Diagnose template, navigation, cart, and mobile UI issues; review Liquid and CSS; validate fixes against responsive layouts.

Deliverables: Documented theme changes, resolved interface defects, structured product components, and maintainable storefront enhancements.

B2B workflow architecture

Responsibilities: Translate aggregate order-weight requirements into eligibility logic and Shopify-native catalogue and automation patterns.

Deliverables: Weight-based workflow designs, notification logic, and an independently authored interactive portfolio simulator using fictional data.

View example

Fulfilment integration engineering

Responsibilities: Connect event-driven warehouse and storefront processes; investigate webhook authentication, tracking updates, and delivery-status mapping.

Deliverables: Integration architecture, normalised status-handling patterns, diagnostics, and workflow documentation without disclosing production credentials.

Analytics and commerce operations

Responsibilities: Compare Shopify and GA4 reporting, inspect GTM and tracking paths, support catalogue audits, SEO, and product-content governance.

Deliverables: Discrepancy analyses, diagnostic findings, audit recommendations, and structured reporting approaches.

04 / SHOPIFY STORES

Store experience references

The following stores were supplied as examples of sites I have helped build, manage or optimise. These links are self-reported experience references. Specific roles, contributions, employment dates and outcomes for each store need supporting project records before they can be attributed to a named business.

These are portfolio references, not endorsements from the businesses listed. No claim of current employment or ownership is implied.