Overview

Welcome to the iVend Retail Release Notes! This document provides an overview of the latest enhancements, fixes, and new features introduced in iVend Retail. Each update is designed to optimize retail operations, enhance user experience, and ensure seamless integration with evolving business needs. 

In this release, we continue our commitment to innovation, stability, and performance, addressing key improvements across various modules. Whether it's refined functionality, improved security, or user-friendly enhancements, our goal is to support retailers in delivering outstanding customer experiences. 

About

Enhancements

Enhancements included in this update are as follows:

1. SchedulerService Loyalty Failed records job interval configurable

In the Enterprise SchedulerService, transactions that fail during loyalty point awarding are retried every 15 minutes. This frequent retry mechanism increases database load, prompting a customer request to make the interval configurable.

This enhancement allows  the retry interval for the job to be configurable. We can specify the desired interval in the Configuration.xml file located within the SchedulerService folder.

2. Patch deployment using shared folder

Previously, when deploying patches using the Application Patch feature in the Management Console on Enterprise, the patch would upload to a cloud location. On Stores and POS, the patch files need to be downloaded from the same cloud location. This caused deployment failures at stores and POS terminals without internet connectivity. With this enhancement, patches can now be deployed using a shared network folder, allowing successful deployment even in offline environments.

3. Coupon as Tender

At present, On POS, coupons could not be used as a tender type during sale transactions. Coupons are used to apply discounts only. With this enhancement, POS allows coupons to be used as a tender type during sales. This can now be configured through the retail profile settings. providing greater flexibility in handling promotions at the POS.

4. Replication Events Generated for Physically Closed Stores in iVend

In iVend, if a store is physically closed but still marked as active in the system, iVend Enterprise continues to generate replication events for that store. Since the store is no longer operational, these events remain unprocessed, resulting in a buildup of “Not Processed” entries in the Enterprise system. To address this, enhancements have been introduced to prevent replication data from being sent to stores that have been physically removed but not permanently deleted from the database. This ensures that replication events are no longer generated for such stores, reducing unnecessary “Not Processed” entries and improving overall system performance.

5. Customer Email Option in Sale Edit View

Enhancements have been made to the system to display and modify the customer email directly on the Sale Edit screen. By entering a valid email address in this view, users can now send emails to customers who are not yet enrolled in the system. This allows for improved communication with walk-in or new customers without requiring full registration, enhancing flexibility and user convenience at the POS.

6. New API Method – UpdateStatusIntegrationRecords

In this system enhancement, a new API method named UpdateStatusIntegrationRecords has been introduced to allow external systems to update the status of integration records within the application, enabling better control, monitoring, and management of integration workflows.

7. Pricelist Rights Based on Retail Profile and UPC Code Search Functionality

The system has been enhanced to improve Pricelist management and product search capabilities:

A new Product UPC field has been added to the Pricelist screen

This allows users to search for products using their UPC codes, enabling faster and more accurate item lookup.

Pricelist Modification Rights have been introduced at the Retail Profile level

This allows system administrators to configure user privileges for adding, updating, and deleting items in the pricelist. This enhancement addresses specific customer requirements by offering more granular control over pricelist modifications based on user roles.

8. New API for Managing Serial Inventory Updates

In this system enhancement. a new API has been developed to handle serial-based inventory updates within the system. This API is designed to create events only when a serial number is not already present, while events related to existing serials will be ignored, ensuring efficient and accurate inventory synchronization.

9. Apply Promotions/Bonus Buys on Quotations Based on Retail Profile Setting

A system enhancement has been implemented to allow the application of Promotions and Bonus Buys on Quotations, controlled by a new setting called "Allow Promotion With Quotation" in the Retail Profile. When this setting is enabled, users can apply applicable promotions directly on quotations as per their business needs, providing greater flexibility in promotional handling during the quotation process.

10. Exposure of UOM Fields in Product API for SAP Integration

To address the issue where iVend POS was not recognizing the Purchase and Sale UOMs defined in SAP for a product, the iVend API has been enhanced to expose the following fields in the Product API:

• PurchaseUOMKey

• PurchaseUOMPackageKey

• SaleUOMKey

• SaleUOMPackageKey

• InventoryCountingUOMKey

This enhancement ensures proper synchronization of unit of measure data between SAP and iVend.

11. Account Type Selection Required for Moneris Payment Processor Integration on POS

When both legacy and new Moneris payment processor integrations are enabled in a store, users are required to manually select the account type in the Credit Card Payment Details screen on the POS, leading to potential user errors and delays during checkout.

