What is trigger for create invoice number?

*bump*

It seems to happen the first time you make a request to get the invoice number. There are several places where this happens, which explains why you could not find a consistent way to trigger it. Though, I’d say generating a printed invoice should always trigger this.

A possible workaround might be to hook into the plugin asap after an order is set to a status that would make sense to send invoices. For example:

function create_invoice_number( $order_id ) {
	WCDN()->print->get_order_invoice_number( $order_id );
}
add_action( 'woocommerce_order_status_completed', 'create_invoice_number', 5 );

If what you say is true; I think it could be good enhancement to make functionality consistent.

Nice.. I’ll try it out and see what happens.

THANKS!!!!

You are welcome. Let me know what happens, we might be able to use your input ??

Okay… that’s solved a WORLD of headaches. I have 4 different statuses to do it for and have just repeated the function four times, which works, but is ugly from a code perspective.

Is there a more elegant way to delcare

add_action when ‘woocommerce_order_status_completed’ or ‘woocommerce_order_status_on-hold’ or ‘woocommerce_order_status_processing’ (etc)?

much thanks from the php n00b ??

I think you only need to call it once, so just call the function on the most early status available that makes sense. I think if you just use on-hold you should be fine for the entire process.

Give it a try ??

Hrm.. if anything woocommerce_order_status_processing, as that’s the one that is effectively a ‘draft’ transaction.. status it has before the payment type is chosen/finalised (bacs = on-hold; paypel/etc = processing; and then I’ve got a couple of custom gateways).. I’ve done all four to be safe ??

THANKS.

marking this as resolved.

Ok, good to hear.

Just double check: you only need one function to which you can let all 4 order actions point. So, you don’t have to create 4 functions.

Cheers!

Thanks, this was useful for solving a problem that when I refreshed the order page the older orders were being given the higher (newer) invoice number!

But now it works for a certain period then all of a sudden the invoice number generated gets stuck on a certain number! No obvious pattern either.

I can reset the numbers using the plugins settings page but this is obviously not an ideal solution.

Just wondering if anybody else floating around this unsupported forum has had this problem?

Cheers

@david (or Smelsworst)

“A possible workaround might be to hook into the plugin asap after an order is set”

am I right in thinking by this you meant putting the code in functions.php or somewhere in the actual plugin code?

yep.. exactly. i hooked in in my functions.php file to force custom invoice number being fired on change of status and it’s worked a treat since. well, I still wittness the odd emailed invoice here and there going out without an invoice number, but it’s maybe a percent of orders, where it used to be all of them and used to constantly play havoc when printing invoices.

Thanks for the quick reply.
Have you noticed any of your orders having the same invoice numbers?

I’ve tried the above function code, pointing various combinations of the statuses to it.

The invoice numbers start off sequential then all of a sudden get stuck on an invoice number and then fail to be incremented so the following orders all end up with he same invoice number, very strange! If I reset the numbers using the plugin settings page they work OK again then randomly get stuck and stop incrementing again (no pattern to it, could get stuck on invoice 5, could be invoice 15,could be 34, I’m having to send a lot of test orders to investigate the problem!).

Would you mind posting the exact code you’ve put in your functions.php to see if it cures my problems?

Cheers again

Hello

Just wondering if anyone else has noticed the invoice numbers (not the order numbers) getting stuck and just repeating the same number on subsequent invoices?
Resetting solves it, but only for a certain time before the problem occurs again.

I’m trying to narrow down if its a problem with this plugin, or conflict with another plugin I’m using.

Cheers
Duncan