Search the Community
Showing results for tags 'store account'.
Found 1 result
Recently Ive been developing a very large addon for store owners to allow their employess to use without having to give them access to the store admin. A employee may view and process orders, email customers, create customer accounts, edit ordrs, and take orders over the phone using its own built in checkout process. Orders can be made for existing customers or strictly guest. Anyhow, while using the mod, it dawned on me that I had esencially created a method of making guest orders for customers that call in and do not want an account. Any order took this way goes into a customer account that is stricly owned by the store, and the address books can be set to a higher number than the regular customer accounts. So I was wondering, with the couple of guest checkouts available, - 1 deletes customer info after checkout, the other flags it as guest and allows the guest to become customer later. I think for guest you should not keep account data if you tell them they are a guest! Why not create a simple flow for guest that is very unintrusive to the core code by: 1) Have a select guest option - when initiated a session is set, lets call it guest_order. If guest_order is set, then the customer_id is the same as the stores customer account. 2) After setting the session, the guest is then directed to the store's customer accounts address book process where they enter their address, with the session set there will also be two more fields in the address book, phone and email. 3) After filling out complete address info, then two more sessions are set for phone and email, they would work very much like the comments session. 4) Customer goes throught the checkout and when checkout_process is initiated it takes the session info for phone and email and inserts it rather than the stores defualt info. Then it clears the phone and email session. - Probably delete any address book entries made as well. But thats another area that would be handled by session assignment as well. 5) On checkout success guest_order session is cleared, order is done, customer can move on. All the while the guest_order session is set certian things need to be disabled, such as access to account areas. Most of this could all be done using a header tag module. The checkout process would need some editing to tell it if guest_phone/guest_email exist then insert this else default. Unless it is possible to override it with a header tag module - but I dont think so. Overall a lot less code changes, no database changes, and orders page would have all the info needed for contacting customer. So far as I can figure in this scenario, - only 2 to 4 core files to change. Or 1 file, checkout_process, and then add new files for the address book/checkout new address selections. Thoughts?