The enhancement ensures to pre-select the required account type on POS credit card payment screen, so that users can proceed without selecting account type, streamlining the Credit Card payment process. The enhancement is specifically triggered when both Moneris integrations are active in a store and properly configured in the POS setup screen.

12. Enhanced Auto-Login for Domain Users

The Point of Sale (POS) and Management Console (MC) systems now support seamless auto-login for domain users, eliminating manual authentication steps. This enhancement streamlines access by leveraging the SAM name configured at Security User, ensuring a more efficient and intuitive login experience.

13. MRP Field Added to Batch Detail

The Batch detail section now includes a new Maximum Retail Price (MRP) field, enabling seamless storage of MRP alongside batch information. This enhancement ensures users can easily view MRP while selecting batch items in the Point of Sale (POS) system, improving pricing transparency and operational efficiency.

14. Exclusion of Price lists from Store backup

To reduce the size of the backup file, filter out any unnecessary price lists from the Store backup. This will ensure that only the applicable price lists for the selected store are included in the store backup. Below are the revised inclusion and exclusion criteria:

For Store Backup

• Price lists attached to any customer will always be included in the backup.

• Price lists that are neither linked to a customer nor a store will be included in the backup.

• Price lists not attached anywhere will always be included.

• Price lists associated with a specific store will always be included.

• Price lists associated with another store will not be included.

• Special price lists created based on a customer will always be included.

• Special price lists created based on a price list and linked to the store will always be included.

• Special price lists created based on a price list that is not associated with any store will always be included.

• Special price lists linked to another store will not be included in the store backup.

• Price lists associated with another store but also attached to a customer will be included in the backup.

For Offline POS Backup

• If the Offline POS is connected to the Head Office (HO), it will display the same data as seen in HO.

• If the Offline POS is connected to a store, it will display the same data visible in that specific store.

15. Transaction Limit for Loyalty Special Days

A new enhancement introduces the Applicable Transaction Count field in the Loyalty Plan definition screen, allowing businesses to set a limit on transactions eligible for special-day loyalty offers. Previously, no restrictions were in place, but this update ensures controlled application of promotions, enhancing fairness and managing usage effectively.

Bug Fixes

Bug fixes included in this release are listed below:

1. Multiple cancellation of single Special order causing Integration Failure

The system encounters an integration failure due to cancelling a single sales order from multiple POS terminals.

Fix:

This patch addresses the issue by ensuring that once a sales order is closed from one POS terminal, it cannot be closed again from another, thereby preventing conflicts during integration.

2. Incorrect refund amount on cancelling a Special Order, which was partially cancelled earlier

When fully cancelling a Special Order that had already been partially cancelled, the system incorrectly calculated the refund based on the original order amount—ignoring the previous partial refund. As a result, the payment screen incorrectly shows that the customer still had an outstanding balance for items that had already been refunded..

Fix:

This patch ensures, the system now accurately calculates the refund amount by taking previous partial cancellations into account, ensuring that both the refund and payment status are displayed correctly.

3. POS incorrectly detecting as Manual Scan when scanned using a Plug and Play barcode scanner

On POS, when scanning barcodes that contain alphabetic characters using a plug-and-play barcode scanner, the POS system was not correctly recognizing the scan as scanned by a Scanner and treating it as a Manual scan, leading to inaccurate processing.

Fix:

This patch ensures the POS system to correctly identify and handle barcode scans that include letters, ensuring accurate recognition as scanned by Scanner when using plug-and-play scanners.

4. Maximum discount not applying correctly

When applying a line item discount in the iVend POS screen, the system did not correctly validate the discount after adjusting item quantities.

Scenario:
If the maximum allowable discount is configured at 5%, and a user initially sets the quantity to 10 units and applies a valid 5% discount, the system accepts it. However, if the quantity is later reduced back to 1, the originally applied discount remains unchanged, even if it exceeds the allowed limit for the updated quantity.

Fix:

This patch ensures the system includes validation to ensure that if the applied discount exceeds the configured maximum, a prompt message is shown. This helps prevent discounts from exceeding the allowed limit when item quantities are modified.

5. Discount Functionality Not Working as Expected in Specific Scenarios

There are three scenarios where the discount mechanism in iVend POS does not function as expected:

Scenario 1:
When a Line Discount is applied using the designated button on the POS screen, the discount appears visually but is not validated at that moment. Validation only occurs after clicking the Payment button.

Scenario 2:
Similar to Scenario 1, the Line Discount is displayed on the POS screen when applied using the button, but it is not immediately validated. The system enforces discount rules only during the payment stage.

