> For the complete documentation index, see [llms.txt](https://docs.digitalriver.com/salesforce-lightning/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digitalriver.com/salesforce-lightning/salesforce-lightning-b2b-commerce-app-1.3/integrate-the-salesforce-lightning-app/step-18-alternative-integrate-the-digital-river-components-into-a-synchronous-checkout-flow/configure-screens-for-a-customized-synchronous-flow/add-custom-components-to-screens-in-the-synchronous-checkout-flow.md).

# Add custom components to screens in the synchronous checkout flow

The Digital River Salesforce Lightning app comes with a completely functional customized synchronous checkout flow named “Sync Checkout Flow”. You may , however, choose to customize your checkout flow to suit your particular needs. This topic describes how you can use the Salesforce Lightning components provided by the application in your Checkout flow.

The table below shows the recommended components to be configured in each screen of the synchronous flow to support OOTB functionality.  Other components may optionally be added.  Consult with your Digital River team and refer to the [Customizing the Lightning web components](/salesforce-lightning/salesforce-lightning-b2b-commerce-app-1.3/extend-the-salesforce-lightning-app/customizing-the-lightning-web-components.md) section to learn more about customization options.

| Custom Screen component Name | Custom Component(s) Used                                                                                                                  |
| ---------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
| Shipping Options             | <p>drb2b\_drUtil</p><p>drb2b\_BuyerInfo</p><p>drb2b\_taxCertificateCheckout</p><p> </p>                                                   |
| Delivery Method Screen       | <p>drb2b\_DRUtil</p><p> </p>                                                                                                              |
| Checkout Summary             | <p>drb2b\_DRUtil </p><p>drb2b\_DrTermsElement</p><p>Drb2b\_DrTaxIdentifier</p><p> </p>                                                    |
| Payment and Billing Address  | <p>drb2b\_Payments</p><p>drb2b\_previousButton</p><p> </p>                                                                                |
| PlaceOrderConfirmation       | <p>drb2b\_Order Summary </p><p>drb2b\_DRUtil </p><p>drb2b\_paymentDetails</p><p>drb2b\_previousButton</p><p>drb2b\_placeOrder</p><p> </p> |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.digitalriver.com/salesforce-lightning/salesforce-lightning-b2b-commerce-app-1.3/integrate-the-salesforce-lightning-app/step-18-alternative-integrate-the-digital-river-components-into-a-synchronous-checkout-flow/configure-screens-for-a-customized-synchronous-flow/add-custom-components-to-screens-in-the-synchronous-checkout-flow.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.