Provisional Vinculum Release Notes

Version 9.3.183

14th April, 2026

Vin OMS & WMS

Order Management: 

Change Requests/ Enhancements/ Improvements:

  • Enhanced SKU Attributes with Extra UDFs                                   

  1. Added additional UDF’s at the SKU level, taking the total UDF count to 25.

  2. Users can now capture up to 25 unique attributes per SKU, allowing for more detailed product data and reporting.

  3. New attributes are fully supported across APIs, ensuring that third-party integrations can sync extended product data without manual intervention.


Navigation: Vin e-Retail >> Master >> SKU Management >> SKU Create/Edit

  • Introduced Payment Details for Return Order                          

  1. Added a new payment details tab for return ensuring return and payment tender information is accurately captured and synchronized during the return process.

  2. Users can now capture returns payment details that involve multiple payment methods, providing better flexibility for complex financial transactions.


Navigation: Vin e-Retail >> Return & Transfers >> Return Create/Edit


  • Enhanced User Master Export with Create and Update Fields               

  1. The User Master export now includes four additional columns: Created Date, Created By, Updated By, and Updated Date.

  2. By adding Create and Update attribute data, the system offers a more secure environment where all administrative actions are traceable, providing immediate visibility into user management activities.    


Navigation: Vin e-Retail >> Admin >> User Enquiry >> Export


Key Bug Fixes:

  • Enhanced Data Validation for Order Creation                                  

  1. The Order Creation now includes a mandatory check for the quantity field at the line-item level. Line items containing items with 0 quantity will now be restricted. Logic has been implemented to ensure that only orders with valid, non-zero line items are created.

  2. Users will no longer see invalid, zero-quantity items in system, reducing confusion during order processing and reporting


Warehouse Management:

Change Requests/ Enhancements/ Improvements:

  • QC Inventory Tracking & Movement from Staging                                 

  1. Introduced a system-driven process to move inbound inventory (LPN/Pallet) between Staging and QC bins. 

  2. Added “QC Movement” option in both Web (LPN Enquiry) and Mobile App (Receiving module). 

  3. Enabled two movement flows:

    1. Staging → QC (for quality check processing) 

    2. QC → Staging (post QC completion)

  4. Implemented bin type validations to ensure movement only to valid QC or staging bins. 

  5. Provided scan-based LPN/Pallet movement with real-time visibility (total scans & last scanned LPN). 

  6. Enabled putaway directly from QC bins without disrupting standard putaway rules. 


Benefits 

  1. Improved Inventory Visibility: Real-time tracking of QC inventory at LPN/Pallet level. 

  2. Process Control: Ensures structured and system-driven QC movement instead of manual/external handling. 

  3. Error Reduction: Validations prevent incorrect bin usage and misplacement of inventory. Operational Efficiency: Faster QC segregation and seamless movement via web and mobile. 

  4. Flexibility in Operations: Supports reverse movement (QC → Staging) for reprocessing scenarios. 

  5. Seamless Integration: Works within existing inbound and putaway flows without impacting current logic.


Navigation: WMS >> Miscellaneous >> LPN Enquiry

  • SKU-Level Scan Mode Control (Bulk vs Each)                             

  1. A new “Disable Bulk Quantity Entry” option in the SKU Master. 

  2. Enabled SKU-level control to restrict scan mode: 

    1. If enabled → Only Each scanning is allowed. 

    2. If disabled → Both Bulk and Each scanning allowed as per existing settings. 

  3. The system will auto-restrict the quantity to 1 when a bulk scan is attempted for restricted SKUs.

  4. Applied across all key warehouse operations: Inbound, Putaway, Picking, Sorting, Inventory Move, Cycle Count, Letdown, Pack Scan. 

  5. Extended support via APIs and Import for SKU create/update.


Benefits 

  1. Improved Accuracy: Prevents incorrect bulk scanning for sensitive or serialized SKUs. 

  2. Better Process Control: Enables SKU-specific scan behavior based on business needs. 

  3. Errors: Eliminates quantity mismatches caused by unintended bulk entries. 

  4. Operational Consistency: Ensures uniform scan logic across all warehouse processes. 

  5. Flexible Configuration: Works alongside existing scan settings without impacting current flows.


