Vinculum Release Notes
Version 9.3.151
March, 2024
Vin eRetail:
Order Management:
Change Requests/ Enhancements/ Improvements:
Manifest No. over B2B Orders:
For B2B orders, users now have the ability to view the B2B manifest number within the Outbound Delivery tab of the Orders. Additionally, clicking on the manifest number will directly route users to the respective manifest.
If the status of the manifest is ‘Confirmed’, then the status is displayed as ‘Manifested’ else ‘Not generated’.
Navigation: Vin e-Retail> Sales> Order Enquiry> Orders
New SKU Update Import:
A new SKU update import feature has been introduced to facilitate the easy updating of attributes for existing SKUs. This allows users to update attributes with simplicity and efficiency
Users have the option to export data from the SKU Enquiry screen, make necessary modifications to the values, and then import the same updated file
Furthermore, a new 'Import' button has been incorporated into the SKU Enquiry screen. This button provides a dropdown menu for users to select between two import types: 'Normal SKU Import' and 'SKU Update Import'.
Navigation: Vin e-Retail> Masters> SKU Management> SKU Master
Bag ID enhancement:
Bag ID is made visible at line level of the return detail screen same as order detail screen.
‘Bag ID’ and ‘Tag loop’ column is also added to the return detail export.
The 'Tag loop' field in the outbound delivery tab has been renamed to 'Other Info.' Under this field, two options are now presented vertically: 'Bag ID' and 'Tag loop'.
Navigation: Vin e-Retail> Returns> Return create/edit
Brandwise extension using SKU Create Import:
When creating a SKU with a specific brand and specifying 'ALL' under the 'Link To Store' column in the SKU Create Import, the SKU will be extended or mapped only to those locations whose brand matches the brand of the SKU.
Navigation: Vin e-Retail> Masters> SKU Management> SKU Import
Flipkart’s return OTC:
Return OTC involves the reverse logistics partner delivering shipments back to the seller following successful verification of the provided OTC. Reverse handover occurs only when the seller's OTC matches the transporter's OTC.
A new sub menu is added under the Returns & Transfer > Returns labeled as Return OTC (Flipkart). This new submenu is handled with a new user right so if the right is assigned to the user, then only the ‘Return OTC’ submenu appears and vice-versa.
Upon clicking on the Return OTC menu, if any Flipkart return is supposed to be delivered to the seller on the day, then the seller will get the OTC and the relevant information corresponding to that day.
Navigation: Vin e-Retail> Returns and Transfers> Return OTC (flipkart)
Key Bug Fixes:
Marketplace returns not getting created due missing reasons:
Earlier the marketplace was not getting created if the return reason was not available in the OMS.
This issue has been resolved, and if there is a marketplace return where the return reason is not present in the OMS, the system will automatically generate that missing reason to facilitate the creation of the return with the newly added return reason.
Warehouse Management:
Change Requests/ Enhancements/ Improvements:
Invoice Qty can be captured in Inbound Realtime:
Invoice Quantity pertains to the quantity as per invoice document against PO received from suppliers.
This may be different from the quantity in the document against which inbound is being performed and different from the actual quantity received.
This information may now be captured and populated to reports for reconciliation.
Bulk picklist print option in Manage Picklist screen:
Users can now print upto 10 picklists in bulk from Manage Picklist Screen.
Select checkbox is added on manage picklist screen to select the picklists that need to be printed.
A dropdown button with options to print picklists in bulk is added on Manage picklist screen.
Print sku wise picklist
Print order wise picklist
Navigation: Vin eRetail> WMS> Order Processing> Manage Picklist
APP - Putaway bin shouldn't be asked in user-defined mode in Scanner:
a. Previously, bins would reset with each SKU scan in user-defined putaway.
b. However, there has been a change, and now the bin will not reset on each scan of SKU, this is on configuration basis.
Navigation: Putaway > Userdefiend putaway
- Short Receiving Tolerance level in Receipt Validation:
The receipt validation now incorporates a "Restrict Less Than PO" option, allowing users to limit receiving below a designated percentage.
Enabling the "Restrict Less Than PO" checkbox will reveal a dynamic input field, allowing users to enter the percentage for the Less Receiving Tolerance.
Two columns are added as Restrict Less Than PO and Less receiving tolerance in the grid.
WMS > Setup > Receipt validation
ASN Tags:
A new feature has been introduced to facilitate the addition of tags in ASN using both the web interface and API.
The ASN tag will be included in both ASN create API and the response obtained from the ASN detail API.
Within the ASN create API, the tag serves as an optional parameter, allowing the addition of multiple tags for a single ASN.
The Manage ASN screen provides users with visibility into the tags associated with ASNs.
Users can view ASN tags during the receiving process via both the web and app interfaces.
Procurement > Manage ASN > ASN create/edit > ASN tags
Procurement > Manage ASN
ASN tags web view at the time of receiving-
ASN tags app view at the time of receiving -
Key Bug Fixes:
Invoice and Label printing in wrong sequence:
The sequence for invoice and label will be the same from both delivery shipping and manage picking screens.
Pigeon Hole Re-Assigning Error:
Users were unable to reuse the pigeonhole that was associated with orders that were cancelled/unallocated post picking. This is corrected now, users can now reuse the pigeon hole that is associated with cancelled/unallocated orders, once the putaway is confirmed for that order.
Vin FBS (Fulfilled by Store):
Change Requests/ Enhancements/ Improvements:
Attachment option for picking:
A provision to upload and save attachments for CnC orders is developed over Vin FBS mobile app.
The users can upload images using the device’s default camera, from order detail as well as Shipment handover screen.
These uploaded attachments can be referred to later from the Order Detail screen.
View Lottables hyperlink on Picking screen:
An option to view Lot details is available on the picking screen of Vin FBS mobile app.
Users can view the lot information in the pop-up that opens upon clicking on the new hyperlink.
Vin Lister:
Change Requests/ Enhancements/ Improvements:
SKU Push - As per requirements to different Marketplace Via Planogram (Auto Assigned Feature):
User will be able to assign Product based on specific requirement for each marketplace
Only selected Variant for each Marketplace will be List on Marketplace
Example : If this information is being passed in Planogram ( AutoAssign ) excel File / API then VinLister can auto push
Channel - Lazada
Variant 002
Status - 1 ( List on Marketplace )
f. Channel - Shopee
g. Variant 003
Status - 1 ( List on Marketplace )
SKU Push - Product Screen Changes for Auto Assign - Planogram:
Once Auto Assign feature is enabled , User will be able to see assigned and Unassigned product against every channel
User will not be able to manually change / Push / Assign SKU from Product screen
User has to provide Marketplace assignments information in Planogram only for Auto Push
Accept Mapped/Indirect Values in Multiselect Attributes in Ext Attributes - External System to VinLister:
a. When user import product information attributes from 3rd Party system ( FTP / PIM / Any Location ) then user wanted to mapped Multi select values to VinLister attributes so this enhancements have been developed and User will be able to mapped Multi select Values.
Key Bug Fixes:
Issue 01 : FTP file consumption issue solved
Issue 02 : Vinlister to E-retail Price push error is handled
Issue 03 : Image transformation for Zalora v2 is solved
Issue 04 : Retry county / Push for Marketplace is handled so sku is re-pushed / retried without manual Intervention
Standard APIs:
Change Requests/ Enhancements/ Improvements:
Changes in Lot level inventory API:
a. A new optional parameter “inclAllLocType” is added to the request of the Lot level inventory API .
b. User’s can now fetch the store/ franchise inventory by passing this parameter.
API touchpoint:
/RestWS/api/eretail/v1/sku/getlotlevelinventory
Change in the payload limit of the Update inventory API:
The limit of the payload size for inventory update is now made configurable so that any POS system/ external system can send a max of 500 stock adjustments in a single payload, default is 100.
API touchpoint:
/RestWS/api/eretail/v2/stock/updateInventory
Myntra Tagloop provision in Order Process/ Pack API:
A new optional parameter ‘tagLoopCode’ has been added to the request of the Order Process API where the user can send the Tagloop value for the tagloop enabled products. If a user tries to skip the Tagloop code for the tagloop enabled product then API will pack the order by giving a warning message in the response i.e “Please make sure to attach a seal tag to this item. If the seal tag is not attached, this item will not be eligible for SPF claims.”
Also, a new optional item array is added to the request of the Order Pack API where the user can pass the tagloop code for tagloop enables products.
API Touchpoint:
/RestWS/api/eretail/v1/order/orderProcess
/RestWS/api/eretail/v2/order/orderProcess
/RestWS/api/eretail/v1/order/orderPack
Request JSON (Order Process)-
Request JSON (Order Pack)-
Change in the ASN Create API:
A new request parameter has been added in the request of the ASN create API labeled as “ASN Tag”.
Users can pass multiple tags for a single ASN.
API touchpoint:
/RestWS/api/eretail/v1/asn/create
/RestWS/api/eretail/v4/asn/create
Request JSON (ASN create)-
Change in the ASN detail API:
A new parameter has been added in the response of ASN detail API labeled as “ASN Tag”.
API touchpoint:
/RestWS/api/eretail/v1/asn/detail
Response JSON (ASN detail)-
Integrations:
Transporter Integrations:
Change Requests/ Enhancements/ Improvements:
Rocketbox:
Region: India
Vinculum is now integrated with the Rocketbox for the below services:
- Forward AWB generation
- Tracking.
Tiki Express:
Region: SEA
Vinculum is now integrated with the Tiki Express for below services:
- Forward AWB generation
- Generate pickup.
- Tracking.
- Cancellation.
Marketplace Integrations:
Change Requests/ Enhancements/ Improvements:
Cred/Meesho/Olabi MPs:
a. Failed Orders visibility on screen for Cred/Meesho/Olabi MP Integrations
Integration Logs Visibility:
a. Integration log Visibility on ElasticSearch
Olabi Integration:
Vinculum is now integrated with the Myntra Olabi for below services:
Order Pull and create
Invoice PD Pull
3PL Integrations (WMS):
Change Requests/ Enhancements/ Improvements:
Delhivery B2C Integrations:
Touchpoints-
SKU Create/Update Push. (eRetail -> Delhivery)
Inventory Push (Delhivery -> eRetail)
Inventory Snapshot (Delhivery -> eRetail)
Order Create/ Update/Customer Cancel Push (eRetail -> Delhivery)
Order Cancel (Seller Cancellation) (Delhivery -> eRetail)
Order Process (Delhivery -> eRetail)
Label, Invoice Push (eRetail -> Delhivery)
Order Ship (Delhivery -> eRetail)
Return Create Push (eRetail -> Delhivery)
Return Cancel Push (eRetail -> Delhivery)
Return Close (Delhivery -> eRetail)
Financial/ E-Filling Systems Integrations :
Change Requests/ Enhancements/ Improvements:
Provision to correct PI information for failed E-invoice and E-Way bill:
NIC has applied lots of validations over customer’s personal identification information like customer name, address, pincode, GSTIN, etc.. If any such information is wrong then the E-invoice and E-way bill generation fails and the user has no option to correct that PI information.
Users will now have the ability to update the PI information like customer’s name, address 1, address 2, address 3, phone number, city, pincode, email address and GSTIN for the failed records.
User needs to navigate to the Tax Integration Log screen and needs to click over the “edit” icon for the failed record and can update the corresponding wrong information.
Navigation: Admint > Tax Integration Log
Addition of Other Charges in E-Way Bill:
If any order contains shipping charge, handling charge or other charge then the same will now be considered in the E-Way bill calculation and generation.
Applicable for all GSPs like Supertax, Clear (India), E&Y and Avalara.
Provision to print Basic/ Detailed E-way Bill document:
a. For E-way bill generation through Supertax, brands will now have the provision to decide whether they want to have either the basic or detailed pdf document of E-way bill.
b. Users need to navigate to external apps and need to choose the option from the “E-Way Bill Report” dropdown.
Navigation: Master > Miscellaneous > External Apps Create/ Edit
Enhancement over E-Way Bill screen:
Below changes are incorporated to fasten the E-Way bill generation : -
Distance will be prefilled as 0 (by default) if the sender’s and receiver's pincode is not the same. users can still override the 0 value. If the pincode is same then a default value as 10 Kms will be passed in the E-way bill generation.
If transporter GSTIN is maintained over the masters then transporter’s GSTIN will also prepopulate on the EWB screen.
Transporter GSTIN field is renamed as GSTIN/ CIN (Common Identification Number)