e-Commerce v4 Goals

You are viewing a wiki page. You are welcome to join the group and then edit it. Be bold!
sime's picture

Very basic summaries, to be fleshed out.

This version has some great new features already, some not listed here. Yet, we need to focus on some bug fixing and making some modules more generic.

e-Commerce 4.0

eC 4.0 beta is planned to be released sometime after the Drupal 6 RC1 (Release Candidate 1).

Address book

  • Improve country/state/postcode checking
  • making it simpler for people add addresses and specify "same as above".

Big clean up

  • Split all modules into separated projects on drupal.org.
  • Formally remove unsupported modules (ie. any module not in the v3 download). (done)
  • Split all admin function of all modules into a new file, reducing the footprint. cart, subproducts, store, products

Charge (former Flexicharge)

  • Rename it as eC Charge.
  • Provide a upgade script to move Flexicharge data to eC Charge. (done)
  • Englobe Tax module.
  • Simplify the module interface.

Customer API

  • Create admin process to allow the conversion of customers between different types. ie. If the site is using e-Commerce and then installs CiviCRM it will convert the existing customers into CiviCRM customers so the transaction information can be viewed in CiviCRM

eC Views

  • Eliminate the module and include the functionality into each module
  • Delete the hardcoded /products page and let the entire job to Views module.

File

  • Fix inumerous bugs
  • Add the support for multiple files
  • Integrate with Parcel and Subproduct modules (currently, they dont work)

Payment module

  • Implement generic callback for when the payment status is changed.
  • Remove "on payment complete" callback in favor of new callback
  • Create Receipting system so that receipts are independent of transactions (done)
  • Remove the Payment module.
  • Convert all payment gateways to the new Receipt system

Product module

  • Convert product types to "plugins" to be applied to a generic product (tangible/shippable, auction, subproduct, file). (there are now product "features")
  • Analyse the possibility of ripping off the "product" node type

Recurring

  • Fix inumerous bugs

Shipping

  • Merge Shipping and Shipcalc. (no more Shipcalc. hook_update() still needed)
  • Smarter shipping options in cart.
  • Avoid conflicts where some items in cart cannot be shipped a certain way.

Store module

  • This will include things like the refactoring of store_transactions_save() and much better hooks for when transactions status's change. (done)
  • Add new hooks hook_transactionapi_pre() and hook_transactionapi_post() so that you can do things before the transaction update, and after the update has finished. (done. see store_transaction_save())
  • Create a transaction cache so that we are not reloading the transaction so many times.
  • Implement generic callback for when there is a change in workflow
  • Create an micro API to let developers and users expand the store overview page with more information. (Overview Widgets feature. Also, eC Dashboards create a series of charts)
  • Implement new function and hook which will return a list of all the roles once the transaction has been completed.

Subproduct module

  • Merge to EC Live Subproducts module. (done)
  • Any node can be an attribute. any product can be (done)
  • Attribute from attributes (done)

Tax API

  • Needed some work for a while.

e-CiviCRM

  • Re-write e-CiviCRM to use the new customer interfaces

Usability Improvements

  • Improve usability by reviewing the checkout process to make sure that it is clear to potential customers and is not overly complex (it relies on receipts module)
  • Review the Ecommerce setup process and configuration organization. Are configuration options too spread out and group in non logical ways? What are there barriers to getting Ecommerce up an running? Can these be fixed without compromising the flexibility of the system?
  • Review Ecommerce transaction workflow from a store administrator perspective. Do things make sense at first glance? Are key options grouped logically?
  • Are there areas where the usability could be improved via additional, niceful degrading AJAX/AHAH or other Javascript enhancments? (Add to cart without reloading the page)
  • Add some icons and images to improve the interface with users

e-Commerce 4.1

eC 4.1 has no release date. It will be some time after the 4.0 version release.

Address book

  • Make changes to allow custom address fields. There is an "profiles as nodes" movement looking at cck driven profiles, this may be the path... however, the actual strategy is not decided. On Hold We will revisit this once we get to Drupal 6.

Charge

  • Weight rate.

Dashboards

  • Include several new dashboards.

File

Payment Gateways

  • Google Checkout official support

Recurring

  • Simplify the setup pages
  • Automatic recurring payments

Shipping

  • Pluggable packaging code (ie. item-grouping) for better shipping prices
  • Local Pickup
  • Free shipping promotion

Store

  • Allow users set what overview widgets they want to see.
  • Create an options API on Overview widgets.
  • Automatic config location settings: measures, currency formats.

Subproduct module

  • Add the attributes that multiply the price, instead sum

e-Commerce 4.2

There is no plans to eC4.2 yet.