Are you using the built in PayPal payment provider? If you are then this is done when you call TransactionLibrary.Checkout(); (remember to call ExecuteBasketPipeline first).

As a side note, it's the payment reference you should be sending to the payment gateway (PayPal) this way you can create a new payment reference if it fails (where as you'd be abusing the order number if you did that).

The order number is typically only used for completed orders. That is assigned in the checkout PipeLine which should be called in some point of time after you get redirected back to your site from PayPal. 

If your not familliar with the pipelines or pipeline pattern in general i'd suggest that you take a look at: 

http://blog.lasseeskildsen.net/post/uCommerce-Pipelines-Explained.aspx

Also you can see how each pipeline are configured in the Pipelines folder under ucommerce in the umbraco folder. 

But as Tim says. You should call ExecuteBasketPipeline which will make the order ready for checkout and afterwards use the TransactionLibrary.Checkout() which will then find your configured paymentmethod and redirect to paypal. 

Hi Lee,

You can just assign an order number to the order before redirecting. If an order number is already assigned when times comes to execute the checkout pipeline uCommerce will keep the existing order number.

Here's how:

purchaseOrder.OrderNumber = new CheckoutService.GetOrderNumber();
purchaseOrder.Save();

You can also resuse the AssignOrderNumber pipeline task, which by default is configured in the Checkout pipeline. You can move it to any other pipeline.

The pipelines you've tried out are meant for a couple of different things:

The SaveOrder pipeline is meant for saving existing orders, which require recalculating order total. Generally speaking the SaveOrder pipeline is executed in the backend whenever the a user clicks the save button on an order.

The Processing pipeline is executed automatically when the order is moved to "Processing" order status. By default this happens when dealing with asynchronous payment gateways, which may take some time to report back whether a payment was processed successfully or not.

The Processing pipeline is executed automatically when the order is moved to "Processing" order status. By default this happens when dealing with asynchronous payment gateways, which may take some time to report back whether a payment was processed successfully or not.

This is exactly the problem AND we are currently using the Processing pipeline before we redirect the user to PayPal (We have a custom PayPal implementation for the new paypal pro hosted solution and using IPN which works fine).

But I expected the order to then be saved and shown in the Processing or Awaiting Payment folder? But its not? Why is this? Reason why it needs to be saved and shown is for two main reasons:

1. So the store admins can check any outstanding unpaid for orders and contact the customer if necessary
2. PayPal beleive it or not goes down from time to time *sarcasm* and unless these orders are saved and we can check. Then we might never know there is an issue with PayPal or know who abandoned the cart/store

I was under the impression if the processing pipeline was executed. It would all be saved, and put in the processing folder?

Re Order Number:

Thanks that'll work perfectly. Again reason for this is for tracking. You need an order number for the code on the order confirmation page.

>I was under the impression if the processing pipeline was executed. It would all be saved, and put in the processing folder?

It depends what your pipeline is configured to do (check the config) but just triggering a pipeline will only do whats in the configuration and nothing else (calling the method e.g. Checkout may do other actions under the hood).

public class MyOrderContext : OrderContext
{
  public override Basket GetBasket(Guid basketId)
  {
    return PurchaseOrder.SingleOrDefault(o => o.BasketId == basketId);
  }
}

Hope this helps.

Thanks for the reply.

I 'think' we have now got around the issue by doing the below just before we go to PayPal. So the order now has an order number (And matches the order number stored against the payment in PayPal) and shows in the backend in uCommerce in the Awaiting Payment folder (It seems if you set the completed date then the order appears in the back end in uCommerce).

            var coService = new CheckoutService();
            paymentRequest.PurchaseOrder.OrderNumber = coService.GetOrderNumber();
            paymentRequest.PurchaseOrder.CompletedDate = DateTime.Now;
            paymentRequest.PurchaseOrder.Save();

We are still doing some testing, but will come back if its not. Unless you can see any issues with us doing this that we might not have thought of?

Just a note though....

I can certainly see the argument for another pre-order status like "PaymentPending" the main issue is that you'd potentially have a lot of orders in that state because people will abondon cart during the payment phase and there's no way to distinguish between the scenario of "a real abondonment" and "a technical issue abandonment".

Personally I think its a high priority for any real online business to know how many abandoned carts you have irrelavant whether is a technical issue or real abandonment. Without knowing this you may never know there is a problem and you are getting a lot of people putting in cart and not completing (Apart from them checking their Google Analytics sales funnel)

Also its very interesting to see what people are putting in there cart and abandoning. Could be a lot of the same product. Which could mean there is a problem with it (Maybe technical), or they like it but something else along the checkout is putting them off (i.e. shipping or don't trust that payment gateway is secure etc..)

Without this information the store owner is slightly blind unless they know there way around Google Analytics and eCommerce setup.

Setting the CompletedDate will not make orders show up in the backend. Only changing order status will do that, however, if you didn't implement the override to OrderContext I posted, the cart will be emptied when order status is changed from "basket", thus customers returning to the store "on purpose" will not see their existing cart, but a new one. This may or may not be what you're after. If you want the cart to still be available upon return to the store without payment completed you need the OrderContext override in place.

I absolutely see the scenario for having an "Awaiting Payment" status. I worry that making it available in the backend will confuse store owners as we're not talking about orders per say, but it still shows up in the order processing work flow. I'd love some input on that.

Hate to disagree with the boss... But setting the CompletedDate 100% makes it appear in our 'awaiting payment' folder (Might be something to do with our pipeline but don't think so). Also the order stays in the cart until the payment is completed? If they redirect to PayPal but abandon there, and come back to the site their order is still in the cart?

Probably a customization. I believe I was in contact with Matt about something along those lines now that I stop and think about it.

is working on a reply...