Jump to content
Larry Ullman's Book Forums


  • Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by CCroxton

  1. If you are looking at shopping cart packages, they come in 2 basic versions: 1) you have to use someone else's server 2) you can use your own server or your own hosting company. If you choose a package that is only hosted on the supplier's servers, then what happens if you want to do something that they do not already have provisions for? Say for example you have developed this beautiful site, excellent content, and now you want to provide feeds to the shopping engines (multi-channel commerce). If the cart company does not offer this service, chances are excellent that they will not allow you to store any of your own scripts on the site. This leaves you with 2 choices to get your multi-channel project accomplished: 1) pay whatever their development fees are for them to write the scripts, make cron jobs, etc. Be aware that you might have to provide all the requirements to the company, even though they are charging you a very stiff fee. 2) use an outside multi-channel company that has already developed the multi-channel scripts, and hope that they are compatible with the shopping cart host you chose. If not, then again you will be paying someone to write a custom interface. If you choose to use a hosting company, do your research carefully first. Do they allow stored procedures? Cron jobs? What about backups? How hard is it get support? Most hosting companies do not support applications or scripts written by others. They guarantee their servers will run, and often that is it. If your site totally crashes, even on Christmas day, is there someone you can call, or is it just a trouble ticket system, that might not get answered until the holiday weekend is over? If you choose to use your own server, then you REALLY need to be careful, especially for ecommerce. Do your research on PCI compliance especially. To really be compliant, you should rent a bank box and store the backups there. Banks have the fire protection, theft protection, etc. You will need UPS systems, halon fire extinguisher, ready access to the server after hours, and no, there is no support team, just you and your team. Whatever route you go, look carefully at MANY sites before deciding what you want. Do you want wish lists, tell a friend, mobile compatible, FAQ section, products can be available in more than 1 category at the same time, related products, similar products, substitute products, gee whiz add-ons that really don't relate to the product, but are fast sellers and make extra money? (Think gum and candy and magazines at the grocery store checkout lines.) Think about software you use daily, and have to put up with limitations. If you are selling serialized products, or bundles, or products with expiration dates, look very closely at what canned packages have to offer, because most of them will not handle these things gracefully, if at all. Above all, think about automation. Assuming your site is successful, will your package interface with your accounting system, or does it have one of its own? If one is supplied, does it handle all the functions you need, including receivables, payables, inventory, shrinkage, sale prices, etc.? If you also have a physical store, does your package include point of sale, so the inventory stays synchronized? Will the cart package handle shipping, including printing labels, allowing for various shipping methods, acquiring the actual weight from the scales in the shipping area? Will it print pick lists and packing lists? Will it tell you when you are low on products, and what to reorder? What kind of reports does it offer, vs what you will need? Plan everything out on paper first. Design it on graph paper. Design the database with the fields you think you will want, and then run some sample data through, still on paper. You might discover that what you thought was an outstanding design is missing several things when you really go to put it in action. Write down the pros and cons of every site you visit. Don't just look at clothing stores if you are going to sell clothing; look at all kinds of stores, geared to all types of buyers. Check out the major retailers, like Amazon, ToyRUs, JCPenney, Sears, etc. What (in your opinion) could be improved to make things easier for a customer? Always look at the front end from a customer's view point. How hard is it to find what you want? More than 3 clicks, and most people go away. Always look at the back end from the attitude that this is supposed to solve your problems, not create them. If you have to update or enter things into multiple systems to get the order, pick it, pack it, ship it, invoice it, and support it, then you will not be able to keep up with a system that generates very many orders each day. Even if you hire staff to do these jobs, how much could you have saved by using software that automated the job? Remember the more times something is entered into different systems, the more chances for errors.
  2. You might want to think along totally different lines. In a clothing store or Wal-Mart, each different item has a unique UPC code, so the store knows what to reorder and what is sold very easily. Yes, this means making 50 product IDs for a pair of jeans in 10 sizes and 5 colors, but then you know EXACTLY what is selling and what to reorder. Unless you are having the products drop-shipped, then inventory costs can be very high, and fashions change quickly. If you use 1 main product ID with variants for size and color, then you can easily associate all the "Farmer John" jeans of the various sizes and colors on one page, and all the "Slim Capri" jeans would show on another page. But you will get more back end info by using categories such as Overalls and Capris, using a separate SKU for each item, and then making a landing page that uses a bit of php code to populate the page based on given parameters. This would also allow you to group all the Farmers Johns on one page, and get better control of your stock, what is selling, what needs to be re-ordered, etc. Look online at various stores that carry clothing, such as Wal-Mart, Sears, JCPenney, Land's End, Brooks Brothers, etc. Pay close attention to how easy it is to find what you are looking for. What kinds of filters would make the search easier? By price, by color, by size, by body type, by waist or inseam size, think of all the possibilities! Of course, this means you have to code all this info into the db, but once done, you will have a very solid back end that will allow you to change the look and feel of your site very easily. Be careful about locking yourself into only one category per item. If you later decide to have a "Sale" or "Clearance" category, then you have to make a choice of showing the item under clearance or the usual category, but not both. The same holds true if you want to use categories like "heavy duty work wear" and "overalls"; how would you fit these overalls into both categories? Clothing is very seasonal, so you might want to think about changing the theme of you site periodically to reflect the changing seasons, various holidays or patriotic events, etc. This would usually indicate featuring something in particular, such as all green clothing on sale for St. Patrick's Day.
  3. Having used Magento for the past year, and OSCommerce and derivatives of it for several years previous, I can tell you something about the limits of using canned software, even if it is opensource. OSCommerce was begun years ago, and is stable, but is not PCI compliant. Magento is PCI compliant, but there is a scripting bug in it somewhere, and people can put comments on my site without logging in. If you want the cart to do something it does not, then you can search for a module (paid or free), install it, and pray for the best. Of course you backup the entire server first, before installing on a live application. If the module does not work, then you have 3 choices: 1) try and figure out what line(s) in the code someone else wrote and probably did not comment very well went wrong 2) try and write your own code to interface with the base software, or 3) hire a programmer to make it work or write you a new one. If no module exists that does what you want, then you have the bottom 2 choices again. On the plus side, there are very active forums for both, lots of modules, and people in the US that can install scripts and make them work for the reasonable fee of abt $50. Magento will pester you with ads and emails periodically to upgrade to their paid hosted version. Both carts will periodically inform you of security issues that need to be addressed. BE AWARE that if you have installed additional modules, the upgrades MIGHT crash your site. Not all modules were written well enough to take code upgrades gracefully. The reason I bought this book is because I am tired of the limitations of canned software and the modules that are available, and I want to know WHY something crashes when it does, and how to fix it. I want to build a site based on extensible modules and solid code, not use code that was started 12+ years ago and cobbled together again and again as holes were found. Having spent over $10K to get open source projects to meld together and produce what I want accomplished, only to have the whole thing crash a month after the programmers signed off, I never want to be in the spot again that my income is dependent on something that someone else did. If it fails, I will learn how to fix it, and I will have the code and the knowledge, because I learned it from the ground up. In short, knowledge is power, and even if I only build 1 or 2 sites, I will know what I am doing, and how to build my own improvements.
  4. Never mind, I found the answer! The keyboard was set to US International, instead of US, so the single quotes and double quotes were not working correctly. Changing the keyboard type to US and doing s system wide application solved the problem.
  5. Hi Larry, I love the book, but none of the scripts will run! I have PHP Version 5.2.6-2ubuntu4.6 loaded, and I am trying to work with the content management application in Chapter 12. The HTML runs fine, but I get errors like Parse error: syntax error, unexpected '/' in /var/www/index.php on line 3 when I try to run the scripts. Unfortunately, I am new enough at PHP that I have no clue what to do from here! If I delete the . then I get overflow by 0. If I delete the / then I get file not found header.html and footer.html. Am I the only one with these difficulties? I looked at the TOC for your more recent books, but none of them seem to have this application, and it is one I really need to develop! Thank you!
  • Create New...