Targets Overview
A target represents where your checkout UI extension will appear.
You register for targets in your configuration file, and you include a JavaScript function that will run at that location in checkout.
Anchor to Checkout locationsCheckout locations
Checkout is where buyers go to purchase goods. Checkout consists of the information, shipping, and payment steps in addition to the order summary and Shop Pay. Learn more about building custom functionality for checkout.
Information
This is the first step in the checkout process where the buyer enters contact information and a delivery address.
Review all extensions targets.
Payment
Point in checkout where the buyer enters their payment information.
Review all extensions targets.
Order summary
Summary of the cart contents, discounts, and order totals.
Review all extensions targets.
Shop Pay
Accelerated checkout where Shopify pre-fills buyer information using their Shop Pay account.
Review all extensions targets.
Split shipping
When multiple shipments are expected, a checkout will render split shipping options.
Review all extensions targets.
Local Pickup
Point in checkout where the buyer can select a store location to pick up their purchase.
Review all extensions targets.
Pickup Points
Point in checkout where the buyer can select a pickup point to have their purchase delivered to.
Review all extensions targets.
One-page checkout
All checkout pages (information, shipping, and payment) are combined into a single page with the order summary.
Get started testing extensions on one-page checkout.
Anchor to Thank you locationsThank you locations
The Thank you page is shown to buyers immediately after a checkout is successfully submitted. Learn more about building for the Thank you page.
Order summary
Summary of the cart contents, discounts, and order totals.
Overlays
Static extension targets that floats above the Thank you page.
Anchor to Static extension targetsStatic extension targets
Static extension targets render immediately before or after most core checkout features such as contact information, shipping methods, and order summary line items. Merchants use the checkout editor to activate and place the extension in the checkout experience.
When a core checkout feature isn't rendered, neither are the static extension targets tied to it. For example, shipping methods aren't shown when customers select the option for store pickup and the UI extensions that load before or after the shipping method aren't rendered.
Choose static extension targets when your content and functionality is closely related to a core checkout feature. An example is a shipping delay notice.
Anchor to Block extension targetsBlock extension targets
Block extension targets render between core checkout features. Merchants can use the checkout and accounts editor to place the extension in the checkout, Thank you pages.
Block extensions are always rendered, regardless of what other checkout elements are present. For example, an extension placed above the shipping address will still render even for digital products which don't require a shipping address.
Choose block extension targets when your content and functionality works independently of a core checkout feature. This is useful for custom content, like a field to capture order notes from the customer.
Block extension targets always support multiple placements. Each placement has an associated placement reference that represents its location on the page. For example, the block extension target purchase.checkout.block.render supports fourteen placements. The placement references include INFORMATION1, DELIVERY1, PAYMENT1, and more.
You can use placement references as URL parameters to test block extensions in all supported placements on a page. You can also use placement references to define the default placement of an extension for merchants.
