LS Central 28.1 Release Notes

About This Release

Released - June 26, 2026

This version is built on Microsoft Dynamics 365 Business Central 2026, release wave 1.

For more details about this BC major version see: https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/whatsnew/whatsnew-update-28-1

Quick links:

Important Notices! 

New or Enhanced Features

Fixed Issues

Hotfixes

Important Notices! 

The LS Central release plan

  • We will release new features for LS Central in two major release waves every year – scheduled for April and October, coinciding with the general availability of Business Central Release Wave 1 & 2. Our partners will be granted access to a feature-complete release candidate five to six weeks ahead of time.

  • We will continue to release new events and hotfixes on a weekly basis and cumulative updates as needed.

  • Minor versions will be made available when considered to be needed by our Development team.

  • In SaaS, we will support the last minor version of the current major version and two back. With this release of LS Central 28.1 we will support 26.1 until 28.1, other and previous versions will not be supported but an upgrade path will be maintained for versions as Microsoft does (see https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/upgrade/upgrade-paths).

We expect to follow this process for the 2026 wave 1 version, with an official release coinciding with the release of Business Central 2026 wave 1 from Microsoft.

New or Enhanced Features

Links to quickly navigate this section:

LS Central Hardware Station Pharmacies
Other POS Commands eCommerce
Hotels    

LS Central

Analytics

Access Analytics for LS Central from Role Centers

Analytics reports can now be accessed from various LS Central Role Centers. Users can setup URLs in the Analytics Setup page to point to the reports. A set default URL function allows to point the reorts to the LS Retail demo reports in the Online Help.

 

Configurable Report URLs in Analytics Setup

A new Analytics URLs group has been added to the Analytics Setup page, giving administrators a single place to manage all report endpoints. The following URL fields are now available:

  • Analytics Dashboard URL
  • Finance Report URL
  • Sales Report URL
  • Inventory Report URL
  • Supply Chain Report URL
  • Bookings Report URL
  • Hotels Report URL
  • Hospitality Report URL
  • Actionable Insights Report URL

One-Click Default Configuration

A new Set Default Values action on the Analytics Setup page populates all URL fields with default values pointing to the reports in the LS Central Online Help. This allows teams to get up and running quickly without manual configuration.

 

Role Center Integration

The Analytics for LS Central action group is available in the following Role Centers:

  • LS Central RC
  • Retail Store Manager RC
  • Retail Store Associate RC
  • Retail Buyer RC
  • Replenishment RC
  • Restaurant Manager RC
  • Bookings Manager RC
  • Membership Manager RC
  • Staff Manager RC
  • Fashion Manager RC
  • Customer Order Manager RC
  • Action Hub RC.

Analytics for LS Central data retention

Analytics provides a retention functionality to delete data from the Analytics database. Users can setup in the Analytics Setup page for how many days data should be kept in the Analytics database. A new pipeline in Analytics, which should be run in a defined interval (for example weekly), cleans up the historical data.

Days to keep Data in Analytics

A new Days to keep Data in Analytics field has been added to the Analytics Setup page. If this value is set to zero (default value), the data retention is inactive. If this value is set to a value greater than zero and the Data Retention pipeline in Analytics is run, the following retention procedures will be called:

  • AnalyticsPurgeOldSalesData
    • stg$Trans_ Sales Entry
    • stg$Transaction Header
    • stg$Sales Invoice Line
    • stg$Sales Invoice Header
    • stg$Sales Cr_Memo Line
    • stg$Sales Cr_Memo Header
    • [DW].[FactSalesPosted]

 

  • AnalyticsPurgeOldPurchaseData
    • stg$Purchase Line
    • stg$Purchase Header
    • stg$Purchase Line Archive
    • stg$Purchase Header Archive
    • stg$Purch_ Rcpt_ Line
    • stg$Purch_ Rcpt_ Header
    • stg$Purch_ Inv_ Line
    • stg$Purch_ Inv_ Header
    • stg$Purch_ Cr_ Memo Line
    • stg$Purch_ Cr_ Memo Hdr_
    • [DW].[fPurchaseOrders]
    • [DW].[fPurchaseReceipts]
    • [DW].[fPurchaseInvoice]
    • [DW].[fPurchaseCreditMemo]

 

  • AnalyticsPurgeOldHospitalityData
  • stg$Din_ Area Plan Statistics
  • stg$Dining Table Receipt Entry
  • stg$Dining Table History Entry
  • stg$Din_ Tbl_ Rcpt_ Entry Arch
  • stg$Din_ Tbl_ Hist_ Entry Arch
  • stg$Din_ Tbl_ Hist_ Entry Res_
  • stg$Din Tbl Hist Entry Res Arc
  • stg$Din_ Reserv_ History Entry
  • stg$KDS Modified Status
  • stg$KOT Line Routing
  • stg$KOT Line
  • stg$KOT Header
  • [DW].[fDiningAreaPlanStatistics]
  • DW].[fDiningReservation]
  • [DW].[fKOTLines]

 

  • AnalyticsPurgeOldTransferData
    • stg$Transfer Line
    • stg$Transfer Header
    • stg$Transfer Shipment Line
    • stg$Transfer Shipment Header
    • stg$Transfer Receipt Line
    • stg$Transfer Receipt Header
    • [DW].[fTransferOrders]
    • [DW].[fTransferOrderShipments]
    • [DW].[fTransferOrderReceipts]

