
Building a shopping cart from scratch is something I could do if I really wanted to, but why re-invent the wheel they say? To create a system which you could just drop in to a new site and be up and running is an undertaking of pretty immense proportions. For that reason, two years ago I chose the open-source solution of osCommerce.
As you may know open-source is your friend, and after dealing with drupal, joomla (mambo), wordpress etc… the same kind of set up is evident in these shopping carts we will talk about today. There are obvious differences in naming schemes and organization but on a whole the idea behind each one is similar so its easy to pick apart an osCommerce if you have a history with other open source projects.
To provide you background my job required me to build or get up and running a shopping cart for a host of different products that also entailed a pretty hectic / varied order fulfillment and purchasing scheme. I searched for a while for the right product, looked at zen cart, a drop-in addition to Drupal, and a few others but settled on osCommerce.
osCommerce : A Post-Use Review
Out of the box osCommerce installed with ease if you have done that sort of thing before, and there were few problems with initial set-up and skinning. However, integration with shipping and payment services took a little bit more effort than I would have liked, the modules took a good deal of reading about to get going. Some of this is par for the course for getting acquainted with a particular piece of software but I did struggle with parts of the system as I bent them to suit my needs.
Design-wise osCommerce is very Web 1.0 and lacks that special pizzaz I wanted. After a complete re-skinning, and butchering of the site’s code to make it work for my particular project, a decent result was established but with the downside being upgrading past that point to a new generation of code would be next to impossible.
Let me touch on the design for one more second… unlike most systems you actually have to install a templating extension if you want to do anything really revolutionary with the code, it wasn’t built in with the ability to change very easily. Still even after that, one osCommerce site looks like another without taking every piece apart and reassembling it on your own. That almost defeats the purpose of using an out of the box system if it takes that much set-up and configuring to complete the job.
Finally the administration side is built with one thing on its mind. Displaying your data in the most boring ways possible and making it impossible for the non-web designers to navigate. Trying to explain the system to my boss or anyone who wanted to maintain it normally resulted in stares, and not because these people aren’t savvy enough to pick up a storefront administration but because it was cumbersome and awkward and didn’t work like you would think it should. If your gonna be passing on osCommerce to the unfamiliar be forewarned, write documentation.
When the site was up… it worked. It maintained customer and purchase data, made orders work, organized my products, displayed them properly and made some money for the company. Still, it was just a store and nothing special, I was not over whelmed or disappointed just content to let it sit there.

Bear in mind that this was 6-9 months ago and software changes, but my interaction with open source e-commerce started off pretty boring.
Stay tuned for Part 2 where I recommend my new favorite toy…..