Skip to content

Domain, hosting, code and data — in your name, in writing

jagaweb

High-Performance E-Commerce Web Solutions

Robust e-commerce platforms with volumetric shipping calculations and fast checkouts.

Hands taping a cardboard parcel closed beside an open laptop

We build e-commerce stores that actually convert. We implement PayPal Orders v2, reliable Resend email dispatch, and volumetric weight calculation for Sabah/Sarawak, with a focus on fast checkout performance.

Malaysians don't all pay the same way

FPX bank transfers, DuitNow QR, cards, and increasingly a checkout that never leaves a chat app: a Malaysian store that only accepts cards is quietly excluding shoppers who trust their own banking app more than they trust typing a 16-digit number into a stranger's site. Billplz and Curlec are built around that FPX-first reality and tend to be cheaper for a Malaysia-only customer base; Stripe is stronger once orders start coming from outside Malaysia but weaker on local rails unless it's paired with a DuitNow or FPX option alongside it. The right combination depends on where the customers actually are and how they already pay for everything else online, not on which gateway has the newest dashboard.

Shipping is a fulfillment problem wearing a shipping costume

Rate calculation is the part every store budgets for. The part that gets skipped is what happens after checkout: pushing the order to J&T, Ninja Van or Pos Laju automatically, syncing tracking updates back into the order record, and notifying the customer without someone on staff manually copying consignment numbers into a spreadsheet. Sabah and Sarawak make this harder, and not only because of volumetric weight, which is a rate problem — transit times and courier coverage genuinely differ there, and a storefront that quotes semenanjung delivery windows to an East Malaysia address is generating a support ticket before the order has even shipped.

Shopee and Lazada aren't a substitute for your own storefront

Marketplaces bring buyers who are already primed to purchase and already trust the platform's own buyer protection, and for a lot of Malaysian sellers that's the fastest route to a first sale. What a marketplace listing doesn't give a seller is the customer's contact details, the ability to retarget them without paying the platform again, or control over how the product sits next to a competitor's listing one row down. An owned storefront is slower to get traffic to, but it's the only channel where the customer relationship, the order data and the margin actually belong to the seller. Most sellers need both; treating the marketplace as the whole strategy means renting a customer list from someone who can change the terms.

Most of your checkout traffic is on mobile data, not fibre

A checkout tested on office wifi and a laptop looks nothing like the same page loading on a mid-range phone over mobile data on a bus. Every unnecessary script, every gateway redirect that adds a few seconds, every one-time password that has to be copied by hand from an SMS instead of read automatically, is a place a real customer gives up and doesn't come back. It's why Daralwahi, an online bookstore we built, runs PayPal's Orders v2 flow with its own Express Smart Buttons rather than a generic hosted redirect, and confirms every order through a dedicated transactional email service instead of hoping the store's own outgoing mail doesn't get flagged as spam.

SST changed what a landed price means online

A cart that calculates SST only on the product price can quote a landed total that turns out wrong once low-value goods sales tax and import handling are factored in on cross-border items. That matters less for a Malaysia-based store selling Malaysia-based stock, but it matters the moment a store drop-ships or brings in inventory from overseas suppliers, and getting the sequencing wrong either eats the margin quietly or shows a customer a price that doesn't match what they're actually charged at the door. Working out where that calculation happens in the checkout flow is a scoping question worth raising with a developer before launch, not a support ticket to file after the first complaint.

WhatsApp