Choose the commerce platform around the business it must run. A convincing storefront demonstration can leave difficult questions unanswered: who owns availability, how trade prices are applied, what happens to a partial refund and which team repairs the connection. ERP-connected platform selection brings those questions into the decision before a contract is signed.
This guide provides an evaluation method for Australian businesses. It is not a universal platform ranking, a client case study or a pricing quotation. Capabilities and commercial terms change; verify the proposed plan, connector and extensions in a demonstration that matches your scope.
Define the decision and the constraints
Start with the reason for the change. Identify the operating failures, unsupported customer journeys or constraints that the current platform cannot reasonably address. Distinguish these from problems caused by poor product data, unclear ownership or an integration that could be repaired.
Record the ERP and its customisations, the channels involved, the order lifecycle, current contracts and the people who will maintain the result. Separate mandatory requirements from preferences. A mandatory requirement should have an observable acceptance check and a business owner.
Agree who owns each kind of data
Create an ownership register for products, variants, prices, customers, available stock, orders, fulfilments and refunds. An owner may be the ERP, commerce platform or another system, depending on the field and process. Specify direction, matching key, allowed delay and conflict handling.
For NetSuite, investigate subsidiaries, locations, item structures, workflows and custom records that affect a connection. For Business Central, investigate companies, items, variants, units of measure, extensions and posting rules. The ERP name alone is not a complete integration requirement.
Use gates before a weighted score
A scoring matrix is useful only after essential requirements have been tested. Label each requirement demonstrated, supported with additional work, unsupported or not yet verified. A vendor presentation is not equivalent to a completed acceptance check.
Ask candidates to demonstrate the same representative process. For trade commerce, this might include an approved account, account-specific pricing, a purchase order reference, a partial shipment and a refund. Use synthetic data and record which applications or extensions are doing the work.
After the mandatory gates, agree relative importance for operational fit, customer experience, maintainability, integration coverage and total cost. Record the evidence and unresolved assumptions beside each judgement. Do not let a high score for visual design cancel out a failed financial control.
Compare platform approaches without assuming a winner
Shopify and Shopify Plus: evaluate the managed storefront and application ecosystem against your B2B, checkout, data and operating requirements. Shopify publishes plan-specific B2B capabilities. Check the current feature table and demonstrate the features you need; do not assume that any ERP connection requires Plus.
BigCommerce: demonstrate the proposed storefront, trade-account experience, catalogue structure and ERP handoffs using the actual edition and applications in the proposal. Identify which business rules are native and which belong to middleware or custom code.
Adobe Commerce: evaluate the control required over catalogue, pricing and customer journeys alongside the responsibility for extensions, hosting, upgrades and testing. Flexibility is useful only when the business can maintain the resulting implementation.
Sana Commerce: test the proposed ERP-connected approach against the supported ERP version, extensions and required journeys. Establish what the customer experience does when the ERP or connection is unavailable.
commercetools: evaluate composable capabilities as an architecture and operating-model decision. Define who builds and owns the storefront, search, content, checkout and integration responsibilities. Treat each additional service as a dependency with a cost and recovery requirement.
Prove the connector covers the whole lifecycle
Compare a native connector, an integration platform and a custom connection against the required records and exceptions. List mappings, supported actions, permissions, failure handling and the owner of future upgrades. A connector being available does not prove it covers your custom process.
Microsoft documents a Shopify connector for Business Central. Check its supported capabilities and configuration against your actual companies, products, inventory and posting process before adding middleware. Test the uncovered requirements rather than replacing a suitable native connection by default.
Include cancellations, split fulfilment, partial refunds, duplicate notifications, stale inventory and interrupted writes in the evaluation. Ask how missing records are found and recovered. Document which responsibilities remain with the ERP, platform provider, implementation team and business operator.
Compare the full cost on the same basis
Use the same scope and planning horizon for every proposal. Separate initial discovery, implementation, data preparation, integration and migration from recurring platform, application, hosting, support and maintenance costs. Include testing environments and the internal effort required to operate the solution.
Record variable charges and the assumptions that drive them. Include change requests, extension upgrades and connector maintenance where relevant. Show exclusions explicitly so an apparently cheaper proposal is not being compared with a broader one. Use current written quotations; there is no reliable universal project price.
Plan migration and search continuity
Inventory existing URLs, products, customers, consent records and open operational work. Map valuable URLs to relevant destinations, retain useful page content and validate redirects. Changing the storefront should not quietly break an established service or product URL.
Agree how open orders and refunds will be handled across the cutover. Specify the final data reconciliation, the point at which new orders move, the owner of each decision and the conditions for rollback. Test these decisions before the launch window.
Make Australian operating requirements testable
Use representative address formats, including postcodes with leading zeroes. Agree displayed and recorded tax treatment with the business and its advisers. Test local payment and fulfilment handoffs, business-timezone cutoffs and the location rules used for collection or delivery.
Document regional and privacy requirements for each vendor and service rather than inferring them from an Australian sales presence. These checks should result in an explicit decision, an open question or an exclusion in the proposal.
What the final recommendation should contain
Retain the requirement register, evidence from demonstrations, the ownership map, integration gaps, comparable cost model, migration plan and unresolved risks. Explain why the recommended option fits, what it does not solve and which assumptions could change the recommendation.
An illustrative decision might favour a simpler storefront when the ERP can remain authoritative and the required journeys are covered. Another might justify a composable approach because a mandatory journey cannot be supported adequately otherwise. The conclusion follows the evidence, rather than a preference for a particular vendor.
Discuss ERP-connected eCommerce consultancy and platform selection