Open leorente opened 3 years ago
Hi Leo, I will send you a slack message so we can better understand this request
Thanks @marcelocouto please let us know any additional information about this use case. @leorente the current plan is for a shopper to be notified once inventory becomes available from ANY seller who has the product in stock. What is the purpose for the back in stock notification being seller specific? I don't believe we'd have a way currently to get the seller information from the broadcaster.
Hi @ebigler , do you know when this will be available?
We need this functionality too. Many thanks!
I have this same request from 2 marketplace customers GM and Oonni. Please let me know any updates
If the notification is from any seller, we need some sort of mechanism to tell the customer which seller, maybe if it is different than the original one they requested. For example, if the item is out of stock for seller A, then ask to be notified if in stock, and another seller starts selling it, we need to know something like "You asked to be notified if Seller A has this product, however, Seller B now sells it, and here is the link"
@ebigler What do you think about this option?
@ajleale The current issue is the VTEX broadcaster that we are relying on for updates is not aware of seller info. For your use case is it a requirement for the buyer to know that the item is coming from a different seller or is that more of a 'nice to have' item?
My understanding is that Broadcaster will know about inventory from any / all sellers becoming available for purchase so the buyer will be alerted. However, they will not have any indication that the stock is from a different seller than where they originally requested the alert. @marcelocouto @btalma, please feel free to add your thoughts or correct me if I'm wrong about any of this info.
@ebigler we have more than one B2B client that has a one-by-one relationship between sellers and customers. That means the customer can see and purchase SKU from a specific seller. In those scenarios, the customer will receive a false-positive e-mail about availability.
Asked my team to validate the following hypothesis:
If the notification has a user with Address defined, add a simulation step to double check the availability based on the SKU and the user address.
I don't know if the simulation flow will trigger the region/session behavior, if not, this simulation step can be more complex.
Hi, @leorente that makes more sense now. In that case, maybe what we need to do is to check if the product is available for each user before sending the email. Run a simulation for the SKU with the customer data.
The simple notification is not working yet, so we need that working before we can move to a more sophisticated solution. One step at a time and we will get there.
@leorente @ajleale @hugocostadev the phase 1 functionality for this app was released with v0.0.10 and is available for beta testing.
We're still evaluating what our options are to try to add seller awareness to the inventory updates coming from Broadcaster.
The seller awareness request is in our teams backlog and will be reviewed during an upcoming sprint planning meeting
Any news regarding seller awareness? THanks
@hugocostadev @leorente We broke the seller awareness work into 2 pieces. The first task is complete, you can see Release v0.1.0 added the Seller information to what's being stored with the user's request data. We're currently working on running the simulation to check if inventory is available for a particular user from the seller that's associated to their notification request.
Hi @ebigler!
Are there any news regarding the simulation that you were going to run? Thanks!
@btalma @tsheng1 @albertm805
Could someone give us more details regarding this implementation? I checked the last releases and I guess that this was already working, but apparently not... The form does not store the right seller
FYI, @ccelisri and @hugocostadev, see updates here from a separate issues thread. This should be resolved now.
We had a client with the following scenario
Do you guys have this feature planned on a roadmap or should we considerer as a customization?
Thanks!