Shopify vs Custom Web: Best Choice for SG Retailers

1. Recurring Cost: S$39/mo vs S$18k Build

Shopify Basic is S$39/month in Singapore, and Plus jumps to S$2,300/month. There is zero upfront for the SaaS route, but the real expense is transactional: 2% surcharge on every order routed to HitPay, Stripe, or any gateway outside Shopify Payments. A mid-range SG agency build — Laravel or Next.js storefront on AWS ap-southeast-1 — runs S$18,000 to S$60,000, plus a S$600 to S$1,500 monthly retainer for hosting, security patches, and feature requests. Three-year totals: Shopify at ~S$1.4k + 2% of GMV versus a typical S$40k build + S$36k retainer = S$76k fixed. The fee drag only overtakes that fixed cost somewhere past S$3.7M in cumulative orders, which is why Shopify wins for volume under ~S$1.2M annually and custom wins above it.

2. Payment Stack: PayNow, Atome, and GrabPay

Shopify Payments handles Visa, Mastercard, Amex, and Apple Pay, but it does not render a PayNow QR at checkout natively. SG retailers either route to a plugin like PayNow Gateway or fall back to manual bank transfer confirmation — which generates failed payments and after-hours reconciliation work. A custom checkout wired to HitPay or Stripe’s SG instance can unify PayNow, Atome BNPL, GrabPay, and ShopBack cashback into one synchronous flow, with HitPay charging roughly 0.8–1.2% per transaction versus Shopify’s 2% third-party fee plus gateway fees. If you run flash sales or Sunday drops, the custom flow also lets you split settlement across DBS, OCBC, and UOB accounts without touching dashboard settings.

3. Delivery and Warehouse Integration Reality

Singapore retail logistics runs on Ninja Van, J&T Express, SingPost SMARTpac, Lalamove SG, and Teleport. Shopify’s app marketplace offers Ninja Van and J&T connectors, but they push order data one-way and force manual reconciliation when a courier marks a parcel failed or reroutes it. Custom builds use Ninja Van’s OpenAPI and Teleport’s API for two-way inventory sync, automatic SLA-based courier switching, and address-level delivery surcharges — essential for bulky goods sent to Sentosa, Jurong Island, or restricted industrial zones. Multi-warehouse retailers also hit a Shopify ceiling: native rate calculation does not handle zone-based surcharges or cold-chain flags without third-party apps like ShipStream working overtime.

4. Front-End Speed Versus Template Speed

Default Shopify themes consistently test LCP at 3.0–4.5 seconds from SG connections. The online store 2.0 framework with Dawn, image compression via TinyIMG, and a CDN can drag that under 2.5 seconds, but script-heavy apps for reviews, chat, and upsells routinely inflate Cumulative Layout Shift back above Google’s thresholds. A custom Next.js storefront on AWS ap-southeast-1 with Cloudflare caching and ISR can hold LCP under 1.8 seconds while running A/B tests and dynamic checkout buttons. Core Web Vitals matter beyond rankings: Shopee and TikTok Shop ads funnel traffic to your domain, and a 1-second LCP improvement correlates with a measurable drop in pre-checkout bounces on mobile.

5. PDPA, Data Ownership, and Exit Costs

PDPA compliance is not optional for SG retailers, and the two routes differ on residency. Shopify’s data processing addendum covers the legal paperwork, but customer profiles, order histories, and abandoned-cart data flow to Shopify’s subprocessors in Canada and the US. Custom builds on AWS ap-southeast-1 keep all personal data within Singapore, a decisive factor for retailers selling to government-linked entities or health supplement buyers. Exit cost is the blind spot: Shopify’s export gives you CSV order and customer files, but discount rules, customer segments, and app-harvested analytics die with the subscription. A custom system exports the full database schema and lets you migrate to any future provider without rebuilding logic.