Button
The Button component triggers actions or events, such as opening dialogs or navigating to other pages. Use Button to let merchants perform specific tasks or initiate interactions throughout the POS interface.
Buttons provide clear calls-to-action that guide merchants through workflows, enable form submissions, and trigger important operations. They support various visual styles, tones, and interaction patterns to communicate intent and hierarchy within the interface.
Use cases
- Primary actions: Create actions like "Save changes," "Add customer," or "Process payment" that complete workflows.
- Secondary actions: Provide supporting actions such as "Cancel," "Edit," or "View details."
- Navigation: Enable screen transitions or launch modal experiences for complex operations.
- Loading states: Display loading indicators during asynchronous operations while preventing duplicate submissions.
Anchor to examplesExamples
Display a button that responds to user interactions. This example shows a button that displays a toast notification when pressed, demonstrating how to handle button taps and provide immediate feedback to merchants.
Show a button

Show a button
Examples
Show a button
Description
Display a button that responds to user interactions. This example shows a button that displays a toast notification when pressed, demonstrating how to handle button taps and provide immediate feedback to merchants.
React
import React from 'react' import { Button, Navigator, Screen, reactExtension, useApi } from '@shopify/ui-extensions-react/point-of-sale' const ModalComponent = () => { const api = useApi() return ( <Navigator> <Screen title="Home" name="Home"> <Button title="Press me!" onPress={() => api.toast.show('Button tapped!')} /> </Screen> </Navigator> ) } export default reactExtension('pos.home.modal.render', () => { return <ModalComponent /> })TS
import { Button, Navigator, Screen, extension, } from '@shopify/ui-extensions/point-of-sale'; export default extension( 'pos.home.modal.render', (root, api) => { const button = root.createComponent(Button, { title: 'Press me!', onPress: () => { api.toast.show('Button tapped!'); }, }); const screen = root.createComponent(Screen, { name: 'Home', title: 'Home', }); screen.append(button); const navigator = root.createComponent(Navigator); navigator.append(screen); root.append(navigator); }, );
Anchor to propertiesProperties
Configure the following properties on the Button component.
- Anchor to titletitlestringrequired
The text set on the button. When using a button for action (menu item) targets, the title will be ignored. The text on the menu item will be the extension's description.
- Anchor to isDisabledisDisabledboolean
Whether the button can be tapped.
- Anchor to isLoadingisLoadingboolean
Whether the button is displaying an animated loading state.
- Anchor to onPressonPress() => void
The callback that's executed when the user taps the button.
- Anchor to typetypeButtonType
The type of button to render. Determines the appearance of the button.
'primary'- Creates a prominent call-to-action button with high visual emphasis for the most important action on a screen'basic'- Provides a standard button appearance for secondary actions and general interactions'destructive'- Displays a warning-styled button for actions that delete, remove, or cause irreversible changes'plain'- Deprecated as of POS 10.0.0. Using this option will automatically default to'basic'
ButtonType
'primary' | 'basic' | 'destructive' | 'plain'Anchor to best-practicesBest practices
- Choose appropriate variants and tones: Use
primaryvariant for the most important action on a screen,secondaryfor supporting actions, andtertiaryfor less prominent options. Applycriticaltone for destructive actions like "Delete order,"successfor positive actions like "Complete sale," andcautionorwarningfor actions requiring attention. - Provide loading states for async operations: Set the
loadingproperty totrueduring async operations. - Use the command system for component control: Use
andcommandproperties to control modals, overlays, and other components without complex event handlers. - Structure button hierarchies clearly: Place primary and secondary actions together using consistent spacing and visual hierarchy. Position destructive actions separately or use confirmation patterns to prevent accidental activation.
Anchor to limitationsLimitations
- Button titles must be plain strings. HTML, markdown, or rich text formatting isn't supported.
- Loading states replace all button content with a spinner. Custom loading indicators or partial content updates aren't supported.
- Complex button layouts or nested interactive components within buttons aren't supported.