Queenberry: An osCommerce
V4 Custom Product Extension

Queenberry wanted the kind of product customization shoppers know from Amazon, where you pick a metal color, then a style, then options that only make sense once you have chosen the first two, and you upload your own image before you buy. The catch was that Queenberry is a live osCommerce V4 store where staff process orders every day, and the client’s hard rule was that none of this could touch the store’s base code. Break the core, and you break the business.

That constraint shaped the whole project. The result is a self-contained osCommerce V4 extension that adds Amazon-style custom-product ordering to Queenberry and installs, disables and uninstalls cleanly, leaving no changes in the base code and nothing behind on removal. An admin marks a product as customizable and defines its options, including options that adapt to earlier selections; the shopper works through those options in a popup, uploads an image, and only then can add the product to the cart; and the finished customization, image scanned for viruses, is tied to the order for staff to fulfill.

Put simply, it delivers rich, branching product customization on a live store without editing a single core file, and it can be switched off at any time with the store carrying on exactly as before.

The Starting Point: A Big Feature on a Live Store

Adding rich, Amazon-style customization to a running osCommerce store is demanding, because the customization has to be flexible, the uploads have to be safe, and none of it can put the live store at risk. Employees process orders on the site every day, so the feature could not be built by editing core files or anything that might destabilize it. The requirements were specific:

• Customization that adapts to choices. Real customization is not a flat list of fields; later options depend on earlier ones, so the admin needs branching layouts and the storefront needs to follow them.
• The store is live. Staff process orders daily, so the feature cannot be built by editing core files or anything that could destabilize the running store.
• Clean install and uninstall. The client requires an extension that installs, disables and removes without leaving changes in, or damage to, the base code.
• Uploaded files are a risk. Customers upload images, which have to be virus-scanned before they are trusted, with the scan configurable by the admin.
• The order needs the full picture. Once an order is placed, staff have to see exactly what the customer customized and be able to download it to fulfill the job.
• It has to feel native. The flow should match how osCommerce already behaves, so it feels built in rather than bolted on.

The Build: Customization Through the Extension System

The extension adds the whole custom-product experience through osCommerce V4’s extension system, without touching the base code. In the admin, a toggle on the product detail page marks a product as customizable, and an Add or Edit Customization button opens a builder where an employee defines the layout and its options, including options that appear or change based on earlier selections. Building a feature this substantial entirely inside the framework’s own extension model is careful osCommerce development, because it has to honor the platform’s conventions rather than work around them.

On the storefront, the customer’s path is a clear sequence:

1. While browsing, a customizable product shows a CHOOSE OPTIONS button, exactly as osCommerce does for products with attributes.
2. On the product page, a Customize now button appears in place of Add to Cart, and clicking it opens a popup presenting the layout the admin defined.
3. The customer works through the options, which adapt to their choices, and uploads an image.
4. Once every required detail is provided, the Add to Cart button appears, and the customer can reopen Customize now to change anything before submitting.
5. When the order is placed, the extension uploads the customization details, virus-scans any image files when scanning is enabled, and associates everything to the order.

On the admin order page, each custom product gets a popup preview of what the customer created and a link to download the full customization as a zip, so staff can see and produce exactly what was ordered. Virus scanning is optional, and when it is enabled the admin sets the path to the scanner. Delivering a feature this self-contained on a live store is really a piece of custom software development shaped by one strict rule: leave the core alone.

Technical Architecture

The heart of the project is a self-contained extension that layers a full customization experience onto a live osCommerce V4 store without modifying its base code. It adds admin controls and a layout builder, a storefront customizer popup with branching options and image upload, safe file handling with optional virus scanning, and order association with an admin preview and zip export. The components break down like this:

