A little more complex checkout

Hi there!

I searched a long time on this forum and didn't find an answer for my problem, so here it is:

HikaShop Business 2.0.0

My webshop checkout should work as follows:

The customer adds some stuff to buy, goes to checkout to place the order, but not pay yet.
So he gets an e-mail about the created order.

Now the shop owner manually adds shipping costs to the order and sets the order status to "confirmed".
The customer gets a new e-mail about this, and only NOW he is able to pay.

So far I am halfway there using the workflow "login_address_coupon_cart_status_fields_terms_confirm,end", but on the customer control page the customer is still able to pay while the order status is "created" and thus no shipping costs have been added yet.

Is there any way to prevent payments while the order status is not "confirmed" yet?

TIA,
Peter

Hi Nicolas,

Thanx for your quick response!

I had already disabled that option, but it doesn't help.

After the customer creates a new order (without paying yet), he can access that order on the customer control page and still pay for it while the order status is "Created" (Dutch: "Aangemaakt").

See:

Rehi,

OK, I am some steps further...

I created a new order status "Requested" at the beginning of the workflow.
Just as a test, I created a new order and manually set the status to "Requested".

When the customer now logs in and browses his orders he sees this:

class plgHikasshopRFP extends JPlugin {
	function plgHikasshopRFP(&$subject, $config){
		parent::__construct($subject, $config);
	}
	// Change the initial order status
	function onBeforeOrderCreate(&$order,&$send_email){
		$order->order_status = "requested";
		return $this->onBeforeOrderCreate($order,$send_email);
	}
}

Hi Nicolas,

I totally understand what you mean, but I can't seem to get it working

Here are my settings:

Hi Nicolas,

The status value in the payment system is what the status will be after execution. Not what the status must be before payment can take place. So I am missing the option to set which statuses are payable?

I experimented some more and also added status "requested" as the new initial status. From that moment on only that status is payable. All the other statuses are no longer payable, including "created", even though the "payed" status remains set to "confirmed".

So am I missing something, or can there be only 1 payable status --> the initial one?

Greetz,
Peter

Thanks!!!

That gets the job done