Navigation: WMS >> SKU Management >> SKU Create/Edit

  •  Document Attachment in GRN In-Process Status              

  1.  Users can now attach documents during the GRN In-Process stage in inbound.

  2. A new “Save Document” button is introduced on the inbound screen when the status is GRN In-Process.

  3. Attachments are securely stored and linked to the respective inbound record.

  4. Supported across both Process by Scan and Process by Table flows.


Navigation: WMS >> Inbound >> Inbound Real Time

  • Dual Scanning Support (EAN + QR Code with EXTLOTNO)                              

  1. The system now supports simultaneous scanning of the EAN and the QR Code (EXTLOTNO).

  2. QR codes mapped to lot attributes (EXTLOTNO) can be scanned directly in the SKU field.

  3. Automatic SKU and lot details identification upon scanning QR codes.

  4. Configurable validation using config based functionality (prefix, suffix, regex, SKU mapping).

  5. Applicable across all major warehouse operations, including:

    1. Inbound

    2. Inbound QC

    3. Putaway

    4. Picking, Packing & Sorting

    5. Inventory Movement 

    6. Stock Adjustment

    7. Cycle Count

Benefits

  1. Eliminates the need to relabel existing inventory, saving significant time and effort.

  2. Supports mixed inventory environments (with and without QR codes).

  3. Improves scanning flexibility for products where QR labeling is not feasible.

  4. Enhances operational speed and accuracy with auto-capture of SKU and lot details.

  5. No disruption to existing barcode workflows, ensuring seamless adoption.

  6. End-to-end traceability is maintained across inbound and outbound processes.

Standard APIs

Change Requests/ Enhancements/ Improvements:

  • Order creation using External Customer Code                           

  1. A new param extCustomerCode has been added in order create api allowing order creation using extCustomer. This update removes the dependency on internal Vinculum customer codes, allowing external systems to create orders using their own identifiers.

  2. Provides a more versatile API structure that caters to the specific data-handling preferences of different ERP and POS systems.


API Touchpoint: /RestWS/api/eretail/v1/order/create


  • New Fields in Inbound Details API                                  

  1. Added two new fields in Inbound Details API (V1 & V3) at the line level -

    1. rejectedQty

    2. putawayQty

  2. No changes to existing request parameters. 

  3. Available across both API versions: /v1/inbound/detail /v3/inbound/detail 


Key Benefits 


  1. Enhanced Visibility: Provides clear insight into rejected and putaway quantities directly via API. 

  2. Better Inventory Tracking: Enables accurate monitoring of QC outcomes and putaway status. 

  3. Improved Integrations: External systems (ERP, reporting tools) can now consume detailed inbound status without additional logic. 

  4. Reduced Manual Effort: Eliminates the need for separate calculations or data extraction for reject/putaway quantities. 


End Points - /RestWS/api/eretail/v1/inbound/detail

/RestWS/api/eretail/v3/inbound/detail

Financials/ E-filing Systems Integrations:

Change Requests/ Enhancements/ Improvements:

  • Accurate Item Name Display and Rate Correction                              

  1. Replaced the SKU Code with the SKU Name in sales return. Resolved an issue where Credit Notes (CN) were generated with a zero sales price. The rate parameter is now correctly included in the API request to apply the accurate sales rate to returns. 

  2. Enhanced the integration logic to ensure these sales return adjustments are reflected accurately within ZohoBooks.

  3. Financial discrepancies are eliminated by ensuring Credit Notes are generated with the correct item rates rather than zero values.


  • Improved Data Traceability in Accounting Exports                       

  1. Correct data values are now reflected in zohobooks exports to focus on data accuracy and better visibility of key identifiers required for accounting audits.

  2. Unified document headers across all transaction types of exports of ZohoBooks to  provide a consistent report format for accounting teams managing multiple transaction types.

  3. The export report has been formally renamed to ZohoBooksExport in the Pending Reports section for easier identification.