Point of sale extensions
The Store Commerce user interface and business logic can be extended to add custom functionality.
The Store Commerce user interface supports the following extension patterns:
- App bar buttons - Add custom buttons to the app bar on selected pages.
- Custom column sets - Replace the grid columns with custom columns on selected pages.
- Custom controls - Add new controls to selected pages.
To illustrate this functionality better, consider a situation where you need to add a custom column and app bar buttons in the Products search page that display additional information about the product. In the Product details page, you should add custom controls that will display the availability of the product.
The following screenshot shows an example of a custom column and app bar buttons that have been added in Store Commerce.
The custom column is named with the label CUSTOM, and at the bottom of the page is an example of custom app bar buttons. In the app bar buttons extension, you can write custom logic to navigate to a different view, business logic, and so on.
The following screenshot shows an example of a custom control in Store Commerce that you can use to display custom information that is related to the product.
Not all Store Commerce views are extensible. For more information, see Extend Store Commerce views to add custom columns and app bar buttons.
For example, if the Store Commerce view contains a grid, then you can add a custom column in it, but you can't add a custom control. Controls can't be added in views that contain a grid. In the Out-of-Band Management (OOB) Store Commerce UI views, you can't hide controls or buttons, you can only add new custom controls or buttons.
Store Commerce business logic extension
Store Commerce workflow or business logic can be extended. The following sections describe the supported patterns for extensions to extend the existing logic in Store Commerce. For example, you might want to change how a serial number is captured in Store Commerce, change the key in price flow for items, and so on.
Extend - This pattern provides the following extension codes that you can choose according to your needs:
- Triggers - The extension code can add pre or post logic before Store Commerce operations.
- Override handlers - The extension code can override Store Commerce handlers to add custom business logic.
Consume - If the extension is creating new functionality in Store Commerce, then the extension can consume some of the existing APIs or controls in Store Commerce. For example, if you want to add the item to the cart, then the extension can use the AddItemToCart API instead of you having to create custom logic to add the item.
POS APIs - Extension can consume Store Commerce APIs in the extension code.
POS UI SDK - Extension can consume Store Commerce controls and dialogs in the extension views.
Store Commerce extension samples
See the following documentation pages for various Store Commerce extension scenarios and samples.
User interface
For Store Commerce extension scenarios and samples for the UI, select the following links:
Extend Store Commerce views to add custom columns and app bar buttons - For non-screen layout designer- based views.
Workflow
For Store Commerce extension scenarios and samples for the workflow, select the following links:
Store Commerce Triggers - To add pre and post-triggers in Store Commerce operations.
Store Commerce APIs - To learn how to consume POS APIs in extension scenarios.
Override Store Commerce request handler - To learn how to override Store Commerce business logic.