Provisional Vinculum Release Notes

Version 9.3.173

05th August, 2025

Vin eRetail

Order Management: 

Change Requests/ Enhancements/ Improvements:

  • Addition of Ext. Customer Code Filter in Order and Return Enquiry   


  1. The Order & Return Enquiry module now includes an "Ext Customer Code" filter in Advanced Search to support filtering based on external customer codes.

  2. This enhancement enables users to filter and manage orders and returns based on external customer codes maintained in the external system, improving flexibility. 


Navigation: Vin e-Retail >> Sales >> Order Enquiry >> Advance Search

                    Vin e-Retail >> Returns and Transfers >> Returns >> Return Enquiry


  • Multi Select Support for Channel Filter in Return & Order Enquiry           

  1. The "Order Channel" field has been enhanced from a single-select to a multi-select dropdown in the Failed Order tab of the Order Enquiry screen and in Return Enquiry.

  2. This improvement enables users to filter across multiple sales channels simultaneously, offering greater flexibility and a more efficient way to analyze and manage orders and returns.

Navigation: Vin e-Retail >> Returns & Transfers >> Return Enquiry
                                  Vin e-Retail >> Sales >> Order Enquiry >> Failed Orders

  • Status Based Filtering on SKU Group Enquiry                       


  1. Earlier, SKU Group Enquiry screen displayed only active SKU groups, which limited users from tracking inactive groups or performing actions like review or cleanup.

  2. With this change "Status" column has been added to this screen. Users can now view, filter, and manage both active and inactive SKU groups, enabling more comprehensive oversight and improved data control.

Navigation: Vin e-Retail >> Master >> SKU Management >> Manage SKU Group


Key Bug Fixes:

  • Restriction on Duplicate Channel and Location Name Creation                     


  1. Previously, the system allowed creation of multiple channels or locations with the same name, leading to data duplication and orders being assigned to incorrect locations.

  2. This has been addressed, the system will now restrict the creation of channels or locations with duplicate names, ensuring data consistency and accurate order mapping.

Warehouse Management:

Change Requests/ Enhancements/ Improvements:

  • Enhancement: Picklist Generation Based on Order Line-Level Tags      


  1. The system now supports picklist generation using order line-level tags in addition to the existing order-level tags.

  2. A new dropdown field has been added to the Manage Picklist screen, allowing users to select an order line-level tag.

  3. If the selected tag is associated with any lines within a delivery, the corresponding delivery will appear in the grid, enabling users to generate picklists accordingly.

  4. This enhancement is available for both Order-wise and Zone-wise picklist generation methods.


             Navigation: Vin e-Retail >> Wms >> Manage Picklist  >> By orderlist

                                 Vin e-Retail >> Wms >> Manage Picklist  >> By Zone/Bin



  • Enhancement: Zone Wise Picklist for SKU Location Tag       


  1. The system will now allow a picker to choose from different filters while generating the picklist—based on the SKU location tag. These filters include options to create a picklist for Food, Non-Food, and Fragile items, along with the SKU location tag.

  2. Along with the SKU location tag, the user can apply these filters on the Generate Picklist screen (Zone/Bin-wise), Cycle Count Wave Generation, Letdown Wave Generation, and Putaway Rule.

  • Dimension and Weight fields captured during the Receiving process         


  1. A new feature has been introduced to ensure validation of SKU dimensions—Length, Breadth, Height, and Weight (LBHW)—during the Inbound process.

    1. Upon scanning a SKU, the system checks for LBHW values in the SKU master table.

    2. If all four values are present, the inbound process proceeds as usual.

    3. If any of the values are missing, a pop-up will prompt the user to input the required information.

  2. This functionality is controlled via configuration and can be enabled as needed.

  3. Additionally, a new column named “Update Wt/Dim” has been added at the end of each line in the inbound grid. This allows users to update the dimensions and weight at the line level, similar to the functionality available in Inbound QC. This enhancement is made generic and is available for all clients.

  4. This change ensures that complete and accurate dimensional and weight data is captured at the time of receiving.

Navigation: Vin e-Retail >> WMS>> Inbound  >> Inbound Real Time

Key Bug Fixes:

  • Inbound QC Report Export Missing Passed Quantities                          


  1. The Inbound QC Export Report was only displaying rejected entries, while passed quantities were not included.

  2. This led to incomplete visibility for warehouse supervisors.

  3. The export now includes both passed and rejected entries.

  4. The user ID performing the QC is captured and displayed for all outcomes—passed, rejected, and hold.

  • QC Dropdown Fix: Inactive Reasons Now Disabled and Reordered            


  1. On the Inbound QC screen, users were able to see and select inactive return QC reasons in the dropdown.

  2. Inactive reasons were displayed alongside active ones with no visual separation or restriction.

  3. Postfix inbound QC inactive reason displayed at the end of the reason dropdown list.

  4. Disabled for selection to prevent incorrect usage.

  5. This ensures only active, valid reasons are selectable during return QC processes.

PIM Lite

