Access POSLink v1.0.4.124 includes new allergen and dietary information support from Collins bookings, improved payment integrations, a security enhancement, and a number of bug fixes.
What's new?
Collins allergen and dietary information - Allergen and dietary requirement information from Collins (DesignMyNight) pre-orders is now displayed in a new Allergens tab on the Booking Info form, and passed through to kitchen display screens and printed tickets. Waiters and chefs can see guest allergen and dietary requirements directly on the POS terminal and kitchen display, helping to improve food safety and reduce the risk of allergic reactions.
Adyen referenced refunds - Sites using Adyen as their payment provider can now process referenced refunds. This restores refund capability for sites where unreferenced refunds are disabled on their Adyen account.
Rezlynx room posting by bill number - A new posting method for Rezlynx room charges groups all items from a single bill into one transaction, posted by bill number. Hotel guests now see a single, clean line item on their room folio per bill, rather than multiple separate entries split by category.
GuestPay transaction cancellation - Operators can now cancel an in-progress GuestPay transaction. A new cancel option is available in the GuestPay interface, giving staff more flexibility when a customer changes their mind or an error occurs during checkout.
Software update retry prompt - When a software update file fails to download, operators are now presented with a clear retry option rather than a silent failure, making it easier to recover from an interrupted update.
Credit card security enhancement - The ability to store credit card details locally on the till has been removed from the Capture Credit Card function. Credit card data is now always handled securely via the card machine, improving PCI compliance across all sites.
What we've fixed
We've resolved several issues within the Access POSLink application:
Opera PMS part-payment posting - Fixed an issue where incorrect values were posted to Opera PMS when part-payments with adjustments such as discounts or surcharges were applied. Hotel guests now see accurate charges on their folio when partial payments are used.
Rezlynx surcharge posting failure - Fixed an issue where room charge postings to Rezlynx failed when adjustments were used for surcharges. Room charges now post reliably when surcharges or adjustments are applied.
Void transaction leaving table open - Fixed an issue where voiding a transaction did not close the associated table, leaving it as an orphaned open entry in the system. Voided transactions now correctly release the table, allowing it to be reused immediately.
GuestPay local mode and stability - Fixed several issues with the GuestPay payment integration, including local/offline mode not being handled correctly, incorrect IP detection in local SDK messages, and a crash that occurred when no URL was configured for the service. GuestPay now works reliably in local mode and handles these edge cases without crashing.
Walk-in booking crash - Fixed an issue where attempting to create a walk-in booking for a non-existent table caused the system to crash. The system now displays an appropriate error message instead.
Software update reliability - Fixed issues with the .NET Framework update process that could prevent software updates from installing correctly. Updates now install more reliably, reducing downtime during update cycles.
PMS guest list search - Fixed an issue where searching the PMS guest list modal only scanned a single column, making it difficult to locate the correct guest. The search now scans across all columns, making it faster and easier to find guests when processing room charges.
β οΈ Important: The credit card security enhancement removes the option to enter card details manually on the till. All card payments and refunds must now be processed via the card machine. Please ensure your team is aware of this change before updating.
How to access this update
This update is available from 3 March 2026. To implement the changes, you need to manually update your software version.
