Within the consume, the APIs are sub categorized by module like cart, peripherals, store operations, etc.Ī list of the all of the APIs is available in .ts, which is part of the Retail SDK (.Retail SDK\POS\Extensions\.ts). For example, if you want to change the price of the item based on an external web service call, you can call PriceOverrideOperationRequest to change the price of the item. POS APIs are categorized into three different scenarios:Ĭonsume – Consume public APIs in your extension.Įxtend – Override public APIs to do some additional logic.Ĭreate – Create new APIs using the exposed POS interface, which can be used across extensions.
All the POS APIs are exposed as request/response like CRT and HWS. The POS API simplifies the extension pattern and provides continuous support to build the extensions.Įxtension patterns have been unified across commerce runtime (CRT), POS, and Hardware station (HWS) by following the request/response pattern.
To do this, you need to call the APIs to do the work. you can consume APIs that will do the work for you. For example, if you are extending the Retail POS application to add new features in which to want to get product details, change prices, or add items to a cart. Retail POS APIs help you to easily build extensions or new features to the POS app.
0 kommentar(er)