Scenario 3:
In cases involving Manager Override, the system allows applying the maximum discount configured in the system only if no discount is defined at the item level. If a specific discount is already set in the Item Master, the Manager Override does not override that item-specific discount.

Fix:

An issue affecting the line level discount functionality during manager override operations has been resolved. The system now correctly applies the discount as per defined rules when a manager override is performed.

6. Inventory Mismatch Between SAP and iVend Due to UOM Set as 'NO' During Inventory Transfer

An issue was identified where an inventory mismatch occurred between SAP and iVend during inventory transfers when the Inventory UOM (Unit of Measure) was incorrectly set as 'NO'. This incorrect UOM setting led to discrepancies in inventory quantities between the two systems.

Fix:

The issue affecting stock transfers for products with inventory UOMs different from their base UOMs has been resolved. The system now accurately processes and reflects inventory movements for such products, ensuring consistency across transactions.

7. GetQueue API Not Returning Data for LoyaltyCardInformation Events

The GetQueue API was not returning any data when the queue contained events of type LoyaltyCardInformation. This issue prevented successful retrieval of such event data during queue processing.

Fix:

The API code has been modified to ensure that LoyaltyCardInformation event data is now correctly returned, resolving the issue where such events were previously not retrieved.

8. Incorrect Results in Inventory Valuation Report with 'Hide Zero' Filter in iVend MC

The Inventory Valuation report in iVend MC was displaying incorrect results when the 'Hide Zero' filter was applied, leading to inaccurate representation of inventory data in the report output.

Fix:

The code for the 'Hide Zero' filter in the report has been updated to improve accuracy and ensure correct data is displayed when the filter is applied.

9. Incorrect Discount Amount in iVend MC Sales Report with Bonus Buy and Manual Discounts

The Sales Report in iVend MC was displaying an incorrect discount amount for POS transactions that included both Bonus Buy discounts and manual discounts, resulting in inaccurate reporting of total discounts applied.

Fix:

All line item discount columns have been replaced with the unified 'Discount Amount' field from the SaleItem table to ensure consistency and accuracy in discount calculations and reporting across the system.

10. Batch Selection Not Processing During Stock Transfer Receipt

When a user attempts to receive a shipment and the batch selection screen appears, selecting a batch and entering the quantity, clicking OK returns to the Stock Transfer Receipt screen without performing any action. The system fails to process or reflect the selected batch and quantity, preventing completion of the receipt operation.

Fix:

The issue affecting stock transfer receipt for batch-managed products has been fixed. Previously, when a stock transfer request was created using an Inventory UOM, the system failed to process the batch selection properly. This behavior has now been corrected, and the batch receipt functions as expected.

11. HTTP 500 Error When Deactivating Loyalty Card Using UpdateLoyaltyCustomer API

An error was occurring while using the UpdateLoyaltyCustomer API method to deactivate a loyalty card, resulting in a HTTP 500 Internal Server Error. This prevented successful processing of the deactivation request.

Fix:

The API code has been fixed to ensure that the provided field values are now saved correctly, resolving previous issues with data not being recorded as expected during API operations.

12. MRP Execution in iVend MC Not Displaying Recommendations

When the customer executed MRP (Material Requirements Planning) in iVend MC, the system failed to display any recommendations, preventing users from viewing or acting upon the suggested procurement or replenishment actions.

Fix:

Changes have been made to the MRP procedure to ensure that recommendations are correctly generated and displayed at the store level for stock transfers, improving the accuracy and usability of the MRP process.

13. MRP Execution Error for Local Transfer Type at Store Level

An error occurs when running MRP at the store level with Local Transfer as the transfer type. The system references the warehouse key of the destination warehouse for the stock transfer request, leading to the following error:

"Conversion failed when converting the nvarchar value to data type int."

This issue is specific to Local Transfer scenarios and prevents successful MRP execution.

Fix:

The issues in the MRP Stored Procedure (SP) have been fixed to ensure accurate and reliable generation of procurement and replenishment recommendations.

14. HTTP 500 Error When Using GetCustomer() API Method

The customer encountered an error while using the GetCustomer() API method to retrieve customer records. The system returned "HTTP/1.1 500 Internal Server Error", preventing the successful extraction of customer data through the API.

Fix:

Changes have been implemented in the GetCustomer API to ensure customer records are fetched correctly during the API call, resolving previous issues with data retrieval.

15. Incorrect Average Item Price in iVend Base Report "Sale by Transaction"

