Magento developer for Australia stores

Afterpay ships an official Magento 2 module via the Magento Marketplace and via Composer (`afterpay/module-afterpay`). Setup is three steps: (1) create an Afterpay merchant account at portal.afterpay.com and grab your Merchant ID + secret key, (2) install the module + configure under Stores → Config → Sales → Payment Methods → Afterpay, (3) test in sandbox before flipping production. The module supports product page messaging (the “4 instalments of A$X” widget), cart messaging, and checkout. Afterpay was founded in Sydney in 2014, it’s the de-facto BNPL rail for AU consumers, particularly fashion / DTC / lifestyle. We’ve integrated it on 30+ AU stores.

Since 1 July 2018, imports under A$1,000 are subject to GST when sold to AU consumers by overseas merchants, previously they were GST-free. If you’re an international seller selling into AU, you must register for GST under the OSR (overseas-supplier registration) scheme once your AU sales exceed A$75,000 in a 12-month period. In Magento, this is configured via Stores → Config → Sales → Tax: set up an AU-specific tax zone, apply 10% GST to all goods + services, and gate B2B orders by ABN to skip GST where appropriate. We’ll wire the tax-class mapping, ABN-based exemption flows, and OSR-compliant invoicing per ATO requirements.

ABN (Australian Business Number) validation is critical for B2B Magento stores so you can skip GST on tax-invoice flows where the buyer is a registered business. Two approaches: (1) Live lookup via the ABR (Australian Business Register) web service, we wire an extension or custom module that calls abr.business.gov.au/json/AbnDetails.aspx at registration / checkout, validates the ABN, and stores the verified entity name. (2) Offline checksum validation using the ABN modulo-89 algorithm for instant client-side validation before the live lookup. We typically combine both: instant feedback on the form, live verification before order placement. Combine with a customer attribute `is_abn_verified` and a customer-group rule to expose B2B catalogues / Net-30 terms only to verified ABNs.

Stripe AU, global rail, best for international DTC stores already on Stripe elsewhere. Lowest international card fees, native Apple Pay / Google Pay, deep developer ecosystem. Settlement to AU bank in 2 business days. eWAY, Australian-founded (now part of Global Payments), best for established AU retailers wanting AU-bank merchant services. Strong AMEX support, mature recurring-billing, AU-based phone support. Pin Payments, Australian-owned, Sydney-based, simplest pricing model (one flat rate, no monthly fees). Best for AU-only SMB stores. Recommendation: Stripe AU for DTC scale, eWAY for B2B + AMEX-heavy, Pin Payments for AU-only SMB. We’ve wired all three across 40+ AU Magento stores.

Yes, BPAY is the standard for B2B Magento stores in Australia, particularly for trading-account / Net-30 customers who prefer to pay via internet banking rather than card. There’s no off-the-shelf Magento BPAY module from BPAY itself, but two community modules + a custom approach work well: (1) generate a unique CRN (customer reference number) per order, (2) display the BPAY biller code (yours) + CRN on the invoice + order-confirmation email + customer order history, (3) reconcile incoming BPAY payments daily via your bank’s BPAY remittance file (CSV import to a custom Magento module). For high-volume merchants, integrate with NAB Transact or Westpac PayWay which both offer real-time BPAY APIs. Combine with ABN-gated customer groups so only verified B2B accounts see BPAY at checkout.

Australia Post ships an official Magento 2 module (free) that wires their MyPost Business API for ParcelPost (regular), Express Post (next-day metro), and StarTrack (B2B / large-parcel / regional). The module handles real-time rate quoting at checkout, label printing, manifesting, and tracking events. StarTrack is Australia Post’s premium B2B / regional service, same module covers it. For multi-warehouse stores (e.g. Sydney + Melbourne), we wire ShipperHQ on top so the cart picks the closest warehouse based on postcode + product availability + carrier-rate-shopping. We also build custom routing rules for rural / NT / TAS where Australia Post has different SLAs and StarTrack is often more cost-effective for parcels > 5kg.

Rural Australia, Northern Territory, and Tasmania need special handling because (a) Australia Post SLAs are 5-10 business days vs 1-3 for capital cities, (b) some couriers (Couriers Please) don’t deliver beyond metro areas, and (c) freight to remote NT / TAS often costs 3-5× metro rates. Our standard build: (1) postcode-based shipping zones in Magento with separate rate tables for metro / regional / remote, (2) carrier fallback chain (Australia Post Express → StarTrack → Sendle → Aramex) configured via ShipperHQ, (3) delivery-time messaging on PDP + cart so customers in remote NT see “5-10 business days” up-front, (4) optional freight surcharge for parcels > 5 kg to NT / remote TAS, (5) signature on delivery default for rural to reduce lost-parcel claims.

