Choose a version:

Post-purchase

The post-purchase screen appears after merchants complete a sale, return, or exchange transaction. This screen displays the transaction summary and provides opportunities for follow-up actions, customer service, and revenue generation.

Anchor to Use casesUse cases

Purchase details: Display warranty information, registration links, and care instructions.
Customer follow-up: Launch satisfaction surveys, loyalty enrollment, and follow-up communications.
Upselling: Present complementary products and service add-ons.
External integrations: Connect with CRM (Customer Relationship Management), marketing automation, and inventory systems.

Anchor to Post-purchase targetsPost-purchase targets

Use these targets for purchase completion workflows, post-sale analytics, or integration with external systems for customer engagement and business intelligence.

Anchor to Post-purchase block ,[object Object]Post-purchase block target

pos.purchase.post.block.render

Renders a custom information section within the post-purchase screen. Use this target for displaying supplementary purchase data like completion status, customer feedback prompts, or next-step workflows alongside standard purchase details.

Extensions at this target appear as persistent blocks within the post-purchase interface and support interactive elements that can launch modal workflows using shopify.action.presentModal() for more complex post-purchase operations.

Examples

jsx

import {render} from 'preact';

export default async () => {

render(<Extension />, document.body);

};

const Extension = () => {

return (

<s-pos-block>

<s-button

slot="secondary-actions"

onClick={() => shopify.action.presentModal()}

Open action

</s-button>

<s-text>This is a block extension</s-text>

<s-text>Order ID: {shopify.order.id}</s-text>

</s-pos-block>

);

};

Examples

Description

Add a custom information section to the post-purchase screen for displaying order details or status. This example shows how to create a block that provides supplementary information after completing a sale, with interactive elements that can launch modal workflows.

jsx

import {render} from 'preact';

export default async () => {
  render(<Extension />, document.body);
};

const Extension = () => {
  return (
    <s-pos-block>
      <s-button
        slot="secondary-actions"
        onClick={() => shopify.action.presentModal()}
      >
        Open action
      </s-button>
      <s-text>This is a block extension</s-text>
      <s-text>Order ID: {shopify.order.id}</s-text>
    </s-pos-block>
  );
};

Anchor to Post-purchase action (menu item) ,[object Object]Post-purchase action (menu item) target

pos.purchase.post.action.menu-item.render

Renders a single interactive button component as a menu item in the post-purchase action menu. Use this target for post-purchase operations like sending receipts, collecting customer feedback, or launching follow-up workflows after completing a sale.

Extensions at this target can access the order identifier through the Order API to perform purchase-specific operations. Menu items typically invoke shopify.action.presentModal() to launch the companion modal for complete post-purchase workflows.

Examples

jsx

import {render} from 'preact';

export default async () => {

render(<Extension />, document.body);

};

const Extension = () => {

return (

<s-button

onClick={() => shopify.action.presentModal()}

);

};

Examples

Description
Add an interactive menu item to the post-purchase action menu for operations after completing a sale. This example shows how to create a menu item that accesses order data and launches modal workflows for tasks like sending receipts, collecting feedback, or follow-up processes.
jsx
```
import {render} from 'preact';

export default async () => {
  render(<Extension />, document.body);
};

const Extension = () => {
  return (
    <s-button
      onClick={() => shopify.action.presentModal()}
    />
  );
};
```

Anchor to Post-purchase action (modal) ,[object Object]Post-purchase action (modal) target

pos.purchase.post.action.render

Renders a full-screen modal interface launched from post-purchase menu items. Use this target for complex post-purchase workflows that require forms, multi-step processes, or detailed information displays beyond what a simple button can provide.

Extensions at this target have access to order data through the Order API and support workflows with multiple screens, navigation, and interactive components.

Examples

jsx

import {render} from 'preact';

export default async () => {

render(<Extension />, document.body);

};

const Extension = () => {

return (

<s-page heading="Purchase Post Action">

<s-scroll-box>

<s-text>Order ID: {shopify.order.id}</s-text>

</s-scroll-box>

</s-page>

);

};

Examples

Description

Build a full-screen modal workflow launched from a post-purchase action menu item. This example demonstrates creating complex post-purchase experiences with multi-step processes, forms, and order data access for operations like receipt customization or customer engagement.

jsx

import {render} from 'preact';

export default async () => {
  render(<Extension />, document.body);
};

const Extension = () => {
  return (
    <s-page heading="Purchase Post Action">
      <s-scroll-box>
        <s-text>Order ID: {shopify.order.id}</s-text>
      </s-scroll-box>
    </s-page>
  );
};

Anchor to Best practicesBest practices

Update purchase information in real time: Update displayed purchase information immediately when changes are made to reflect current state, like updated order status, refreshed inventory levels, and changed customer records.
Show clear action confirmations: Show clear success or error messages that specify which purchase was affected and what action was completed, using messages like "Purchase #1001 processed successfully," "Customer survey sent," or "Unable to process - system error."
Ensure purchase continuity: Ensure that post-purchase actions integrate properly with the overall transaction lifecycle and business processes, like updated inventory records, triggered follow-up workflows, and recorded sales analytics.
Handle error states gracefully: Communicate purchase processing limitations clearly instead of generic error messages. If your extension processes purchase data or triggers post-purchase workflows, ensure you handle completion states responsibly, provide clear feedback about processing stages, and communicate any requirements or restrictions that affect purchase finalization or follow-up actions.
Write clear and action-oriented labels: Use action-oriented labels that specify what will happen for this particular purchase, with descriptive titles that clearly indicate the information type. Use labels like "Send receipt by email" or "Purchase Summary" instead of generic labels like "Purchase options" or "Purchase App."
Show current status and purchase information: Show current purchase status, relevant metrics, and action eligibility to support completion decisions, like purchase completion status, "Purchase completed successfully," and order ID and customer details.

Anchor to LimitationsLimitations

You can only render one button component for each POS UI extension using the action (menu item) target.
Order data is read-only through the Order API, which provides only the order ID, name, and customer ID. To access additional purchase information or modify purchase data, use external API calls or integrate with the Admin API through your app backend.

Was this page helpful?

Post-purchase

Anchor to Use casesUse cases

Anchor to Post-purchase targetsPost-purchase targets

Anchor to Post-purchase block ,[object Object]Post-purchase block target

Supported components

Available APIs

Supported components

Available APIs

jsx

Anchor to Post-purchase action (menu item) ,[object Object]Post-purchase action (menu item) target

Supported components

Available APIs

Supported components

Available APIs

jsx

Anchor to Post-purchase action (modal) ,[object Object]Post-purchase action (modal) target

Supported components

Available APIs

Supported components

Available APIs

jsx

Anchor to Best practicesBest practices

Anchor to LimitationsLimitations