The iVend base report "Sale by Transaction" was displaying an incorrect average price for items, leading to inaccurate reporting of item-level sales performance.

Fix:

The formula for calculating the average price has been corrected by updating it to use UOM Quantity instead of Quantity, ensuring accurate average price values in the report.

16. Duplicate Loyalty ID created

When two POS terminals in the same store simultaneously create a loyalty customer, the system incorrectly assigns the same loyalty ID to both loyalty cards.

Fix:

The patch resolves the issue with a Validation has been implemented to prevent duplicate loyalty ID assignment by ensuring each loyalty card receives a unique ID during creation.

17. Premature Purchase Order Closure Triggers Integration Error

When a user creates a GRPO in iVend, the system also creates a PO at nearly the same time. Because of this, the PO is marked as "closed" too early in both SAP B1 and iVend. So later, when the system tries to link the GRPO with the PO, it fails and triggers an error stating, "PO is already closed."

Fix:

This patch addresses the issue by preventing the premature closure of Purchase Orders in SAP B1 and iVend when a GRPO is created concurrently, ensuring proper linkage and eliminating the "PO is already closed" error during integration.

18. Duplicate Transaction Id generated from Mobile POS

When using Mobile POS in offline mode, doing several transactions before syncing can cause duplicate transaction IDs to be created.

Fix:

The patch solves the issue by adding a check that stops duplicate transaction IDs. Before setting an ID, the system looks to see if it already exists. If it does, it creates a new one and checks again—making sure every ID is unique.

19. Sales Order Update Restriction Causing iVend to SAP B1 Integration Failure

The integration between iVend and SAP Business One fails with the error message: "Field cannot be updated on Sales Order." This occurs when the system attempts to update sales order lines that have already been closed during synchronization.

Fix:

This patch ensures that only open sales order lines from SAP Business One are transmitted to iVend, preventing unintended modifications to closed sales orders and maintaining data integrity.

20. Stock Transfer Shipment Line Item Replication Issue

Some line item details in stock transfer shipments were not transmitted from the enterprise to the destination store, resulting in incomplete data at the receiving location.

Fix:

This patch updates the database script to first clear outdated procedure references before applying the latest version. This ensures the updated logic is executed correctly, allowing complete replication of stock transfer shipment details at the receiving store.

21. POS Screen Freeze During Credit Card Refund with Elavon Payments

When processing a credit card refund through Elavon Payments, the POS screen freezes and stays stuck on the "Processing" message.

Fix:

This patch updates the POS logic to use the UniqueIdentifier field from the TrxTransactionPayment table to find the original payment transaction. This ensures the system correctly identifies and retrieves the matching record, preventing freezes and allowing refunds to process smoothly.

22. Loyalty Points Incorrectly Awarded for Layaway Transactions in iVend POS

In iVend POS, layaway transactions are mistakenly earning loyalty points, even though the loyalty program settings exclude them. This leads to incorrect point calculations

Fix:

This patch adds validation checks to ensure loyalty points are calculated correctly. It enforces exemption rules so that layaway transactions do not earn points, keeping the system aligned with the loyalty program settings.

23.  Purchase Order Row Status Discrepancy in SAP B1

When a row is deleted and a new one is added to a Purchase Order (PO) in iVend, the newly added row is incorrectly marked as "closed" in SAP Business One (SAP B1). This leads to processing issues and causes discrepancies in PO status between the two systems.

Fix:

This patch ensures that any new rows added to a Purchase Order in iVend remain open in SAP B1, resolving the issue of premature closure and maintaining consistency between the systems.

24. Inconsistent Audit Log Entries Due to UserKey Mismatch

The Audit Log fails to capture certain user updates when the UserKey (lbrUser) does not match the SecurityUserKey (SecSecurityUser). This mismatch prevents the system from logging the activity, leading to incomplete audit trail records.

Fix:

This patch resolves a system issue that was preventing some audit entries from being recorded or displayed. It ensures that all relevant user updates are properly captured and visible in the Audit Log.

25. Preventing Duplicate Job Executions in HO Store Scheduler Due to SchSchedule Table Backup

The Store Backup process includes data from the SchSchedule table, causing the HO Store Scheduler Service to execute duplicate instances of the same job multiple times. This results in redundant job executions and potential scheduling conflicts.

Fix:

This patch modifies the Store Backup process to exclude the SchSchedule table, ensuring the Store Scheduler Service does not execute duplicate jobs, which are running on HO Scheduler Service.

26. Refund Transaction Failure Due to Duplicate Expense Code in Integration

