Skip to main content

Order status

The Order status page displays details for a single order, including line items, fulfillment progress, customer information, and payment status. Extensions on this page help customers get richer context for a specific order without leaving the page.

  • Order tracking widgets: Display real-time shipment tracking with carrier updates and estimated delivery dates directly on the Order status page.
  • Loyalty and rewards context: Show loyalty points earned from the order or progress toward a reward tier.
  • Custom line item details: Add product care instructions, warranty information, or personalization details beneath individual line items.
  • Post-purchase upsells: Surface relevant product recommendations or subscription offers based on the items in the order.

Anchor to Order status static targetsOrder status static targets

Use static targets to extend specific sections of the Order status page with contextual information.

Static targets render after specific page elements, including line items, the line item list, and the customer information section. The examples demonstrate using the Order API and the Order Status Localization API or fetching data from your app's backend.

customer-account.order-status.cart-line-item.render-after

Renders after each individual line item on the Order status page. Use this target to add product-specific information like care instructions, warranty details, or personalization summaries beneath each item.

Extensions at this target can access order data through the Order API and locale context through the Order Status Localization API. This target renders once per line item, not once per order. Avoid making API calls in your extension's root — they'll fire for every line item. Fetch data outside the render function or memoize results.

Support
Components (62)
APIs (29)

customer-account.order-status.cart-line-list.render-after

Renders after the entire line item list on the Order status page. Use this target to display order-level summaries, cross-sell recommendations, or aggregate information that applies to all items.

Extensions at this target can access order data through the Order API and locale context through the Order Status Localization API.

Support
Components (62)
APIs (29)

Anchor to Customer information (render after) ,[object Object]Customer information (render after) target

customer-account.order-status.customer-information.render-after

Renders after the customer information section on the Order status page. Use this target to display additional customer context like account tier, contact preferences, or organization details.

Extensions at this target can access order data through the Order API and locale context through the Order Status Localization API.

Support
Components (62)
APIs (29)

Anchor to Order status announcement and block targetsOrder status announcement and block targets

Use static and block targets to extend the Order status page with announcements and custom block content.

Announcement targets render as dismissable banners at the top of the page, while block targets display as inline cards that merchants can position using the checkout and accounts editor. The examples demonstrate using the Order Status Localization API or fetching data from your app's backend.

customer-account.order-status.announcement.render

Renders a dismissable announcement at the top of the Order status page. Use this target to surface time-sensitive information like delivery updates, delays, or order-specific promotions.

Extensions at this target can access order data through the Order API and locale context through the Order Status Localization API. The root element should be an announcement component.

Support
Components (62)
APIs (29)

customer-account.order-status.block.render

Renders inline content on the Order status page. Use this target to display persistent information like tracking widgets, estimated delivery dates, or order-specific recommendations.

Extensions at this target appear as blocks that merchants can position using the checkout and accounts editor. To preview your extension in each supported location, use the placement reference for that location as a URL parameter.

Support
Components (62)
APIs (29)

  • Guard against missing order data: Always check that shopify.order.value is defined before rendering order-specific content. The order data loads asynchronously and might be undefined on the initial render.
  • Return null for empty states: If your extension has no data to display, such as missing warranty or tracking information, return null to avoid rendering an empty container on the page.
  • Keep announcements order-specific: Unlike order index announcements, order status announcements should relate to the specific order being viewed. Include the order name or relevant order details in the message.

Was this page helpful?