The Privacy Act 1988 + Australian Privacy Principles (APPs) apply to any business with annual turnover > A$3M (and to all health-data / credit-data businesses regardless of size). For Magento stores: (1) cookie consent banner (we wire CookieYes or CookieFirst with AU-specific text), (2) privacy policy covering APP 1 (open and transparent), APP 5 (notification), APP 6 (use / disclosure), APP 12 (access), APP 13 (correction), (3) opt-out flows for marketing / SMS (Spam Act 2003), (4) data-subject-access requests (DSAR) automation, we build an admin tool that exports a customer’s data on request within the 30-day APP-12 deadline, (5) Notifiable Data Breaches scheme, if you’re breached, you have 30 days to notify the OAIC + affected individuals. We configure logging + monitoring so a breach can actually be detected, not just notified after the fact.

Adobe Commerce Cloud (Sydney region), managed Magento, Adobe handles patches / upgrades / Fastly CDN / New Relic. Best for stores doing > A$5M/yr that want zero infra burden. Costs A$1,500, A$5,000+/month depending on tier. Lock-in to Adobe’s deploy flow (ECE-Tools). Self-host on AWS Sydney (or Cloudways Sydney / MyHost / BigCloud), cheaper (A$200, A$1,500/month), full control, can use any Magento version / extension. Best for stores doing < A$5M/yr or technical teams that want flexibility. Trade-off: you (or we) own patches / upgrades / CDN / monitoring. Recommendation: under A$3M/yr revenue, AWS Sydney + Cloudways for managed-VPS comfort. Over A$5M/yr, Adobe Commerce Cloud Sydney is worth the price for the SLA + Fastly + auto-scaling. We’ve migrated stores both directions.

Real overlap is 4-6 hours per day between IST (India Standard Time, UTC+5:30) and AEST (Australian Eastern Standard Time, UTC+10), or AEDT (UTC+11) during daylight saving. Specifically: 1 PM, 7 PM IST = 5:30 PM, 11:30 PM AEST (your business afternoon / early evening, our late afternoon / evening). We schedule daily stand-ups, calls, screen-shares in this window. For early-morning Sydney calls (8-10 AM AEST = 3:30-5:30 AM IST), we offer that on launch nights or for critical incidents. Async tools we use: Loom for code walkthroughs, written end-of-day status notes (sent before our 7 PM IST = your 11:30 PM AEST), Notion project board kept current. WA / NT (UTC+8) overlap is 2 hours longer; SA / NT during AEST is similar to east-coast.

Common Shopify / BigCommerce → Magento migration path for AU stores: (1) data export, products, customers, orders, blog posts via Shopify’s API or BigCommerce’s API (we use Cart2Cart for bulk + custom scripts for edge-cases), (2) URL preservation, map old `/products/` → new `/.html` via 301 redirects so SEO doesn’t drop, (3) payment-rail re-wire, Shopify Payments → Stripe AU + Afterpay + Zip (we install + configure all three), (4) tax + GST, Shopify auto-calculates AU GST; on Magento we wire ATO rate tables + ABN-based exemption, (5) app → extension swap, e.g. Klaviyo → Mailchimp/Klaviyo for Magento, Yotpo → Yotpo for Magento, ReCharge → Aheadworks Subscription. Typical timeline: 6-10 weeks for a 5k-product Shopify store with 50k orders of history. AU-specific gotchas: GST low-value-threshold logic, AU postcode validation, ParcelPoint pickup-point integration if Shopify had it.

Yes, Hyvä is the right choice for any AU fashion / DTC store launching or replatforming in 2026. Three reasons: (1) Speed, Hyvä loads 5-10× faster than Luma. AU mobile networks have slightly higher latency on rural routes, so the speed gain is more visible than in metro-only Shopify benchmarks. (2) Afterpay / Zip messaging, Hyvä has clean Tailwind components for the “4 instalments of A$X” widget on PDP / cart / checkout, much easier to style than Luma’s KnockoutJS. (3) Conversion, AU fashion DTC stores are mobile-first (60-75% mobile traffic). Hyvä’s Lighthouse 95+ + green Core Web Vitals = better mobile rankings = lower CAC. We’ve migrated 8 AU fashion / DTC stores to Hyvä, average conversion uplift 12-22% in the 90 days post-launch. See our /hyva-theme-development-service page for details.