Source
Catalogue & checkout — found from sitemap — Vendure
Checked for Vendure on 3 Nov 2026
- Page
- https://docs.vendure.io/current/framework/storefront/checkout-flow
- Checked
- 3 Nov 2026, 15:42 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:3c5321fa198724cd08ef85c4ab9451643808c00425328569569997751e63869d
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Set customer for order Report an error
“If the customer is not logged in, then the setCustomerForOrder mutation must be called. This will create a new Customer record if the provided email address does not already exist in the database.”
-
Set order shipping address Report an error
“The setOrderShippingAddress mutation must be called to set the shipping address for the order.”
-
Eligible shipping methods Report an error
“we can check which shipping methods are available with the eligibleShippingMethods query.”
-
Set order shipping method Report an error
“The desired shipping method's id is then passed to the setOrderShippingMethod mutation.”
-
Eligible payment methods Report an error
“The eligiblePaymentMethods query can be used to get a list of available payment methods.”
-
Arranging payment state Report an error
“we need to transition the order to the ArrangingPayment state. This state ensures that no other changes can be made to the order while the payment is being arranged.”
-
Add payment to order Report an error
“The addPaymentToOrder mutation is the general-purpose mutation for adding a payment to an order. It accepts a method argument which must corresponde to the code of the selected payment method, and a metadata argument which is a JSON object containing any additional information required by that particular integration.”
-
Coupon removed during checkout error Report an error
“If the order has a coupon code applied whose usage limit was exhausted by a concurrent checkout (or whose promotion was disabled or whose eligibility conditions are no longer met) and removing it would increase the customer's total, addPaymentToOrder returns a CouponRemovedDuringCheckoutError rather than charging the customer the new (higher) total.”
-
Community payment integrations Report an error
“The following community plugins provide payment integrations: @vendure-community/stripe-plugin @vendure-community/braintree-plugin @vendure-community/mollie-plugin”
-
Dummy payment handler Report an error
“the demo data populated in a new Vendure installation includes a "Standard Payment" method, which uses the dummyPaymentHandler to simulate a payment provider.”
-
Order by code confirmation Report an error
“the activeOrder query will return null. Instead, the orderByCode query can be used to retrieve the order by its code to display a confirmation page.”
-
Order by code access window Report an error
“By default Vendure will only allow access to the order by code for the first 2 hours after the order is placed if the customer is not logged in.”
-
Default order process assumed Report an error
“This guide assumes that you are using the default OrderProcess, so if you have defined a custom process, some of these steps may be slightly different.”
-
Customer addresses query Report an error
“If the customer is logged in, you can check their existing addresses and pre-populate an address form if an existing address is found.”
Scores citing this record
- The B2B Seller Catalogue & checkout
- The Data Protection Officer Catalogue & checkout
- The Developer Catalogue & checkout
- The Merchant Catalogue & checkout
- The Operations Lead Catalogue & checkout
- The Skeptic Catalogue & checkout