iprice.my

When I first walked into iPrice Ventures, I quickly realized that the biggest bottlenecks were not about market fit. They lived inside a handful of stubborn technical issues that slowed down both our users and our internal teams. Over my time working on the platform, my mission became turning those pain points into concrete business wins by improving stability, automating workflows, and refining the user experience.

Here are the core technical improvements I tackled during this project:

1. Stabilizing the Australian launch
   The initial rollout for Australia kept crashing because a few critical bugs threw the site offline. I dug into the code, identified the most common failure points, and rewrote the error handling logic. This change cut downtime by around fifty percent. The trade off was that we spent sprint capacity on debugging instead of building a fresh interface, but it was absolutely worth it. The product team could finally ship new features without fearing another outage, leading to much faster iteration cycles.
2. Automating localization validation
   Each market required its own set of localized pages with proper hreflang tags, and our search engine optimization team was drowning in manual checks while errors still slipped through. I built a Python crawler that walks every public link, verifies the HTTP status, and validates the hreflang markup. I set the script to run on our continuous integration server so we did not have to provision new infrastructure. Accuracy of localization doubled, and the bulk of manual tickets disappeared. The only limitation is that it cannot see internal staging environments, so those still require a separate verification step.
3. Adding a peeled off coupon animation
   Coupons drive conversion, but users often skim past them. To fix this, I recently created a lightweight CSS keyframe animation that peels the coupon open on hover or tap, revealing the code underneath. This visual hook forces a brief pause and prompts interaction. After launch, redemption rates jumped significantly across all markets. Keeping the animation tiny meant it did not hurt load times, which was an acceptable trade off for the added front end complexity and the massive engagement lift.
4. Streamlining coupon management in OctoberCMS
   Our editors were previously stuck with a flat list of coupons, which often led to the wrong promotion appearing on product pages. Within OctoberCMS, I built a native plugin that lets editors tag coupons by type and assign a priority order. This improvement boosted the correctness of promotional displays dramatically, slashing shopper confusion and cutting support tickets. Choosing a native plugin over an external service kept everything in one place, even though it required writing a bit more custom PHP.

All of these initiatives share the exact same principle. I wanted to eliminate the friction that slows users or internal teams down. By automating validation, tightening content management workflows, and sprinkling a bit of visual delight into the interface, I turned hidden inefficiencies into measurable growth. I still run the Python crawler nightly, keep the coupon animation live, and rely on the content management categorization every single day. It is solid proof that solving the right technical problems can have a lasting business impact.