Mewz

Thanks for the suggestion, @rosalitoudtohan. We’ll take it into consideration.

Hi @singhmc,

A few things to note here:

• Attribute stock is separate to product stock, their quantities are not shared directly like this. I suggest you read more about how it works in our documentation.

• Only the full version will affect product stock availability on the frontend. The free lite version does not affect product availability or prevent over-purchasing, as mentioned in the description. It can only be used to track stock quantities internally.

• If you already have the full version please reach out via our premium support channel and I’ll be more than happy to guide you on how to configure shared stock for the double seat.

Is this what you’re looking for?

https://wcas-docs.mewz.dev/rest-api-webhooks

This is related to functionality only available in the full version. Please feel free to reach out via our premium support channel for assistance:

https://codecanyon.net/item/woocommerce-attribute-stock/25796765/support

Sure. We have this action for when an attribute stock item is updated for any reason:

do_action('mewz_attribute_stock_updated', $stock, $data, $updated);

And this action for when one or more attribute stock items are reduced/restored from an order item:

do_action('mewz_wcas_order_item_updated', $hook_data);

I don’t see the problem?

I suggest you read through our documentation and you’ll have your answer once you have a better understanding of how attribute stock works. It’s just a tool and how you use it is up to you.

If you need more hands-on assistance with setting up stock on your site, please reach out via our premium support channel after purchasing the full version.

Ihre Bewertung bedeutet mir sehr viel ??

Did you just add this in the recent update last night?

Well no, this function was already available in v2.0.0. I just made the 2nd parameter optional so it’s easier to use.

Your code works for me. But keep in mind there are many different ways to show custom metadata on order items. For example, your current code will show on frontend order details, but not in the backend when editing an order.

You have to take a different approach if you want this to show on admin orders, frontend orders, or both. There’s also the decision to be made whether to show it dynamically, or add it as real order item metadata when the order is placed/created.

If your code isn’t even working on frontend order details, then it could be that you’re using “any” variations which requires a different approach, or perhaps the specific product variation doesn’t exist anymore. In the latter case the product type will be variable instead of variation. Adding order item metadata when the order is placed helps to avoid issues like this.

Hi @theginaddict,

This has already been fixed in the latest update. Please make sure you’re running the latest version 2.0.1.

Hi @westham00,

In the latest version 2.0.1 you’d do something like this:

$total_qty = $cart_item['quantity'] * mewz_wcas_get_product_multiplier($cart_item['data']);

You’re too kind. Thank you so much! ??

Thanks for the amazing reviews, @ddapparel. It’s greatly appreciated! Your feedback regarding the lite version has also been noted.

Hi @erikanapoles,

I’d just like to let you know that we’ve released a new update that makes this much easier to do now.

Hi @ddapparel,

You’re not missing anything. Linking by SKU doesn’t fit the functionality we’re trying to offer for the simple reason that WooCommerce doesn’t allow products or product variations to use the same SKUs. That’s why you’ll have trouble finding plugins that allow you to do this.

Attribute stock also allows very complex stock setups, many of which just aren’t possible with the constraints of regular product stock. This is why attribute stock items are used, to separate your stock from your product listings.

But of course this might not be feasible for all types of stores. That said, we’re always looking to make different types of stock setups easier to set up and manage, so we’d love to hear more about the specific stock functionality you’re trying to achieve.

It should be _mewz_wcas_multiplier with a leading underscore.

Apologies, I left it out in my initial reply before editing.