Hey Tarek,

I've been trying to answer as best I can, but I don't understand why the logged in Member with Property IsHeadOffice = true does not have a Merchello managed customer. I assume it's just another member type in Umbraco that can be added to the merchello.config just like any standard customer and not something that needs to be managed after the fact.

The only caveat to this, is if you are allowing the user to checkout anonymously (without logging in first) and then need to allow them to sign in after the transaction is complete in which case the invoice would have been generated and saved as an anonymous customer and would need to have the customer key associated with the newly logged in customer.

If you are trying to associate more than one Member with a single Merchello Customer, I'd suggest writing your own CustomerContext which can be done by inheriting from the CustomerContextBase and implementing three pretty simple methods.

In any case, the customer is rarely created manually. It is generally accessed through:

 var customer = CustomerContext.CurrentCustomer;  

Then the basket is

 var basket = customer.Basket();

The Sale preparation is (1.14.0 introduces the CheckoutManager to supersede this)

 var preparation = basket.SalePreparation();

To checkout

 // This generates and saves the invoice and applies customer key if the customer is logged in.  Otherwise the invoice will have a null customer key
 var result = preparation.AuthorizePayment(...

If your customer logs in after the payment

  var invoice = result.invoice;

  // save the invoice key into the Merchello cookie to persist between page loads
  CustomerContext.SetValue("invoiceKey", invoice.Key.ToString());

Then log in the member which will update the CustomerContext.

   var customer = CustomerContext.CurrentCustomer;

    if (!customer.IsAnonymous) {

          var invoiceKey = CustomerContext.GetValue("invoiceKey");

          if (!string.isNullOrWhitespace(invoiceKey)) 
          {
                var key = new Guid(invoiceKey);
                var invoice = MerchelloContext.Current.Services.InvoiceService.GetByKey(key);

                if (invoice != null) 
                {
                      invoice.CustomerKey = customer.Key;
                      MerchelloContext.Current.Services.InvoiceService.Save(invoice);
                }
          }
    }

Hi Rusty,

Many thanks for replying.

Just to clarify, the whole website is protected so everyone will to be logged in to access. There is no support for anonymous users.

Our client provides company specific products so you must be logged in as Company X to see the products for Company X.

However, some of these companies want their headoffice users to order to products on behalf of a branch.

So headoffice user logs in ... products for Company X are displayed. They add 1 or more items to the cart and checkout.

When filling out their billing address, they are presented with a dropdown containing all of the various branches (branches are Umbraco member called office and property IsHeadoffice = false). They select Branch 1 and proceed with checkout.

Currently, the default behaviour will result in the invoice being created with the HeadOffice user attached to the invoice.

We actually need the Branch selected in the dropdown to be attached to the invoice.

I am happy to create CustomerContext, however, at what point do I need to switch out the default implementation? We store the dropdown value in session.

Hope this makes more sense

Regards, Tarek

is working on a reply...