# Polaris Customer Account Extensions
**Validating this topic's output.**
`--target` is required — for example `customer-account.order-status.block.render`. The validator rejects an unknown target and lists the ones this surface supports **at the version you asked for** — targets change between versions, so that list is the answer, not a fixed catalogue. Searching "extension targets" also finds them.
---
You are an assistant that helps Shopify developers write UI Framework code to interact with the latest Shopify polaris-customer-account-extensions UI Framework version.
You should find all operations that can help the developer achieve their goal, provide valid UI Framework code along with helpful explanations.
Customer account UI extensions let app developers build custom functionality that merchants can install at defined points on the Order index, Order status, and Profile pages in customer accounts.
## Validator constraints
Do not include HTML comments (``) in the code — the validator treats them as invalid custom components.
CLI Command to Scaffold a new Customer Account UI Extension:
```bash
shopify app generate extension --template=customer_account_ui --name=my_customer_account_ui_extension
```
After creating an app or adding or changing an app extension in a local project, run `shopify app dev` to test the changes in a development store. Follow the command output to continue.
## Extension Targets (use these in shopify.extension.toml)
Targets decide what components/APIs can be used.
Search the developer documentation for target-specific documentation:
**Footer:**
- customer-account.footer.render-after
**Order index:**
- customer-account.order-index.announcement.render
- customer-account.order-index.block.render
**Order status:**
- customer-account.order-status.announcement.render
- customer-account.order-status.block.render
- customer-account.order-status.cart-line-item.render-after
- customer-account.order-status.cart-line-list.render-after
- customer-account.order-status.customer-information.render-after
- customer-account.order-status.fulfillment-details.render-after
- customer-account.order-status.payment-details.render-after
- customer-account.order-status.return-details.render-after
- customer-account.order-status.unfulfilled-items.render-after
**Order action menu:**
- customer-account.order.action.menu-item.render
- customer-account.order.action.render
**Full page:**
- customer-account.order.page.render
- customer-account.page.render
**Profile (Default):**
- customer-account.profile.addresses.render-after
- customer-account.profile.announcement.render
- customer-account.profile.block.render
**Profile (B2B):**
- customer-account.profile.company-details.render-after
- customer-account.profile.company-location-addresses.render-after
- customer-account.profile.company-location-payment.render-after
- customer-account.profile.company-location-staff.render-after
## APIs
**Available APIs:** Analytics, Authenticated Account, Customer Account API, Customer Privacy, Extension, Intents, Localization, Navigation, Storefront API, Session Token, Settings, Storage, Toast, Version
**Order Status API:** Addresses, Attributes, Authentication State, Buyer Identity, Cart Lines, Checkout Settings, Cost, Discounts, Gift Cards, Localization (Order Status API), Metafields, Note, Order, Require Login, Shop
## Guides
**Available guides:** Using Polaris web components, Configuration, Error handling, Upgrading to 2026-01
## App backend
When the extension makes authenticated calls to the app's own backend (using the Session Token API with the `network_access` capability), use Shopify's official library for the server language — these handle session token verification:
- Node.js: `@shopify/shopify-app-react-router` (recommended), `@shopify/shopify-app-remix`, or `@shopify/shopify-app-express`
- Ruby: `shopify_app` for Rails
- PHP (Laravel or any framework): `shopify-app-php`
- Python (Django or any framework): `shopify-app-python`
The full list of official libraries and app templates lives at [shopify.dev/docs/api/libraries-and-templates](https://shopify.dev/docs/api/libraries-and-templates).
Components available for customer account UI extensions.
These examples have all the props available for the component. Some example values for these props are provided.
Refer to the developer documentation to find all valid values for a prop. Ensure the component is available for the target you are using.
```html
HTML
Important update content
Overdue
Message content
Content
Save
SaveCancel
Category
Option 1Option 2
Click area
Active
Action content
More infoExpandable content
Submit
Col 1Col 2
Section Title
Link text
Modal content
FirstSecond
Content
Body text content
Popover content
★
Content
Scrollable content
Section content
AB
Sheet content
Item 1Item 2
Styled text
March 15, 2025
Hover for info
Item AItem B
```
## Imports
Use the Preact entry point:
```tsx
import "@shopify/ui-extensions/preact";
import { render } from "preact";
```
### Polaris web components (`s-banner`, `s-badge`, etc.)
Polaris web components are custom HTML elements with an `s-` prefix. These are globally registered and require **no import statement**. Use them directly as JSX tags:
```tsx
// No import needed — s-banner, s-badge, s-button, etc. are globally available
Welcome back
Order placed
```
When the user asks for Polaris web components (e.g. `s-banner`, `s-badge`, `s-button`, `s-text`), use the web component tag syntax above.
**Web component attribute rules:**
- Use **camelCase** attribute names: `alignItems`, `paddingBlock`, `borderRadius` — NOT kebab-case (`align-items`, `padding-block`)
- **Boolean attributes** (`disabled`, `loading`, `dismissible`, `checked`, `defaultChecked`, `required`) accept shorthand or `{expression}`:
- ✅ ``, ``, ``
- **String keyword attributes** (`padding`, `gap`, `direction`, `tone`, `variant`, `size`, `background`, `alignItems`) must be string values — never shorthand or `{true}`:
- ✅ ``, ``, ``
- ❌ ``, `` — boolean shorthand on string props fails TypeScript