Start with the business flow.
Before choosing a component or API, I want to understand what the customer, merchant and connected systems are actually trying to do.
About
I'm Gilriel Rodriguez, a Shopify developer in the Philippines with 3+ years focused on Shopify and more than 7 years in professional web development.
I currently work across a 10-store Shopify ecosystem—9 D2C storefronts and 1 B2B storefront—connected through shared ERP, PIM, catalog, inventory and commerce workflows.
Alongside development and integrations, I collaborate with marketing on SEO, promotions, merchandising and conversion-focused customer journeys, so I tend to think from interface through system and business outcome.

Background
I started with PHP, SQL, JavaScript and business systems—records, workflows, permissions and operational rules—before moving deeper into eCommerce.
That foundation is why I treat Shopify as a commerce system, not only a theme layer. I follow the data, system boundaries and user states behind the storefront. Independent product experiments live separately under RXR Code.
How I work
Patterns that guide the projects and Lab.
Before choosing a component or API, I want to understand what the customer, merchant and connected systems are actually trying to do.
Complexity can live behind the interface. The customer-facing experience should stay clear, fast and predictable.
ERP, APIs and platform connections affect the experience just as much as the visible frontend, so they need deliberate states and failure handling.
When production source must stay private, I prefer showing safe experiments, architecture and evidence instead of vague claims.