A proposed approach to explore with your business. Scope, implementation and outcomes depend on the engagement.
Plan composable commerce with a connected ERP
Ideal for
Australian DTC brands that have outgrown Shopify/Magento and need composable architecture for international expansion.
The situation
A fast-growing Australian DTC brand scaling beyond $10M needing multi-currency, multi-region, and subscriptions
Shopify and Magento serve well to a point, but international DTC at scale introduces complexity. Region-specific catalogues where products are approved in some markets but not others due to ingredient regulations. Multi-currency pricing beyond simple conversion - each market needs psychological price points, local tax handling, and local payment methods. Subscription models needing tight ERP integration across multiple currencies and subsidiaries.
Performance is another requirement to validate. Establish the actual mobile traffic mix and measure real-user performance before changing platforms. Frontend code, images, third-party scripts and network conditions can all affect the experience; architecture alone does not establish a conversion gain.
The approach
Commerce Engine: CommerceTools
MACH-architecture platform. Each country is a CommerceTools "store" with its own product selection, pricing, tax categories, and shipping methods. A single product record can be available in 5 markets with 5 different prices without duplication. Subscription engine built as a CT API extension.
Frontend: Next.js on Vercel
Headless Next.js with ISR (60-second revalidation). Edge functions for personalisation (returning customer vs new, region detection, A/B tests). Sub-400ms TTFB globally.
Celigo Integration Layer
Order sync (CT to NetSuite): Correct subsidiary mapping per market, currency conversion via NetSuite exchange rate tables, tax code translation, subscription reference tracking.
Inventory sync: Multi-warehouse per CT channel with safety stock thresholds per market.
Product sync: Per-market pricing from NetSuite price levels to CT embedded prices.
Customer sync to Klaviyo: Market-segmented email marketing.
Payment reconciliation: Stripe multi-currency settlements matched to NetSuite revenue per subsidiary.
Expected outcomes
The aim is to separate commerce capabilities while retaining agreed ERP ownership. Performance, conversion and market-launch effort depend on implementation, third-party services and operating complexity.
Measure real-user performance, checkout errors, conversion by device and the work required for each launch. Compare equivalent traffic and scope before attributing an improvement to the architecture.