I agree that we need to be focusing on what our core requirements are. I started that discussion earlier in another thread, and lots of ideas were thrown into the ring. Some of them were what *I* would consider more phase two items.
Like you said Mike, this is a pretty long list. Below is a copy of that list and I'm going to make my suggestions for what should be in the core program and what should be a plug-ins. Some items I've left un-commented, because I just don't know what to do with them, but don't necessarily feel like they should be in the core.
I'm excited to come to a consensus on the core components so that we can start working on the object model.
If this discussion needs to be had in the wiki, then by all means let's move it there. But above all, lets move on getting a core set of components finalized. :o)
Cheers, Chris
1. *Back-end Admin* 1. User management (CORE) 1. Add, edit, deactivate users (CORE) 2. Inventory Management (CORE) 1. Add/Edit/Delete products in the catalog (CORE) 2. Product image management (CORE) 3. Purchase order creation (Plug-In?) 4. Product forcasting (Plug-In?) 5. Inventory day (What is Inventory Day? Can it be a plug-in?) 6. Quantity changes (perhaps included under Edit Products?) 3. Data Entry 1. Bulk price / data updates from forms or files 2. Bulk item entry from spreadsheets 4. Reporting (Plug-Ins - probably all reporting functions could be plug-ins) 1. Top categories, items 2. Most profitable categories, items 3. Seasonal sales 4. Advertising revenue 5. Affiliate revenue 6. Best customers by sales, profit, segment 5. Fulfillment which includes order processing, receiving and shipping (Core?/Plug-In?) 6. Marketing (if you want to have email blasts integrated with your system) 7. Possible retail point of sale 8. Article / content management 9. Affiliate management (Plug-In?) 10. Data feed management (Froogle, Shopzilla, etc.)(Plug-In?) 11. Banner admin (Plug-In?) 12. Order Management 1. Phone orders (Plug-In? or perhaps a phone rep just creates the order online?) 2. Mail-in orders (Perhaps a store rep just creates orders online based on the mailed in request?) 3. Order changes (CORE) 4. Cancellations (CORE) 5. Address, payment and shipping changes (CORE) 6. Customer notification (CORE) 2. *Registration/authentication *(CORE) 3. *User Admin (meaning the ability for users to manage their own accounts) *(CORE)* * 1. HTML 2. Flex 3. AIR 4. *Product Catalog * 1. Personalization* *(for monograms, engraving) 2. Customizable items (shirt size / color) - This is tough as inventory control says you need to keep count of each style variation. Needs some thought for implementation. 3. Product comparison (Plug-In?) 4. Gift certificates (Plug-In?) 5. Coupons (Plug-In?) 6. Different image displays for items (lightbox, 360 view, popups or on page, etc) (CORE) 7. Robust product search that can make use of verity or real language search or plugins such as the Google appliance. (CORE?/ Plug-In?) 8. Articles about products (CORE) 9. Customer product reviews (CORE) 10. Audio samples (CORE) 11. Downloadable products (CORE) 5. *Shopping Cart* 1. Product up / cross sell 2. Flexible promotions (product and cart based) 3. Add/Edit/Delete cart contents (CORE) 4. Guest Cart (CORE) 5. Member Cart (CORE) 6. *Checkout System* 1. Ability to handle different tax schemes * *(CORE) 2. Purchase orders for credit accounts.* * 7. *Plug-in development. Provide a way for other authors to easily develop plug-ins* 1. payment gateways (CORE) 2. shipping methods (CORE)
------------------------------- END FEATURE LIST ------------------------------------
On 10/18/07, Mike Henke <henkem...@gmail.com> wrote:
> Looks like a lot on the the list. I wonder if it was broke down into > core cfcommerce then bells and whistles :-)
> I agree that we need to be focusing on what our core requirements are. I > started that discussion earlier in another thread, and lots of ideas were > thrown into the ring. Some of them were what *I* would consider more phase > two items.
> Like you said Mike, this is a pretty long list. Below is a copy of that > list and I'm going to make my suggestions for what should be in the core > program and what should be a plug-ins. Some items I've left un-commented, > because I just don't know what to do with them, but don't necessarily feel > like they should be in the core.
> I'm excited to come to a consensus on the core components so that we can > start working on the object model.
> If this discussion needs to be had in the wiki, then by all means let's > move it there. But above all, lets move on getting a core set of components > finalized. :o)
> Cheers, > Chris
> 1. *Back-end Admin* > 1. User management (CORE) > 1. Add, edit, deactivate users (CORE) > 2. Inventory Management (CORE) > 1. Add/Edit/Delete products in the catalog (CORE) > 2. Product image management (CORE) > 3. Purchase order creation (Plug-In?) > 4. Product forcasting (Plug-In?) > 5. Inventory day (What is Inventory Day? Can it be a > plug-in?) > 6. Quantity changes (perhaps included under Edit > Products?) > 3. Data Entry > 1. Bulk price / data updates from forms or files > 2. Bulk item entry from spreadsheets > 4. Reporting (Plug-Ins - probably all reporting functions > could be plug-ins) > 1. Top categories, items > 2. Most profitable categories, items > 3. Seasonal sales > 4. Advertising revenue > 5. Affiliate revenue > 6. Best customers by sales, profit, segment > 5. Fulfillment which includes order processing, > receiving and shipping (Core?/Plug-In?) > 6. Marketing (if you want to have email blasts integrated with > your system) > 7. Possible retail point of sale > 8. Article / content management > 9. Affiliate management (Plug-In?) > 10. Data feed management (Froogle, Shopzilla, etc.)(Plug-In?) > 11. Banner admin (Plug-In?) > 12. Order Management > 1. Phone orders (Plug-In? or perhaps a phone rep just > creates the order online?) > 2. Mail-in orders (Perhaps a store rep just creates > orders online based on the mailed in request?) > 3. Order changes (CORE) > 4. Cancellations (CORE) > 5. Address, payment and shipping changes (CORE) > 6. Customer notification (CORE) > 2. *Registration/authentication *(CORE) > 3. *User Admin (meaning the ability for users to manage their own > accounts) *(CORE)* > * > 1. HTML > 2. Flex > 3. AIR > 4. *Product Catalog * > 1. Personalization* *(for monograms, engraving) > 2. Customizable items (shirt size / color) - This is tough as > inventory control says you need to keep count of each style variation. Needs > some thought for implementation. > 3. Product comparison (Plug-In?) > 4. Gift certificates (Plug-In?) > 5. Coupons (Plug-In?) > 6. Different image displays for items (lightbox, 360 view, > popups or on page, etc) (CORE) > 7. Robust product search that can make use of verity or real > language search or plugins such as the Google appliance. > (CORE?/Plug-In?) > 8. Articles about products (CORE) > 9. Customer product reviews (CORE) > 10. Audio samples (CORE) > 11. Downloadable products (CORE) > 5. *Shopping Cart* > 1. Product up / cross sell > 2. Flexible promotions (product and cart based) > 3. Add/Edit/Delete cart contents (CORE) > 4. Guest Cart (CORE) > 5. Member Cart (CORE) > 6. *Checkout System* > 1. Ability to handle different tax schemes * * (CORE) > 2. Purchase orders for credit accounts.* > * > 7. *Plug-in development. Provide a way for other authors to easily > develop plug-ins* > 1. payment gateways (CORE) > 2. shipping methods (CORE)
> ------------------------------- END FEATURE LIST > ------------------------------------
> On 10/18/07, Mike Henke <henkem...@gmail.com> wrote:
> > Looks like a lot on the the list. I wonder if it was broke down into > > core cfcommerce then bells and whistles :-)
> Okay, I'm an idiot and forgot that Nick moved this list to the wiki, so I > also made updates to that list indicating my suggestions. :o)
> Chris
> On 10/18/07, Chris Jordan <chris.s.jor...@gmail.com> wrote:
> > I agree that we need to be focusing on what our core requirements are. I > > started that discussion earlier in another thread, and lots of ideas were > > thrown into the ring. Some of them were what *I* would consider more phase > > two items.
> > Like you said Mike, this is a pretty long list. Below is a copy of that > > list and I'm going to make my suggestions for what should be in the core > > program and what should be a plug-ins. Some items I've left un-commented, > > because I just don't know what to do with them, but don't necessarily feel > > like they should be in the core.
> > I'm excited to come to a consensus on the core components so that we can > > start working on the object model.
> > If this discussion needs to be had in the wiki, then by all means let's > > move it there. But above all, lets move on getting a core set of components > > finalized. :o)
> > Cheers, > > Chris
> > 1. *Back-end Admin* > > 1. User management (CORE) > > 1. Add, edit, deactivate users (CORE) > > 2. Inventory Management (CORE) > > 1. Add/Edit/Delete products in the catalog (CORE) > > 2. Product image management (CORE) > > 3. Purchase order creation (Plug-In?) > > 4. Product forcasting (Plug-In?) > > 5. Inventory day (What is Inventory Day? Can it be a > > plug-in?) > > 6. Quantity changes (perhaps included under Edit > > Products?) > > 3. Data Entry > > 1. Bulk price / data updates from forms or files > > 2. Bulk item entry from spreadsheets > > 4. Reporting (Plug-Ins - probably all reporting functions > > could be plug-ins) > > 1. Top categories, items > > 2. Most profitable categories, items > > 3. Seasonal sales > > 4. Advertising revenue > > 5. Affiliate revenue > > 6. Best customers by sales, profit, segment > > 5. Fulfillment which includes order processing, > > receiving and shipping (Core?/Plug-In?) > > 6. Marketing (if you want to have email blasts integrated > > with your system) > > 7. Possible retail point of sale > > 8. Article / content management > > 9. Affiliate management (Plug-In?) > > 10. Data feed management (Froogle, Shopzilla, etc.) > > (Plug-In?) > > 11. Banner admin (Plug-In?) > > 12. Order Management > > 1. Phone orders (Plug-In? or perhaps a phone rep just > > creates the order online?) > > 2. Mail-in orders (Perhaps a store rep just creates > > orders online based on the mailed in request?) > > 3. Order changes (CORE) > > 4. Cancellations (CORE) > > 5. Address, payment and shipping changes (CORE) > > 6. Customer notification (CORE) > > 2. *Registration/authentication *(CORE) > > 3. *User Admin (meaning the ability for users to manage their own > > accounts) *(CORE)* > > * > > 1. HTML > > 2. Flex > > 3. AIR > > 4. *Product Catalog * > > 1. Personalization* *(for monograms, engraving) > > 2. Customizable items (shirt size / color) - This is tough > > as inventory control says you need to keep count of each style variation. > > Needs some thought for implementation. > > 3. Product comparison (Plug-In?) > > 4. Gift certificates (Plug-In?) > > 5. Coupons (Plug-In?) > > 6. Different image displays for items (lightbox, 360 view, > > popups or on page, etc) (CORE) > > 7. Robust product search that can make use of verity or real > > language search or plugins such as the Google appliance. > > (CORE?/Plug-In?) > > 8. Articles about products (CORE) > > 9. Customer product reviews (CORE) > > 10. Audio samples (CORE) > > 11. Downloadable products (CORE) > > 5. *Shopping Cart* > > 1. Product up / cross sell > > 2. Flexible promotions (product and cart based) > > 3. Add/Edit/Delete cart contents (CORE) > > 4. Guest Cart (CORE) > > 5. Member Cart (CORE) > > 6. *Checkout System* > > 1. Ability to handle different tax schemes * * (CORE) > > 2. Purchase orders for credit accounts.* > > * > > 7. *Plug-in development. Provide a way for other authors to easily > > develop plug-ins* > > 1. payment gateways (CORE) > > 2. shipping methods (CORE)
> > ------------------------------- END FEATURE LIST > > ------------------------------------
> > On 10/18/07, Mike Henke <henkem...@gmail.com> wrote:
> > > Looks like a lot on the the list. I wonder if it was broke down into > > > core cfcommerce then bells and whistles :-)
I think that reporting and exporting data into spreadsheets at the least should be part of the core. A Quickbook export feature could be a plug in. Apart from building a good cart model, we should be encouraging good business practices. Without reporting, a business is flying blind.
Inventory Day is when you do inventory of your stock on hand. At our company we set all quantities to zero, add up everything that we have on hand manually then the system automatically goes through any open orders to deduct quantities and confirms that everything we need is on purchase orders to vendors. Then it spits out a before and after report to give us our inventory variance.
Product forecasting is when the system has the ability to predict future sales based on past data and adds those quantities to purchase orders automatically. This could be a stub in the core that would take any algorithm cfc that you want to use - or none at all if you only want to order for immediate need.
A basic verity search would be a good core option with plugins to do some fancier stuff like relevancy and segmentation.
Purchase orders and credit accounts for b2b could be a plug in but should be considered throughout design because there are many places that get touched by payment methods and billing.
We should also add wish lists and registries in as plug ins. Maybe with an rss feed option?
I really feel like all reports should be plug-ins. That doesn't mean that the program wouldn't have some stock reports installed out-of-the-box, but the user should be able to add and remove reports at will (imo) upto and including no reports at all.
Product forecasting just seems like something that not everyone will need. It seems to me like something that larger companies might want. Again, I think it should be a plug-in that can be installed and un-installed at will.
I know that I really dislike when I'm looking for a piece of software to do something really simple, and instead all I can find are applications that have a bunch of stuff crammed into them. That's why I think the plug-in idea is a good one. Out-of-the-box, the application can be very simple, and then the user can customize as they need by adding simple configurable plug-ins.
I completely agree that a basic search should be part of the core.
I also think I agree that some things that will be plug-ins should be in the back of our minds as we design and develop. Honestly, I'm still thinking about how plug-in development might work. What hooks the core will have for plug-in developers to make use of.
Thoughts?
Chris
On 10/19/07, athanasiusrc <webmas...@aquinasandmore.com> wrote:
> I think that reporting and exporting data into spreadsheets at the > least should be part of the core. A Quickbook export feature could be > a plug in. Apart from building a good cart model, we should be > encouraging good business practices. Without reporting, a business is > flying blind.
> Inventory Day is when you do inventory of your stock on hand. At our > company we set all quantities to zero, add up everything that we have > on hand manually then the system automatically goes through any open > orders to deduct quantities and confirms that everything we need is on > purchase orders to vendors. Then it spits out a before and after > report to give us our inventory variance.
> Product forecasting is when the system has the ability to predict > future sales based on past data and adds those quantities to purchase > orders automatically. This could be a stub in the core that would take > any algorithm cfc that you want to use - or none at all if you only > want to order for immediate need.
> A basic verity search would be a good core option with plugins to do > some fancier stuff like relevancy and segmentation.
> Purchase orders and credit accounts for b2b could be a plug in but > should be considered throughout design because there are many places > that get touched by payment methods and billing.
> We should also add wish lists and registries in as plug ins. Maybe > with an rss feed option?
> I really feel like all reports should be plug-ins. That doesn't mean that > the program wouldn't have some stock reports installed out-of-the-box, but > the user should be able to add and remove reports at will (imo) upto and > including no reports at all.
> Product forecasting just seems like something that not everyone will need. > It seems to me like something that larger companies might want. Again, I > think it should be a plug-in that can be installed and un-installed at will.
> I know that I really dislike when I'm looking for a piece of software to > do something really simple, and instead all I can find are applications that > have a bunch of stuff crammed into them. That's why I think the plug-in idea > is a good one. Out-of-the-box, the application can be very simple, and then > the user can customize as they need by adding simple configurable plug-ins.
> I completely agree that a basic search should be part of the core.
> I also think I agree that some things that will be plug-ins should be in > the back of our minds as we design and develop. Honestly, I'm still thinking > about how plug-in development might work. What hooks the core will have for > plug-in developers to make use of.
> Thoughts?
> Chris
> On 10/19/07, athanasiusrc <webmas...@aquinasandmore.com> wrote:
> > I think that reporting and exporting data into spreadsheets at the > > least should be part of the core. A Quickbook export feature could be > > a plug in. Apart from building a good cart model, we should be > > encouraging good business practices. Without reporting, a business is > > flying blind.
> > Inventory Day is when you do inventory of your stock on hand. At our > > company we set all quantities to zero, add up everything that we have > > on hand manually then the system automatically goes through any open > > orders to deduct quantities and confirms that everything we need is on > > purchase orders to vendors. Then it spits out a before and after > > report to give us our inventory variance.
> > Product forecasting is when the system has the ability to predict > > future sales based on past data and adds those quantities to purchase > > orders automatically. This could be a stub in the core that would take > > any algorithm cfc that you want to use - or none at all if you only > > want to order for immediate need.
> > A basic verity search would be a good core option with plugins to do > > some fancier stuff like relevancy and segmentation.
> > Purchase orders and credit accounts for b2b could be a plug in but > > should be considered throughout design because there are many places > > that get touched by payment methods and billing.
> > We should also add wish lists and registries in as plug ins. Maybe > > with an rss feed option?
|
