Re: [WebDNA] Re: shopping sites and the "old commerce tags"

This WebDNA talk-list message is from

2012


It keeps the original formatting.
numero = 108704
interpreted = N
texte = > It would be nice if someone would build a new shopping > system that does not rely on commerce tags... Several months ago I rewrote one of my client's sites, previously a typical WebDNA eCommerce site. I did the whole thing using cookies and his products.db. No cart files were created, and the only time anything gets written to his orders.db is when the customer clicks the final purchase button. Until then everything is stored in cookies. This is a great system because only fulfilled orders are stored in the orders.db. Incomplete orders remain in the customer's persistent shopping cart -- which is never emptied unless he completes his order, removes items manually, or deletes his cookies. The system works really well, but it is a very customized system. The whole reason I created it was to break out of the frustrating limitations of the old WebDNA commerce framework so I could easily and efficiently add unique features the old system did not offer. It is very frustrating to have to deal with a file-based system where you cannot even use your own field names! I agree that what you're suggesting would be nice. But at the same time I disagree with your claim that a new commerce system would sell here. Instead I seriously doubt that more than a handful of copies could be sold in a year's time, and even those 5 sales would likely depend heavily upon the price ... My guess is that $200 would probably be the maximum most would pay before they start complaining about the price. I can hear it now: "Well, if you offered features X, Y and Z I would pay up to $300 or maybe even $500, but only if I can duplicate your system and use a separate copy on each of my client's websites -- at no additional cost of course!" So basically I cannot imagine most WebDNA programmers spending more than a couple hundred bucks for something like a new commerce system -- nor can I imagine selling anywhere near 100 copies during the first few years. Yet selling at least 100 copies a year would likely be necessary if the creation of such a new eCommerce system were to be done (and supported on an ongoing basis) as a profitable business venture. > A new system just needs to be basic ... Sorry to disagree again, but I think that just the opposite is true. I do not believe that anyone will be "weaned off" the old shopping cart / order file system until a new replacement system offers all the features of the old system ... and much much more. Sincerely, Kenneth Grome WebDNA Solutions http://www.webdnasolutions.com WebDNA Programming and Linux Server Administration Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] shopping sites and the "old commerce tags" (Rob 2012)
> It would be nice if someone would build a new shopping > system that does not rely on commerce tags... Several months ago I rewrote one of my client's sites, previously a typical WebDNA eCommerce site. I did the whole thing using cookies and his products.db. No cart files were created, and the only time anything gets written to his orders.db is when the customer clicks the final purchase button. Until then everything is stored in cookies. This is a great system because only fulfilled orders are stored in the orders.db. Incomplete orders remain in the customer's persistent shopping cart -- which is never emptied unless he completes his order, removes items manually, or deletes his cookies. The system works really well, but it is a very customized system. The whole reason I created it was to break out of the frustrating limitations of the old WebDNA commerce framework so I could easily and efficiently add unique features the old system did not offer. It is very frustrating to have to deal with a file-based system where you cannot even use your own field names! I agree that what you're suggesting would be nice. But at the same time I disagree with your claim that a new commerce system would sell here. Instead I seriously doubt that more than a handful of copies could be sold in a year's time, and even those 5 sales would likely depend heavily upon the price ... My guess is that $200 would probably be the maximum most would pay before they start complaining about the price. I can hear it now: "Well, if you offered features X, Y and Z I would pay up to $300 or maybe even $500, but only if I can duplicate your system and use a separate copy on each of my client's websites -- at no additional cost of course!" So basically I cannot imagine most WebDNA programmers spending more than a couple hundred bucks for something like a new commerce system -- nor can I imagine selling anywhere near 100 copies during the first few years. Yet selling at least 100 copies a year would likely be necessary if the creation of such a new eCommerce system were to be done (and supported on an ongoing basis) as a profitable business venture. > A new system just needs to be basic ... Sorry to disagree again, but I think that just the opposite is true. I do not believe that anyone will be "weaned off" the old shopping cart / order file system until a new replacement system offers all the features of the old system ... and much much more. Sincerely, Kenneth Grome WebDNA Solutions http://www.webdnasolutions.com WebDNA Programming and Linux Server Administration WebDNA Solutions

DOWNLOAD WEBDNA NOW!

Top Articles:

Talk List

The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...

Related Readings:

[WebDNA] Processor Maxing out (2010) HTML encoding in URLs (1997) [WebDNA] fastcgi 7+ & [cart]? (2010) WebCatalog dying in WebTen (1998) Webcat run amuk (2002) I'm having trouble using [url][interpret][math] together in lookup (1997) Three new problems, maybe a fourth (1997) Unanswered trigger questions ... (2003) Help--WebCat setup (2000) Going to anchors within a template page (1997) Re:Remote stockroom ? (1998) AuthorizeNet Declines (2005) Help! WebCat2 bug (1997) user/password validation (1998) Variables for chat (1997) WebCat2.0 [format thousands .0f] no go (1997) [WebDNA] Search question (2013) [lookup] speed sales pitch (2003) Format all of a sudden doesn't work (1997) Authorizenet and expiration dates (2002)