LS Central version 29.0
With this release, Replenishment functionality will be separated from the core LS Central application and delivered as a dedicated extension.
What's changing?
- Replenishment will be available as the Replenishment for LS Central extension, which requires LS Central as a prerequisite.
- All Replenishment-related objects (except tables) will be moved to this extension.
- Related tables, fields, and data will remain in LS Central for this version. The tables and fields will be marked with ObsoleteState = PendingMove. These remaining components will be fully migrated to the extension in a future release.
- For Actionable Insights, KPIs from the Budgets, Replenishment, and Forecast families, along with KPIs from the Stock Coverage and Store Capacity groups within the Inventory family, will be moved to the Actionable Insights Replenishment Pack. This pack is delivered as part of the Replenishment for LS Central extension.
Frequently asked questions
Upgrading to LS Central v29 (Fall 2026)
Technical details about LS Central v29
Customizations and extensions in v29
Technical details about LS Central v30
Customizations and extensions in v30
General information
| What is changing regarding Replenishment in LS Central v29? | Starting with LS Central v29, Replenishment is no longer part of the LS Central base application. It becomes a separate app, Replenishment for LS Central, distributed through Microsoft Marketplace - similar to LS Retail's Hotels solution. |
| Why is Replenishment being separated from LS Central? |
The change gives partners and customers greater deployment flexibility. Replenishment is a substantial module, so customers who do not use it no longer need to install it. This results in smaller databases, faster deployments and simplified maintenance. For LS Retail, the separation also significantly improves development agility and release management. |
| When does the transition take place? |
The transition happens in two phases across two releases.
The change was deliberately split into two steps so that partners only have to adapt one type of object per release, which keeps the effort and the risk of disruption low. |
| Has this change already been communicated? |
Yes, through several channels. The change was presented to the community at conneXion 2026 in Wiesbaden and has been announced in the LS Central Online Help for some time. A partner newsletter will be distributed to raise broader awareness, and this FAQ page is being published in the Online Help alongside the object mapping tables. Partners are asked to share the information with their consulting, onboarding and sales teams, and to inform any customers whose v29 upgrade planning is affected. |
| Will Replenishment be licensed or charged for separately? |
No. Customers who use Replenishment today continue to be entitled to it. The change is purely about how the functionality is packaged and deployed. The new objects for the Replenishment for LS Central app are in the object range from 73042075 to 73042574. |
| When will the Replenishment for LS Central app be available on Microsoft Marketplace? |
We currently expect the app to become available approximately two weeks after the release of LS Central v29. The exact date is not fully in our control, as publishing on Marketplace depends on Microsoft's review and publishing process, so treat the two weeks as an estimate rather than a committed date. Note: Because of this, customers who use Replenishment should plan their v29 upgrade for after the new app is published. Pre-release versions of LS Central and the Replenishment app will be made available beforehand, so partners who've built customizations can start their preparation without waiting for the release on Marketplace. |
| Will Replenishment have a different release cycle than LS Central? |
No. Replenishment for LS Central follows the same major release cycle as LS Central - two releases per year, on the same timing and with matching version numbers (for example, Replenishment for LS Central v29 accompanies LS Central v29). Because Replenishment is now a separate app, we can in addition publish minor releases for it independently of LS Central if needed, so smaller improvements can reach customers sooner. |
| How much risk does this change carry? | The transition is extensively tested, and the two-step approach across v29 and v30 was specifically designed to minimize disruption for partners and customers. |
Upgrading to LS Central v29 (Fall 2026)
| How does this change affect upgrades to LS Central v29? |
The effect depends on whether the customer uses Replenishment, and whether it has been customized. There are three cases:
Note: The three cases are described in detail in the questions below. |
| Do customers need to update their license? |
It depends:
|
| Do all customers need to postpone their upgrade to v29? |
No. Only customers who actually use Replenishment are affected. For them, the upgrade to v29 may need to be postponed until the Replenishment for LS Central app becomes available on Microsoft Marketplace, because the functionality is no longer part of the LS Central base application. Customers who do not use Replenishment are not affected at all and can upgrade as soon as v29 is released. If you are unsure whether a customer uses Replenishment, check this before planning the upgrade date. |
| What do customers who do not use Replenishment need to do? | No action is required. They can upgrade to LS Central v29 as soon as it is available and do not need to install the Replenishment for LS Central app. These customers benefit directly from the change, since the Replenishment module is no longer deployed into their environment - resulting in a smaller database, faster deployments and simpler maintenance. If such a customer decides to start using Replenishment at a later point, the app can simply be installed from Microsoft Marketplace at that time. |
| What do customers using Replenishment without customizations need to do? |
For these customers the upgrade is straightforward, but it has to wait for the app. The steps are:
|
| What do customers using Replenishment with customizations need to do? |
This group needs the most lead time, so preparation should start as early as possible. The steps are:
Note: A second, smaller adaptation will be needed in v30, when the table objects move to the Replenishment app as well. |
| What actions are taken automatically when the Replenishment app is installed? |
When the Replenishment for LS Central app is installed for the first time, the OnInstallApp trigger handles most of the switch-over automatically:
|
| Which actions are needed after installing the Replenishment app? |
A few things must be done manually after the app is installed.
|
Technical details about LS Central v29
| What happens to the Replenishment objects inside LS Central v29? |
Table objects (tables, table extentions, and table-related enums) remain unchanged and stay in LS Central, so no Replenishment data is moved or converted in v29. Non-table objects (pages, reports, codeunits, and so on) are set to become obsoleted and get the text (Obsolete) appended to their object captions. This means they still exist and can technically still be used, but they are no longer searchable. Note: We do not recommend using those objects - the equivalent objects in the Replenishment for LS Central app should be used instead, since the obsolete ones are removed in v30. |
| What happens to the Replenishment Role Center in LS Central v29? | It is renamed to Replenishment (Obsolete) and disabled by default, so it no longer appears as a selectable Role Center. If someone wants to keep using it, it must be re-enabled. Its actions still point to the original (obsolete) objects, and a warning has been placed on the Role Center to indicate that it is obsolete. Users are switched to the new Replenishment Role Center delivered with the Replenishment for LS Central app automatically when the app gets installed for the first time. |
| What does the Replenishment for LS Central v29 app contain? | Only non-table objects (pages, reports, codeunits, and so on) - the tables and table-related enums remain in LS Central until v30. All objects in the app have new object IDs and new names. With very few exceptions the names are similar to the previous ones, just with a new prefix: LSC REPL instead of LSC. The app also contains a new Replenishment Role Center that points to the new objects, and it is this Role Center that users should work with from v29 onwards. |
| How exactly do object and procedure names change? | In most cases the new object name is the old name with the prefix changed from LSC to LSC REPL. Procedure names are kept the same in most cases; changes were only made to fix typos in names or because of field length constraints. An Excel file with mapping tables for the old and new object names is available in the Online Help. You can find a link in the customizations section below. |
Customizations and extensions in v29
| How are existing customizations and extensions on top of Replenishment affected in v29? | Only non-table objects are affected. For page extensions and similar objects, change the dependency from the LS Central app to the Replenishment app and repoint from the old object to the new object. Event subscribers and the usage of public procedures must be handled in the same way. An Excel file with mapping tables for the old and new object names is available in the Online Help. |
| How can partners prepare their customizations early? | Obtain the pre-release versions of LS Central and the Replenishment app as soon as they become available, redirect the existing customizations from LS Central to the new Replenishment app, and complete testing before upgrading the customer. |
| Where do I find the Excel with the mapping tables? | The Excel files includes information about the old and new Object IDs and names for your reference. It also includes names of public procedures and integration events which were moved and potentially renamed. Please find the file here: |
Technical details about LS Central v30
| What changes in LS Central v30 (Spring 2027)? | Table objects are moved to the Replenishment app using Microsoft's MovedTo / MovedFrom functionality. The non-table objects (pages, codeunits, and so on) that were marked obsolete in v29 are removed from LS Central. The MOVE functionality triggers a SQL Server schema change and does not copy or delete data. You do not need to expect lenghty database operations during the upgrade. |
| What does the Replenishment app contain in v30? | All objects, both table and non-table. The table objects keep their existing object IDs and names. |
Customizations and extensions in v30
| How are existing customizations affected in v30? | Only table-related objects are impacted. For table extensions and similar objects, change the dependency from the LS Central app to the Replenishment app. Event subscribers and the usage of public procedures must be handled in the same way. |
Questions and contact
| Where can partners raise questions or concerns about this change? | If you have any questions, please submit a support ticket to Technical Support or to Martin Kleindl (martin.kleindl@lsretail.com) directly. |