Note: The changes in the Analytics Setup page need to be synched to the Analytics database before the Retention pipeline is executed.

Backoffice

Item Status for Block PO, rather than Purchasing

Retail Item Status was split, to Block Purchase Create and Purchase Process instead of a simple Purchase block.

Add PTE JSON carrier and integration events to CustomerOrderCreate V6 (header, lines, and payments)

You can now attach a small JSON payload to a customer order, its lines, and its payments when you create the order through the Customer Order Create web service (V6).

Two new events let a per tenant extension fill in that data before the request is sent, and read it back once the order's created at the head office.

Note: LS Central never stores this data itself; it is there purely so your extension can pick it up and save it where you need it.

Action required by partners:

  • None to keep using the web service as-is.
  • To use the new capability: Rdeploy the head office with the updated extension and re-register the CustomerOrderCreateV6 request per store so it picks up the new XML schema, then build a per-tenant extension that subscribes to OnBeforeSendCustomerOrderCreateV6 to populate the JSON carrier and to OnAfterCreateCustomerOrderCreateV6 to read it back (correlated by the final document ID) at the head office.

BOM Aggregate for Statement

This new feature should not impact current customers, as the feature is disabled by default.

To use the feature, enable Aggregate BOM at Statement Posting in the Retail Setup. And Prevent Negative Inventory must be off to avoid statement posting error if it hit negative balance.

  • When enabled, at the statement posting the system skips the posting of the BOM and insert the records into a new table BOM Staging Lines.
  • Then the BOM Staging Lines records are processed by a LS Scheduler Job, that sums up the records and posts the consumption and adds the BOM item to inventory.

Add PTE JSON carrier and integration events to CustomerOrderCreate V6 (header, lines, and payments)

You can now attach a small JSON payload to a customer order, its lines, and its payments when you create the order through the Customer Order Create web service (V6).

  • Two new events let a per tenant extension fill in that data before the request is sent, and read it back once the order is created at the head office.
  • LS Central never stores this data itself; it's there purely so your extension can pick it up and save it where you need it.

Action required by partners:

  • None to keep using the web service as-is.
  • To use the new capability: redeploy the head office with the updated extension and re-register the CustomerOrderCreateV6 request per store so it picks up the new XML schema, then build a per-tenant extension that subscribes to OnBeforeSendCustomerOrderCreateV6 to populate the JSON carrier and to OnAfterCreateCustomerOrderCreateV6 to read it back (correlated by the final document ID) at the head office.

eCommerce for LS Central

AL: Make CustomerOrderEditV2 public

LSCCustomerOrderEditV2Utils was made public.

BC Shopify April Updates

  • Support LS Central version 28.
  • LS Central Smart Order routing support.
  • Expired payments in CO were checked.
  • Delete related product data when product is deleted.
  • LS Central Gift card support.
  • Foreign currency handling.
  • Store API key in Isolated storage.

Item sync is deleting Compare at price

Skip Compare Price option was added for Shopify to skip sending Compare price during price updates.

LS Central for hotels

LS Central for hotels for is a separate app extending LS Central.

When using RMS system, allow user to select which derived rate to publish

You can now choose exactly which derived rate codes Atomize updates when it pushes a new base rate. On any Rate-type BEC mapping with Publish Derived Rates enabled, use the new Derived Rates to Publish action to list the codes that should get the recalculated price — codes you leave off stay untouched, with no Daily Room Rate change and no channel-manager push. Leave the list empty to keep today's behavior, where every BEC-enabled derived rate of the base is published.

Action required by partners:

  • None to keep current behavior.
  • To manage specific derived rates by hand, open the Rate-type BEC mapping, enable Publish Derived Rates if needed, and list the codes to publish under Derived Rates to Publish — codes left off are no longer auto-updated by Atomize.

LS Central for pharmacies

LS Central pharmacies for is a separate app extending LS Central.

Pharmacy and CO implementation - CO RX(s) counter is not clickable

FactBox with counter is now allowing access to the Customer Orders related RX lines.

Customer Orders - Usage of LS Central Picking Panel

Changes were added:

  • Unused logic on Picking Panel was deleted.
  • Publishers were changed from obsoleted to new correct one, provided by LS Central team.
  • "LSC CO Line Action" was extended.

Pharmacy and CO Implementation - Modify Pharmacy Customer Orders XMLPorts for the new status logic

The XMLPorts, from the description, are now adopting the new status‑handling logic introduced for Pharmacy Customer Orders.

Regression tests, using the endpoints, are needed.

Pharmacy and CO Implementation - All Pharmacy Customer Orders endpoints under the new enum logic