• Self-contained extension. The feature is delivered entirely through osCommerce V4’s extension system, so installing, disabling or removing it leaves the base code untouched and the store fully functional without it.
• Admin toggle and layout builder. A toggle on the product detail page marks a product customizable, and an Add or Edit Customization builder lets an employee define the layout and its branching options, stored as a definition rather than hard-coded.
• Storefront customizer. Customizable products show CHOOSE OPTIONS while browsing and a Customize now popup on the product page that renders the admin’s layout, adapts options to the customer’s choices, and reveals Add to Cart once every required detail is provided.
• Uploads and virus scanning. The customer’s image is uploaded and, when scanning is enabled, checked with the virus scanner at the admin-set path before it is kept, so untrusted files are never trusted blindly.
• Order association and admin tools. On submission the customization and files are attached to the order, and the admin order page provides a popup preview and a zip download of the full customization for fulfillment.
• Safe on a live store. Because nothing modifies the core and the extension can be disabled instantly, the feature can be installed and tested in the live environment with a clean rollback path.

The branching layout builder and the safe upload handling were the two pieces worth building carefully. Between them they let the admin add customizable products by configuration rather than code, and keep customer uploads checked before they are ever shown, which is what makes the feature usable across a growing catalog. That kind of admin-controlled, catalog-wide customization is a natural fit for retail and ecommerce brands that sell personalized or made-to-order products.

Challenges Solved

Adding a big feature without touching the core was the defining challenge, and the extension system answered it: the whole customization experience installs and uninstalls cleanly, and the store runs unchanged with it disabled, meeting the client’s hard no-core-modification rule. Making customization adapt to choices meant a data-driven layout whose options depend on earlier selections, rendered and followed by the storefront popup, so customization is configured per product rather than coded. Making it feel native meant reusing osCommerce’s own CHOOSE OPTIONS behavior and putting Customize now exactly where Add to Cart would sit, so customers are not learning a new pattern.

Handling uploads safely meant virus-scanning customer images when scanning is enabled, using an admin-set scanner path, so untrusted files are checked before they are stored or shown. Giving staff what they need to fulfill meant a popup preview and a zip download of the full customization on every order, so employees can produce exactly what was ordered without chasing details. And deploying on a live store was safe precisely because the extension changes no core files and can be disabled instantly, giving a clean, low-risk rollback rather than a risky core change.

The Result

The outcome is rich product customization that Queenberry gained without any risk to its running store. Employees define branching customization layouts per product with no code. CHOOSE OPTIONS and Customize now make the flow feel built into the store. Staff preview and download exactly what each customer customized. Optional virus scanning checks customer images before they are trusted. The extension installs, disables and uninstalls cleanly, leaving the store intact. And because nothing touches the core, the whole feature could be installed and tested on the live store with an instant rollback.

The extension fits the business because it was built around the client’s real constraint, a live store that must keep working, rather than around the easiest way to ship the feature. If you want to add customization or another substantial feature to a live osCommerce store without risking the core, you can hire PHP developers who build clean, removable extensions, or tell us what you want to add to your store and we will scope it as a self-contained build.

Frequently Asked Questions

Can you add product customization to osCommerce without editing the core?

Yes. This project delivered Amazon-style customization for Queenberry entirely through osCommerce V4’s extension system, so it installs, disables and uninstalls cleanly, leaves no changes in the base code, and lets the store run unchanged with the feature turned off.

What does Amazon-style, branching customization mean here?

It means the options adapt to earlier selections rather than being a flat list of fields, the way Amazon shows a metal color, then a style, then options that depend on both. The admin defines that branching layout, and the storefront popup renders and follows it.

How are customer image uploads kept safe?

When virus scanning is enabled, each uploaded image is checked with the virus scanner at an admin-set path before it is kept, so untrusted files are never trusted blindly. Scanning is optional, so the admin can match it to their environment.

How do staff see what a customer customized?

On the admin order page, each custom product has a popup preview of what the customer created and a link to download the full customization as a zip, so staff can see and produce exactly what was ordered without chasing details.

Is it safe to install the extension on a live store?

Yes. Because the extension changes no core files and can be disabled instantly, it can be installed and tested in the live environment with a clean rollback path, rather than requiring a risky change to the store’s base code.