Provisional Vinculum Release Notes
Version 9.3.180
20th January, 2026
Vin eRetail
Order Management:
Change Requests/ Enhancements/ Improvements:
AWB Links Now Generate Clean, Functional URLs for Shipment Tracking
Corrected the tracking link formation logic to create a functional transporter tracking URL across all screens and APIs to ensure consistency.
AWB tracking links now work seamlessly without requiring manual URL correction, enabling users to track shipments directly from the system to access real-time tracking information from Aramex, FedEx, DHL, and other couriers without encountering broken links.
Key Bug Fixes:
Order Cancellation Status Mismatch Between Shopify and Vinculum
Fixed the order status update mechanism in the Web-Order Processing module to properly capture and process Shopify cancellation.
Cancellations are now reflected across systems immediately, reducing confusion and eliminating manual status correction workflows.
Order Activity Log Now visible across Delivery Shipping Screens
Fixed Order Activity Log in the Delivery Shipping screen where it was showing as blank.
Consistent order activity log display across Delivery Shipping screens providing complete delivery visibility for logistics teams processing shipments
Navigation: Vin e-Retail >> WMS >> Order Processing >> Delivery Shipping
Warehouse Management:
Change Requests/ Enhancements/ Improvements:
Validation Required for Putaway Vs GRN Qty
A new validation has been introduced during Inbound Confirmation to ensure that putaway is fully completed before confirming the inbound.
When enabled via configuration, the system now checks that the Putaway Quantity matches the GRN Quantity before allowing inbound confirmation. If the quantities do not match, inbound confirmation will be blocked with a clear error message.
This enhancement helps prevent partial quantity postings to SAP and ensures consistency between WMS and SAP GRN data. The feature is configurable and will only apply where enabled.
Addition of the ExtLineNo Field in ASN Export for Visibility
The ASN Export report has been enhanced to include a new Ext Line No column, along with Line No, to support inbound scenarios where multiple ASN lines share the same SKU, Lot, and LPN.
This update allows users to retrieve the required Ext Line No directly from the export and use it during inbound processing, ensuring accurate line-level identification.
Inbound QC- Auto Hold USN handling
Currently, during inbound QC, the system automatically places items on hold based on the configured paramcode and allows users to pass items without selecting a reason.
This behavior was not previously supported for USN scenarios; with this change, USN handling has now been implemented to ensure consistent inbound QC processing.
Transhipment Enquiry Enhancement for Head Office
The Transhipment Enquiry screen has been enhanced to allow Head Office users to view and track transhipments across all locations.
A new Transhipment Hub filter has been added for Head Office users.
When logged in from Head Office, users can:
Filter results by selecting a specific hub (location code).
The Transhipment Hub field is visible only for Head Office logins and displays all active locations for the organization.
For non-Head Office users, the login location is prefilled and behavior remains unchanged.
This enhancement enables centralized visibility and tracking of transhipments from the Head Office, improving operational monitoring and control.
Navigation: WMS > Miscellaneous > Transhipment
Return Type, Channel Typ,e and Transporter filter on -Inbound Real Time- Bulk RTO/Delivered Return.
This release introduces the ability to segregate DTO and RTO returns during bulk return creation.
Users can now select the return type (RTO or Delivered Return) before creating a return inbound, with optional filters for channel type and transporter.
This ensures proper QC handling, as QC is mandatory for DTO returns and not required for RTO returns.
If no filters are selected, the system will continue to behave as it does today.
Navigation: Wms > Inbound Real Time > Bulk RTO/delivered return
Standard APIs
Change Requests/ Enhancements/ Improvements:
Invoice Qty In Inbound Detail API V1 & V3 Response
The Inbound Detail API (V1 and V3) has been enhanced to include a new line-level field, invoiceQty, in the response.
It represents the quantity billed on the vendor invoice.
End Point -: /RestWS/api/eretail/v1/inbound/detail
/RestWS/api/eretail/v3/inbound/detail
Required Ext. customer code in ASN create API
The ASN Create API (V1 and V4) has been enhanced with a new conditional field extCustomerCode, for Customer-type ASNs.
The API now supports ASN creation using either the internal customer code or the external customer code.
When both customerCode and extCustomerCode are provided, and their values differ, the system will give priority to customerCode.
Duplicate external customer code validation is applied to prevent incorrect ASN creation.
End Point -:/RestWS/api/eretail/v1/asn/create
/RestWS/api/eretail/v4/asn/create
Introducing a new API for Unpack
A new REST API has been introduced to automate the order unpack process and reduce manual intervention.
With this enhancement, orders can now be automatically unpacked based on key order details, and the delivery status will be updated to “Pick Complete” at both header and line levels. This ensures real-time status updates and improved process efficiency.
This functionality is applicable to B2C orders only, and all existing unpack validations available on the UI are now consistently enforced through the API.
End Point- RestWS/api/eretail/v1/order/orderUnpack
Financials/ E-filing Systems Integrations:
Change Requests/ Enhancements/ Improvements:
Sales Return Processing Now Includes Required Invoice Identification
Enhanced the API payload structure to include invoice-level reference information, as required to create credit notes in sales return scenarios.
Credit notes are now automatically recorded in ZohoBooks with complete invoice reference information, ensuring accurate financial reporting.