The remaining Pharmacy Customer Orders endpoints are now following the same Enum logic as used on PHCOSourcingLocationListV.

Pharmacy and CO Implementation - Deprecated LS Central event OnAfterAssignUpdateBufferShipping

The subscriber is now assigned to the event OnAfterAssignCompressedUpdateBufferShipping, which replaces OnAfterAssignUpdateBufferShipping.

Hardware Station for LS Central

Release 2.59.2.0 and 2.59.3.0 in LSPay

The LSPay package was updated, in Hardware Station to 2.59.3.0.

Other

Online Help

The LS Central Help is constantly being updated with the latest information. In this release, articles for the following have been added to the help.

eCommerce

Tips(Gratuity) In Order

Analytics

Analytics - Power BI Guide

POS Commands

There are no new or changed POS commands in this release.

See POS Commands in the LS Central Help and the corresponding Excel list with filters for a complete list of POS commands.

Fixed Issues

Links to quickly navigate this section:

LS Central Pharmacies Fashion
Replenishment KDS and Web KDS eCommerce

LS Central

Backoffice

Member Management

Add possiblity to search for Member Contact Name when selecting an Account to link a new member to

When a new Member Contact is created in the MEMBERCONTACT POS Command, it is possible to link to an account. In the link to account panel, a new Search Contacts button was added. If pressed then Member Contact is searched.

Retail Item

Item Template field not copying to new items ( Assign SerialNo/LotNo In CO Picking field)

The field Assign SerialNo/LotNo In CO Picking is now populated when using an Item Template to create a new Retail Item.

Customer Order

Discount Offer with multi currency in basket calc.

A fix was verified.

Customer Order - discount should not calculate on Sales Order

Customer Orders from eCommerce no longer pick up unintended discounts when converted to a Sales Order.

Previously, when a Customer Order created from a web request was converted into a Sales Order, Business Central would automatically apply the customer's discount group discount to the order lines — even when the original Customer Order had no discount.

  • This lowered the line amounts and triggered an automatic invoice rounding line to reconcile the totals back to the original amount.
  • Customer Orders now transfer to the Sales Order exactly as ordered: line amounts and discounts are preserved, no discount group is re-applied during conversion, and no spurious rounding line is generated.

Safe and Cash management

Safe Management Z-Report Difference Amount showing Transaction from other POS

There was an issue where Safe Management Z-Report Difference Amount showed Transaction from other POS, with Statement method Staff and floating cashier off. This was fixed.

Staff Login Stuck on Terminal on Hybrid Server

Retry action for UpdateStaffCashStatusUtils was added in POS Transaction Server Utility.

POS

Check Endorsement – wrong design string used in the Print Utility

Check endorsement prints, now show the terminal ID once. A wrong design string in the print layout caused the terminal ID to print three times on each endorsement.

Fashion

Price List Line Fixes for Item Import Journal

Several issues were resolved, related to Price List Line creation when importing items via the Item Import Journal:

  • Sales Price Lists are now created according to the Sales Price per Variant setting in the Item Import Vendor Setup, instead of always creating lines per variant.
  • The Assign-to No. and Variant Code fields in the Price List Line are now correctly populated during item creation.

Issue with Purchase Price Factor in Item Import Journal

There was an issue, when importing items using the Item Import Journal, where the New Unit Price was not calculated correctly based on the Purchase Price Factor from Vendor Sales Price Margin. This was fixed.

Replenishment

Invalid Variant Records in Replen. Item Quantity Calculation

When recalculating Replen. Item Quantity (RIQ) for items with variants, records for deleted variants were not removed. This was fixed.

LS Central Modules

eCommerce for LS Central

AL: Missing payment lines on Order Import Shopify

There was an issue, when orders from Shopify, with mix of fulfilled and unfulfilled where pulled, caused missing payment lines in Customer Orders. This was fixed.

Variant Shopify ID inconsistent

There was a mix up in Shopify Variant IDs when Variant Framework included logical order that was not in a standard alphabetical order.

KDS and Web KDS for LS Central

If the Store Filter it is filled, it should only show stores from that filter

The webKDS Restaurants Configured (KDSReport) and Select Store (StoreSelection) pages now correctly honor the Stores To Filter field on BC connections, restricting the displayed stores to those listed across active connections.

  • Previously, an empty or separator-only Stores To Filter produced phantom empty store IDs that were forwarded to the backend, causing no stores to be returned from that connection.
  • Inactive connections also still contributed their filter values, and the Select Store page applied no filter at all.
  • With this fix only active connections (isActive=true) contribute to the filter; an empty filter on any active connection is treated as "no restriction" so all stores are shown; otherwise the union of trimmed, non-empty store IDs across active connections is shown.
  • The same filtering is applied on the Select Store page.

WebKDS users who configured the Stores To Filter field on one or more BC connections now see exactly the stores they expect on both the main page and the Select Store page.

Customers who left the field empty see all configured stores as before.

Hotfixes

See the LS Central Help for information about hotfixes that have been released since the previous release.