Forum Moderators: buckworks
I just had a template designed for an online store i'm developing. The template includes a main index page, a subpage (with product listings), and a "catalogue" page (where the individual product description is).
Which shopping carts could I use which would allow fairly seemless integration with the above?
Andrew.
The products i'm selling will likely be on a continual basis - i.e// no turnaround. I will sell them indefinately (until my ecommece store closes down).
The template i have is coded in simple HTML + CSS, so hopefully this could mold to most shopping carts...no?
Finally, I do not want "advanced" functionality... i want something simple. VERY Simple:
1. Can calculate sales tax at a certain provicne.
2. Shipping Calculor (fixed at % of every purchase)
3. Simple Inventory Management.
That's about it. Simple, easy, fast...and most importantly, i can integrate it into my design.
Anyone have such suggestions, or where i can start looking?
Andrew.
If you happen to want Perl code and plan to use PayPal let me know and I'll write a script for you. (Or maybe I'll write it anyway; could be fun.)
By different look, i mean for the main page it ill just be a nice clean look, while the subpage will have the menu on the left (as will the product page)...
Andrew.
For fully functional carts like X-Cart, osCommerce, etc you'll need to dig into the code and change their templates to what you want. You can't simply apply your template - unfortunately.
It sounds like what you need is more of the back end - the actual cart (as oppossed to a catalog/cart combo like X-Cart and osCommerce provide). You may be able to strip what you need from the ecommercetemplates or from a freely available cart script someplace. In either case, you'll need to do some code work to make your stuff blend with whatever you use. Here're a few free PHP carts [google.com] you can download and dig into to learn how they built the actual cart.
things to know, no matter who makes it..
any form submited is a potential hazard.
any url varaible is a potential hazard.
any cookie read is a potential hazard.
so test the snot out of a new script that your thinking about using.