Hosted platform or custom build?
A hosted store can be a practical starting point for a standard catalogue and checkout. Consider custom development when pricing, approvals, fulfilment or integration requirements do not fit supported configuration. Test your actual B2B ordering and customer-specific pricing needs against the current plan; features change, so broad claims about what a platform cannot do become outdated.
Confirm local payment support
Check FPX, DuitNow, cards and relevant e-wallets with the chosen gateway and platform. Confirm merchant eligibility, onboarding, refunds, settlement and charges. Platform transaction fees and gateway processing fees may be separate. A custom store also has payment costs. Use the provider's current written terms when comparing options.
Plan fulfilment before launch
Decide which system owns stock and when an order reserves it. Test the final available unit, a failed payment and two simultaneous orders. Map picking, partial shipments, cancellations, returns and stock corrections. For several outlets, define transfer records and who may change quantities. Staff should see unresolved exceptions rather than silently losing them.
Keep tax and invoice decisions explicit
SST treatment and MyInvois requirements are separate matters. Have your accountant confirm what applies to the business, then translate that into product, customer and invoice rules. Do not configure every retailer from one assumed tax threshold. Record invoice identifiers and correction steps so the finance team can reconcile orders.
Compare the cost of operating the store
Include subscriptions, extensions, payment charges, content updates, integrations and support over the same period. Ask who owns product data, media, accounts and domain access. Before launch, test a full refund, a duplicate payment callback and a failed stock update. The team's recovery process matters as much as the successful checkout.