This project is read-only.

Ecommerce Module to Orchard

Topics: Announcements
Sep 26, 2012 at 4:21 PM
Edited Sep 27, 2012 at 4:07 AM

Ecommerce Module to Orchard
This is Ecommerce Module to Orchard based on SkyWalker's excellent serial blogs.


if u want to expand the function of the project, u r warmly welcomed to join.

Sep 30, 2012 at 10:45 PM

How about contributing to Nwazet.Commerce, also derived from Sipke's code?

Oct 1, 2012 at 4:58 PM


I follow the differents steps from the tutorial.

I confirm step1 to 7 worked perfectly!!

Really a good manner to understand how Orchard works.

I realize the important place of Dynamic and Clay. 

Too many things to learn in a really short time, not really easy to understand clearly the orchard code (dynamic, func, action, generic etc).

I am really impress :)

Best regards,


Oct 1, 2012 at 7:26 PM
bertrandleroy wrote:

How about contributing to Nwazet.Commerce, also derived from Sipke's code?

You should put a URL to the repository Bertrand!! But this time only I will do it for you...

Oct 6, 2012 at 6:48 PM
Edited Oct 6, 2012 at 6:51 PM

hi guys:

i have created   a repo. on

what should i do next? I think we can link the two repos between diff. accounts according to bitbucket.

Oct 10, 2012 at 1:55 AM

You can configure TortoiseHg to have two distant repositories and push/pull from both, and merge on your dev box.

Oct 15, 2012 at 8:52 PM

I have a kind of merge of skywalkerwebshop and Nwazet.Commerce.

Genarally, there are:

  • 4/3. steps checkout. Shipping method, Payment method, Order creation, Proceed to pay.
  • Order management and customer management (Most of it taken from skywalkerwebshop)
  • Payment is done similar ways as Nwazet.Commerce shipping method.
  • There is no customer record - I'm using UserPart, Customer is just a role.
  • Very simple cart widget. Similar to Nwazet.Commerce, but without ajax calls.
  • Some messaging, roles, permissions are done.

Bad things are that:

  • It is relatively hard to extend with other methods (shipment/payment). (at least it need content part, controller and views). Code generation might help here.
  • Paid SMS notifications, Vouchers or Discount rules, Stock are hard to extend without touching the core.
  • Models are building frontend shape. Which of course not a nice way.
  • It is not yet tested in live.

If somebody is interested to help. I'll share the code in codeplex.

Oct 15, 2012 at 9:13 PM

HI ikutsin:

Nice job, thanks

I have already added you as coordinator , hope to share with you.

you can also join BertrandLeRoy's project.

it is your free choice.



Oct 15, 2012 at 10:31 PM


for the customer, i have an idea:

1) give admin the choice that customer need log in or not(through payment of google checkout,paypal, then become user).

2) integrate with oauth?

3)with crm

it could be a module

Oct 16, 2012 at 10:31 AM

Sorry, I have it already in my private SVN repo. I can upload it to some version control, preferably codeplex.

  • OAuth is a good idea as long as I use UserPart is is possible without changing the module.
  • I don't like the idea to offer order creation for non registered users. That's why I followed skywalkerwebshop approach. But it is still possible to support it with some changes, the main issue that ship/pay modules has to be able to "ask" additional information their selves if there is no user.
  • CRM (stock) - it is possible to subscribe order creation and status change events. But there is no way to tell the user that it is out of stock. Might be a good idea to make an interface method for Product (or some PriceProvider) which could change the product price on the fly. But still not sure about bundled discounts and vouchers. I feel that it should be implemented similar way, but yet not sure how exactly.
Oct 18, 2012 at 4:02 PM

hope to see your repo.thanks

Oct 19, 2012 at 11:13 AM

Here it is: