Our powerstore solution has inventory control and uses eCart. eCart has the capacity for inventory control now, but inventory and control of it is a back end concept and eCart doesn't really go there at all. Having said that, we agree and we plan on working toward that direction.
The problem with inventory control and options, two of the largest feature requests for ecart, is that they are so dependent on the database. The database queries, database structure, and administrative back end become more important and difficult to create. In fact, the most difficult aspects to inventory control are writing your SQL queries, conceptualizing the database, and creating the administrative interface and have nothing to do with the eCart or any of its functionality.
Currently our solution is to use DataAssist for creating the Administrative back and and the Catalog. Since that is where the difficulty in inventory control exists, we would probably have to account for it there, and since the most difficult task is writing the SQL statements, it is kind of hard to actually include this as a feature at all.
Really it becomes an education task to help people understand the database design and queries necessary to make it work with our current tools.
Another approach that we may take in the long run is to include DataAssist with eCart and create a catalog builder and product admin builder. If you could build a catalog with inventory control and an administrative section to update inventory, eCart functionality really isn't and wouldn't be the problem.
Our eventual solution will probably involve a combination of dataAssist, siteAssist, and eCart as well as all of our other products, so that they can work together to create an entire store. Currently the powerstore is an example of what we hope that wizard might create. It will continue to evolve and we will continue to work toward creating wizards so that users can more easily create these complex solutions on their own.
These are the problems we are working on. The problem isn't convincing us that we want inventory control or options to be easy for our users, we all agree those are features that would be great to have. The problem is how to implement them and figuring out what exactly the missing pieces are.
In my opinion the most difficult task in inventory control is writing the SQL query in the DW Recordset. If we want to make that easier outside of education then we may need to rewrite the Recordset... anyway it is a complex problem, and one that we are very educated on and aware of.
We need to put all of our tools together to make a beginning to end product. We plan on making that happen, but it will still take years before that vision is complete.