Channel-side calculations for available physical inventory for stores
Important
This content is archived and is not being updated. For the latest documentation, see Microsoft Dynamics 365 product documentation. For the latest release plans, see Dynamics 365 and Microsoft Power Platform release plans.
| Enabled for | Public preview | General availability |
|---|---|---|
| End users by admins, makers, or analysts |  Feb 24, 2020 |
May 1, 2020 |
Business value
Many retailers prefer to get an estimated on-hand value for their store inventory without having to perform real-time service (RTS) calls back to Commerce Headquarters (HQ) to obtain this on-hand data.
Feature details
Channel-side calculation logic that provides an estimated physical available on-hand value will be available for configuration for the point of sale (POS) application. The channel-side estimated inventory calculation will require a periodic "sync" of inventory data from Commerce Headquarters through product availability batch and data sync jobs. The sync is required as the store channel database might not know about inventory transactions posted for the store (such as receipts, count journals, or sales orders processed against the store warehouse from HQ) without getting this information from HQ.
The channel-side calculation will use the data provided by HQ and do a channel-side data check for any unposted sales or returns transactions in the channel database that might impact the store's physical availability for a particular item. The calculation logic will derive an estimated on-hand value for the store inventory as well as any other stores or warehouses that are linked to that store's fulfillment group.
The calculation provides an estimated available inventory only. Because the HQ database is the inventory master, it is not possible to ensure 100% reliability at all times for inventory on hand in the store database. Events can happen in HQ that affect a store's inventory and might not be known by the channel database.
The use of trickle feed statement posting is also required for this functionality.