shopping cart - which method?

[dila125]

Hi,

Using PHP 5/MySQL 4.1/IIS6

Currently our shopping cart systems stores the cart data in session variables, and the order is only stored in the mysql database once the shopper proceeds through the checkout and clicks the final button to confirm their purchase.

I am considering changing the way our cart works, so that all basket data is also stored in a database table with the following fields for example:

autonumber, sessionID, itemID, itemQty, dateAdded

Does anyone have any thoughts on the advantages/disadvantages of each method? Are then other methods?

[Roger_Ramjet]

The main advantage of storing the cart data in a table is that it will still be there if the user leaves your site:kills the session and then returns. Could be a much more user-friendly system that way.

You could also use the data to gather some statisticss about what users considered purchasing but did not. And what they did purchase after comparison shopping: they came back for it after all.

[dila125]

Thanks for the reply.

I am wondering what I would need to do to have a setup as you described. I was thinking about using the PHP session ID to link basket items to users, but I can't see how this would work if the browser was closed and the session killed.

Would I need to add another field to the table to store a userID, and then have this userID also stored in a cookie to link users to baskets when they return to the site?

[camowel]

you could have users log in, or try storing it using the user's IP address,

it may also help (since it is shopping cart, money is involved users may view loosing their data as a lack of security) to keep track of users more than one way, for example, using cookies as the primary way to keep track of a user's ID, but also have IP addresses stored in case they delete their cookies, so you can use that to re-set the cookie

hope that helps a bit 🙂

[Roger_Ramjet]

Except that many people get dynamic IPs or use ISP with a proxy. Never try to rely on IP for individual identity it is too fraught. Just imagine their reaction if you showed them someone elses details cos they had a dynamic IP - they're gonna think you are showing their details to other people????

Forcing people to login is the BIGGEST turnoff a site can have. My football team does that for parts of it's site so I just don't go there very often.

Just set a cookie like eg Amazon does. Then you can welcome them back with their name etc if they registered, or just show them their cart if they did not bother.

If they know enough to delete cookies then they know that this will kill site-recognition as well.