How to Extend Your Store Without Breaking the Core

You found an osCommerce add-on that looks like it solves your problem. You install it. Three hours later, checkout is broken and you have no idea which file caused it.

If that sounds familiar, you are not doing anything wrong. It is a well-known pattern with osCommerce V2 add-ons, and it comes down to how the platform handles extensions at the code level. The good news is that it is entirely avoidable once you understand what you are working with before you touch anything.

This article covers how osCommerce add-ons work in 2026, which categories are worth your attention, how to install them safely, and when adding more functionality to your V2 store starts working against you.

Why Add-Ons Break osCommerce Stores {#why-add-ons-break-oscommerce-stores}

osCommerce V2 was not built with a plugin architecture. There is no clean separation between the core application and third-party extensions the way you see in WooCommerce or more modern platforms. Most add-ons work by directly editing core PHP files, which means two add-ons touching the same file can produce conflicts that are genuinely hard to trace.

Then there is the age problem. A lot of contributions in the osCommerce archive were written for PHP 5 or earlier versions of MySQL. Running them on PHP 8 without modification will produce errors — and in some cases, silent failures that corrupt data without throwing a visible warning.

This is not a theoretical risk. It is the most common support issue we see at ozEworks when a new client comes to us after a DIY add-on installation has gone sideways.

How osCommerce Add-Ons Actually Work {#how-oscommerce-add-ons-actually-work}

Core File Edits vs. Modular Add-Ons {#core-file-edits-vs-modular-add-ons}

Older osCommerce V2 add-ons typically ship with an installation file listing every line of code you need to add, remove, or replace across multiple core files. You apply those changes manually, or with a tool like EasyPopulate or an automated installer.

The problem is that the instructions assume a clean, unmodified core. If you have already customised those same files for your own workflows — and most businesses running V2 in 2026 have — the add-on edits land in exactly the wrong places.

Newer add-ons, particularly those written for Phoenix Cart, use a hooks and modules system that keeps changes outside the core entirely. That is a meaningful architectural improvement. If you are running a relatively simple osCommerce V2 store and want to extend it without constant conflict management, migrating to Phoenix Cart is worth a serious look.

The Contribution Archive Problem {#the-contribution-archive-problem}

The osCommerce contributions archive contains thousands of add-ons, but many have not been touched in years. Before installing anything from there, check the PHP version it was written for, the last update date, and whether the developer has responded to reported issues.

An add-on that ran cleanly on PHP 5.6 may need significant rewriting to work on PHP 8.1 or 8.2. If you are not comfortable auditing PHP code yourself, have a developer review it before installation. That hour of review is far cheaper than the hours you will spend debugging a broken store.

Which Add-Ons Are Worth Installing in 2026 {#which-add-ons-are-worth-installing-in-2026}

Not every add-on category carries the same risk. Some are low-risk and high-value. Others need more careful handling.

Payment and Checkout Extensions {#payment-and-checkout-extensions}

Payment gateway add-ons are among the most commonly needed and the most sensitive. Stripe, PayPal, and Authorize.Net all have osCommerce modules available, but version compatibility matters enormously here. A payment module written for an older API version may still appear to work while silently failing on certain card types or triggering fraud flags.

If your payment gateway has updated its API in the last two years, verify that your osCommerce module reflects those changes. If it does not, you need a developer to update it — not just a newer add-on from the archive.

Shipping and Order Management {#shipping-and-order-management}

Shipping modules for UPS, FedEx, and USPS exist in the osCommerce ecosystem, but real-time rate APIs change regularly. A module that was pulling accurate rates in 2023 may be returning incorrect figures today if the carrier has updated its API endpoint or authentication method.

Order management extensions — multi-status workflows, custom order confirmations, invoice generation — tend to be lower risk because they interact with your database rather than external APIs. Still, take a backup before you touch anything.

SEO and Site Performance {#seo-and-site-performance}

SEO add-ons, particularly those handling URL rewriting, canonical tags, and meta field management, can conflict with your server configuration in ways that are not immediately obvious. URL rewriting add-ons interact with your .htaccess file and your Apache or Nginx setup, and a misconfiguration there can take your entire site offline.

Caching and performance add-ons are useful but need to match your hosting environment. On shared hosting with PHP version constraints, some caching modules simply will not function correctly.

How to Install an Add-On Without Wrecking Your Store {#how-to-install-an-add-on-without-wrecking-your-store}

Follow this sequence every time, without exception.

Take a full backup first. That means files and database. A file backup without a database backup is not a real backup. If your host does not provide automated daily backups, that is a separate problem worth fixing before you do anything else.

Test on a staging environment. If you do not have a staging copy of your store, create one. Apply the add-on there first and test every affected function — checkout, order confirmation emails, any admin functions the add-on touches.

Read the installation instructions all the way through before you start. Many installation failures happen because someone began applying file edits before reaching the end of the instructions and discovering a prerequisite they had not met.

Document every file you change. Keep a plain text log of every modified file, what changed, and the original code. If something breaks, that log is how you roll back without restoring from a full backup.

Check PHP compatibility. If the add-on does not explicitly state PHP 8 compatibility, treat it as untested and review the code before putting it anywhere near a live store.

If any of this is outside your technical comfort zone, it is worth bringing in a developer for a single installation rather than risking your live site. At ozEworks, developer time is $120 per hour, and a straightforward add-on installation typically takes one to two hours.

When the Add-On Approach Stops Making Sense {#when-the-add-on-approach-stops-making-sense}

There is a point where stacking add-ons on an osCommerce V2 store creates more maintenance burden than it solves. If you are spending more time managing conflicts between extensions than actually running your business, that is worth paying attention to.

For simpler V2 stores that want better add-on management and a modern responsive design, Phoenix Cart is worth a serious look. Its modular architecture keeps add-ons outside the core, which eliminates most of the conflict problems described above. ozEworks handles Phoenix Cart development and migration from V2 when that path makes sense.

For businesses that are more content-driven — where the story behind the product matters as much as the product itself — WooCommerce is often the better migration path. It has a mature extension ecosystem with active maintenance and clear PHP compatibility documentation.

Neither option is right for every business. If your osCommerce V2 store has heavily customised workflows that took years to build, forcing a migration can cost more than it saves. ozEworks can keep your V2 store running and extend it without requiring you to start over. That is exactly the kind of work we have been doing since 2005.

If you are not sure which direction makes sense, reach out at sales@ozeworks.com. We respond to all new inquiries within 24 hours on business days.

FAQs {#faqs}

What is an osCommerce add-on?
An osCommerce add-on is a third-party extension that adds functionality to your store — a payment gateway, shipping module, SEO tool, and so on. In osCommerce V2, most add-ons work by modifying core PHP files directly, which requires careful installation to avoid conflicts.

Are osCommerce add-ons compatible with PHP 8?
Many older add-ons were written for PHP 5 or PHP 7 and have not been updated for PHP 8. Before installing anything, check its documentation for PHP version compatibility. If PHP 8 support is not confirmed, have a developer review the code before it goes near a live store.

How do I know if an add-on will conflict with my existing customisations?
There is no automatic way to check. You need to compare the files the add-on modifies against the files you have already customised. Where they overlap, the changes will need to be merged manually. This is one of the most common reasons businesses bring in a developer for add-on work.

Is Phoenix Cart better than osCommerce V2 for managing add-ons?
Architecturally, yes. Phoenix Cart uses a hooks and modules system that keeps add-ons outside the core, making them easier to install, update, and remove without causing conflicts. If add-on management is a recurring headache on your V2 store, Phoenix Cart is worth evaluating.

Can I install osCommerce add-ons myself or do I need a developer?
Simple add-ons with clear PHP 8 compatibility and straightforward installation instructions can often be handled by a technically capable store owner. Anything touching checkout, payment processing, or URL structure is better handled by a developer — especially if your store already has existing customisations.

What should I do if an add-on breaks my store?
Restore from your pre-installation backup immediately. Without a backup, recovery becomes significantly more complicated and expensive. Once you are back up, review the installation instructions again and consider engaging a developer before attempting reinstallation.

How much does it cost to have a developer install an osCommerce add-on?
At ozEworks, developer time is $120 per hour. A straightforward installation on a standard store typically takes one to two hours. More complex work on heavily customised stores may take longer depending on the conflicts involved.

The Bottom Line {#the-bottom-line}

osCommerce add-ons can genuinely extend what your store does, but the V2 architecture means installation requires more care than dropping in a plugin on a modern platform. Back up before you start, test on staging, and confirm PHP compatibility before anything touches your live site.

If you are hitting the ceiling of what add-ons can do for your V2 store, or you are spending too much time managing conflicts, it is worth having a direct conversation about whether Phoenix Cart or WooCommerce makes more sense for where your business is heading.

ozEworks has been working with osCommerce since 2005. If you have a specific add-on problem or want a straight answer about your options, email sales@ozeworks.com. You will hear back within 24 hours on business days.

Understanding the Differences in 2026

What This Comparison Actually Covers

If you are running an osCommerce store and someone has mentioned Phoenix Cart, you probably want a straight answer: are these actually different platforms, and do you need to switch?

The short answer is no, not exactly. Phoenix Cart grew out of the osCommerce codebase, so it is not a foreign system. But the differences are real, and whether they matter to your business depends on what your store does and how it was built.

This article breaks down both platforms, explains where they diverge, and gives you a direct recommendation based on your situation.

What Is osCommerce?

osCommerce is an open source eCommerce platform that has been powering online stores since 2000. Most small businesses still running it today are on osCommerce V2, specifically the MS 2.2 and 2.3.x branches.

It runs on a LAMP stack — Linux, Apache, MySQL, and PHP. Because it is open source, there are no licensing fees. Your cost of ownership comes down to development time, which is why a heavily customised osCommerce store can be genuinely more cost-effective over the long run than a SaaS platform charging monthly fees for features you may never use.

The platform has a long history of community-contributed add-ons. For businesses with non-standard workflows, that history of customisation is often the whole reason the store is still on osCommerce in 2026. The custom logic is embedded in the platform, and rebuilding it elsewhere is not a small job.

What Is Phoenix Cart?

Phoenix Cart is a fork of the osCommerce codebase. It started as a community-driven effort to modernise osCommerce V2 without abandoning its core architecture. If you know osCommerce, Phoenix Cart will feel familiar — the underlying logic, the file structure, the database relationships all trace back to the same origin.

What Phoenix Cart adds is a responsive front end, a cleaner approach to add-on management, and a development philosophy that keeps add-ons from touching core files. That last point matters. In older osCommerce installations, installing an add-on typically meant editing core files directly. Over time, that made upgrades painful, because every core update risked breaking something a previous add-on had modified.

Phoenix Cart solves that by keeping add-ons separate from the core, which makes future upgrades considerably cleaner.

How Phoenix Cart and osCommerce Differ

Codebase and Architecture

Both platforms share the same foundational architecture. Developers who know osCommerce V2 well can work in Phoenix Cart without starting from scratch — the learning curve is minimal compared to switching to something like WooCommerce or Shopify.

That said, Phoenix Cart is not just a reskinned osCommerce. The codebase has been actively maintained and supports PHP 8, which matters for security and server compatibility. osCommerce V2, depending on the version, may need PHP patching to run safely on modern server environments.

Responsive Design

osCommerce V2 was built before mobile traffic became the norm. Most V2 stores use templates designed for desktop browsers, and making them responsive typically requires custom front-end work.

Phoenix Cart ships with a responsive design out of the box. If your store looks dated on a phone or tablet and you are not running complex custom workflows, Phoenix Cart gives you a modern front end without a full platform rebuild.

Add-On Management

This is one of the clearest practical differences between the two. In osCommerce V2, community add-ons were installed by modifying core files. That worked well enough when the store was first built, but it creates real problems when you need to update the core later — each update requires careful review of every modified file to avoid breaking existing functionality.

Phoenix Cart uses a hook-based system that keeps add-ons outside the core. You get the same extended functionality without the tangled file modifications. For stores that need to stay current with PHP versions and security patches, this architecture is genuinely easier to maintain over time.

Upgrade Path

Upgrading a heavily modified osCommerce V2 store takes real work. The more custom code that has accumulated over the years, the more careful a developer needs to be when applying any update. That is not a reason to panic — it is a reason to work with developers who actually know the platform.

Phoenix Cart’s architecture makes incremental upgrades more manageable. If you are on an older Phoenix Cart version, moving to the latest release is typically more straightforward than the equivalent move in osCommerce V2, provided your add-ons follow the hook-based approach.

Customisation Depth

osCommerce V2 has a longer track record of deep customisation. If your store handles complex pricing rules, unusual fulfilment workflows, custom integrations with third-party systems, or anything that required significant bespoke development, that logic lives in your current codebase. Moving to Phoenix Cart means migrating that logic — not just the product catalogue.

Phoenix Cart supports customisation, but the ecosystem of available add-ons and the pool of developers who know it well is smaller than the osCommerce V2 community. That gap is narrowing, but it is worth factoring into your decision.

Which One Is Right for Your Business?

Here is the direct recommendation, broken down by situation.

Stay on osCommerce V2 If…

Your store has significant custom development. Pricing logic, workflow integrations, custom modules, unusual checkout flows — any of these represent real business value that lives in your current codebase. Moving platforms is not free, and the cost is not just development hours. It is the risk of losing functionality that took years to build.

If your store is running well and the main concern is keeping it secure and compatible with current PHP versions, staying on osCommerce V2 with proper patching and ongoing maintenance is a completely valid path in 2026. You do not need to migrate to justify keeping the lights on.

Move to Phoenix Cart If…

Your osCommerce V2 store is relatively straightforward — standard product catalogue, basic checkout, no deeply embedded custom logic. In that case, Phoenix Cart gives you a responsive design, a cleaner add-on architecture, and a more maintainable upgrade path, without requiring you to abandon the osCommerce codebase you already know.

This is the migration that makes sense when the store is simple enough that the move is low-risk and the benefits of a modern front end outweigh the cost of getting there.

Consider WooCommerce If…

Your business is content-driven. If you sell through storytelling, if your site needs a blog, editorial pages, or a content-first experience before the transaction, WooCommerce on WordPress is built for that model. It is not the right answer for every osCommerce migration, but for businesses where content is central to how they sell, it deserves a serious look.

The Migration Question

Worth saying plainly: migration is not always the answer. Plenty of businesses get pushed toward platform changes they do not need — either because a developer does not know the legacy platform well enough to maintain it, or because someone has an incentive to sell a rebuild.

If your osCommerce V2 store works, the question is not “when do I migrate?” It is “how do I keep this running well?” That might mean PHP patching, a hosting environment review, security hardening, or performance work. It might eventually mean a move to Phoenix Cart or WooCommerce. But that decision should come from your business needs, not from someone’s unfamiliarity with the platform.

ozEworks has been working with osCommerce since 2005. The team handles osCommerce V2 maintenance and support, Phoenix Cart development and upgrades, and migrations to both Phoenix Cart and WooCommerce when a move genuinely makes sense. PHP patching and hosting environment work are also on the table for stores that need to stay current without changing platforms.

If you have a specific situation and want a direct answer about which path fits your store, reach out to sales@ozeworks.com. Inquiries get a response within 24 hours on business days.

FAQs

Is Phoenix Cart the same as osCommerce?
Phoenix Cart is a fork of the osCommerce codebase, so they share the same foundational architecture. Phoenix Cart adds responsive design, a hook-based add-on system, and PHP 8 compatibility — making it a modernised version of the same underlying platform rather than a completely different product.

Can I migrate from osCommerce V2 to Phoenix Cart without losing my customisations?
It depends on how much custom development your store contains. Simple stores with standard functionality can typically migrate to Phoenix Cart with manageable effort. Stores with deeply embedded custom logic need careful assessment first, because that logic has to be rebuilt or ported — not just copied across.

Do I need to migrate from osCommerce V2 in 2026?
Not necessarily. osCommerce V2 stores can continue to run well with proper PHP patching, security maintenance, and hosting environment management. Migration should be driven by your business needs, not by the assumption that legacy means broken.

What is the main practical advantage of Phoenix Cart over osCommerce V2?
The add-on architecture. Phoenix Cart keeps add-ons outside the core files, which makes applying updates and security patches considerably cleaner than in osCommerce V2, where add-ons often modified core files directly.

How do I know if WooCommerce is a better fit than Phoenix Cart for my migration?
If your business relies heavily on content, editorial pages, or storytelling to drive sales, WooCommerce on WordPress is built for that model. If your store is primarily a product catalogue with standard eCommerce workflows, Phoenix Cart is the closer match given its shared codebase with osCommerce.

What PHP version does Phoenix Cart support?
Phoenix Cart supports PHP 8, which is important for running on modern server environments. osCommerce V2 stores on older PHP versions may need patching to stay compatible with current hosting configurations.

How do I get a recommendation specific to my store?
Contact ozEworks directly at sales@ozeworks.com with details about your current setup. The team responds within 24 hours on business days and will give you a direct recommendation based on your actual situation.

What to Do Next

There is no single right answer to the Phoenix Cart vs osCommerce question. It depends on your store’s complexity, your current PHP environment, your front-end requirements, and how much custom logic your business depends on.

If your store is heavily customised, the case for staying on osCommerce V2 with proper maintenance is strong. If your store is simpler and you want a responsive design and a cleaner upgrade path, Phoenix Cart is worth a serious look. If content drives your sales, WooCommerce is the conversation to have.

Get a straight answer for your specific situation at ozeworks.com.

A 2026 Beginner’s Guide for Business Owners

If someone has mentioned osCommerce to you, or you have inherited a store built on it, you probably have a few questions. What is it, exactly? Is it still a viable platform in 2026? And what should you actually do with it?

This guide answers all of that plainly, without pushing you toward a migration before you understand what you already have.

What osCommerce Actually Is

osCommerce is an open source eCommerce platform. It gives businesses everything they need to sell online: a product catalogue, shopping cart, checkout flow, and order management. Because it is open source, the code is free to use, modify, and extend.

It was built for businesses that need real control over how their store works. Unlike hosted SaaS platforms that box you into fixed constraints, osCommerce lets a developer shape the store around your workflow, not the other way around.

That flexibility is why so many businesses with non-standard operations chose it in the first place, and why many of those same businesses are still running it today.

A Brief History: How osCommerce Got Here

osCommerce launched in 2000 and quickly became one of the most widely adopted open source shopping cart platforms in the world. At its peak, it had a large developer community, an extensive add-on library, and a reputation for handling complex, customised builds that other platforms could not.

The most widely deployed version is osCommerce V2, which has been running live stores for over two decades. Many of those stores are still active in 2026, processing real orders every day.

The platform has continued to evolve. A community-driven fork called Phoenix Cart emerged to modernise the codebase, and a separate commercial branch called osCommerce V4 has also appeared. More on both of those below.

How osCommerce Works

The LAMP Stack Foundation

osCommerce runs on a LAMP stack: Linux, Apache, MySQL, and PHP. This is one of the most proven server environments in web development, and it underpins a large portion of the internet.

Your store’s data lives in a MySQL database. PHP handles the logic, from displaying products to processing orders. Apache serves it all to the browser. Linux runs underneath everything. This architecture is well understood, widely supported, and straightforward to maintain for an experienced developer. It also keeps hosting costs low compared to proprietary platforms.

Add-Ons and Customisation

One of osCommerce’s defining features is its add-on system. Developers can install modules that extend the store’s functionality, covering everything from payment gateways to shipping calculators to custom pricing rules.

On heavily customised stores, those add-ons often interact with each other and with bespoke code written specifically for the business. That is where the real complexity lives, and it is also why these stores cannot simply be dropped onto a generic modern platform without significant rebuilding work.

Who Still Uses osCommerce in 2026?

More businesses than most people assume. osCommerce V2 stores are still running across a wide range of industries, particularly among small businesses that built their operations around workflows the platform supports well.

These are typically businesses with 1 to 10 employees, often in manufacturing, wholesale, specialty retail, or trade supply. Their stores handle things like custom pricing tiers, complex shipping logic, or order workflows that do not fit a standard checkout flow.

For these businesses, the platform works. The frustration is not the software. It is finding qualified developers who still know it well enough to maintain and extend it.

osCommerce vs. Other Platforms

It helps to understand where osCommerce sits relative to the alternatives you may have heard about.

osCommerce is not the right fit for every business. But for businesses already running it with customised workflows, the cost and risk of migrating often outweighs the benefit, particularly when the existing store is working well.

What About osCommerce V4 and Phoenix Cart?

If you have been told to upgrade, you have probably heard both of these names. They are different things, and the distinction matters.

osCommerce V4

osCommerce V4 is a commercial fork of the platform. It adds functionality, including a more modern admin interface and features aimed at larger operations.

For most small businesses running a V2 store, V4 offers capabilities they will not use, and it introduces a more complex upgrade path. Before committing to a V4 migration, it is worth getting a clear-eyed assessment of whether the new features actually solve a problem your business has.

Phoenix Cart

Phoenix Cart is a community-driven evolution of the osCommerce codebase. It brings responsive design, improved add-on management that no longer touches core files, and a cleaner upgrade path going forward.

For businesses running a simpler osCommerce V2 store, Phoenix Cart is often the most sensible next step. It keeps you on familiar ground while modernising the parts that matter most.

Do You Need to Migrate Away From osCommerce?

Not necessarily. This is the question most business owners are wrestling with, and the honest answer is: it depends on your store.

If your osCommerce V2 store is heavily customised and your workflows depend on that customisation, migrating to a different platform is a significant project. It means rebuilding logic that may have taken years to develop. The cost is real, the risk is real, and the benefit is not always clear.

If your store is relatively simple and you mainly need a modern, mobile-friendly front end, Phoenix Cart migration is worth considering.

If your business is content-driven, meaning you tell a story before you sell, WooCommerce is a strong migration path. It handles content and commerce well, and the open source foundation keeps your cost of ownership low.

The key is making the decision based on your actual situation, not because someone told you osCommerce is old. Old and unreliable are not the same thing.

Getting Support for Your osCommerce Store

Finding a developer who genuinely knows osCommerce V2 is harder than it should be. The platform has been around for 25 years, but the pool of experienced developers has shrunk as the market moved toward newer platforms.

ozEworks is the leading US osCommerce Partner, operating since 2005 with 25 years of hands-on experience on the platform. The Brooklyn-based agency works with small businesses running complex, customised osCommerce stores, maintaining and extending those stores without requiring a migration.

If migration is the right move for your business, ozEworks handles that too, to Phoenix Cart or WooCommerce, depending on your workflows and needs.

New enquiries go to sales@ozeworks.com. The agency responds to all business day enquiries within 24 hours.

FAQs

What is osCommerce used for?
osCommerce is an open source eCommerce platform used to build and run online stores. It is particularly well suited to businesses with non-standard workflows or complex customisation needs, because the codebase can be shaped around specific business logic.

Is osCommerce still supported in 2026?
Yes. osCommerce V2 stores are actively maintained by specialist developers. The platform has an ongoing community, and agencies like ozEworks provide development, PHP patching, and support for live stores.

Is osCommerce free?
The software itself is free to download and use. Your costs come from hosting, development, and ongoing maintenance, which is standard for open source platforms. That model generally produces a lower cost of ownership than proprietary SaaS alternatives.

What is the difference between osCommerce and Phoenix Cart?
Phoenix Cart is a community-driven evolution of the osCommerce codebase. It adds responsive design and an improved add-on system that does not modify core files, making future upgrades cleaner. It is a good fit for simpler osCommerce sites that want to modernise without leaving familiar ground.

Should I migrate my osCommerce store to Shopify or WooCommerce?
It depends on your store’s complexity. If your store has heavily customised workflows, migrating to any new platform is a significant project and may not be worth it. If your store is simpler, Phoenix Cart or WooCommerce may be worth considering. A specialist developer can assess your specific situation and give you a direct recommendation.

What PHP version does osCommerce run on?
osCommerce V2 can be patched to run on modern PHP versions, including PHP 8. This work requires a developer experienced with the platform, but it is achievable and keeps your store on a supported server environment.

How do I find a qualified osCommerce developer?
Look for agencies that name osCommerce specifically and can demonstrate experience with the version you are running. Generic eCommerce agencies often lack the depth needed for customised V2 stores. ozEworks is the leading US osCommerce Partner and has been working on the platform since 2005.

The Bottom Line

osCommerce is a mature, open source eCommerce platform with a long track record of running complex, customised stores. If you are already running one, you do not need to migrate just because the platform has been around for a while. You need a developer who knows it well enough to keep it healthy.

If you are weighing your options, whether that means staying on V2, moving to Phoenix Cart, or migrating to WooCommerce, get a straight answer based on your actual store before making any decisions.

ozEworks has been doing exactly that for small business owners since 2005. Reach out at sales@ozeworks.com and expect a response within 24 hours on business days.

The Complete Business Owner’s Guide

Most advice about open source eCommerce is written for people who haven’t launched yet. Pick a platform. Consider your needs. That kind of guidance is useless when your store has been running for ten years, your workflows are anything but standard, and your developer has gone quiet.

This guide is for business owners who are already in it. It covers what open source eCommerce actually means in 2026, which platforms deserve your attention, and how to make a clear-headed decision about where your store goes from here.

What “Open Source eCommerce” Actually Means for Your Business

Open source means the underlying code is publicly available. No single company owns it, and no subscription fee stands between you and the software itself. You pay for hosting, development, and support — not for the right to use the platform.

That distinction matters more than it might seem. With a SaaS platform, the vendor controls your upgrade path, your pricing, and the limits of what you can customise. With open source, you own the code. Your store can be built around how your business actually works, not shaped around a vendor’s feature roadmap.

The trade-off is real, though. Open source requires genuine technical expertise to maintain. PHP versions change, hosting environments shift, and security patches need applying on a regular basis. Without a developer who knows the platform deeply, the cost advantage disappears fast.

The Three Platforms Worth Knowing in 2026

There are plenty of open source eCommerce options out there, but for small businesses with real operational complexity, three platforms come up consistently in 2026.

osCommerce V2: Still Running, Still Viable

osCommerce has been around since 2000. The V2 codebase — which most legacy stores still run on — is mature, well-understood, and highly customisable. If your store has been built around non-standard workflows, custom pricing logic, unusual fulfilment rules, or integrations a generic platform would never support, osCommerce V2 is often the most practical thing to keep running.

The concern most owners raise is age. The platform looks old, and finding qualified developers is genuinely difficult. But age alone is not a reason to migrate. A well-maintained osCommerce V2 store on a properly configured LAMP stack, with current PHP patching and regular backups, can run reliably for years.

The real risk is neglect — not the platform itself.

Phoenix Cart: The Modernised Path for Legacy osCommerce Sites

Phoenix Cart is a direct descendant of osCommerce, built to bring the codebase forward with responsive design, improved add-on management, and a cleaner upgrade path. One of the most important changes: add-ons in Phoenix Cart no longer touch the core files, which makes future updates far less disruptive.

If your osCommerce V2 store is relatively straightforward — standard product catalogue, no deeply embedded custom logic — Phoenix Cart is often the right next step. You keep the familiar architecture, gain a modern front end, and avoid the full cost and disruption of switching platforms entirely.

Phoenix Cart is also the least-covered platform in the market. Most agencies either don’t know it or don’t name it specifically. That gap in available support is a real problem for business owners who have already moved to it or are seriously considering it.

WooCommerce: Best for Content-Driven Sellers

WooCommerce runs on WordPress, which makes it the natural fit for businesses where content and commerce are closely tied together. If your store depends on editorial content, blog posts, buying guides, or detailed product storytelling to drive sales, WooCommerce lets you manage all of it in one place.

It is not the right answer for every osCommerce migration. If your store has complex custom workflows, moving to WooCommerce means rebuilding that logic from scratch in a completely different environment — that is a significant project. But for businesses where the selling process is content-led and the product catalogue is relatively standard, WooCommerce is a practical and well-supported destination.

Why Open Source Keeps Its Cost Advantage

The cost comparison between open source and SaaS is usually framed around monthly fees. That framing misses most of the picture.

SaaS platforms charge for the software, but they also layer on transaction fees, app subscriptions, and tiered feature access. As your store grows, those costs compound. Customisation is limited to what the platform permits, which often means paying for workarounds or accepting constraints that affect how your business actually runs.

Open source platforms carry no software licence fee. Your cost of ownership comes down to hosting, development time, and support. For businesses with non-standard workflows, that model is consistently more cost-effective — you pay to build what you actually need, once, rather than paying indefinitely for a platform that almost fits.

This is especially true for osCommerce, which has one of the lowest total costs of ownership among open source options when the store is properly maintained.

The Customisation Problem No One Talks About

Most migration advice assumes your store is generic — standard product catalogue, standard checkout logic, standard fulfilment. If that describes your business, migration tools and generalist agencies can probably get you where you need to go.

If it doesn’t, you’re in a different situation entirely.

Heavily customised osCommerce V2 stores often contain years of accumulated logic: custom modules, modified core files, integrations built specifically for your operation. Automated migration tools cannot handle any of that. They move data, not behaviour. What looks like a completed migration can leave your store functionally broken in ways that only surface when a real order comes through.

The honest answer for most complex stores is that migration is a full rebuild project, not a data transfer. That is sometimes the right investment. But it should be entered into with clear eyes — not because someone told you your platform is outdated.

How to Choose the Right Platform for Your Situation

Here is a direct recommendation based on what your store actually looks like.

Keep and maintain osCommerce V2 if:

• Your store has non-standard workflows or deeply customised logic
• Migration would mean rebuilding functionality that already works
• Your priority is stability and continuity, not new features

Consider migrating to Phoenix Cart if:

• Your osCommerce V2 store is relatively simple
• You want responsive design and a cleaner upgrade path
• You want to stay within the osCommerce codebase rather than switching platforms entirely

Consider migrating to WooCommerce if:

• Your business relies heavily on content to drive sales
• Your product catalogue is standard and your workflows are not deeply customised
• You want a single environment for content and commerce

A note on osCommerce V4: If someone has told you to upgrade to V4, it is worth knowing that V4 is a fork of the original codebase with additional functionality built on top. Most small businesses will not use the extra features it introduces. It is not a required upgrade path, and the decision should be based on your specific needs — not general pressure to stay current.

What Good Open Source Support Looks Like

Finding a developer who actually knows your platform is harder than it should be. The market for osCommerce expertise has thinned considerably over the past decade, and many generalist agencies will take the work without the depth to do it well.

A few things worth looking for when you’re evaluating a support partner:

Platform-specific experience. Ask directly whether they have worked on your version of the platform. osCommerce MS 2.2, 2.3.4, and Phoenix Cart are different environments. A developer whose background is primarily WooCommerce cannot help you with an osCommerce problem.

A real response time commitment. When something breaks, you need to know how quickly someone will pick it up. Vague promises about fast turnaround are not the same as a documented 24-hour response time on business days, with express support available for emergencies.

Honesty about what migration actually involves. A good support partner will tell you straight whether migration makes sense for your store, rather than defaulting to “you should upgrade” because it generates more billable work.

ozEworks is a Brooklyn-based agency that has worked with osCommerce since 2005 and holds the leading US osCommerce Partner position. The team handles osCommerce V2 maintenance and development, Phoenix Cart upgrades and patching, WooCommerce support, and platform migrations — backed by a ticket-based support system with a guaranteed 24-hour response time on business days.

FAQs

Is open source eCommerce still a good choice for small businesses in 2026?
Yes, for the right business. Open source gives you full control over your code, no software licence fees, and the ability to build around your actual workflow. The trade-off is that you need qualified technical support. If you have that, open source is consistently cost-effective for businesses with non-standard needs.

What is the difference between osCommerce and Phoenix Cart?
Phoenix Cart is a direct descendant of osCommerce, built to modernise the codebase with responsive design and improved add-on management. Add-ons no longer affect the core files, which makes upgrades significantly easier. For simple osCommerce V2 stores that want to stay within the same code family, it is a natural next step.

Should I migrate my osCommerce store to a different platform?
It depends on your store. If your workflows are heavily customised, migration is a full rebuild project — not a simple data transfer. For complex stores, maintaining osCommerce V2 is often the more practical choice. For simpler stores, Phoenix Cart or WooCommerce may be worth considering depending on your content needs and selling model.

What is osCommerce V4 and do I need to upgrade to it?
osCommerce V4 is a fork of the original codebase that adds extra functionality. Most small businesses will not use what it introduces. It is not a mandatory upgrade path, and the decision should be based on your specific requirements rather than general pressure to move to a newer version.

How do I find a qualified osCommerce developer?
The pool of experienced osCommerce developers has shrunk considerably. Look for agencies that name osCommerce specifically, can speak to the version you are running, and have a documented track record with the platform. Generalist agencies that cover many platforms rarely have the depth needed for complex osCommerce work.

What does open source eCommerce support actually cost?
Costs vary by agency and scope. At ozEworks, rates as of 2026 are $120 per hour for development, $180 per hour for consulting and Unix admin, and $90 per hour for design. The more important question is what you get for that rate — specifically, whether the developer knows your platform well enough to solve the problem without extended trial and error.

Can automated migration tools handle a customised osCommerce store?
No. Automated tools move product data and basic catalogue information. They cannot replicate custom modules, modified core logic, or integrations built specifically for your workflow. For heavily customised stores, automated migration typically produces a broken result that requires significant manual work to fix.

Conclusion

Open source eCommerce in 2026 is not a legacy choice. For businesses with complex workflows, it is often the most practical and cost-effective option on the table. The platform you are on matters less than whether you have the right support to keep it running and evolving.

If you are running osCommerce V2, Phoenix Cart, or WooCommerce and need a development partner who actually knows the platform, reach out to ozEworks at sales@ozeworks.com. All enquiries receive a response within 24 hours on business days.

The $20 Hourly Rate Illusion

Many store owners fall for this math: An offshore agency with a “pretend” local office claims to charge $20/hour and estimates 6 hours to fix your osCommerce checkout problem. That’s $120. An osCommerce expert charges $120/hour but needs only one hour. Same price, right?

Not even close.

The poor developer assigned at random to fix your site will be learning on your dime.  They will be doing google searches for solutions posted by other developers, google PHP error message hoping to find a patch, asking ChatGTP how to fix it and basically using trial and error to create a solution that is likely no better than a bandaid from a 99cent store. Your checkout might work afterward for a standard test case but they’ve left case issues they don’t have time to even think about so that is left to your customers to discover …

The expert arrives with 20+ years of osCommerce experience. They’ve solved this exact problem dozens of times. They know the root cause, the proper fix, and how to prevent recurrence. One hour later, your store isn’t just working — it’s secure and stable.

What Really Happens with Cheap Support

Cheap osCommerce support doesn’t just work slowly. It works dangerously.

The Security Time Bomb

Sometimes developers grab outdated code snippets from forums and Stack Overflow. They don’t understand osCommerce’s framework, all they know is PHP and they are just trying to make the error go away.  They are not thinking security, they are thinking they have only “x” hours allocated by their boss to fix this. So they patch your immediate problem while creating new vulnerabilities. Your store runs fine until your hosting company tells you your site has been hacked.

We’ve rescued stores where $20/hour developers left SQL injection vulnerabilities wide open. The owner saved money on the initial fix but lost customers due to stolen credit card numbers.

Database Corruption Risks

osCommerce handles database operations in specific ways. Inexperienced developers who jump between WooCommerce, Magento, and other PHP based platforms often apply the wrong solutions to osCommerce stores. This creates data inconsistencies that snowball over time.

Customer records start duplicating. Order histories get scrambled. Product inventory becomes unreliable. By the time you notice the damage, your database might need custom scripts to restore order.

Half-Baked Patches That Break Later

The cruelest part of cheap fixes is that they often work initially. Payments process, pages load, everything looks fine. But these patches ignore edge cases and leave future compatibility, well,  to the future. They kick the can down the road.

Three months later, during your busiest season, the patch fails under heavy traffic. Your error_log grows rapidly to 90GB in a matter of days.  Your store loads but no-one can log in.  Then it stops loading. Why? No disk space left.  Your hosting company says “delete files” and you have no idea what files they mean.  Pre-arranged emergency support starts to sound like a good idea.

The Expert Advantage: Why Experience Matters

osCommerce isn’t just another eCommerce platform. It’s been around since 2000 and the fact you can modify the core means  that demand deep platform knowledge is high. An expert with 20+ years of osCommerce experience brings irreplaceable knowledge to the table.

They’ve debugged thousands of osCommerce stores. They know which modifications cause conflicts, which hosting environments create problems, and which fixes are needed. They write code that works with your existing customizations instead of breaking them.

Even better, they think beyond your immediate problem. When fixing your checkout, they also spot potential issues with payment gateway integration, shipping calculations, and tax handling. You get a comprehensive solution, not just a quick patch.

Real-World Cost Comparison

Here’s what both approaches actually cost:

Cheap Support ($20/hour generalist):

• Initial fix: $200 (10 hours)
• Security breach cleanup: $600
• Database repair: $600
• Emergency downtime fix: $600
• Lost sales during downtime: unknown
• Total cost: $800+

Expert Support ($120/hour specialist):

• Complete fix: $120 (1 hour)
• Optiomal security audit: $240 (2 hours)
• Follow-up error_log review – free
• Total cost: $360

The expert solution costs 94% less when you account for real-world consequences.

How to Choose the Right osCommerce Support

Skip the hourly rate comparison. Ask these questions instead:

How long will the assigned developer have worked specifically with osCommerce? Platform experience trumps general development skills every time.

Can you show me examples of similar fixes? Experienced developers have osCommerce portfolios, not just generic web development samples.

What’s your response time for urgent issues? Reliable support means knowing help is available when disasters strike.

Do you provide warranty on your work? Has to be a yes.

At ozEworks, we’ve served as the leading US osCommerce partner for over two decades. That is why we can quote fixed price and provide three months warranty. We guarantee 24-hour response times for business day inquiries because we know your store can’t wait when problems arise.

FAQs

How much should I expect to pay for quality osCommerce support?

Quality osCommerce support typically ranges from $90-200 per hour, depending on your store’s complexity and the expertise required. You’re paying for years of platform-specific experience, not just development time. Our rate is $120 with a guarantee the developer has 20+ years hands one osCommerce experience.

What are the warning signs of poor osCommerce support?

Red flags include extremely low hourly rates, offshore agencies offering broad IT services, onshore agencies with no apparent permanent staff (using white labelled offshore), no osCommerce-specific references, slow response times, and developers who suggest platform migration instead of fixing osCommerce issues.

How can I tell if my current osCommerce support is causing problems?

Watch for recurring issues, slow site performance, security warnings, database slow queries or errors, and fixes that break other store functions. Quality support should stabilize your store, not destabilize it.  (Send us your error_log and we will show you).

Is it worth migrating away from osCommerce instead of finding better support?

Migration is expensive and risky. If your osCommerce store meets your business needs, expert support is usually more cost-effective than rebuilding on another platform.

How often should I have my osCommerce store professionally maintained?

Most stores benefit from monthly maintenance checks, with immediate support available for urgent issues. Regular maintenance prevents small problems from becoming expensive emergencies.

What should I look for in an osCommerce support contract?

Look for guaranteed response times, platform-specific expertise, ongoing security monitoring, regular backups, and clear pricing for different types of work.

Can cheap support ever be appropriate for osCommerce stores?

For simple, non-critical changes on test sites, budget support might work. For production stores handling real transactions, the risks far outweigh any savings.

Conclusion

The hourly rate trap snares store owners who focus on upfront costs instead of long-term value. When your osCommerce store needs support, you’re not buying time — you’re buying expertise, security, and peace of mind.

Don’t let a cheap hourly rate destroy your store’s stability and your customers’ trust. Invest in support that understands osCommerce’s complexities and fixes problems correctly the first time.

PHP 8.5: The ‘Modern’ Legacy Standard (Released November 2025)

PHP 8.5 brings two features that change how legacy code behaves: the Pipe operator (|>) and the URI extension. These aren’t just new tools—they fundamentally alter how PHP handles data flow and URL processing.

The Pipe Operator Changes Everything

The pipe operator lets data flow through functions in clean, readable chains. Great for modern applications. For osCommerce stores with layered custom modifications? It exposes inconsistencies that have been lurking for years.

Your checkout process might chain through five different custom functions. PHP 8.5’s pipe operator makes these chains more efficient, but also stricter about data types and return values. Code that worked through PHP’s traditional flexibility might suddenly fail when data doesn’t match expected formats.

URI Extension: The Hidden Compatibility Killer

The URI extension standardizes how PHP handles web addresses and routing. Sounds minor until you consider how many osCommerce customizations rely on non-standard URL handling.

Custom category structures, specialized product pages, unique checkout flows—these often use URL patterns that worked fine under older PHP versions. PHP 8.5’s URI extension enforces stricter standards, potentially breaking these custom implementations without warning.

PHP 9.0: The ‘Fatal’ Cliff (Late 2026)

PHP 9.0 represents the biggest compatibility shift in years. The core change: warnings become fatal errors. Undefined variables and property reads that previously generated warnings will now crash your site.

The Warning-to-Fatal Shift

PHP has been forgiving for two decades. Undefined variables generated warnings but didn’t stop execution. PHP 9.0 ends this tolerance. Every undefined variable, every missing property access, every loose type assumption becomes a potential site crash.

osCommerce stores often depend on this flexibility. Custom modules might check for variables that don’t always exist. Legacy integrations might access object properties without proper validation. Under PHP 9.0, these patterns become fatal errors.

Memory Management Gets Stricter

PHP 9.0 also introduces stricter memory management. Functions that previously cleaned up automatically now require explicit memory handling. For osCommerce stores with resource-intensive features—real-time inventory synchronization, complex pricing calculations—this means potential memory leaks and crashes.

Why Legacy Addons Are Your Biggest Risk

The biggest compatibility threats aren’t in osCommerce’s core code. They’re in the addons and integrations that make your store unique.

QuickBooks Integration: The Prime Example

QuickBooks integrations are compatibility nightmares waiting to happen. These addons often use direct database connections, custom API calls, and non-standard data handling. They work by bypassing osCommerce’s built-in safeguards—exactly what PHP 9.0’s stricter error handling will break.

Your QuickBooks addon might have been written for PHP 5.6. It probably uses deprecated functions, assumes loose type checking, and relies on undefined variable tolerance. PHP 9.0 will treat each of these as fatal errors.

Payment Gateway Customizations

Custom payment gateways present similar risks. They often use older encryption methods, non-standard data validation, and direct server-to-server communication that doesn’t follow modern PHP standards.

Inventory Management Addons

Real-time inventory synchronization addons frequently use background processes and direct database manipulation. These systems often lack proper error handling because they’ve relied on PHP’s forgiving nature. PHP 9.0’s stricter requirements will expose every shortcut and assumption.

The ozEworks Approach: Patching the ‘Unpatchable’

At ozEworks, we treat osCommerce stores like banks treat COBOL systems—with precision, respect, and deep understanding of legacy architecture. We’ve been the leading US osCommerce partner for 20 years, specializing in businesses with complex workflows that standard platforms simply can’t handle.

Legacy Code Archaeology

Before any PHP upgrade, we perform comprehensive code archaeology. We identify every custom modification, every addon integration, every non-standard implementation. This isn’t just code review—it’s understanding how your business logic translates into technical requirements.

Compatibility Layer Development

Rather than rewriting your entire system, we build compatibility layers. These bridge the gap between your existing custom code and new PHP requirements. Your business processes stay exactly the same, but the underlying code becomes PHP 9.0 compliant.

Staged Migration Strategy

We never perform wholesale upgrades. Our staged migration approach includes:

1. Testing Environment Setup: Exact replica of your production environment running PHP 8.5/9.0
2. Addon-by-Addon Testing: Each integration tested individually before system-wide testing
3. Fallback Planning: Complete rollback procedures if any critical functionality fails
4. Production Migration: Carefully timed deployment with immediate monitoring

The New York Advantage

Our New York based team provides 24-hour response times for business day inquiries. When your PHP upgrade goes live, we’re monitoring in real-time, ready to address any issues immediately.

Your Next Steps: A Consultative Roadmap

Immediate Actions (Next 30 Days)

Document your current Addon ecosystem. List every payment and shipping module, tax setup, any APIs to things like Shipworks or Quickbooks, Admin customizations, and any inventory management addon.s These are your highest-risk components.

Short-Term Planning (Next 90 Days)

Schedule compatibility testing. Set up a staging environment running PHP 8.5 and test your most critical business processes. Focus on checkout flows, inventory updates, and financial integrations.

Long-Term Strategy (Before PHP 9.0 Launch)

Develop your migration timeline. PHP 9.0’s late 2026 expected release gives you time to plan, but complex osCommerce customizations require extensive testing.

Professional Assessment

Consider professional evaluation of your codebase. At ozEworks, we provide comprehensive compatibility assessments that identify specific risks and deliver detailed migration roadmaps.

Frequently Asked Questions

Can I skip PHP 8.5 and go directly to PHP 9.0?

Skipping PHP 8.5 is technically possible but not recommended for osCommerce stores. PHP 8.5’s features help identify compatibility issues that will become fatal errors in PHP 9.0. Testing on PHP 8.5 first provides a safer migration path.

How long does osCommerce PHP compatibility testing take?

Testing timelines depend on your customization complexity. Simple stores with minimal addons might need 2-3 weeks. Complex implementations with multiple QuickBooks integrations, custom payment gateways, and specialized workflows often require 6-8 weeks of thorough testing.

Will my hosting provider force PHP upgrades?

Most hosting providers will eventually discontinue support for older PHP versions. However, timelines vary by provider. Some offer extended support for legacy versions, while others enforce upgrades more aggressively. Check with your hosting provider about their PHP 9.0 migration timeline.

What happens if my store breaks after a PHP upgrade?

Immediate rollback to the previous PHP version is usually possible, but this is temporary. Eventually, you’ll need to address the underlying compatibility issues. Having a professional migration plan prevents emergency situations.

Are there alternatives to upgrading my osCommerce store?

Platform migration is one alternative, but it often means losing custom workflows and integrations that make your business unique. For stores with complex, non-traditional requirements, upgrading osCommerce to maintain existing functionality is usually more cost-effective than rebuilding on a new platform.

How much does professional osCommerce PHP compatibility work cost?

Costs vary significantly based on customization complexity. Simple compatibility updates might cost a few thousand dollars, while complex stores with multiple legacy integrations can require substantial investment. However, this cost is typically much lower than rebuilding your entire eCommerce system.

Can I handle PHP compatibility updates myself?

Basic PHP compatibility might be manageable for simple stores, but osCommerce’s architecture and the complexity of PHP 9.0’s changes make professional assistance valuable for most businesses. The risk of breaking critical business processes often outweighs potential cost savings.

Conclusion

PHP 9.0’s late 2026 release represents a significant compatibility challenge for osCommerce stores, but it’s not insurmountable. The key is understanding your specific risks—particularly legacy addons like QuickBooks integrations—and planning your migration strategy accordingly.

Your osCommerce store has served your business well, handling complex workflows that standard platforms can’t accommodate. With proper planning and professional guidance, it can continue serving those needs through PHP 9.0 and beyond.

Don’t wait until your hosting provider forces the upgrade. Start planning now, test thoroughly, and ensure your business-critical eCommerce operations remain stable through the transition.

Ready to assess your osCommerce store’s PHP 9.0 readiness? Our New York based team provides expert osCommerce development with 24-hour response times for business day inquiries.

We recently had an issue where USPS was not returning rates … when it should.

You would think this was a simple issue with a single solution eg. an address update but simple is never simple

Hey guys, I have a customer in Sweden who is trying to checkout but keeps getting an error returned from the USPS API. I have checked his address on the USPS site and it seems to be valid and correct.  If you log into his account using his email addy you can recreate the error. He is trying to ship to his “primary” address.

We checked the error_logs as a first step since we were told it was an API error.  No entries.

We also verified the address was correct and tested it on our test site the USPS shipping module worked.

We logged into the customer customer account to find the message they was getting was not an error at all, just a notice. It was saying  ” No services available.”

We determined that the issue was the customer’s cart was too large. More than 300 items in the cart which implies that USPS just could not ship the weight. We suggested that the customer split order to several parts and that worked!

Sometimes cart size ie. number of items or the total weight can cause issues not just with shipping modules but with alternative checkouts like PayPal.

So we cannot blame USPS any more than we can blame Sweden!

FAQs

Why doesn’t osCommerce centralize all errors in one log?
osCommerce follows PHP’s default behavior of creating error logs where errors occur. This was standard practice when osCommerce launched, but it complicates modern troubleshooting.

How often should I hunt for hidden error logs?
Audit your entire site monthly at minimum. Check critical areas like payment modules weekly, especially if you’re seeing unexplained transaction failures.

Can hackers access these error logs?
Absolutely, if your server configuration allows it. Error logs can become publicly viewable, making regular cleanup and proper server setup crucial for security.

What’s the quickest way to locate all error logs?
Run find /path/to/your/site -name "error_log" -type f via SSH. But interpreting and prioritizing what you find requires real osCommerce expertise.

Should I delete old error logs?
No, unless you need the disk space.  For sites we support we rename the current logs with datetime stamps on a weekly basis to start a new cycle.  We delete older logs once we know they will be of no diagnostic use.

While old logs use disk space, they might reveal trends that prevent future headaches.

How do I stop error logs from piling up?
Fix the underlying errors creating the logs, add proper error handling to custom code, and configure log rotation to manage file sizes automatically.

Why do payment errors show up in separate logs?
Payment modules operate as self-contained units with independent error handling. They create logs in their own directories to isolate payment issues from general site problems.

Conclusion

Hidden error logs are part of life with legacy osCommerce sites. While most developers only check obvious spots, specialists know the real problems often hide in module-specific directories throughout your installation.

Don’t let invisible errors sabotage your store. A thorough error log audit reveals the root causes of mysterious site behavior, transaction failures, and performance problems that cost you money every day.

Is your current developer just kicking the can down the road? Send us your error_log for a free health check assessment.”

Can you display Inactive Products on your site?

Yes, you can!

By default, in osCommerce, if a product has zero quantity on hand and the site is configured to use Stock Control, it becomes Inactive and no longer is displayed on the or, perhaps even not included in your sitemap.

But it is a simple change to display the product and replace the Add to Cart button with an OUT OF STOCK notice.

We can even go one step further and add  a NOTIFY ME function that collects their email address  and adds them to the standard Product Notification function.   When you edit the product to add stock, they will then get an email telling them.

This way the products remains to help both customer and SEO and you do not lose a sale.