Refund transactions (Credit Memos) fail during integration with the error message:

"System.Exception: DI:480000058 - Expense code 1 is duplicated; please change it."

This duplication of expense codes causes the integration process to halt and prevents successful transaction processing.

Fix:

This patch resolves the issue by skipping expense codes with zero amounts, preventing duplication errors and enabling smooth processing of refund transactions.

27. Zeroed Item Costs in iVend POS for SAP-Generated Purchase Orders

When Purchase Orders are sent from SAP to iVend POS, the item costs are incorrectly reset to zero upon receipt at the stores. This leads to inaccurate cost data within the POS system.

Fix:

This patch resolves the issue by ensuring that item costs from SAP are correctly retained in iVend POS during the PO update process.

28. Loyalty Points Discrepancy in Customer Loyalty Cards

There are discrepancies in the loyalty points recorded on customer cards, leading to incorrect point balances which affects the accuracy of the loyalty program.

Fix:

This patch introduces a validation check to ensure loyalty payments do not exceed the available balance. If the payment amount is greater than the allowed limit, an error is displayed, preventing over-redemption and maintaining accurate point tracking.

29. Object Reference Error Blocks Data Retrieval

The GetTransaction API encounters an object reference error, preventing it from retrieving transaction data and disrupting downstream processes.

Fix:

This patch adds null value checks within the iVend API to prevent object reference errors, ensuring reliable data retrieval and maintaining data integrity across processes.

30. SaveTransaction API Failing to Store AdditionalInformation Field in TrxTransactionPayment Table

The SaveTransaction API isn't storing data in the AdditionalInformation field of the TrxTransactionPayment table, causing missing payment details in transaction records.

Fix:

This patch fixes data storage issues by ensuring the SaveTransaction API correctly saves field values in the table.

31. Customer Balance Not Updating After Advance/Payment Document Generation

Customer balances in iVend are not updating after advance or payment documents are created, resulting in inaccurate balances and potential reconciliation discrepancies.

Fix:

This patch corrects the credit limit field mapping in the Customer API, ensuring accurate data integration and proper updating of customer balances in the system.

32. Duplicate Loyalty Expiry Points Detected in Loyalty Points Table

Duplicate entries for expiring loyalty points are appearing in the Loyalty Points table, potentially leading to inaccurate point balances and issues with tracking expirations.

Fix:

This patch prevents concurrent executions of the Loyalty Expiry Job in the Scheduler Service, ensuring it runs correctly and eliminating the risk of duplicate entries.

33. Password Restriction Notice for New User Setup

When setting up a new user, the system displays the message: "Password should be different from the last five passwords," which can be misleading since new users do not have any password history.

Fix:

This patch corrects the logic to ensure that new users no longer receive the "last five passwords" message during initial password setup, eliminating confusion and improving the user experience.

34. Incorrect User Data Transfer in POS Setup

Using the "Copy Information from Existing User" feature in the Management Console to create a new POS user results in incorrect transfer of certain user details, leading to setup inaccuracies and potential security concerns.

Fix:

This patch resolves the issue by correcting the user copy functionality in the Management Console, ensuring accurate data transfer and preventing historical password data from affecting new user creation.

35. Incorrect Attribute Mapping for Transaction Line Items in POS

In the POS system, transaction line item attributes are misaligned, resulting in attribute values being displayed under incorrect attribute columns. This misrepresentation leads to incorrect item information during the sales process.

Fix:

This patch corrects the mapping of sale item attributes in the POS display template, ensuring that each attribute appears under the appropriate column.

36. MRP Field Not Updating for Batch Items via API in Goods Receipt

The newly added MRP field on Goods Receipt for Batch Items is not being updated when using the API, resulting in missing or outdated MRP information for batch item receipts.

Fix:

This patch ensures that the MRP field for batch items on the Goods Receipt is correctly updated when processed via the API.

37. Duplicate Goods Receipt Issue Due to Unclosed Purchase Order

When a full Goods Receipt is created against a Purchase Order, the system fails to close the Purchase Order as expected. This results in the possibility of creating multiple Goods Receipts for the same order, causing data inconsistencies and operational errors.

Fix:

This patch addresses the issue by ensuring that Purchase Orders are properly closed upon full receipt, preventing duplicate Goods Receipts and maintaining data integrity.

38. Stock Transfer Shipment Fails Due to an error in Store Management Console

While creating a stock transfer shipment in the Store Management Console, users encounter the error:

