First of all, a special thank you to you and your team for providing what may become the most important module ever developed for DotNetNuke.  Kudos for a job well done!

I would like to contribute one simple suggestion before this forum explodes with excitement and enthusiasm…

Please do not implement every possible enhancement request for the module.

An extensible API is by far the best way to go, especially if you can hook functionality at different stages during ordering and processing.

Until today, every shopping cart developed for DotNetNuke has grown into an unmanageable mass of features and possibilities. Often based on single requests, the feature and enhancement list ends up being the bug list instead. Combined with the complexity of conflicting systems including rebates, discounts, product and pricing options and tax collection systems, you end up with a system that is extremely difficult to operate as a store owner, or an end user.

Your project team does not need to spend sleepless nights writing code that will rarely be used. We will not have to spend countless hours removing functionality just to get it to work. For those who need specific functionality they can do it themselves or hire someone to complete the task.

Consider this clever wisdom that comes from a scene in Star Trek where Spock rasps “It is logical. The needs of the many outweigh the needs of the few.”

“Or the one.” Kirk finishes.

I am hoping that this simple advice at the get go will offer the greatest reward for the entire DotNetNuke community.

Thanks again for your awesome contribution with the Store module.  We really appreciate this beta release and are looking forward to a final release whenever your team is ready!

Certainly some good advice from Dwayne, but I still believe there are a number of solid enhancements that people have been requesting in these forums that can benefit "the many". I agree that getting into too many advanced features will result in a difficult to implement Store and that support for APIs is an excellent way to go. However, lets remember that not everyone is capable or financially able to have the Store module customized to add in some of the enhancements that would make this Store extremely usable. The Store module is a fantastic starting point and with some well thought out enhancements can still be kept simple and powerful out of the box.

Keep up the great work!

Richard

I wrote a post very early on related to make the Store module rely on an API in order to avoid having a large module that can't please everyone no matter how many features in includes. I suggested breaking out the shopping cart from the rest of the module. Anyhow, I have a very good suggestion that will ease defining an API and will give a very strong combination of DNN modules :o).

Start with the Repository module. Give an option to the Repository module to submit its objects to the Shopping cart. This will work as a base to create product feed API, as well as give ppl that uses the Repository module an option to sell their stuff. All payment transaction is managed by the Shopping cart, and authorization is based on the payment reported by the Shopping cart upon request.

This is a start, but opens a series of opportunities for the DNN module community!

Cheers,
/Rob