Just checking on the status of Out of stock threshold #50. This would be a great feature.
Hello everyone, I'm also currently trying to figure out how to handle the lack of this feature (manage inventory per site/location). Any updates on the status? If it's still a long time away from being ready, is the easiest/best solution writing a plugin or running a separate instance/DB (in this case 2 instances would be enough) in your opinion? Thanks!
@lukeholder @brandonkelly Can you provide any update on the status of this issue? Is it in your pipeline or still future development?
@jacobrussell Was and is, but we can't give a timeline on it sorry. Should be in Commerce 4.
Is there a plan to have the backorder-feature arriving in Commerce 3?
@denisyilmaz no plan in Commerce 3 sorry.
is there any update on a timeline when commerce 4 will be available? some of these features are urgently requested by some projects and it would be very nice to give the project-owners a idea of when these features can be revisited / or if a solution must be found in any other way.
@lukeholder Can you provide any update here? Is this expected at some point this year? Solid inventory management is a core e-commerce feature that's hard to backfill with custom solutions well. Would be very helpful to know if we can still expect this with Commerce 4.0, and if that's coming soon.
@denisyilmaz @jacobrussell we are beginning work on multi-store support, and a stock/inventory system to support each store is a core feature of that. Sorry for the delay, but we are working on it. Sorry I can't give a timeline.
@lukeholder Is creating a custom stock-field the only fix to make backorder possible in Commerce 3 ?
Couldn't this feature be enabled by adding an extra checkbox next to the "Is unlimited", name "Allow backorder", and then simply make af check for $this->allowBackorder in craft\commerceelementsVariant getLineItemRules ?
Adding this field wouldn't break anything, if its set to false as default (which i think i general should be the default value).
馃憖
Most helpful comment
@lukeholder @brandonkelly Can you provide any update on the status of this issue? Is it in your pipeline or still future development?