"Load failed Criteria - Nhibernate.Criterion.QueryOver'2[CXS.SubSystem.Inventory.Batch, CXS.SubSystem.Inventory.Batch]."

This error prevents successful shipment processing and disrupts inventory movement workflows.

Fix:

This patch resolves the issue by ensuring the system correctly selects a single Batch record to validate the existence of the Batch number during Stock Transfer Shipment creation.

39. Inaccurate Open Quantities Causing Order and Inventory Discrepancies

Some sales orders show issues where the open quantity is more than what was ordered or delivered, causing problems with order status and inventory tracking.

Fix:

This patch ensures that sales orders maintain the open quantity at or below the ordered quantity.

40. Incorrect Cumulative Discount Calculation for Reused Coupons in POS

When a customer applies the same coupon multiple times in POS transactions, the system fails to calculate the total discount accurately, resulting in incorrect billing amounts.

Fix:

This patch ensures that for "amount" type coupons, the full coupon value is correctly applied based on the total value of item sales, even when used multiple times in POS transactions.

41. Missing Validation for PaymentTypeAttributeKey in SaveTransaction API

The SaveTransaction API currently does not validate whether the provided PaymentTypeAttributeKey matches the correct PaymentType, which can result in data inconsistencies or errors during transaction processing.

Fix:

This patch enforces validation to ensure that when a PaymentTypeAttributeId  is provided, only the matching PaymentTypeAttributeKey is saved. If only the key is supplied without the ID, the system bypasses this check to maintain compatibility and avoid disruptions for existing users.

42. Customer Display Not Syncing with POS During Promotion Application

Applying a promotion on the POS transaction screen causes a mismatch between the POS and the customer display, resulting in inaccurate or outdated item information being shown to the customer.

Fix:

This patch ensures that the customer display stays in sync with the POS transaction screen, accurately reflecting added promotional items and updated transaction details in real time.

43. Arabic Text in Customer Address Prevents Event Generation and Causes Integration Failure

When customer addresses containing Arabic characters are updated through the Management Console (MC) or POS, the system fails to trigger the corresponding Customer event. This results in integration failures and produces the error: "System.Exception: DI: Invalid value." The issue appears to be improper handling of Arabic text in address fields.

Fix:

This patch resolves the issue by properly processing customer address updates that include Arabic characters, ensuring the "Ship to" address is correctly saved and the necessary integration events are successfully triggered.

44. Incorrect Promotion Key Update After Recall of Suspended Promotion

In transactions with multiple promotions applied, suspending and then recalling the transaction causes the promotion key in the TrxTransactionPromotionDetail table to be incorrectly updated. This leads to inaccurate promotion tracking and potential inconsistencies in transaction data.

Fix:

This patch ensures that when multiple promotions are involved, the correct promotion key is preserved and accurately applied to the corresponding item details, maintaining consistency and accuracy in promotion tracking.

45. Incorrect Loyalty Points Awarded for Gift Certificate Items

When a loyalty plan awards points based on the Bill Value for a specific Tender Type, the system incorrectly includes Gift Certificate items in the calculation, even though they should be excluded. 

Fix:

This patch ensures that Gift Certificate items are properly excluded from loyalty point calculations when the Bill Value criterion is applied, improving the accuracy of loyalty rewards.

46. Payment Signature Retrieval Error After Suspended Transaction Recall 

Recalling a suspended transaction that includes a payment signature in the POS system results in the error: "Signature not found with payment." This prevents the transaction from being completed, as the system fails to retrieve or associate the stored payment signature during the recall process.

Fix:

This patch ensures that payment signatures are properly retained and linked when suspended transactions are recalled, allowing the transaction to complete without errors.

47. Invalid Date Format in SQL Query Halts Loyalty Award Processing

The Enterprise-level Scheduler service failed to execute loyalty award transactions due to an incorrect date format in the SQL query. As a result, loyalty award jobs were interrupted, leading to missed point allocations for qualifying transactions.

Fix:

This patch corrects the date formatting logic in the loyalty award processing module to prevent future failures and ensures that previously failed transactions are reprocessed once the issue is resolved.

48. Replication Timeout Halts LoyPointsSummary Update, Affecting Data Synchronization

Replication is failing due to a timeout error encountered during the update of the LoyPointsSummary table. This issue is causing the replication process to stop mid-way, resulting in incomplete data synchronization between systems. As a result, loyalty point balances may not be accurately reflected across all terminals or backend systems, potentially impacting customer experience and reporting accuracy.

Fix:

This patch ensures that the replication service continues to function reliably during updates to the LoyPointsSummary and LoyPoints tables, preventing disruptions and maintaining accurate synchronization.

