If you are researching an oscommerce website for an Australian business, you may be trying to answer one of two questions: should you build a new store with osCommerce, or should you modernise an existing store that has been running for years? Both situations need careful assessment. osCommerce remains an active open-source ecommerce platform, but the condition of an individual website depends heavily on its version, customisations, hosting, integrations, security practices and maintenance history. Therefore, the platform name alone does not tell you whether a particular store is modern, outdated or suitable for future growth.
From a practical ecommerce development perspective, this distinction matters. A well-maintained store with documented integrations can be far easier to manage than a heavily modified installation that nobody wants to update because one change could break checkout. Consequently, Australian businesses should evaluate osCommerce as a complete operating system for online sales rather than simply judging the appearance of the storefront.
What Is an osCommerce Website?
An osCommerce website is an online store built on the open-source osCommerce ecommerce platform. It gives a business control over its storefront, catalogue, checkout, integrations and hosting environment. For Australian retailers, its suitability depends on version, maintenance quality, security, payment and shipping integrations, and ongoing development capability.
Table of Contents
- What osCommerce is today
- How an osCommerce website works
- Why Australian businesses still use osCommerce
- When osCommerce is a good fit
- When another platform may be better
- Legacy osCommerce versus osCommerce v4
- Australian ecommerce requirements
- Security and maintenance
- Performance and Core Web Vitals
- SEO for an osCommerce store
- Payments, shipping and integrations
- Development and migration checklist
- Onshore versus offshore development
- Costs and budgeting
- People Also Ask
- Expert Q&A
- Conclusion
What Is osCommerce Today?
osCommerce is an open-source ecommerce platform with a long history in online retail. Importantly, businesses sometimes associate the name exclusively with older ecommerce sites created in the 2000s. That can create the impression that osCommerce itself is no longer being developed.
That assumption is inaccurate.
The official osCommerce website currently promotes osCommerce v4 as its active platform and provides current v4 documentation. The project describes the software as a free, open-source ecommerce shopping cart and states that the current platform is designed for modern server environments.
Businesses evaluating the platform can review the official osCommerce platform and current v4 information.
However, there is an important distinction between today’s osCommerce platform and an existing store installed many years ago.
An Australian business might have:
- an old osCommerce 2.x installation;
- a heavily customised legacy version;
- a partially upgraded store;
- an osCommerce v4 store;
- custom modules created by previous developers;
- payment integrations that are no longer maintained;
- a modern-looking theme sitting on an ageing backend.
Therefore, asking “Is osCommerce modern?” is less useful than asking “What version and architecture does our osCommerce website actually use?”
How an osCommerce Website Works
At its simplest, an oscommerce website combines a customer-facing shop with an administration system.
The storefront handles activities such as:
- browsing categories;
- searching products;
- viewing product information;
- adding products to a basket;
- creating customer accounts;
- entering delivery information;
- selecting shipping;
- making payments;
- receiving order confirmations.
Meanwhile, the administrative side manages functions such as:
- products;
- categories;
- pricing;
- inventory;
- orders;
- customers;
- promotions;
- shipping rules;
- payment settings;
- reporting;
- integrations.
The current osCommerce v4 documentation includes administration functions covering customers, orders, products, stock, product categories, sales channels and related ecommerce operations.
Because osCommerce is open source, developers can also modify and extend the platform.
That freedom is one of its greatest advantages. At the same time, it can create technical debt if custom development is performed without documentation or an upgrade strategy.
For example, imagine that an Australian wholesaler needs different pricing for trade customers. A developer could build custom logic around customer groups, pricing and account approval.
That may solve the immediate business requirement.
However, three years later another developer may need to upgrade the store. If the original work directly modified core files rather than using maintainable extensions, the upgrade becomes much more difficult.
Therefore, customisation should never be judged solely by whether it works today. Good development also considers whether someone can safely maintain it tomorrow.
Why Australian Businesses May Still Use an osCommerce Website
There are several legitimate reasons an Australian company may continue operating or consider developing an oscommerce website.
1. Control Over the Application
Open-source ecommerce gives businesses significant control over their software environment.
Depending on the hosting and implementation arrangement, your development team can control:
- application code;
- database;
- server configuration;
- integrations;
- checkout logic;
- catalogue structure;
- custom business workflows.
This differs from fully hosted SaaS ecommerce platforms, where certain parts of the infrastructure and application are controlled by the platform provider.
Greater control can be valuable when a business has unusual requirements.
However, greater control also creates greater responsibility.
Someone must maintain the code, monitor security, manage backups, test changes and maintain hosting.
2. Existing Investment
Many established retailers have invested substantial amounts in their ecommerce systems.
An existing osCommerce store may already connect to:
- accounting software;
- ERP systems;
- warehouses;
- freight providers;
- payment gateways;
- customer databases;
- product information systems;
- internal reporting tools.
Replacing the platform can therefore involve much more than redesigning a website.
Consequently, maintaining or modernising osCommerce may sometimes be economically sensible.
3. Custom Business Processes
Standard ecommerce platforms work well when a company’s requirements fit common retail patterns.
However, some Australian businesses have more specialised needs, including:
- wholesale ordering;
- account customers;
- dealer pricing;
- complex product configurations;
- unusual fulfilment workflows;
- multi-store operations;
- distributor integrations;
- specialised inventory rules.
In such cases, the flexibility of an open-source platform can be useful.
4. Ownership and Portability
Open-source ecommerce can reduce dependence on a single hosted platform.
Nevertheless, businesses should not confuse software ownership with complete independence.
You may still depend on:
- developers;
- hosting providers;
- extensions;
- payment gateways;
- APIs;
- freight integrations;
- third-party services.
Therefore, technical documentation and access management remain essential.
Is an osCommerce Website Right for a New Australian Store?
Possibly, but the decision should be based on business requirements rather than nostalgia or platform loyalty.
An oscommerce website may be worth considering when your organisation needs substantial customisation and has access to developers who understand the platform.
It may be especially relevant when:
- you already operate osCommerce;
- migration would be operationally complex;
- your business needs specialised workflows;
- you want open-source flexibility;
- you require custom integrations;
- your organisation can fund ongoing maintenance;
- you want greater control over infrastructure.
However, osCommerce may not be the most straightforward choice for every small business.
For example, a new retailer selling twenty standard products may value simplicity more than deep source-code control. In that situation, a managed ecommerce platform could reduce the technical workload.
The important point is that platform selection should start with requirements.
Do not begin with:
“Which ecommerce platform is best?”
Instead, determine:
- what must the store do?
- what systems must it integrate with?
- who will maintain it?
- how much custom development is required?
- how frequently will the business change?
- what is the realistic three-to-five-year cost?
Once those answers are available, platforms can be evaluated objectively.
Legacy osCommerce Website vs osCommerce v4
Australian businesses with older stores need particular care because “osCommerce” can describe systems from very different generations.
| Approach | Best suited to | Main advantage | Main concern |
| Maintain a legacy store temporarily | Stable stores preparing for replacement | Lower immediate disruption | Security and maintainability can deteriorate |
| Upgrade or rebuild on osCommerce v4 | Businesses wanting to remain with osCommerce | Modern platform while retaining osCommerce direction | Custom features may require rebuilding |
| Replatform to another system | Businesses whose requirements have changed substantially | Opportunity to simplify architecture | Data migration, SEO and integration risk |
| Hybrid staged migration | Complex stores that cannot move at once | Reduces operational change at one time | Requires strong project planning |
The wrong approach is often a never-ending series of emergency patches.
For instance, imagine checkout only works because a developer manually altered an obsolete module five years ago. Updating PHP then breaks the module, so PHP upgrades are postponed. Eventually, hosting becomes harder to maintain because the application depends on an old runtime.
This is how technical debt compounds.
Therefore, if your oscommerce website is several generations behind, first commission a technical audit rather than requesting another cosmetic redesign.
What Should an osCommerce Audit Examine?
A useful audit should identify:
- exact osCommerce version;
- PHP version;
- database version;
- installed extensions;
- modified core files;
- custom modules;
- payment gateway integration;
- shipping integrations;
- customer authentication;
- admin access controls;
- database size;
- product catalogue structure;
- cron jobs or background processes;
- APIs;
- email configuration;
- analytics;
- tracking scripts;
- SSL/TLS configuration;
- backup procedures;
- staging environment;
- deployment process;
- known errors;
- SEO configuration.
The result should be a prioritised technical roadmap.
Ideally, issues should be separated into:
Critical: security, checkout, payment or data risks.
High: unsupported software, major performance problems or unstable integrations.
Medium: maintainability and operational improvements.
Low: cosmetic or convenience improvements.
This prevents redesign work from consuming budget while more important infrastructure issues remain unresolved.
Australian Requirements for an osCommerce Website
An Australian ecommerce project involves more than displaying prices in Australian dollars.
Businesses should also consider consumer information, privacy, security, accessibility, taxation administration and operational expectations.
Australian Consumer Law
Australian online shoppers retain normal consumer rights when buying online. The ACCC states that businesses must follow applicable consumer laws, including consumer guarantees, and must not make false or misleading representations through websites, advertising or other channels.
Businesses can review the ACCC’s Australian online-shopping and consumer-rights guidance.
For an ecommerce website, this may affect how you present:
- product descriptions;
- refund information;
- warranties;
- delivery claims;
- product availability;
- promotional claims;
- pricing;
- customer service information.
For example, writing “NO REFUNDS UNDER ANY CIRCUMSTANCES” can create problems because business refund policies cannot remove applicable consumer guarantee rights.
This article provides general administrative and website-planning information, not legal advice. Businesses should have policies and legal wording reviewed by appropriately qualified Australian advisers where necessary.
Privacy Considerations
An ecommerce business may collect significant quantities of customer information, including:
- names;
- email addresses;
- addresses;
- telephone numbers;
- order history;
- account information;
- customer service communications.
Depending on the organisation and circumstances, Australian privacy obligations may apply.
The Office of the Australian Information Commissioner explains that the Australian Privacy Principles cover areas including collection, use, disclosure, security, access and correction of personal information.
The current OAIC Australian Privacy Principles guidance provides authoritative information for organisations assessing their obligations.
Importantly, do not assume every Australian organisation has identical Privacy Act obligations. Coverage can depend on organisational circumstances and activities.
Therefore, treat privacy review as a business administration and compliance task, with professional advice where required.
Security for an osCommerce Website
Security should be treated as an ongoing process rather than a launch-day task.
An ecommerce store is particularly sensitive because customers trust it with personal information and transactions.
A sensible security programme should include several layers.
Keep the Application Maintained
An old application becomes more difficult to defend when:
- core software is no longer updated;
- modules are abandoned;
- server software becomes unsupported;
- developers are afraid to change the system;
- nobody knows which files were customised.
Therefore, maintain an inventory of your technology stack.
Minimise Administrator Access
Not everyone needs full administrative privileges.
Use role-based permissions where supported and remove inactive accounts.
Additionally:
- use unique credentials;
- avoid shared admin accounts;
- use strong authentication;
- review administrator accounts regularly;
- restrict developer access after projects finish.
Protect Payments
Where possible, avoid unnecessarily handling sensitive card data directly within your application.
Australian businesses commonly integrate specialist payment providers so payment processing occurs through appropriate gateway infrastructure.
The exact implementation depends on your provider.
However, the key principle is simple: do not collect or store sensitive payment information merely because custom code makes it technically possible.
Maintain Backups
A backup should be useful for restoration, not simply exist somewhere on the same server.
Consider maintaining:
- database backups;
- uploaded product images;
- application code;
- configuration;
- integration settings;
- infrastructure documentation.
More importantly, test restoration.
A backup that has never been restored is an assumption rather than a proven recovery plan.
Use a Staging Environment
Changes should ideally be tested away from the live store.
A staging environment allows developers to test:
- upgrades;
- extensions;
- checkout changes;
- payment integrations;
- shipping rules;
- templates;
- PHP updates.
Without staging, every substantial change becomes a live experiment.
How to Improve osCommerce Website Performance
Performance matters because ecommerce users move rapidly between categories, search results, product pages, basket and checkout.
Slow responses create friction throughout that process.
Instead of installing a generic “speed optimisation” package, identify the actual bottleneck.
Server Response
Investigate:
- hosting resources;
- PHP configuration;
- database performance;
- inefficient queries;
- overloaded shared hosting;
- external API delays.
Images
Large product photography can dramatically increase page weight.
Therefore:
- resize images appropriately;
- compress them;
- use modern formats where practical;
- avoid loading oversized originals;
- lazy-load appropriate off-screen images.
JavaScript
Many stores accumulate scripts over time.
Examples include:
- analytics;
- advertising tags;
- chat applications;
- review tools;
- personalisation;
- popup systems;
- remarketing scripts.
Each tool may seem harmless individually. Together, they can make the page significantly heavier.
Therefore, periodically audit third-party scripts.
Database Health
Large legacy databases can contain years of:
- logs;
- abandoned carts;
- old sessions;
- obsolete tables;
- extension data.
Do not delete database content without understanding its purpose.
Instead, have a developer identify whether unnecessary data or poor indexing is affecting performance.
SEO for an osCommerce Website in Australia
Technical ecommerce SEO requires more than adding keywords to product descriptions.
A strong oscommerce website should provide search engines with a logical, crawlable structure.
Product URLs
Aim for stable, descriptive URLs where practical.
If URLs are changed during redevelopment, use appropriate redirects from important old URLs.
Otherwise, a redesign can unintentionally cause valuable indexed pages to disappear.
Page Titles
Each important category and product page should have a meaningful title.
Avoid hundreds of pages with titles such as:
“Product | My Store”
Instead, describe the actual product or category.
Meta Descriptions
Meta descriptions do not guarantee rankings. However, useful descriptions can help searchers understand the relevance of a page.
Therefore, write them for people rather than stuffing them with repeated keywords.
Category Architecture
Categories should reflect how shoppers search and browse.
For example, avoid creating dozens of near-identical category pages merely to target slight keyword variations.
Instead, build clear commercial categories supported by useful product content.
Duplicate Content
Ecommerce stores can create multiple URLs for very similar content through:
- filtering;
- sorting;
- pagination;
- search;
- tracking parameters;
- product variants.
Therefore, technical SEO should examine canonicalisation, crawl paths and indexation rules.
Structured Data
Where appropriate, structured data can help search engines understand products, prices, availability and other information.
However, the markup should represent information genuinely shown on the page.
Do not add misleading structured data simply to pursue enhanced search results.
Internal Linking
Important products and categories should be accessible through logical navigation.
An orphan product that exists only in the database but has no useful internal links may be difficult for both shoppers and crawlers to discover.
Payments and Shipping for Australian osCommerce Stores
Payments and delivery are two areas where apparently small technical decisions can affect everyday operations.
Payment Integration
Before selecting or rebuilding a payment integration, ask:
- Is the integration actively maintained?
- Does it support the current application?
- Does it work with the chosen checkout?
- How are refunds processed?
- How are failed payments reported?
- Does the order status update automatically?
- How are webhooks handled?
- What happens when a callback fails?
Test unsuccessful transactions as carefully as successful ones.
A website that handles successful payments perfectly but creates duplicate orders after a failed callback still has a serious problem.
Shipping
Australian ecommerce may require combinations of:
- flat-rate shipping;
- postcode rules;
- metro and regional rates;
- free-shipping thresholds;
- carrier integrations;
- click and collect;
- bulky-product rules;
- international shipping.
Therefore, define shipping logic before development begins.
Avoid vague requirements such as “integrate shipping”.
Instead document rules.
For example:
“Orders below $120 use standard shipping. Orders above $120 receive free standard shipping except oversized products. Express shipping remains chargeable.”
That statement is testable.
“Make shipping work” is not.
osCommerce Website Integration Planning
An ecommerce platform rarely operates alone.
Your store might need to communicate with:
- inventory systems;
- accounting systems;
- ERP platforms;
- CRMs;
- email marketing platforms;
- fulfilment providers;
- warehouses;
- marketplace systems.
Before developing an integration, document the direction of data.
For example:
Website → ERP
- new order;
- customer information;
- payment status.
ERP → Website
- inventory;
- dispatch status;
- tracking number.
Then determine:
- which system is authoritative;
- update frequency;
- error handling;
- retry behaviour;
- duplicate prevention;
- logging;
- alerting.
These details are far more important than simply saying two systems are “integrated”.
10-Step osCommerce Website Development Checklist
Use this checklist before starting a new build, upgrade or migration.
- Audit the existing environment.
Record versions, integrations, custom modules, hosting and current problems.
- Document business requirements.
Separate must-have functionality from optional improvements.
- Map the customer journey.
Review discovery, product selection, basket, checkout, payment and post-purchase communication.
- Document integrations.
Identify payment, freight, ERP, CRM, accounting and marketing connections.
- Review data quality.
Check products, customers, orders, categories, URLs and historical data before migration.
- Define SEO requirements.
Record valuable URLs, metadata, redirects and indexation requirements.
- Create a staging environment.
Test development separately from production.
- Run functional testing.
Test successful and unsuccessful payments, discounts, shipping, emails, accounts and admin workflows.
- Plan deployment and rollback.
Decide what happens if launch fails.
- Create a maintenance schedule.
Assign responsibility for upgrades, monitoring, backups, security and future development.
The tenth step is frequently neglected.
Yet ecommerce development does not finish when the website launches.
Launch marks the beginning of production maintenance.
Onshore vs Offshore osCommerce Website Development
Australian businesses often compare local development with overseas teams.
Neither option is automatically superior.
| Factor | Australian/onshore team | Offshore team | Hybrid model |
| Communication overlap | Usually high | Depends on timezone | Usually manageable |
| Australian market context | Usually strong | Varies | Can be strong |
| Hourly cost | Often higher | Often lower | Mid-range |
| Specialist availability | Depends on market | Potentially broad | Broad |
| Project coordination | Simpler locally | Requires strong management | Requires defined ownership |
| Scalability | Depends on agency size | Can be high | Often flexible |
| Best use | Strategy and business-critical delivery | Defined technical tasks | Strategy locally, distributed delivery |
The decision should not be based only on hourly rates.
Suppose Team A charges $80 per hour and Team B charges $150.
If Team A requires 80 hours because requirements are misunderstood while Team B requires 35 hours, the cheaper hourly rate produces the more expensive project.
Therefore, compare:
- estimated total effort;
- technical expertise;
- communication;
- testing process;
- documentation;
- warranty or defect handling;
- maintenance capacity.
For a legacy oscommerce website, platform-specific experience can be particularly important because developers may need to understand old conventions and custom modifications before safely changing the application.
How Much Does an osCommerce Website Cost in Australia?
There is no responsible single-price answer.
An oscommerce website could range from a relatively contained maintenance project to a complex ecommerce redevelopment involving hundreds of development hours.
Major cost drivers include:
- current platform condition;
- design requirements;
- number of products;
- custom functionality;
- data migration;
- payment integrations;
- freight integration;
- ERP connectivity;
- wholesale features;
- customer migration;
- SEO migration;
- automated testing;
- hosting;
- documentation;
- maintenance.
Therefore, treat published generic ecommerce price ranges cautiously.
A Better Way to Budget
Break the project into workstreams:
- discovery and audit;
- UX and design;
- platform setup;
- frontend development;
- custom features;
- integrations;
- data migration;
- testing;
- SEO migration;
- deployment;
- post-launch support.
Then request assumptions for each estimate.
For example:
Integration estimate assumes the ERP provides an operational documented API.
That sentence is important.
If the API later proves incomplete, the project scope may change.
Clear assumptions make quotations easier to compare.
Should You Upgrade or Replace a Legacy osCommerce Website?
Start with business outcomes.
Replacing technology because it is old can waste money.
Keeping technology merely because it still runs can also become expensive.
Consider upgrading or rebuilding when:
- current architecture still suits business processes;
- integrations would be expensive to replace;
- the organisation wants to stay with osCommerce;
- required features can be implemented cleanly.
Consider replatforming when:
- the current store is exceptionally difficult to maintain;
- customisations prevent safe upgrading;
- modern requirements differ substantially from the original system;
- specialist support is difficult to obtain;
- operating costs outweigh migration costs.
In many cases, the right first step is a technical discovery project.
That discovery should estimate both options rather than assuming the answer before investigation begins.
Questions to Ask an osCommerce Developer
Before appointing a developer or agency, ask:
Which osCommerce versions have you worked with?
Legacy and current development may require different knowledge.
Will you modify core platform files?
If yes, ask why and how future upgrades will be managed.
How do you test checkout changes?
A credible answer should include staging and multiple transaction scenarios.
How will custom code be documented?
Future developers need to understand what was changed.
Who owns the source code and accounts?
Ensure commercial arrangements are clear before development.
How are backups handled?
Ask whether recovery has been tested.
How will deployment occur?
Uploading files directly to production without a controlled process creates unnecessary risk.
How do you protect SEO during migration?
Developers should account for URLs, redirects, metadata and crawlability.
What happens after launch?
Maintenance arrangements matter just as much as launch delivery.
People Also Ask About osCommerce Websites in Australia
Is osCommerce still available?
Yes. osCommerce currently offers its v4 ecommerce platform and maintains official documentation for osCommerce v4. Therefore, the project should not be confused with an unsupported legacy installation simply because older versions of osCommerce still exist online.
Is an osCommerce website suitable for Australian businesses?
It can be. Suitability depends on your requirements, development capability, integrations, maintenance plan and total operating cost. Businesses with complex custom processes may value its open-source flexibility, while simpler retailers may prefer platforms requiring less technical administration.
Can an old osCommerce website be upgraded?
Often, but the effort depends on its version and customisations. A heavily modified legacy store may require a structured rebuild or data migration rather than a straightforward in-place software update.
Is osCommerce good for SEO?
osCommerce can support SEO-friendly ecommerce development when URLs, metadata, internal links, crawl controls, structured data, performance and content are configured correctly. However, the platform does not remove the need for technical SEO planning.
Is osCommerce free?
The core osCommerce shopping-cart software is presented by osCommerce as free and open source. However, operating a commercial store still involves costs such as hosting, design, development, integrations, maintenance, payment processing and ongoing support.
Expert Q&A About an osCommerce Website
1. How do I know whether my existing osCommerce installation is dangerously outdated?
Start by identifying the application version, PHP version, database version and extension inventory. Then check whether the environment can receive current updates without breaking critical functions. If developers cannot safely update the server or application because undocumented customisations will fail, treat that as a major maintainability warning.
2. Can product and customer data be migrated from an old osCommerce store?
Usually, structured data can be migrated, but migration should not be treated as a basic database copy. Product relationships, passwords, addresses, historical orders, attributes, URLs, customer groups and extension-specific data may require transformation and validation.
Run trial migrations before launch.
Then compare counts and samples between the source and destination.
3. Should an Australian retailer keep all historical orders during migration?
Not necessarily inside the new ecommerce platform.
The correct choice depends on operational, accounting, customer-service, privacy and record-retention requirements. Some businesses migrate complete histories, while others retain older records in an accessible archive.
This is a business administration and data-governance decision. Obtain appropriate accounting, privacy or legal guidance where required.
4. How can I prevent a redevelopment from damaging Google rankings?
Create an SEO migration plan before development finishes.
Export important existing URLs, identify pages receiving organic traffic, retain URLs where practical and implement one-to-one redirects when addresses must change. In addition, migrate important content and metadata, verify canonical tags, review robots directives and test the site after launch.
Redirect planning performed the night before launch is rarely sufficient.
5. What should happen after an osCommerce website goes live?
Monitor real-world behaviour.
Review:
- payment failures;
- checkout errors;
- server logs;
- 404 errors;
- integration failures;
- page performance;
- search indexing;
- analytics;
- backups;
- security alerts.
Then establish a maintenance calendar for application updates, extension reviews, security checks, performance work and regression testing.
Choosing the Right Future for Your osCommerce Website
An oscommerce website should be evaluated according to its actual technical condition and commercial requirements, not the age of the osCommerce brand.
The current osCommerce project continues with v4, while many businesses still operate older implementations created under very different technical conditions. Consequently, two websites described as “osCommerce stores” may have almost nothing in common from a maintenance perspective.
For Australian businesses, a sensible review considers five questions.
First, is the platform maintainable?
You should be able to update software without treating every upgrade as an emergency.
Second, is the website secure?
Security includes infrastructure, administrator accounts, backups, integrations and ongoing patching.
Third, does the platform support your business processes?
Technology should simplify operations rather than force staff to compensate manually for system limitations.
Fourth, can customers use it easily?
Mobile browsing, product discovery, checkout and payment should be straightforward.
Fifth, is keeping the platform economically sensible?
Compare the real multi-year cost of maintenance with upgrading or replatforming.
A stable, well-designed osCommerce implementation can remain a practical ecommerce system. Conversely, an undocumented legacy installation dependent on obsolete custom code can become expensive to maintain regardless of how attractive the frontend looks.
Therefore, begin with evidence.
Audit the technology. Map the integrations. Review the customer journey. Document operational problems. Identify security and compliance considerations. Then compare realistic upgrade, rebuild and migration options.
If your Australian business needs help assessing an existing store, planning an upgrade or developing a more maintainable ecommerce environment, explore ecommerce development support for Australian businesses and start with a technical assessment of your current platform rather than making a platform decision based on assumptions.
