Update: SKU Selector logic for default #1124
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
beatrizmaselli
requested review from
gabpaladino,
vsseixaso and
leo-prange-vtex
|
Hi! I'm VTEX IO CI/CD Bot and I'll be helping you to publish your app! 🤖 Please select which version do you want to release:
And then you just need to merge your PR when you are ready! There is no need to create a release commit/tag.
|
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
iago1501
requested review from
iago1501
and removed request for
gabpaladino,
vsseixaso and
leo-prange-vtex
iago1501
approved these changes
Nov 4, 2024
|
Your PR has been merged! App is being published. 🚀 After the publishing process has been completed (check #vtex-io-releases) and doing A/B tests with the new version, you can deploy your release by running:
After that your app will be updated on all accounts. For more information on the deployment process check the docs. 📖 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What problem is this solving?
The SKU selector, when there were multiple SKUs with the same specifications, was always selecting the first SKU without considering the product’s sale feasibility. This issue could lead to displaying an SKU that is not actually available for purchase, affecting customer experience and conversions.
How to test it?
Ensure that you have multiple SKUs with identical specifications but differing in sale feasibility. Verify that the SKU selector now prioritizes SKUs that are available for sale when displaying the SKU options in the context.
Workspace
Screenshots or example usage:
Before adjustment:
After adjustment:
Describe alternatives you've considered, if any.
No significant alternatives were considered, as the focus was on improving SKU selection based on sale feasibility.
How does this PR make you feel? 🔗
