What are the Slack Archives?
It’s a history of our time together in the Slack Community! There’s a ton of knowledge in here, so feel free to search through the archives for a possible answer to your question.
Because this space is not active, you won’t be able to create a new post or comment here. If you have a question or want to start a discussion about something, head over to our categories and pick one to post in! You can always refer back to a post from Slack Archives if needed; just copy the link to use it as a reference..
👋 morning, from what I understand Spryker never updates the stock level, and depends on the ERP
Comments
-
I think in this case we should update the stock level accordingly until the level is "normalized" by the ERP ?
0 -
Product should remain in
reservedstate until the stock update from the ERP.0 -
so when we process the stock update we should check to see if there are any reserved items that have a specific state and unreserve them?
0 -
sounds easier to just decrement the stock when we remove the reserved flag?
0 -
conceptually the stock should actually be decremented then
0 -
I'm not a developer but heard that this should be processed by a State machine. Until the stock update all steps should have
reservedflag.0 -
☝
0 -
but the stock update isn't part of the SM
0 -
so how would the stock update unreserve items?
0 -
(it's possible to do this, but seems easier to just decrement the stock)
0 -
there should be a command somewhere, i would agree
0 -
the unreserve comes from the next state simply missing the flag
0 -
it's an implciit action?
0 -
or the stock update condition would be triggered by the ERP? (guessing this is an example state machine?)
0 -
no, the stock reduction should happen during the state transition between the last reserved and the first unreserved state in the screenshot above
0 -
there should always be a reduction
0 -
from the erp should be mere corrections that we should not rely on here
0 -
yeah, that's my expectation
0 -
i guess it is then implicit when the flag is removed
0 -
‘it’ being the un-reservation or the stock reduction?
0 -
the stock reduction
0 -
No, it's just missing a command iirc
0 -
ok, then I'll investigate, thanks 🙂
0 -
I'll try to have a look later as well
0 -
As I know and the Feedback I got from you some month ago was, that spryker never touches the stock since this is the job of the erp. Spryker only calculates the availability from stock and product reservations
0 -
You keep the reserved flag even when the order was already exported. This ensures that you don’t oversell any products. You may decreased them twice for a short amount of time but that’s acceptable.
Some time later you a stock update from WMS which usually contains
SKU - QTYThen you trigger the event for those sales-order-items which belong the these SKUs and are exported to WMS already.0 -
And yes, you never change the spy_stock table directly by some custom logic. Only stock importer is doing the that, everything else is handled by oms reservations.
0 -
hm, so the event would remove the
reservedflag for all items that are ... ?0 -
not sure i see the downside of simply decrementing the stock though once the order has been placed / exported
0 -
(depends on how complicated it is to react on a stock change event)
0
Categories
- All Categories
- 42 Getting Started & Guidelines
- 7 Getting Started in the Community
- 8 Additional Resources
- 7 Community Ideas and Feedback
- 76 Spryker News
- 930 Developer Corner
- 788 Spryker Development
- 89 Spryker Dev Environment
- 362 Spryker Releases
- 3 Oryx frontend framework
- 35 Propel ORM
- 68 Community Projects
- 3 Community Ideation Board
- 30 Hackathon
- 3 PHP Bridge
- 6 Gacela Project
- 26 Job Opportunities
- 3.2K 📜 Slack Archives
- 116 Academy
- 5 Business Users
- 370 Docker
- 551 Slack General
- 2K Help
- 75 Knowledge Sharing
- 6 Random Stuff
- 4 Code Testing
- 32 Product & Business Questions
- 70 Spryker Safari Questions
- 50 Random