Hotfixes on LS Central version 28.1.x.x

83715 Store Inventory Journal - Duplicate Purchase Orders when posting, when journal contains “Import Incomplete” lines

• Post a Store Inventory journal that still holds lines imported from the Mobile Inventory app but not yet fully received, and you do not get duplicate purchase orders anymore.
• Posting now skips those incomplete lines until the mobile import finishes, and processes them on a later post once they are received.

83600 Discount Amount Issue On Customer Orders

• Details not available.

83594 Collect for Compressed CO Lines Not Working

• There was an issue were Collect did not finish when partially collecting. This was fixed.

83221 EFT Card Printing "Print Buffer" does not have correct Transaction No.

• Details not available.

83144 Resend Kots that were send giving a duplication error

• When the push Kot was being used, the success was, to never send the Touched to false, making the next push send old kots too.

82960 SC-3929-V25 | POS data entry not found issue

• Web requests GetDataEntryBalance and GetVoutcherEntries have been backported to versions 26.1 to 25.0.

82759 Customer Order lines are marked as click and collect = true on ship orders

• Customer Order — POS Collect with inventory transfer
  • When pressing Collect for a Customer Order at POS and the POS store has no inventory of the requested item, sourcing locations configured as ship-only (Will Ship Orders = Yes, Orders can be Collected = No) are now offered in the sourcing-locations lookup as collect-with-transfer options.
  • Selecting such a location creates the Customer Order together with a Transfer Order that moves the item from the remote sourcing location to the POS store where the customer collects it.
  • Previously these locations were excluded from the lookup.

• Customer Order — Optional upfront Sales Order for POS ship orders from stores
  • A new opt-in setup field Derive C&C from Sourcing was added to Customer Order Setup (Click and Collect group).
  • When the field is left disabled (default), the existing behaviour is preserved: POS Customer Order lines sourced from a store-mapped location are marked as Click and Collect and fulfilled via picking and a Sales Order Posted Shipment.
  • When the field is enabled, the line's Click and Collect classification is instead derived from the sourcing location's Orders can be Collected setting.
  • A store-mapped ship-only sourcing then produces a regular ship line with a Sales Order created upfront — allowing the order to be routed through the standard back-office Sales Order workflow (rate shopping, carrier integration, label printing).

80717 POS : SalesPerson Selection Modify Record and Update instead of Multiple Insert

• When a Sales Person is selected the current sales person line is updated instead of adding a new line.

83715 Store Inventory Journal - Duplicate Purchase Orders when posting, when journal contains “Import Incomplete” lines

• Post a Store Inventory journal that still holds lines imported from the Mobile Inventory app but not yet fully received, and you do not get duplicate purchase orders anymore.
• Posting now skips those incomplete lines until the mobile import finishes, and processes them on a later post once they are received.

83144 Resend Kots that were send giving a duplication error

• When the push Kot was being used, the success was, to never send the Touched to false, making the next push send old kots too.

82759 Customer Order lines are marked as click and collect = true on ship orders

• Customer Order — POS Collect with inventory transfer
  • When pressing Collect for a Customer Order at POS and the POS store has no inventory of the requested item, sourcing locations configured as ship-only (Will Ship Orders = Yes, Orders can be Collected = No) are now offered in the sourcing-locations lookup as collect-with-transfer options.
  • Selecting such a location creates the Customer Order together with a Transfer Order that moves the item from the remote sourcing location to the POS store where the customer collects it.
  • Previously these locations were excluded from the lookup.

• Customer Order — Optional upfront Sales Order for POS ship orders from stores
  • A new opt-in setup field Derive C&C from Sourcing was added to Customer Order Setup (Click and Collect group).
  • When the field is left disabled (default), the existing behaviour is preserved: POS Customer Order lines sourced from a store-mapped location are marked as Click and Collect and fulfilled via picking and a Sales Order Posted Shipment.
  • When the field is enabled, the line's Click and Collect classification is instead derived from the sourcing location's Orders can be Collected setting.
  • A store-mapped ship-only sourcing then produces a regular ship line with a Sales Order created upfront — allowing the order to be routed through the standard back-office Sales Order workflow (rate shopping, carrier integration, label printing).

80717 POS : SalesPerson Selection Modify Record and Update instead of Multiple Insert

• When a Sales Person is selected the current sales person line is updated instead of adding a new line.

84096 Keep current rates does not preserve the price on date changes, room-type changes, or upgrades

• Set Keep current rates on the Rate Change page and the price you already have sticks — no matter how you change the reservation.
  • When you move the stay to new dates, change the room type, or upgrade to a higher room type, each night keeps its current rate instead of jumping to the standard rate for the new dates or room.
  • If you manually set a price on a night you add, that price is kept after you confirm.
• Action required by partners:
  • None. Apply the hotfix. The Keep current rates option works as before — no reconfiguration needed.

83879 Balance Recalculation Incorrect After Moving Charges Between Reservations

• When you move a charge from one reservation to another within a group and then take payment, the charge now stays on the reservation you moved it to. Balances on both reservations stay correct, so you no longer see the moved charge lingering on the original reservation, or a negative balance on the reservation you moved it to.
• Action required by partners:
  • None.

83656 Charge-to-room fails for service-charge items from outlet POS ('Property[] not found in Hotel Setup'); add Select All to refund lookup

• Charge an item that carries a service charge profile to a guest's room directly from an outlet POS, such as a restaurant. Selling the item, sending it to the kitchen, and charging the table to the room now posts the item and its service charges to the reservation.
  • Previously this failed with Property[] not found in 'Hotel Setup' and nothing was posted.
  • The POS item-refund lookup also gets a Select all command that marks every line at once — the inverse of the existing Reset all.
• Action required by partners:
  • None. To use the fix, make sure outlet stores have their Service Charge Location configured in Hotel Setup as usual.

83151 ReservationExtraSave API - Updating an existing extra (lineNo ≠ 0) fails with "record is not up-to-date"

• Updating an existing reservation extra through the hotel web API now works.
  • Previously, re-sending an extra with its assigned line number to change a value — such as quantity, unit price, or discount — failed with a record is not up-to-date error, and the change was lost.
  • The line now updates in place, with no duplicate line, and the linked revenue stays in sync.
• Action required by partners:
  • None, beyond applying the 27.1 hotfix.

83150 ReservationExtraSave API - postingPattern=3 (Reservation) silently persists nothing

• Saving a reservation extra with the Reservation posting pattern through the hotel web API now works.
  • Previously the call reported success but saved nothing — no extra line and no revenue entry were created.
  • The extra and its revenue entry are now created.
  • You can also send an optional consumption date to set when the extra posts; omit it and it defaults to the reservation arrival date (matching the back office), and any date you supply must fall within the reservation window.
  • Posting patterns the API cannot handle now return a clear error instead of silently doing nothing.
• Action required by partners:
• None. Optionally, send the optional consumptionDate field on a Reservation-pattern extra to control its posting date; if you omit it, the reservation arrival date is used.

84193 LSC NA - EBT Balance Inquiry sent as GIFT (INVALID PAYMENT TYPE) – LS Pay / Verifone Point

• EBT balance inquiries at the POS now reach the payment terminal with the correct EBT tender type, so cashiers can check a SNAP EBT cardholder’s remaining balance without the terminal rejecting the request.

83586 AL: Order Events and more

• New Event:
  • OnBeforeInsertTempCOHeader
• Public Functions:
  • MakeGQLId
  • GetGQLId
  • ShopifySendGQLReq.