49. Fixing POS Pricing Errors Due to Unit of Measure (UOM) Selection

In the POS system, item prices fail to adjust according to the selected Unit of Measure (UOM), leading to inaccurate pricing during transactions.

Fix:

This patch ensures that item prices dynamically update based on the selected Unit of Measure (UOM), displaying the correct price on the POS transaction line.

50. Fixing Data Retention Issues in SaveTransaction API

The SaveTransaction API is not persisting data in several fields across different transaction components. Specifically:

• In the Transaction object, 

The Comment field is not retaining its value.

• In TransactionFulfillments, 

The DeliveryDate and PromisedDate fields are not being saved.

• In TransactionFulfillmentDetailList, 

The ProductPromisedDate field is not retaining data.

This results in incomplete transaction records and impacts downstream processes dependent on these fields.

Fix:

This patch ensures that the specified fields correctly save data to their respective database tables:

• In Transaction: 

The Comment field will now retain data.

• In TransactionFulfillments:

The DeliveryDate and PromisedDate fields will now retain data.

• In TransactionFulfillmentDetailList: 

The ProductPromisedDate field will now retain data.

51. Addressing Multiple Fulfillment Conflict in POS Transactions

In the POS system, attempting to add the same product as both a regular Sale and a Special Order within a single transaction triggers the error: "Some product associated with multiple fulfillment" which blocks the transaction from proceeding.

Fix:

This patch introduces configurable settings that enable businesses to add the same product as both a regular Sale and a Special Order in the same POS transaction without triggering fulfillment conflicts.

52. Fixing Price Update Issues After Stock Transfer Receipt in New Stores 

In newly created stores, product prices are not correctly updated following a Stock Transfer Receipt, resulting in zero pricing that must be manually corrected in SAP.

Fix:

This patch ensures that product prices are properly initialized and maintained during store setup, preventing incorrect pricing after stock transfers.

53. Issue: Ensuring Applied Discounts Are Retained in Quotation to Sale Process

Line-level discounts applied in a Quotation are not retained when the Quotation is converted into a Sale, leading to missing discount values in the final transaction.

Fix:

This patch ensures that all line-level discounts from the Quotation are correctly transferred when the document is converted into a Sale, preserving the intended pricing.

54. Fixing Incorrect PromotionKey Updates in TransactionPromotion Table

The TransactionPromotion table is recording an incorrect PromotionKey, resulting in inaccurate tracking and reporting of applied promotions.

Fix:

This patch ensures that the TransactionPromotion table is updated with the correct PromotionKey, enabling accurate promotion tracking and data integrity.

55. Fixing POS Freezing Issue During Coupon Printing After Transaction

The POS system becomes unresponsive when attempting to print a coupon immediately after completing a transaction, leading to workflow disruptions and delays.

Fix:

This patch addresses the issue causing the POS system to freeze during post-transaction coupon printing, ensuring smooth and uninterrupted operation.

56. Resolving Outdated Pricing in POS Due to Deleted Special Price List

The POS system continues to apply prices from a Special Price list that has already been deleted at the Head Office, leading to the use of outdated pricing during transactions.

Fix:

This patch ensures that stores correctly update their pricing by recognizing and removing deleted Price lists, maintaining accurate and up-to-date pricing at the POS.

57. Resolving Default Selection Issue: "Is Mandatory" Checkbox in Bonus Buy Setup

In the Bonus Buy Setup screen, the "Is Mandatory" checkbox is incorrectly enabled by default for Coupon and Gift Certificate options in the "Get" section, which may lead to unintended configuration behavior.

Fix:

This patch updates the default settings to ensure the "Is Mandatory" checkbox is disabled by default for Coupon and Gift Certificate options, allowing for more accurate promotion setup.

58. Fixing Missing Signature in Transaction Receipt Footer After Editing

In the Management Console’s Receipt Designer, the signature section in the Transaction Receipt footer is removed when the receipt is reopened for editing, causing layout inconsistencies.

Fix:

This patch ensures that the receipt format, including the signature section, remains intact after reopening and saving, preserving the intended design.

59. Resolving Transaction Errors for Batch Numbers Exceeding 32 Characters

Refund or exchange transactions for batch items fail when the batch number exceeds 32 characters, resulting in processing errors.

Fix:

This patch removes the 32-character limit on batch numbers, ensuring that refunds and exchanges for batch items with longer batch numbers are processed without errors.

60. Issue: Remove Attached Price List from Customer Profile using API

