Skip to content

feat: pending order status (PEXP-1358)#209

Merged
jeffersontuc merged 11 commits into
masterfrom
patch/order-status
Feb 11, 2026
Merged

feat: pending order status (PEXP-1358)#209
jeffersontuc merged 11 commits into
masterfrom
patch/order-status

Conversation

@jeffersontuc

Copy link
Copy Markdown
Contributor

What is the purpose of this pull request?

Warning

This PR depends on and should be merged after https://github.com/vtex/order-placed-graphql/pull/40

The aim here is to add a pending order confirmation message for the scenario where the API returns a 202 status code for the /orders endpoint. Check the above PR for more info.

Now, we check for the new OrderGroup.status field, which can be pending or confirmed, and then display the proper confirmation message, based on this figma spec.

How should this be manually tested?

Pending order status

  • Access this workspace
  • Ensure there's a "Estamos processando seu pedido" as it's defined by the above figma spec

Confirmed order status

  • Create a new shopping cart
  • Use 22210060 as the postal code
  • Proceed to payment
  • Finish the purchase using the following credit card information:
4444 3333 2222 1111
Test Approved
02/30
333
  • Ensure the order will be placed correctly and you see the confirmation message, ensuring no regression was introduced by these changes
image

Screenshots or example usage

image

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Requires change to documentation, which has been updated accordingly.

@jeffersontuc jeffersontuc requested review from a team as code owners January 19, 2026 23:30
@jeffersontuc jeffersontuc requested review from RodrigoTadeuF, gabpaladino and leo-prange-vtex and removed request for a team January 19, 2026 23:30
@vtex-io-ci-cd

vtex-io-ci-cd Bot commented Jan 19, 2026

Copy link
Copy Markdown
Contributor

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:

  • Patch (backwards-compatible bug fixes)

  • Minor (backwards-compatible functionality)

  • Major (incompatible API changes)

And then you just need to merge your PR when you are ready! There is no need to create a release commit/tag.

  • No thanks, I would rather do it manually 😞

@vtex-io-docs-bot

vtex-io-docs-bot Bot commented Jan 19, 2026

Copy link
Copy Markdown

Beep boop 🤖

I noticed you didn't make any changes at the docs/ folder

  • There's nothing new to document 🤔
  • I'll do it later 😞

In order to keep track, I'll create an issue if you decide now is not a good time

  • I just updated 🎉🎉

@jeffersontuc jeffersontuc requested review from a team, evertonstrack and vmarcosp and removed request for a team January 19, 2026 23:56
@jeffersontuc jeffersontuc requested review from Lurian and carolkrroo and removed request for a team, RodrigoTadeuF, gabpaladino and leo-prange-vtex January 23, 2026 19:22
Add translations to order status messages
@jeffersontuc jeffersontuc requested a review from a team as a code owner February 11, 2026 18:01
@jeffersontuc jeffersontuc merged commit 5361e2b into master Feb 11, 2026
9 checks passed
@jeffersontuc jeffersontuc deleted the patch/order-status branch February 11, 2026 18:43
@vtex-io-ci-cd

vtex-io-ci-cd Bot commented Feb 11, 2026

Copy link
Copy Markdown
Contributor

Your PR has been merged! App is being published. 🚀
Version 2.19.0 → 2.20.0

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:

vtex deploy vtex.order-placed@2.20.0

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants