Menu
Feedback
Start here
Tutorials
Developer portal

Known Issues
Support Rules
Troubleshooting

Frequently Asked Questions
Announcements
Known issues
Pickups inherited between whitelabel sellers are treated as different/independent pickups on the purchase flow
Pickups inherited between whitelabel sellers are treated as different/independent pickups on the purchase flow
ID: 438630
Backlog
Published on 5/12/2022
Last update on 11/25/2022

Summary

There's a feature in the Logistics module to inherit pickup points between franchise accounts, and so between whitelabel sellers. While registered on a seller X, they'll appear as pickup options for a seller Y according to what is configured on the shipping strategy. Although they are the same, their ID will be different between each seller, and so they'll be seen as different and independent pickup options.

The issue is that the purchase experience will be compromised when the customer wants to get the items from their cart in this pickup, but they are coming from different sellers behind everything. They can be shown repeated times on the pickup points list (one per WL seller), and each one of them will cover only specific items (the ones provided by each WL seller).

Also, it's important to consider that the checkout's native frontend doesn't offer the option to select different pickup points for different items in the cart (although they were from different regular sellers, which doesn't apply to a SWL scenario). So you can't buy the entire cart on this "same" pickup point option. The remaining items, which aren't covered by the selected pickup, will be offered to be delivered to an address – if it's an available delivery channel for the context, otherwise, they'll be shown as "selected another pickup or remove from the cart".

Simulation

There's no quick scenario to reproduce the issue, but you just need two items coming exclusively from two different sellers (can be the seller 1 and one of their SWLs), and there's a single pickup inherited from the SWL to the seller 1.

Workaround

N/A

Contributors
2
Photo of the contributor
Photo of the contributor
+ 2 contributors
Contributors
2
Photo of the contributor
Photo of the contributor
+ 2 contributors
On this page
Still got questions?
Ask the community
Find solutions and share ideas in the VTEX community.
Join our community
Request support from VTEX
For personalized assistance, contact our experts.
Open a support ticket
GithubDeveloper portalCommunityFeedback