A customer requested the ability to remove an assigned price list from a customer record using the API.

Fix:

This patch introduces support for detaching a price list from customer by specifying -1 as the Price List ID in the API request.

61. Resolving Incorrect Discounts for UOM-Based Sales in POS

In the POS system, coupons are not being correctly applied to items sold using Units of Measure (UOM), leading to incorrect discount calculations.

Fix:

This patch ensures that coupon discounts are accurately calculated and applied to items sold with UOM, correcting the discrepancy.

62. Fixing Multiple Integration Events Triggered by UDF Updates in Customer Records

In the Management Console, updating a customer record that includes UDF fields triggers multiple integration events instead of a single expected event, potentially causing redundant processing and integration issues.

Fix:

This patch ensures that when a customer record with UDF fields is updated, only one integration event is triggered, streamlining the process and preventing duplicate actions.

63. Handling Zero-Quantity Batches: Preventing Confusion in Inventory View and Label Printing

Batches with zero quantity continue to appear on the Inventory View and Label Printing screens in the Management Console, causing potential confusion during inventory checks and label printing.

Fix:

This patch ensures that batches with zero quantity are properly hidden from the Inventory View and Label Printing screens, by correctly enforcing the Allow Zero Batch Number setting in the Retail Profile.

64. Store-Specific Limitations in Batch Processing and Order Cancellation

Issues arise when processing batch-wise items or canceling sales orders from a store different than the one where the order was originally created, affecting transaction accuracy.

Fix:

This patch ensures proper handling of batch-wise item processing and sales order cancellations from any store location, enabling accurate fulfillment and tracking of Batch and Serial items across stores.

65. Missing Comment Field in Product Export: Ensuring Complete Data Capture

The exported product list does not include the "Comment" field, while all other relevant data is captured. As a result, the comment field is missing from the output.

Fix:

This patch ensures that the "Comment" field is properly included in the exported product list, providing a complete and accurate data export.

66. Expired Loyalty Points Not Reflecting in Balance Calculation

Expired loyalty points are not being deducted from the customer's available points balance, resulting in an incorrect total of usable loyalty points.

Fix:

This patch ensures that expired loyalty points are properly deducted, keeping the Available Loyalty Points balance accurate and up to date.

67. Stock Transfer Error Preventing Transaction Completion

An error message Id cannot be left blank appears while performing a Stock Transfer from the General Warehouse to the Retail Warehouse. This prevents the completion of the stock transfer transaction.

Fix:

This patch ensures that the Document Number Series configured at the Enterprise level is correctly applied during Stock Transfers from the General Warehouse, allowing the process to complete without errors.

68. Empty POS Patch Update Popup Appears During Startup in Commingled Stores

In Cloud POS for Enterprise across all Commingled stores, an empty POS Patch Update popup appears during POS startup. The popup is displayed without listing any POS terminals, causing confusion for the users.

Fix:

This patch will ensure that the POS Patch Update popup appears only when there are applicable POS terminals listed, preventing confusion during startup in Commingled stores.

69. iVend Management Console Crash Due to Restricted User Permissions

The iVend Management Console crashes when users without permissions to modify "Search Grid" or "Search Grid Column" settings attempt to make changes. This results in an error message—"The application has encountered an error. All the errors have been logged in the system."—followed by an unexpected shutdown.

Fix:

This patch prevents the iVend Management Console from crashing when restricted users try to modify "Search Grid" or "Search Grid Column" settings, ensuring the application remains stable and secure.

70. Report Load Failure with Dynamic UDF Dropdown Multi-Selection

When using a dynamic UDF dropdown parameter with multi-selection enabled in a report, the report loads successfully on the first run. However, if a selection is made and then cleared, the report fails to load and returns the error: "Invalid length parameter passed to LEFT or SUBSTRING function."

Fix:

This patch ensures that dynamic UDF dropdown parameters with multi-selection handle cleared values properly, preventing errors and allowing reports to load as expected.

71. POS Freezing Issue When Clicking 'Payment' After Large Item Scan

The POS application becomes unresponsive when the "Payment" button is clicked repeatedly after scanning a large number of items (around 100) in a transaction. This causes the system to hang for up to 30 minutes, preventing the cashier from continuing with the transaction.

Fix:

This patch ensures the POS remains responsive and stable, even when the "Payment" button is clicked multiple times after scanning a high volume of items, effectively preventing system hangs.

Conclusion

By swiftly deploying patches, retailers can maintain seamless transactions, protect customer data, and uphold efficiency in their daily operations.