Disable for Virtual Orders?

Thanks for your reply, but the link seems to be broken.

Hi, ok, try this link:
https://www.zorem.com/manage-orders-for-virtual-and-physical-products-on-the-same-woocommerce-store/

Thanks. This seems sort of complicated. I don’t understand why the AST plugin re-names ‘Completed’ as ‘Shipped’ instead of just creating a new, separate ‘Shipped’ order status like you did with ‘Delivered.’ You can still trigger emails like the ‘Delivered’ status can, so why not just leave ‘Completed’ alone and add ‘Shipped’ separately? Then virtual orders would work fine and you could just remove the action buttons and tracking box from them with a simple conditional. Adding a whole other plugin just to restore default functionality seems way more complicated than it needs to be.

AST is using the WooCommerce Completed Order for Both Virtual & and Shipped orders, there is not difference in the default WooCommerce orders flow.

The Completed order status definition by WooCommerce is – The order is fulfilled and no further actions required and email notification that lets the customer that his order is Completed.

AST adds the tracking info to the Completed order status email. The same as the official WC plugin and any other plugins.

For the majority of stores that use AST this status means that the order was Shipped so we allow these stores to rename the Label to Shipped. THIS IS OPTIONAL, if you do want to rename, so don’t.

There are 2 main solution, AST provides you a flexibility to do it both ways:

I recommend to go with our solution, you can rename the Completed to Shipped, set the Completed order email to use Shipped in the language and create a custom order status for the Completed and set custom email that will fit the Virtual orders text.

or another option that will require a bit more custom development:
You can use the Completed only for the virtual orders and create Custom order status Shipped and on AST settings, add the tracking info to the custom order status email and control on which status it will show the add tracking action menus. But, in this way, you will not be able to use the quick option to set the order status as Completed when adding tracking info to orders.

Thanks and good luck.

Thanks for the explanation, but renaming Completed and then creating another custom status of Completed makes no sense. AST should’ve made Shipped a separate custom status in the first place instead of renaming Completed, because the default statuses need to be used by other things. If Shipped was a separate custom status, then non-virtual orders would get auto-marked as Processing and virtual orders would get marked Completed as normal, and we could just click AST’s action button on the Processing orders to change them to Shipped. Making people do a bunch of custom coding just to un-do a problem that AST created isn’t good design.

The version you released a while ago before you had to reverse it because people had PHP errors worked perfectly for me, why wasn’t it possible to just fix the PHP errors on that version?

@simonkane It doesn’t look like I have an email from you – can you link to the thread? If they’re not going to do anything about it then I’m not sure it matters, but if you’ve found a simpler solution that’d be helpful.

@zorem Having no Shipped status is confusing for physical orders and renaming Completed is confusing for virtual orders, and also could create conflicts with other plugins that would further confuse customers, so although I’ve been managing with AST so far and it works great for non-virtual orders, ultimately I may just look for a different plugin. I haven’t looked at AST’s code but it seems like you could just duplicate the functionality you’re using for the Delivered status to create a Shipped status. In any case, I don’t really have time to custom code this right now and although I have gotten emails from customers related to this, I’m only using it on one small store, so it’s manageable until I have time to look into it. Mostly it’s just frustrating that this shouldn’t be an issue in the first place with a plugin as high-quality as yours clearly otherwise is.