Change Requests/ Enhancements/ Improvements:

  • Export Failed Records from Lister Import Sheet                         


  1. A new enhancement is requested for the Lister system, applicable to all clients.
    Currently, during Lister Excel sheet import, some SKUs fail due to attribute value mismatches (i.e., values not matching the predefined dropdown options).

  1. To correct these errors, clients are currently required to download the full Lister sheet, identify the failed SKUs, and manually rectify the data.

  2. Only the SKUs that failed during import should be available for download directly from the import result.

  3. This allows clients to easily identify, correct, and re-import only the affected SKUs.
    This change should be applicable only when importing via Lister Excel sheet (not applicable for manual entry or other import types).

  • Frontend Access to Assign/Remove Master Categories for Clients           


  1. Currently, assigning specific master categories to clients is done manually through the database (DB).

                    b. This process limits flexibility and requires backend support each time a change is needed.
                         The new enhancement is to:
                               -  Provide frontend access to manage master category visibility for clients.
                               -  Ensure each client sees only the relevant categories.

  • SKU Attributes Deletion from PIMlite UI Screen 


  1. Currently, the "SKU Attribute Delete" option in the SKU Management screen allows deletion of dynamic attribute data for specific SKUs. 

  2. The same functionality has been enabled for SKU attributes as well.

  • PIMlite Product Creation API Key Generation from UI Screen         


  1. This enhancement has been implemented to generate lister api token from UI screen itself. This has removed the dependency on backend and DB.


Navigation: Admin >> API>> Manage API

  • Output Sorting Method Enhancement    


  1. Previously, sorting in marketplace output from Pimlite was applied only to dropdown attributes.

  2. Now, sorting is enabled for both dropdown and text attributes. Sorting will be applied to a maximum of 6 attributes.

  3. Sorting of attributes can be done at Local and global level from the screen itself.

  1. Path - Configuration >> Local/Global>> Business rule

  • SKU Pull Channel Popup & Pull Date/Time Persistence  


  1. Functionality to have the popup to display the actual channel name(s) where SKU Pull/SKUPull by Id is already enabled.

  1. Add a clear note (thumb rule) stating : "SKU Pull/SKUPull by Id can only be enabled for one channel at a time."

  1. Ensure the "Pull Date & Time" field retains and displays the most recently saved value for each channel, unless it is explicitly cleared by the user.

  1. Only the channel(s) for which the selected SKUPull is enabled should be displayed on the right side.

  2. Introduced  a way to visibly differentiate the type of SKU Pull in both modules:

  • Added a new column or metadata tag like:

  • Trigger Type: Timestamp / SKU ID

  • Or enhance Int Code dynamically to reflect this, e.g., MP_SKUPULL_TS vs. MP_SKUPULL_ID

  • This improved transparency, usability, and internal debugging efficiency.

Key Bug Fixes:

  • Image Re-Generation Now Functional in SKU Management           


  1. While re-generating images from SKU Management , processed images showing 0

  1. The issue has been resolved now.

  • MSRP Validation Bug Fixed in Channel Price Sheet Upload                                                 


  1. There was an error while importing the channel price sheet. Error showed “MSRP should be numeric”

  2. Bug has been rectified now.

Standard APIs

Change Requests/ Enhancements/ Improvements:

  • Addition of New Parameters in Order Invoice Pdf API                        

  1. A new parameter "additionalInvoice" has been introduced in the request of the Order Invoice PDF API to support retrieval of different invoice types.

  2. This enhancement allows users to fetch B2B, Addendum, and e-invoices along with existing B2C invoice through a single API, improving flexibility and reducing integration effort.

                  API Touch point: /RestWS/api/eretail/v1/order/orderinvoicepdf (All versions)

  • Addition of Delivery Location Attributes in PO Pull API Response           


  1. The PO pull API response has been enhanced to include delivery location attributes such as address, phone, email, city, pincode, and GSTIN, offering details pertaining to delivery locations. 

  2. These additions enable more precise and comprehensive retrieval of PO delivery data, improving accuracy in order processing and logistics planning.


                         API Touch point: /RestWS/api/eretail/v1/po/popull  (All versions)


Key Bug Fixes:

  • Enhancements in the Return Cancel API                                       


  1. Earlier, return cancellation was allowed via screen for "Reverse Pick Up Initiated" status, but the same action was failing when attempted through the API.

  2. This inconsistency has been resolved, and the API now supports return cancellation for this status, ensuring consistent behavior across both web and API.


API Touch point: /RestWS/api/eretail/v1/order/returncancel


Financials/ E-filing Systems Integrations:

Change Requests/ Enhancements/ Improvements:

  • Enabling Mandatory E-Invoicing Based on Customer Type            


  1. In certain cases, GSTIN is not available at the time of order creation, preventing the generation of IRN and disrupting the e-invoicing flow for B2B transactions.

  2. To address this, a new "E-invoicing Mandatory" flag has been introduced at the customer type level. When enabled, it ensures that an IRN request is automatically triggered for all orders associated with that customer type, even if the GSTIN is missing, thereby regulating and streamlining the e-invoicing process for B2B orders.


Navigation: Vin e-Retail >> Master >> Other Masters >> Customer Type