The Wish List feature lets LS Central capture member intent in a structured list that can be created on e-commerce sites, mobile apps, or in-store POS, and later fulfilled through POS or back office processes. This document explains how to set up, operate, and troubleshoot the end-to-end process.
This guide should help store teams, ecommerce integrators, and support staff in understanding how wish lists travel from creation through fulfillment inside LS Central
Key building blocks
Wish list master data
- Table LSC Wish List Header (page LSC Wish Lists / LSC Wish List Card) stores core attributes like number, calculation type, owner, barcode, visit counters, and timestamps.
- Deleting a header cascades to lines and links.
Wish list lines
- Table LSC Wish List Line (page LSC Wish List Lines) keeps the desired items, quantities, variants, and hospitality flags.
- FlowFields display purchased quantity and descriptions.
Member links
- Table LSC Wish List Link (page part LSC Wish List Members) ties wish lists to membership cards, defines ownership, edit permission, and sharing status.
Setup
- Page/table LSC Wish List Setup enforces the singleton setup record that holds the number series and optional barcode mask, used when new lists are inserted.
POS panels
- Codeunits LSC Wish List Panel and LSC Wish List Lines Panel provide modal panels that users use to browse, search, print, and apply wish lists to the active transaction.
Web services
- Codeunits such as LSC Wish List Service expose create/get/update/delete/link operations that are consumed through xmlports (for example WishListCreate.xmlport.al).