Our code sprint at the end of June resulted in an abundance of tickets for outstanding development on existing systems and projected improvements to checkout to accommodate the payment system. Several of these include UI mock-ups provided by Bojhan for us to work towards. We also planned out the payment implementation as much as possible, considering different payment workflows (CC on site, hosted payment, hosted checkout, etc.) and payment information security. There were also certain items that we tabled for future discussion, like the implementation of shipping and taxes.

Tangibly, this discussion and development boils down to two things. First, there's a fine queue of issues tagged dcsprint3 in the d.o tracker to complete. Second, we have the following roadmap for development leading up to DrupalCon Copenhagen:

After DrupalCamp Colorado, we'll be flying back to the Commerce Guys office in Jackson, MI for a Drupal Commerce sprint. We'll be traveling Monday June 28, so the sprint will be Tuesday through Friday, June 29 - July 2. DamZ and bojhan will be joining us from Europe, and it looks like we'll have mfer for a day.

If you're interested in joining us, let us know so we can work out travel arrangements from the airport in Detroit and lodging in Jackson. I'm looking forward to a productive week after an extended weekend of hacking and brainstorming in Denver.

Prior to the sprint we'll post a list of high priority issues for our time together. This is bound to include further work on the Rules based price handler and completion of the critical Addressfield module.

Those wishing to pitch in virtually can also keep the low-hanging fruit issue queue handy. We've had some good participation in there this past week and I'm eager to see it pick up.

I'll be heading to DrupalCamp Colorado with some of the other Commerce Guys to present the current status of Drupal Commerce, promote the project, and collaborate with other Drupallers there. We went last year in a combined DrupalCamp / Ubercamp, and the e-commerce focus of the camp was very well received. Hopefully we can repeat the success and get some other contributors to show up... or find new contributors while we're there!

If you're interested, the camp is in Denver, CO on June 26-27th. The price of the event is dirt cheap, and we'll be hanging out around town the day before. I'd love to do a Commerce sprint while we're there, and I'd encourage anyone interested in presenting Drupal Commerce or general e-commerce sessions to do so!

Comment here if you're thinking of going so we can coordinate our time in town.

What follows is a rough summary of our conception of orders on Drupal 7. This brainstorming began in October at the first San Francisco sprint, and we spent a lot of time on Monday in Paris hashing out the details. There's still plenty more to consider, so feel free to speak up!

Order Summary

Like Products, Orders in Drupal Commerce are top-level fieldable entities. Unlike Products, we are initially supporting only a single Order Type, but this in no way limits the ability of contributed modules to alter in support for multiple Order Types.

Overview

Unfortunately pricing is not as simple as a decimal, because the price stored with a product is simply a starting point. By the time a customer completes checkout, the price may have discounts, fees, taxes, and nearly unlimited unforeseen modifications. In order to handle the wide variety of pricing models, taxes, and other price alterations, we must create a well defined, flexible price system.