@shopify/ui-extensions 2026.7.0-rc.7 → 2026.7.0

package/src/surfaces/point-of-sale/event/data/TransactionCompleteData.ts

@@ -5,30 +5,10 @@ import type {ReturnTransactionData} from './ReturnTransactionData';
 import type {ReprintReceiptData} from './ReprintReceiptData';
 import {BaseApi} from './BaseApi';
 
-/**
- * The data object provided to receipt targets containing transaction details.
- * @publicDocs
- */
-export interface TransactionCompleteData extends BaseData, BaseApi {
-  /**
-   * Provides access to persistent local storage methods for your POS UI extension. Use this to store, retrieve, and manage data that persists across sessions.
-   */
-  storage: BaseApi['storage'];
-  /**
-   * The transaction data, which can be one of the following types:
-   * - `SaleTransactionData`: Defines the data structure for completed sale transactions.
-   * - `ReturnTransactionData`: Defines the data structure for completed return transactions.
-   * - `ExchangeTransactionData`: Defines the data structure for completed exchange transactions.
-   */
-  transaction:
-    | SaleTransactionData
-    | ReturnTransactionData
-    | ExchangeTransactionData;
-}
-
 /**
  * The data object provided to receipt targets containing transaction details and reprint information.
- * @publicDocs
+ *
+ * @private
  */
 export interface TransactionCompleteWithReprintData extends BaseData, BaseApi {
   /**

package/src/surfaces/point-of-sale/event/data.ts

@@ -1,17 +1,7 @@
 export type {BaseData} from './data/BaseData';
 export type {BaseApi} from './data/BaseApi';
 export type {ReprintReceiptData} from './data/ReprintReceiptData';
-export type {
-  TransactionCompleteData,
-  TransactionCompleteWithReprintData,
-} from './data/TransactionCompleteData';
-export type {
-  CashTrackingSessionCompleteData,
-  CashTrackingSessionStartData,
-} from './data/CashTrackingSessionData';
-
-export type {CartUpdateEventData} from './data/CartUpdateEventData';
-
+export type {TransactionCompleteWithReprintData} from './data/TransactionCompleteData';
 export type {SaleTransactionData} from './data/SaleTransactionData';
 export type {ReturnTransactionData} from './data/ReturnTransactionData';
 export type {ExchangeTransactionData} from './data/ExchangeTransactionData';

package/src/surfaces/point-of-sale/events/cash-tracking-session-events.ts

@@ -1,7 +1,7 @@
 /**
  * Shared fields for every cash tracking session event.
  */
-interface CashTrackingSessionEvent extends Event {
+interface CashTrackingSessionEvent {
   /** The numeric identifier for the cash tracking session. */
   readonly id: number;
   /** ISO 8601 timestamp when the session was opened. */

package/src/surfaces/point-of-sale/events/transaction-complete-event.ts

@@ -8,7 +8,7 @@ import type {TaxLine} from '../types/tax-line';
  * Shared fields on every transaction-complete event, available regardless of
  * `transactionType`.
  */
-interface BaseTransactionCompleteEvent extends Event {
+interface BaseTransactionCompleteEvent {
   /**
    * The transaction type identifier indicating which kind of transaction was completed (for example, `'Sale'` for new purchases, `'Return'` for refunds, `'Exchange'` for item swaps). Narrow on this field to access transaction-type-specific properties.
    */

package/src/surfaces/point-of-sale/events.ts

@@ -17,7 +17,7 @@ export const POS_EVENT_NAMES = {
 } as const;
 
 /**
- * Maps Shopify POS event names to their corresponding `Event` subclass types.
+ * Maps Shopify POS event names to their corresponding payload types.
  *
  * Used as the generic type parameter for `shopify.addEventListener` and
  * `shopify.removeEventListener`.
@@ -25,8 +25,14 @@ export const POS_EVENT_NAMES = {
  * @publicDocs
  */
 export interface ShopifyEventMap {
+  /**
+   * Dispatched when a sale, return, or exchange transaction completes.
+   * Narrow on `transactionType` to access per-type fields.
+   */
   [POS_EVENT_NAMES.TRANSACTION_COMPLETE]: TransactionCompleteEvent;
+  /** Dispatched when a cash tracking session opens. */
   [POS_EVENT_NAMES.CASH_TRACKING_SESSION_START]: CashTrackingSessionStartEvent;
+  /** Dispatched when a cash tracking session closes after reconciliation. */
   [POS_EVENT_NAMES.CASH_TRACKING_SESSION_COMPLETE]: CashTrackingSessionCompleteEvent;
 }
 

package/src/surfaces/point-of-sale/extension-targets.ts

@@ -1,14 +1,3 @@
-import {BaseOutput} from './event/output';
-import {
-  // eslint-disable-next-line import/no-deprecated
-  CashTrackingSessionStartData,
-  // eslint-disable-next-line import/no-deprecated
-  CashTrackingSessionCompleteData,
-} from './event/data/CashTrackingSessionData';
-import {TransactionCompleteData} from './event/data/TransactionCompleteData';
-// eslint-disable-next-line import/no-deprecated
-import {CartUpdateEventData} from './event/data/CartUpdateEventData';
-
 import type {RenderExtension, RunnableExtension} from '../../extension';
 
 import type {DataTargetApi} from './api/data-target-api/data-target-api';
@@ -33,58 +22,6 @@ import type {ReceiptComponents} from './components/targets/ReceiptComponents';
 import type {BasicComponents} from './components/targets/BasicComponents';
 import type {TransactionCompleteWithReprintData} from './event/data';
 
-/**
- * @publicDocs
- */
-export interface EventExtensionTargets {
-  /**
-   * Fires when a transaction completes successfully.
-   *
-   * @deprecated Deprecated as of version `2026-07`. Use the
-   * [`pos.app.ready.data` target](/docs/api/pos-ui-extensions/{API_VERSION}/targets/pos-app-ready-data) with
-   * `shopify.addEventListener('transactioncomplete', callback)` instead.
-   * @private
-   */
-  'pos.transaction-complete.event.observe': (
-    data: TransactionCompleteData,
-  ) => Promise<BaseOutput>;
-  /**
-   * Fires when a cash tracking session starts.
-   *
-   * @deprecated Deprecated as of version `2026-07`. Use the
-   * [`pos.app.ready.data` target](/docs/api/pos-ui-extensions/{API_VERSION}/targets/pos-app-ready-data) with
-   * `shopify.addEventListener('cashtrackingsessionstart', callback)` instead.
-   * @private
-   */
-  'pos.cash-tracking-session-start.event.observe': (
-    // eslint-disable-next-line import/no-deprecated
-    data: CashTrackingSessionStartData,
-  ) => Promise<BaseOutput>;
-  /**
-   * Fires when a cash tracking session completes.
-   *
-   * @deprecated Deprecated as of version `2026-07`. Use the
-   * [`pos.app.ready.data` target](/docs/api/pos-ui-extensions/{API_VERSION}/targets/pos-app-ready-data) with
-   * `shopify.addEventListener('cashtrackingsessioncomplete', callback)` instead.
-   * @private
-   */
-  'pos.cash-tracking-session-complete.event.observe': (
-    // eslint-disable-next-line import/no-deprecated
-    data: CashTrackingSessionCompleteData,
-  ) => Promise<BaseOutput>;
-  /**
-   * Fires when the cart is updated.
-   *
-   * @deprecated Deprecated as of version `2026-07`. Use `api.cart.current.subscribe()` on the
-   * [`pos.app.ready.data` target](/docs/api/pos-ui-extensions/{API_VERSION}/targets/pos-app-ready-data) instead.
-   * @private
-   */
-  'pos.cart-update.event.observe': (
-    // eslint-disable-next-line import/no-deprecated
-    data: CartUpdateEventData,
-  ) => Promise<BaseOutput>;
-}
-
 /**
  * @publicDocs
  */
@@ -126,6 +63,8 @@ export interface RenderExtensionTargets {
    * Renders a single interactive button component as a menu item in the post-return action menu. Use this target for post-return operations like generating return receipts, processing restocking workflows, or collecting return feedback.
    *
    * Extensions at this target can access the order identifier through the Order API to perform return-specific operations. Menu items typically invoke `shopify.action.presentModal()` to launch the companion modal for complete post-return workflows.
+   *
+   * @private
    */
   'pos.return.post.action.menu-item.render': RenderExtension<
     StandardApi<'pos.return.post.action.menu-item.render'> &
@@ -137,6 +76,8 @@ export interface RenderExtensionTargets {
    * Renders a full-screen modal interface launched from post-return menu items. Use this target for complex post-return 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.
+   *
+   * @private
    */
   'pos.return.post.action.render': RenderExtension<
     ActionTargetApi<'pos.return.post.action.render'> & OrderApi,
@@ -146,6 +87,8 @@ export interface RenderExtensionTargets {
    * Renders a custom information section within the post-return screen. Use this target for displaying supplementary return data like completion status, refund confirmations, or follow-up workflows alongside standard return details.
    *
    * Extensions at this target appear as persistent blocks within the post-return interface and support interactive elements that can launch modal workflows using `shopify.action.presentModal()` for more complex post-return operations.
+   *
+   * @private
    */
   'pos.return.post.block.render': RenderExtension<
     StandardApi<'pos.return.post.block.render'> & OrderApi & ActionApi,
@@ -155,6 +98,8 @@ export interface RenderExtensionTargets {
    * Renders a single interactive button component as a menu item in the post-exchange action menu. Use this target for post-exchange operations like generating exchange receipts, processing restocking workflows, or collecting exchange feedback.
    *
    * Extensions at this target can access the order identifier through the Order API to perform exchange-specific operations. Menu items typically invoke `shopify.action.presentModal()` to launch the companion modal for complete post-exchange workflows.
+   *
+   * @private
    */
   'pos.exchange.post.action.menu-item.render': RenderExtension<
     StandardApi<'pos.exchange.post.action.menu-item.render'> &
@@ -166,6 +111,8 @@ export interface RenderExtensionTargets {
    * Renders a full-screen modal interface launched from post-exchange menu items. Use this target for complex post-exchange 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.
+   *
+   * @private
    */
   'pos.exchange.post.action.render': RenderExtension<
     ActionTargetApi<'pos.exchange.post.action.render'> & OrderApi,
@@ -175,6 +122,8 @@ export interface RenderExtensionTargets {
    * Renders a custom information section within the post-exchange screen. Use this target for displaying supplementary exchange data like completion status, payment adjustments, or follow-up workflows alongside standard exchange details.
    *
    * Extensions at this target appear as persistent blocks within the post-exchange interface and support interactive elements that can launch modal workflows using `shopify.action.presentModal()` for more complex post-exchange operations.
+   *
+   * @private
    */
   'pos.exchange.post.block.render': RenderExtension<
     StandardApi<'pos.exchange.post.block.render'> & OrderApi & ActionApi,
@@ -373,6 +322,8 @@ export interface RenderExtensionTargets {
    * Renders a custom section in the footer of printed receipts. Use this target for adding contact details, return policies, social media links, or customer engagement elements like survey links or marketing campaigns at the bottom of receipts.
    *
    * Extensions at this target appear in the receipt footer area and support limited components optimized for print formatting, including text content for information display.
+   *
+   * @private
    */
   'pos.receipt-footer.block.render': RenderExtension<
     {[key: string]: any} & StorageApi & TransactionCompleteWithReprintData,
@@ -382,6 +333,8 @@ export interface RenderExtensionTargets {
    * Renders a custom section in the header of printed receipts. Use this target for adding custom branding, logos, promotional messages, or store-specific information at the top of receipts.
    *
    * Extensions at this target appear in the receipt header area and support limited components optimized for print formatting, including text content for information display.
+   *
+   * @private
    */
   'pos.receipt-header.block.render': RenderExtension<
     {[key: string]: any} & StorageApi & TransactionCompleteWithReprintData,
@@ -425,17 +378,12 @@ export interface RenderExtensionTargets {
  */
 export interface ExtensionTargets
   extends RenderExtensionTargets,
-    EventExtensionTargets,
     DataExtensionTargets {}
 
 /**
  * @publicDocs
  */
 export type RenderExtensionTarget = keyof RenderExtensionTargets;
-/**
- * @publicDocs
- */
-export type EventExtensionTarget = keyof EventExtensionTargets;
 /**
  * @publicDocs
  */

package/src/surfaces/point-of-sale/types/base-transaction-complete.ts

@@ -7,7 +7,8 @@ import type {TransactionType} from './transaction-type';
 
 /**
  * Base interface for completed transaction data shared across all transaction types.
- * @publicDocs
+ *
+ * @private
  */
 export interface BaseTransactionComplete {
   /**

package/src/surfaces/point-of-sale/types/cart.ts

@@ -199,6 +199,10 @@ export interface LineItemComponent {
    * An array of tax lines applied to this component.
    */
   taxLines: TaxLine[];
+  /**
+   * An array of discount allocations applied to this component, providing a detailed breakdown of how discounts are distributed across bundle components. Returns `undefined` if no allocations exist.
+   */
+  discountAllocations?: DiscountAllocation[];
   /**
    * The unique numeric identifier for the product variant this component represents, if applicable.
    */
@@ -259,6 +263,17 @@ export interface Discount {
   type?: string;
 }
 
+/**
+ * Optional configuration for `addLineItem`. Lets a single call create a line item and decorate it with line-item properties, avoiding the extra native call and cart sync of a separate `addLineItemProperties` call.
+ * @publicDocs
+ */
+export interface AddLineItemOptions {
+  /**
+   * Custom key-value properties to attach to the newly created line item. Equivalent to calling `addLineItemProperties` with the returned `UUID`, but applied in the same operation.
+   */
+  properties?: Record<string, string>;
+}
+
 /**
  * Specifies the parameters for adding custom properties to line items. Properties are key-value pairs used for storing metadata, tracking information, or integration data.
  * @publicDocs

package/build/ts/surfaces/point-of-sale/event/data/CartUpdateEventData.d.ts

@@ -1,16 +0,0 @@
-import { BaseData } from './BaseData';
-import { Cart } from '../../api';
-import { BaseApi } from './BaseApi';
-/**
- * The data object provided to cart update extension targets. Contains the current cart state along with device, session, and connectivity information. This data is passed to extensions whenever the cart changes, enabling real-time cart monitoring and cart-based business logic.
- * @deprecated Deprecated as of version `2026-07`. Use `api.cart.current.subscribe()` on the
- * [`pos.app.ready.data` target](/docs/api/pos-ui-extensions/{API_VERSION}/targets/pos-app-ready-data) instead.
- * @private
- */
-export interface CartUpdateEventData extends BaseData, BaseApi {
-    /**
-     * The complete current `Cart` object containing all cart data including line items with products and quantities, pricing totals (subtotal, tax, grand total), associated customer information, applied discounts, custom properties, and editability state. This represents the cart's state at the moment the extension is triggered, reflecting all recent changes. The cart object is read-only in this context—modifications should be made through the Cart API methods.
-     */
-    cart: Cart;
-}
-//# sourceMappingURL=CartUpdateEventData.d.ts.map

package/build/ts/surfaces/point-of-sale/event/data/CartUpdateEventData.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"CartUpdateEventData.d.ts","sourceRoot":"","sources":["../../../../../../src/surfaces/point-of-sale/event/data/CartUpdateEventData.ts"],"names":[],"mappings":"AAAA,OAAO,EAAC,QAAQ,EAAC,MAAM,YAAY,CAAC;AACpC,OAAO,EAAC,IAAI,EAAC,MAAM,WAAW,CAAC;AAC/B,OAAO,EAAC,OAAO,EAAC,MAAM,WAAW,CAAC;AAElC;;;;;GAKG;AACH,MAAM,WAAW,mBAAoB,SAAQ,QAAQ,EAAE,OAAO;IAC5D;;OAEG;IACH,IAAI,EAAE,IAAI,CAAC;CACZ"}

package/build/ts/surfaces/point-of-sale/event/data/CashTrackingSessionData.d.ts

@@ -1,51 +0,0 @@
-import { BaseData } from './BaseData';
-import { BaseApi } from './BaseApi';
-/**
- * The data object provided to cash tracking session start extension targets. Contains information about a newly opened cash tracking session along with device and session context.
- * @deprecated Deprecated as of version `2026-07`. Use `CashTrackingSessionStartEvent` on the
- * [`pos.app.ready.data` target](/docs/api/pos-ui-extensions/{API_VERSION}/targets/pos-app-ready-data) with
- * `shopify.addEventListener('cashtrackingsessionstart', callback)` instead.
- * @private
- */
-export interface CashTrackingSessionStartData extends BaseData, BaseApi {
-    /**
-     * The cash tracking session start data containing the session identifier and the time when the session began. Cash tracking sessions represent the period during which a cash drawer is open and being used for transactions, typically corresponding to a staff member's shift.
-     */
-    cashTrackingSessionStart: {
-        /**
-         * The unique numeric identifier for this cash tracking session. This ID distinguishes this session from other cash tracking sessions and can be used for session-specific operations, reporting, or linking transactions to sessions. The ID is assigned when the session opens and remains constant until the session closes.
-         */
-        id: number;
-        /**
-         * The [ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) timestamp when the cash tracking session was opened and cash drawer operations began (for example, `"2024-05-15T09:00:00Z"`). This marks the start of the staff member's shift or cash handling period. Commonly used for calculating session duration, shift reporting, or determining which transactions belong to which session.
-         */
-        openingTime: string;
-    };
-}
-/**
- * The data object provided to cash tracking session complete extension targets. Contains information about a completed cash tracking session including when it opened and closed, along with device and session context.
- * @deprecated Deprecated as of version `2026-07`. Use `CashTrackingSessionCompleteEvent` on the
- * [`pos.app.ready.data` target](/docs/api/pos-ui-extensions/{API_VERSION}/targets/pos-app-ready-data) with
- * `shopify.addEventListener('cashtrackingsessioncomplete', callback)` instead.
- * @private
- */
-export interface CashTrackingSessionCompleteData extends BaseData, BaseApi {
-    /**
-     * The cash tracking session complete data containing the session identifier, opening time, and closing time. This represents the full lifecycle of a cash drawer session from opening to closing.
-     */
-    cashTrackingSessionComplete: {
-        /**
-         * The unique numeric identifier for this cash tracking session. This ID matches the ID from when the session was opened and can be used to correlate session start and end events, retrieve session-specific data, or link all transactions that occurred during this session.
-         */
-        id: number;
-        /**
-         * The [ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) timestamp when the cash tracking session was opened and began (for example, `"2024-05-15T09:00:00Z"`). This marks the start of the session and can be compared with `closingTime` to calculate the total session duration or shift length.
-         */
-        openingTime: string;
-        /**
-         * The [ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) timestamp when the cash tracking session was closed and ended (for example, `"2024-05-15T17:30:00Z"`). This marks when the staff member completed their shift, closed out the cash drawer, and finalized the session. The time between `openingTime` and `closingTime` represents the active session duration. Commonly used for shift reporting, calculating hours worked, or determining the timeframe for session-specific transactions.
-         */
-        closingTime: string;
-    };
-}
-//# sourceMappingURL=CashTrackingSessionData.d.ts.map

package/build/ts/surfaces/point-of-sale/event/data/CashTrackingSessionData.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"CashTrackingSessionData.d.ts","sourceRoot":"","sources":["../../../../../../src/surfaces/point-of-sale/event/data/CashTrackingSessionData.ts"],"names":[],"mappings":"AAAA,OAAO,EAAC,QAAQ,EAAC,MAAM,YAAY,CAAC;AACpC,OAAO,EAAC,OAAO,EAAC,MAAM,WAAW,CAAC;AAElC;;;;;;GAMG;AACH,MAAM,WAAW,4BAA6B,SAAQ,QAAQ,EAAE,OAAO;IACrE;;OAEG;IACH,wBAAwB,EAAE;QACxB;;WAEG;QACH,EAAE,EAAE,MAAM,CAAC;QACX;;WAEG;QACH,WAAW,EAAE,MAAM,CAAC;KACrB,CAAC;CACH;AAED;;;;;;GAMG;AACH,MAAM,WAAW,+BAAgC,SAAQ,QAAQ,EAAE,OAAO;IACxE;;OAEG;IACH,2BAA2B,EAAE;QAC3B;;WAEG;QACH,EAAE,EAAE,MAAM,CAAC;QACX;;WAEG;QACH,WAAW,EAAE,MAAM,CAAC;QACpB;;WAEG;QACH,WAAW,EAAE,MAAM,CAAC;KACrB,CAAC;CACH"}

package/build/ts/surfaces/point-of-sale/targets/pos.cart-update.event.observe.d.ts

@@ -1,8 +0,0 @@
-import type { ExtensionTargets } from '../extension-targets';
-import '../globals';
-export type * from '../events';
-
-type Target = ExtensionTargets['pos.cart-update.event.observe'];
-export type Api = Target['api'];
-export type Output = Target['output'];
-

package/build/ts/surfaces/point-of-sale/targets/pos.cash-tracking-session-complete.event.observe.d.ts

@@ -1,8 +0,0 @@
-import type { ExtensionTargets } from '../extension-targets';
-import '../globals';
-export type * from '../events';
-
-type Target = ExtensionTargets['pos.cash-tracking-session-complete.event.observe'];
-export type Api = Target['api'];
-export type Output = Target['output'];
-

package/build/ts/surfaces/point-of-sale/targets/pos.cash-tracking-session-start.event.observe.d.ts

@@ -1,8 +0,0 @@
-import type { ExtensionTargets } from '../extension-targets';
-import '../globals';
-export type * from '../events';
-
-type Target = ExtensionTargets['pos.cash-tracking-session-start.event.observe'];
-export type Api = Target['api'];
-export type Output = Target['output'];
-

package/build/ts/surfaces/point-of-sale/targets/pos.transaction-complete.event.observe.d.ts

@@ -1,8 +0,0 @@
-import type { ExtensionTargets } from '../extension-targets';
-import '../globals';
-export type * from '../events';
-
-type Target = ExtensionTargets['pos.transaction-complete.event.observe'];
-export type Api = Target['api'];
-export type Output = Target['output'];
-

package/src/surfaces/point-of-sale/event/data/CartUpdateEventData.ts

@@ -1,16 +0,0 @@
-import {BaseData} from './BaseData';
-import {Cart} from '../../api';
-import {BaseApi} from './BaseApi';
-
-/**
- * The data object provided to cart update extension targets. Contains the current cart state along with device, session, and connectivity information. This data is passed to extensions whenever the cart changes, enabling real-time cart monitoring and cart-based business logic.
- * @deprecated Deprecated as of version `2026-07`. Use `api.cart.current.subscribe()` on the
- * [`pos.app.ready.data` target](/docs/api/pos-ui-extensions/{API_VERSION}/targets/pos-app-ready-data) instead.
- * @private
- */
-export interface CartUpdateEventData extends BaseData, BaseApi {
-  /**
-   * The complete current `Cart` object containing all cart data including line items with products and quantities, pricing totals (subtotal, tax, grand total), associated customer information, applied discounts, custom properties, and editability state. This represents the cart's state at the moment the extension is triggered, reflecting all recent changes. The cart object is read-only in this context—modifications should be made through the Cart API methods.
-   */
-  cart: Cart;
-}

package/src/surfaces/point-of-sale/event/data/CashTrackingSessionData.ts

@@ -1,52 +0,0 @@
-import {BaseData} from './BaseData';
-import {BaseApi} from './BaseApi';
-
-/**
- * The data object provided to cash tracking session start extension targets. Contains information about a newly opened cash tracking session along with device and session context.
- * @deprecated Deprecated as of version `2026-07`. Use `CashTrackingSessionStartEvent` on the
- * [`pos.app.ready.data` target](/docs/api/pos-ui-extensions/{API_VERSION}/targets/pos-app-ready-data) with
- * `shopify.addEventListener('cashtrackingsessionstart', callback)` instead.
- * @private
- */
-export interface CashTrackingSessionStartData extends BaseData, BaseApi {
-  /**
-   * The cash tracking session start data containing the session identifier and the time when the session began. Cash tracking sessions represent the period during which a cash drawer is open and being used for transactions, typically corresponding to a staff member's shift.
-   */
-  cashTrackingSessionStart: {
-    /**
-     * The unique numeric identifier for this cash tracking session. This ID distinguishes this session from other cash tracking sessions and can be used for session-specific operations, reporting, or linking transactions to sessions. The ID is assigned when the session opens and remains constant until the session closes.
-     */
-    id: number;
-    /**
-     * The [ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) timestamp when the cash tracking session was opened and cash drawer operations began (for example, `"2024-05-15T09:00:00Z"`). This marks the start of the staff member's shift or cash handling period. Commonly used for calculating session duration, shift reporting, or determining which transactions belong to which session.
-     */
-    openingTime: string;
-  };
-}
-
-/**
- * The data object provided to cash tracking session complete extension targets. Contains information about a completed cash tracking session including when it opened and closed, along with device and session context.
- * @deprecated Deprecated as of version `2026-07`. Use `CashTrackingSessionCompleteEvent` on the
- * [`pos.app.ready.data` target](/docs/api/pos-ui-extensions/{API_VERSION}/targets/pos-app-ready-data) with
- * `shopify.addEventListener('cashtrackingsessioncomplete', callback)` instead.
- * @private
- */
-export interface CashTrackingSessionCompleteData extends BaseData, BaseApi {
-  /**
-   * The cash tracking session complete data containing the session identifier, opening time, and closing time. This represents the full lifecycle of a cash drawer session from opening to closing.
-   */
-  cashTrackingSessionComplete: {
-    /**
-     * The unique numeric identifier for this cash tracking session. This ID matches the ID from when the session was opened and can be used to correlate session start and end events, retrieve session-specific data, or link all transactions that occurred during this session.
-     */
-    id: number;
-    /**
-     * The [ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) timestamp when the cash tracking session was opened and began (for example, `"2024-05-15T09:00:00Z"`). This marks the start of the session and can be compared with `closingTime` to calculate the total session duration or shift length.
-     */
-    openingTime: string;
-    /**
-     * The [ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) timestamp when the cash tracking session was closed and ended (for example, `"2024-05-15T17:30:00Z"`). This marks when the staff member completed their shift, closed out the cash drawer, and finalized the session. The time between `openingTime` and `closingTime` represents the active session duration. Commonly used for shift reporting, calculating hours worked, or determining the timeframe for session-specific transactions.
-     */
-    closingTime: string;
-  };
-}