Sell Anywhere Faster
ARS is Auto Replenishment System is used for automatic purchase order creation. The auto replenishment is an operation that consists in making the stock full again in order to avoid stock-out. Here in eRetail we have introduced the Auto Replenishment Schedule where user can create the rules for auto replenishment based on sales history or min-max quantities and other factors.
The WMS setup is the initial configuration process where all the warehouse management setup steps are performed on the basis of which the transactions will take place. User can create and configure bins, zones, lottables which will be helping in business reporting and Interfaces.
ARS (Auto Replenishment Schedule)
ARS is Auto Replenishment System is used for automatic purchase order creation. The auto replenishment is an operation that consists in making the stock full again in order to avoid stock-out. Here in eRetail we have introduced the Auto Replenishment Schedule where user can create the rules for auto replenishment based on sales history or min-max quantities and other factors.
NAVIGATION
Procurement –> ARS
Our ARS module is primarily divided into three sections.
NAVIGATION
Procurement –> ARS –> ARS SKU-Location Link
ARS SKU Location Link
ARS SKU Location linking enables the user to link or map the Existing SKU which is getting configured for the auto replenishment with the location of its fulfillment. Clicking on the this option the user will get landed on to the ARS SKU-Location Link enquiry page. From here all the details of ARS SKU location linking already added will get displayed.
Lets understand all the search fields in details:
Location *: The Location filter enables the user to filter the records related to selected location for ARS SKU Location link.
Location Type : User can filter the ‘ARS SKU-Location Link’ records on the basis of location type. Few location types available in the systems are : Franschise, Store, Warehouse.
SKU: From SKU filter the user can search the ‘ARS SKU-Location Link’ record for any particular SKU.
Category: The Category filter enables the user to filter the records based upon the category. Clicking on this filter will pop up the Merchandising Hierarchy pick list for the user to choose the category.
Brand: Brands filter will enable the user to search the ‘ARS SKU-Location Link’ record based on the brands created in the system.
Primary Vendor : User can filter the records on the basis of primary vendors also.
Fulfilment Method: By choosing the fulfilment method(Direct Purchase, distribution centre etc.) from the filter drop down the user can narrow the search results.
Fulfilment WH: The fulfilment WH is the location from where the user wants the fulfilment to be done. User can choose the Fulfilment WareHouse from this section to narrow the search results.
Stock Cover Days: User can filter the search by entering the stock cover days. Stock Coverage is a functionality which enables users to calculate how long a store is able to continue selling items or groups of items given a sales history and inventory.
ARS Flag: User can choose the filter of ARS flag to filter between Active and inactive ARS.
ACTION BUTTON
Search: Clicking on the search button without entering any filter criterion will populate the list of all the ARS SKU LOCATION LINK based on default filter setting. User can further narrow down the search by using filter options to get any specific information.
Reset: Reset button will refresh the filter fields to default settings, i.e. to an initial state to start fresh search.
Advance Search: Advance search further improves the search results of ARS SKU LOCATION LINK enquiry by providing more fields to filter from. SKU field get added for the advance search option.
Add new: User can add new ARS SKU-Location link from here by filling in the below fields in the pop up box.
SKU *
SKU Name
Location *
Fullfillment Method
Fullfillment WH
WH Lead Time(In Days)
Primary Vendor
Stock Cover Days
ARS Flag
Bulk Update: The bulk update enables the users to update the fields like ARS Flag, Stock Cover Days, Primary Vendor, Fullfillment Method, Fullfillment WH and WH Lead Time(In Days) on the basis of Location Type/ Location/ Category/ SKU group/ Vendor/ Brand/ SKU.
ARS RULE
From ARS Rule section user can set up rules so that an automatic replenishment for SKU’s based on factors like Min/Max stock, Sales history and other factors can be done. Lets understand it in detail.
NAVIGATION
Procurement >>> Setup >>> ARS Rules
This is the ARS Rule Enquiry screen, from here the user with the help of various filter can search any particular ARS rule.
Location: User can choose the location out of the locations created in WMS, to see the existing rules created.
Product Set: From product set user can choose the one of product set from the drop down options (Brand/Group/Hierarchy/SKU/Vendor) to view the ARS rules only for that product set.
Rule ID: Rule Id is the Unique ID assigned to every rule created in the system. Based on these ID’s the rule can be searched .
Description: User can search the rule based on the description from this section.
Status: Based on the rule Status i.e. Pending, Active, Inactive & Discontinued the user can filter the status of the ARS rule.
ARS Method: User can filter and narrow down the search results based upon ARS methods:-
Min-Max & Sales History.
Frequency: By choosing the frequency option from this filter out of the options given below; user can get the filtered results of ARS rules created.
ACTION BUTTON
Search: Clicking on the search button without entering any filter criterion will populate the list of all the ARS Rules based on default filter setting.
User can further narrow down the search by using filter options to get any specific information.
Reset: Reset button will refresh the filter fields to default settings, i.e. to an initial state to start fresh search.
Add New: To add a new ARS rule. Refer to details below about how to create a new ARS rule.
Rule ID: Rule Id is the Unique ID assigned to every rule created in the system.
Rule Description: Rule description is the description of rule created by user describing about its functions. This is a mandatory field.
Remarks: User can enter the remarks while creating the ARS rule.
ARS Method : ARS methods are divided into two parts:
1. Min-Max: Choosing the Min Max option will create two fields on screen of Minimum quantity and Maximum Quantity, which will get implied on this method. For example let’s say for this method the minimum quantity set is 01 and the maximum is 10, so it means that whenever the minimum quantity of the selected SKU’s will reach 01 then automatically the replenishment quantity will reach 10 and will create a PO/STO for the same.
2. Sales History: If user selects the Sales History method then here replenishment of quantities are done based upon the sales history. After selecting this the user will mention the rate of Sale period and based upon that periods sales history the ASR rule for auto replenishment will function.
How to configure ROS calculation?
Navigation
Admin >>> Settings >>> B2B configuration
After navigating till B2B configuration, on the screen user will find the ROS configuration.From here ROS will be enables by the User and the ROS Calculation hour can be chosen from the drop down.And the ROS period options can be enables to get available in the drop down while creating the ARS rule.
Vendor Type : Vendor type is a mandatory field while creating the ARS rule. The Vendor type is divided into 03 types here:
1.Min Cost: If this vendor type is chosen them the auto replenishment will happen based upon the vendor who is providing the minimum cost for the SKU’s.
2.Min Lead Time: If this vendor type is chosen them the auto replenishment will happen based upon the vendor who is minimum lead time for the fulfilment.
3.Primary: Primary vendor will be the primary vendor assigned for that SKU while creation.
Output Type: The output type is the result which means that this output type will decide the status in which the PO will get created.
There are 03 output type:
1.Confirmed: If confirmed is selected while creating the ARS rule then the purchase order will get created for auto replenishment in the confirmed state.
2.Pending: If while creating the ARS rule, the output type is chosen as pending then the PO for replenishment of SKU inventory will be in the Pending state.
Location : From here the User can specify the locations for which this rule will be true and applicable.
Start Date & End Date: ARS rule period will get specified here based upon the start and end date, which will define the duration for which any rule will be applicable.
Status: While creating the rule user can choose the status in which he wants the ARS rule to get created based on the rule Status i.e. Pending, Active, Inactive & Discontinued
Frequency : Frequency is chosen to define the duration after which this rule will run. For example if the frequency is set as 02, then in every 02 hours this rule will run in the system for autoreplenishment.
TALLY CONFIGURATION OVERVIEW
Configuration of Tally in Vin eRetail enables the user to configure the data related to Sales, Sales Return, Purchases, Purchase Return, SKUs and much more.
By configuring this section the user will be able to push the sales, sales return, purchase, purchase return data to Tally.
UTILITY
NAVIGATION
Masters —> Miscellaneous —> Tally Configuration
CONFIGURATION
Tally Configuration is primarily divided into two parts:
1. Sales & Sales Return
This section is configured by user in order to map the Sales and Sales return data from eRetail to Tally. Once this section is configured then the Sales and Sales Return data can be pushed to Tally.
The Sales and Sales Return section is divided into five sections:
1.1 Sales Details
In Tally we have Vouchers, which is a document that shows goods have bought or services have been rendered, authorizes payment, and indicates the ledger account(s) in which these transactions have to be recorded.
So in Sales Details we configure the settings for Sales Voucher in eRetail. Lets Understand all the fields in details:
Voucher Type : The default Voucher type for Sales details section is ‘Sales’, which needs to be entered by the user. But in case the user wants to enter the Voucher type name other than ‘Sales’ here then that can be done as well. For example: Users also prefer to put the Voucher type as party names as well.
Voucher Number*: A voucher number is a unique number defined in Tally. Now user on eRetail can choose out of the given options that which one would be the voucher number with respect to Tally. The options for Voucher number given are:
->External Invoice Number
->Invoice Number
->External Order Number
Reference Number*: A reference number is the number which is generated against every Voucher number. User can choose as per his/her configuration on Tally that what will be the reference number here out of the two given options:
->Invoice Number
->External Order Number
Date: User can choose from here which event’s date needs to be pushed to Tally with respect to the options given:
->Invoice Date
->Order Date
->Shipping Date
1.2 Sales Return Details
Just like sales details, we have sales return details for the transactions related to Returns.
Lets Understand all the fields in details:
Voucher Type : The default Voucher type for Sales Return details section is ‘Credit Notes’, which needs to be entered by the user. But in case the user wants to enter the Voucher type name other than ‘Credit Note’ here then that can be done as well.
Voucher Number* : User can select the preference for voucher number from the list. A voucher number is a unique number defined in Tally. Now user on eRetail user will be selecting the “Return Number” as the voucher number with respect to Tally.
Reference Number*: A reference number is the number which is generated against every Voucher number. User can choose as per his/her configuration on Tally that what will be the reference number here out of the two given options:
->Invoice Number
->Return Number
->External Order Number
Date*: User can choose from here which event’s date needs to be pushed to Tally for returns with respect to the options given:
->Return Date
->Received Date
1.3 Sales Ledger Name
A Sales Ledger is the record of whether or not you have received the money, and how much you are still owed and a sales ledger has an account for every customer.
Here in this section the sales ledger name on Vin eRetail with respect to Tally is configured.
Sales Ledger Type* : User will have to select the ledger type that needs to be configured as per the requirement our of the two options given:
->Item Wise
->Local/Interstate
*In case of Item wise ledger, the sales ledger name needs to be entered in the configuration.
*In case of Local/Interstate, the Local ledger name and Interstate ledger name needs to be entered separately.
With Tax Percent : If this Tax Percent is checked or enabled, then in that case the ledger will be created with respect to the bifurcation based upon the Tax percentage.
1.4 Tax Ledger Name
This section enables the user to enter the all Tax details related to Tax percentage, CGST, SGST and IGST.
1.5 Party Alias
From this Party Alias user can define the Party Name and click on Alias Name to Enter Tally Specific Party Name for your Marketplaces, Transporters and B2B Customers
After choosing the Party from the DropDown the user can Map the channels on Vinculum to that of tally’s.
Refer to the clip below:
2. PURCHASES & PURCHASE RETURN
This section is configured by user in order to map the Purchases and Purchase return data from eRetail to Tally. Once this section is configured then the Purchase and Purchase Return data can be pushed to Tally. Purchase voucher is used to record all the Purchase transactions of the company.
The Purchase and Purchase Return section is divided into five sections:
2.1 Purchase Details
In Tally we have Vouchers, which is a document that shows goods have bought or services have been rendered, authorizes payment, and indicates the ledger account(s) in which these transactions have to be recorded. When a company buys goods on credit or cash, Purchase voucher is used to record all the Purchase transactions of the company.
So in Purchase Details we configure the settings for Purchase Voucher in eRetail. Lets Understand all the fields in details:
Voucher Type : The default Voucher type for Purchase details section is ‘Purchase’, which needs to be entered by the user. But in case the user wants to enter the Voucher type name other than ‘Purchase’ here then that can be done as well. For example: Users also prefer to put the Voucher type as party names as well.
Voucher Number*: A voucher number is a unique number defined in Tally. Now user on eRetail can choose out of the given options that which one would be the voucher number with respect to Tally. The options for Voucher number given are:
->Inbound Number
->GRN
->PO Code
Reference Number*: A reference number is the number which is generated against every Voucher number. User can choose as per his/her configuration on Tally that what will be the reference number here out of the three given options:
->GRN Number
->Invoice Number
->PO Code
Date: User can enter the Inbound Date from here which needs to be pushed to Tally.
2.2 Purchase Return Detail
Just like Purchase Details, user can configure the purchase return detail section for all the purchased return transactions.
Lets understand in detail:
Voucher Type : The default Voucher type for Purchase Return details section is ‘Purchase Return’, which needs to be entered by the user. But in case the user wants to enter the Voucher type name other than ‘Purchase’ here then that can be done as well.
Voucher Number* : A voucher number is a unique number defined in Tally. Now user on eRetail will enter the return number as the voucher number Purchase return detail.
Date*: User can enter the Return Date from here which needs to be pushed to Tally.
2.3 Purchase Ledger Name
The Purchase ledger is the ledger to record the purchase transactions.The purchase ledger is part of the accounting department’s database; it is not maintained by the purchasing department. The ledger is useful for segregating into one location a record of the amounts a company spends with its suppliers.
Lets understand about its fields in detail:
Purchase Ledger Type: User will have to select the ledger type that needs to be configured as per the requirement our of the two options given:
->Item Wise
->Local/Interstate
*In case of Item wise ledger, the sales ledger name needs to be entered in the configuration.
*In case of Local/Interstate, the Local ledger name and Interstate ledger name needs to be entered separately.
With Tax Percent : If this Tax Percent is checked or enabled, then in that case the ledger will be created with respect to the bifurcation based upon the Tax percentage.
1.4 Tax Ledger Name
This section enables the user to enter the all Tax details related to Tax percentage, CGST, SGST and IGST.
1.5 Party Alias
From this Party Alias user can define the Vendor Name and click on Alias Name to Enter Tally Specific Vendor Name. After choosing the Party from the DropDown the user can Map the channels on Vinculum to that of tally’s.
***** Apart from these configutaions, the user will have to generate the Vinculum eRetail API key as well to enter that in respective Tally account so that the data can be pushed from eRetail to Tally.
The inbound process starts when items arrives in the warehouse location,
either received from external sources or from another company location.
An order becomes an inbound shipment when a purchase order release is packed and it is physically ready
to be shipped.
INBOUND QC
The Inbound QC process is carried out in order to do the quality check of the SKU’s inward
during inbound.
User carries out this process with the help of inbound numbers for the inbound already registered
in the system.
Vin eRetail’s Client Portal is the process that works in an multi client system where our customers lets say 3PLs provide access of a portal to their clients to view and manage details like customers, orders, purchase orders and much more.
Lets Understand this in details:
The Client Portal is primarily divided into six sections:
1. Master
2. Order
3. Purchase Order
4. Product
5. ASN
1. MASTER
Master data setup helps to configure your Masters related to trading partners based on which the future transactions will run.
The user can view, enquiry and create the customers from the Masters –> Customer Master.
The masters section is divided into two parts:
1.1 Customers Master
1.2 Customer Create/edit
Navigation
Masters –> Customer Master
Below are the fields on the basis of which user can search their customers:
Customer Code: Customer Code is the unique code provided by the system to each customer and helps differentiating 2 or more records. Once customer is saved, customer code becomes un-editable.
Customer Name: User given name to the Vendor with which he is registering in the system.
Vendor Names can be identical and hence we require the vendor codes to differentiate.
Type: Customer Type here in drop down will be the type of customer categories created in the database by the user. For example: B2B type, B2C, any other type etc.
Status: User can filter based on Active and Inactive Customer status. Only the active customers with activated transactions will be displayed on selecting active as an option and vice versa.
Primary Contact & Primary Email: User will have to enter the primary contact & email id of the customer as contact detail.
Created Date: Filter the customers based on the date of creation.
Action Button
1.Search: Clicking on the search button without entering any filter criterion will populate the list of all the Customers based on default filter setting. User can further narrow down the search by using filter options to get any specific information.
2. Reset:Reset button will refresh the filter fields to default settings, i.e. to an initial state to start fresh search.
3. Download: To download the filtered or searched result in CSV format which is displayed in the data grid.
4. Add New: To add a new Customer to the database.
1.2 Customer Create/ Edit
To create a new Customer or to edit/update an existing one.
It is divided into three tabs:
1.2.1 Customer Details
1.2.2 Address
1.2.3 Other Shipping Address
1.2.4 UDF
Navigation:
Masters —- > Customer Master —-> Add New
1.2.1 Customer Details
Customer Code: Customer Code is the unique code provided by the user to each customer and helps differentiating two or more records. Once customer is saved, customer code becomes un-editable.
Customer Name*: Name of the customer could be similar with one another, that is why we have codes to differ the customers with same name.
Is Active: Check this to mark a customer as active one and vice versa.
Parent Customer: Parent customer is the primary customer who can further have the customers within itself.
Ext Customer Code: External Customer code is the code given in case where the customers are getting synced from a different platform/ or given by user.
Payment Terms: Payment terms could be the option of number of days to choose from for the payment settlement.
GL Code: GL code means the general ledger code to be entered. It is a set of numbered accounts a business uses to keep track of its financial transactions and to prepare financial reports
Tax Zone: State/city/county under which a particular vendor is registered becomes the tax zone for that Customer.
Type*: Customer Type here in drop down will be the type of customer categories created in the database by the user. For example: Marketplace type, B2B type, B2C type etc.
PAN No.: PAN number of the customer for financial recordings. For example: in India the pan card becomes mandatory for the Transactions above certain limit.
GST No.: GST no means the Goods & Service Tax Number GSTIN of the Vendor. This is for the B2B customers.
The fields marked with asterisk are the mandatory ones.
1.2.2 Address
Shipping Address Details & Billing Address Details
Customer’s full shipping and billing address required here in these tabs for the case of returns and other related activities.
The fields marked with asterisk are the mandatory ones.
1.2.3 Other Shipping Address
From here user can add other shipping addresses as well. Refer the video below:
1.2.4 UDF
User Defined Fields: These are the custom fields which can be created by the User for customers in case of any extra information required.
2. ORDER
Order Section enables the user to configure your Sales Channels, managing & adding the new sales channels with respect to the already integrated marketplaces and order enquiry, order creation & much more.
UTILITY
Sales section enables user to target business on various sales channels.
Enables user to configure, pull, manage orders and much more after creating the sales channel.
Listing and Description
2.1 Manage Channels
2.2 Manage Order
2.3 Order Import
2.1 Manage Channels
2.1.1 Overview
Manage channel enables the user to view listing of all the channels created (active or inactive) and add any new sales channel.
It also enables the user to search the existing sales channels on the basis of the channel code and channel name.
Navigation
Orders –> Manage Channels
Fields on the basis of which the sales channel can be searched:
Channel Code: Channel code is the auto generated unique code by the system for each channel.
Channel Name: Channel name is the name given by the user to the channel while creating the channel.
Action Button
1. Search: Clicking on the search button without entering any filter criterion will populate the list of all the sales channel whether active or inactive. User can further narrow down the search by using filter options: Channel code and channel name.
2. Reset: Reset button will refresh the filter fields to default settings, i.e. to an initial state to start fresh search.
4. Add New: To add a new channel to the database. User will see the list of already added/integrated channels, selecting any one of those will enable user to add a new channel.
Further the Add channel is divided into 4 major sections.
*Master
*Order
*Channel SKU
*Inventory
Lets Understand these in detail.
Channel Detail
Channel Code: Channel code is the system generate unique ID given to the channel to differentiate these channels from one another.
Channel Name*: User will enter the name of the channel getting created.
Status: User will specify the channel’s state as active or inactive by selecting from the dropdown.
Order Fulfillment WH*: User will choose order fulfillment warehouse from the list of warehouses given.
Auto Range SKU: Auto range SKU enables the user to configure that with a particular channel location whether the SKU’s will be getting Automatically mapped/synced or not. Based on the requirement the user can select yes or no from the option.
Configure Interface: User can configure the API from here by entering the details here.
Channel SLA(in hrs)*: This is the service level agreement between the channel and the user. Here various aspects of the service – quality, availability, responsibilities – are agreed between the service provider and the service user.
Orders Enquiry
Order Sync*:User can choose to sync the order from the channel to eRetail by managing this option.
Order Sync From Date*: Order Sync action can be performed by the user by choosing the from date and from that till present’s period order will get sync.
Order Sync From Order No*: Order Sync action can be performed by the user by choosing the order number and from that order number till present’s period order numbers will get sync.
Shipping By: User can configure from here that the shipping will be done by the marketplace or by the seller.
Bill To Party & Its Master*: User gets the option to choose the billing party in case of multiple parties. These bill to party options can be created or managed from the
Masters — > Other Master — >Channel Configuration –> Bill to Party Tab.
Invoice No By: User will choose that the Invoice no will get generated by the user or by the channel.
PrePack Enabled: User can enable prepack for the order from here.
Mark ReadyToShip At: User can choose to mark the status of ready to ship at any of the two events :
-at Manifest
or
-at Pack
Each Qty Per Line: User can enable to sync the each quantity per line order.
International Invoice & Domestic Invoice: user can choose which format of invoice suits his requirement from here.
Channel Sku
Channel SKU Suffix & Prefix: User can put the different suffix and prefix on SKUs of different channels to differentiate them from one another.
SKU Sync: SKU Sync between Channel and eRetail can be done via PULL & PUSH.
User can choose Pull to Pull the SKU’s from the channel to eRetail panel.
And User can choose Push to send the SKU data or changes from eRetail to the channel.
-In SKU pull the user is given with two options:
Create
&
Moderate
CREATE: In create SKU pull, all the SKU will be pulled and created on the eRetail panel in order to get mapped.
&
MODERATE: In moderate SKU pull only the Product Id’s of other platform will get pulled and then mapped with the eRetail’s SKU Id’s.
Inventory
Inventory Sync:User will have to choose the option of Yes or No, in case he wants to enable or disable the inventory sync respectively.
Safety Stock: Safety stock is the stock kept by user to describe a level of extra stock that is maintained to mitigate risk of stockouts (shortfall in raw material or packaging) caused by uncertainties in supply and demand.
Sync Method: In Sync method, users can choose that whether they want to sync the inventories from all the Locations, or they want to sync from different selected or custom locations.
Channel Inventory percentage: User can define the safety stock in percentage of the total stock.
2.2 Manage Orders
Orders across all the channels are visible here on a common screen. User can enquire for all the order related information from here on the basis of various filters available to narrow down the search result.
All the orders from various vendors and channels will get displayed here, and the order can be confirmed, saved, allocated, shipped, put away from here.
User can quick ship the orders from here.
The order enquiry section consists of four sections:
2.2.1 All orders
2.2.2 Failed Orders
2.2.3 Cancel orders post Shipping
2.2.4 Pending MP Label Shipment
2.2.1 ALL ORDERS
User will select the ‘to’ & ‘from’ dates and all the orders of that date selection will appear. User can also narrow down the search of orders by using various filters available like Order number, External Order Number, channel, order type, status, order amount & much more.From the order listing user can choose the order and manage it completely by clicking on the order number.
Selecting any Order user can manage its
allocation,
can quick ship,
save & confirm the order,
can part pick the order,
can update Warehouse,
Can hold the Order,
can unallocated the order,
can cancel the order and much more.
Action Button
1. Search: Clicking on the search button without entering any filter criterion will populate the list of all the Orders. User can further narrow down the search by using various filter options like Order number, External Order Number, channel, order type, status, order amount etc.
2. Reset: Reset button will refresh the filter fields to default settings, i.e. to an initial state to start fresh search.
3. Export: To download and export the displayed search results in the form of CSV.
4. Advance Search: Advance search further improves the search results of Orders by providing more fields to filter from. Below fields get added for the advance search option of the order enquiry.
2.2.2 Failed Orders
User will select the ‘to’ & ‘from’ dates and all the orders that have not been synced or pulled of that date selection will appear. User can also narrow down the search of orders by using various filters available like Order number, External Order Number, channel, order type, status, order amount & much more.
From this section the failed orders can be pulled from FORCED PULL button.
2.2.3 Cancel Order Post Shipping
User will select the ‘to’ & ‘from’ dates for order and all the orders which are cancelled for that date selection will appear. User can also narrow down the search of orders by using various filters available like Order number, External Order Number, channel, order type, status, order amount & much more.
From this section the PUTAWAY for cancelled orders can be processed.
2.3 Order Import
Orders can be imported by the user from here. Refer the video clip below:
3. Purchase Order
Using this screen, one will be able to view existing POs and edit/update the same.
Utility
Fields on the basis of which the POs can be searched:
PO Code: This is a system generated unique code which gets autogenerated when a new PO is created.
PO Date: User can see POs with respect to dates by filling this field.
Vendor: Helps to search all existing POs for that particular vendor.
PO type: If a user wants to see POs of a certain type, then he/she can use this field.
Status: User may narrow search using status of POs.
Delivery Location: User may filter POs based on delivery location.
Action Buttons:
To create the PO for vendor, user will be required to add the SKU in it.Add New: To create a new PO click on the add new button.
Navigation
Product –> SKU Enquiry
Utility
ACTION BUTTON
1.Search: Clicking on the search button without entering any filter criterion will populate the list of all the Transporters based on default filter setting. User can further narrow down the search by using filter options to get any specific information.
2. Reset: Reset button will refresh the filter fields to default settings, i.e. to an initial state to start fresh search.
3. Download: To download the filtered or searched result in CSV format which is displayed in the data grid.
5. Advance Search: Advance search further improves the search results of Transporter by providing more fields to filter from. Below fields get added for the advance search option of the Transporter.
4. Add New: To add a new SKU to the database.
This section will enable user to add new items into the system
Utility
On the SKU Create/Edit screen, below tabs are present to capture all vendor related information.
SKU DETAIL
It is further divided into four sections.
-> Product Detail
-> Pricing Detail
-> Dimension Detail
-> SKU Image
SKU DETAIL section will consist of all the primary information related to the SKU.
SKU Code: Any unique code which a user gives to the SKU while creating it. This SKU code is a mandatory field and once created and saved cannot be changed and must be a unique number.
SKU Name & SKU Short Name: Enter the SKU name & Short name.
SKU Classification: SKU type out of the four types will be defined here initially when you click on create SKU button.
SKU Source: To mention the source of SKU here by selecting from the drop down whether it is a consignment product or an outright purchase.
Attribute Set-Size Group-Size-Color-Material: All these fields input values which appear in drop down are created & configured by user from the Other Masters of the Master section.
Primary UPC/EAN: UPC (Universal Product Code) or EAN (European Product Code) are the bar code for the SKU which will be entered here. Multiple barcodes can be supported by the single SKU.
Base UOM: UOM is the Unit of Measurement in which the SKU will be measured or weighed which is used in advanced Shipment Notice, Invoice, Purchase Order documents etc.
Pack Size: Pack size again is the field which is configured from the Other masters by the User defining the size of the SKU.
Hierarchy Code: Hierarchy code helps user to configure merchandising hierarchy for SKU from the list as they could be the sub category or sub-sub category of the SKU.
Primary Vendor: Every SKU in system is linked to a Primary vendor which is a mandatory field. There can be multiple other secondary vendors also linked to the same SKU.
Is Approved: Mention the status of the Vendor.
Country of Origin: Enter the country of origin of SKU by choosing from the down.
Pricing Detail
In this section below given pricing related details of the SKU will be entered.
Dimension Detail
All the below given dimension criterion will be filled in w.r.t. to each SKU as this information is further required for the Shipping purposes.
Height (CM)
Length (CM)
Width (CM)
Cube
Weight (KG)
SKU Image
Image URL
Product Page URL
User Defined Field
These are the custom fields which can be created by the User for SKU in case of any extra information required.
C. Other Detail
Other Detail section is further divided into two sections:–
Detail 1: This section requires the user to input all the details of the product related to its shelf life and nature of the product w.r.t. shelf life. Below are the list of fields which needs to be filled or checked by the user in detail-1 section.
– Detail 2: This section requires the user to input all the details of the product related to the SKU rotation and validation. Below is the list of fields which needs to be filled or checked by the user in detail-1 section.
4.2 Inventory View
Inventory view section enables the user to view real time status of inventory present in the warehouse. It shows item wise inventory for each of the products like total stock in hand, Free stock or available quantity.
In inventory view section the inventory can be viewed or searched by SKU, by SKU Bin, by Description, by Mfg SKU code etc. Lets understand each in detail.
By SKU
Here user can get the inventory detail by searching the inventory by SKU based on below fields.
SKU Code
SKU Description
Mfg SKU Code
Hierarchy Code
Brand Code
Vendor Code
By SKU BIN
Here user can get the inventory detail by searching the inventory by SKU BIN based on below fields.
SKU Code
SKU Description
Mfg SKU Code
BIN
Inv Bucket
Zone
Subsequently the inventory can be searched based on below mentioned tabs and to narrow down the search the filter fields can be used in each tab.
By SKU LOT
By SKU BIN LOT
By SKU IMEI
By SKU UNIQUE NO
Market Place Inventory
By SKU BOM
Fields based on which the inventory move history can be searched:
SKU Code: Any unique code which a user gives to the SKU while creating it. This SKU code is a mandatory field and once created and saved cannot be changed and must be a unique number.
SKU Description: User can search or filter the inventory history based on the SKU description of each SKU.
Move date: Search or filter the inventory move history based on the move date.
Site Location: User can choose the warehouse location for which the user is enquiring about the inventory move history.
Move Quantity: Mention the move quantity.
From Zone to To Zone: User can view the inventory move history from zone and to zone.
From Bin & To Bin: User can view the history of inventory move from one bin to another.
Putaway Number: Inventory move history can also be searched or filtered based upon the putaway number.
Action Button
1.Search: Clicking on the search button without entering any filter criterion will populate the list of all the Inventory move history based on default filter setting. User can further narrow down the search by using filter options to get any specific information.
2. Reset: Reset button will refresh the filter fields to default settings, i.e. to an initial state to start fresh search.
3. Export: To download the filtered or searched result in CSV format which is displayed in the data grid.
4. Add New: To add a new Inventory Move to the database.
5. Advance Search: Advance search further improves the search results of Inventory move history by providing one more fields to filter from i.e. Style Code.
5. ASN [Advance Shipping Note]
Advance Shipping Notice (ASN) is a notification document having all the important information about a future delivery. The main purpose of the ASN is to provide a prior notice to the customer regarding the delivery so that customer can get prepared to accept the delivery. It notifies the customer when shipping occurs and provides physical characteristics like weight, dimension of the box etc. about the shipment.
Manage ASN
Using this screen, one will be able to view existing ASNs and edit/update the same.
Action Buttons in the screen are listed below:
SELLER PANEL
Vinculum’s eRetail Seller Panel enables a seller of the marketplace to efficiently manage the Orders in OMS and also to help collaborate and synergize in WMS, OMS, returns, Shipping labels, Invoices and also enables the seller to support multiple fulfilment modes.
UTILITY
Vin eRetail Seller Panel is designed for Marketplaces to help collaborate and synergize with their partner network through –
1.1 Active Order
Active order section gives the details of all the confirmed order and all those order which are pending for seller’s action.
Navigation
Manage Orders –> Active Orders
In active order section there are four modes under which different orders are placed and processed.
They are:
1.1.1 Dropship
1.1.2 Fulfilled By 3PL (one ship)
1.1.3 Ship via FC
1.1.4 Vendor Self Delivery
1.1.1 Drop Ship
In all the modes of orders there are 03 tabs of order processing.
*Confirmed: Confirmed tab here shows the orders which are confirmed to be drop shipped, seller can generate invoices from here and can also reject one or more orders from the listing displayed.
Once a user selects a line to print the invoice, the following screen will appear which will ask for confirmation if the invoice status is correct. The information that is typically generated once the print invoice is pressed is Invoice No., Identification of the transporter and the generation of AWB Number.
*Ready to be Shipped: All the ready to be shipped orders of drop shipping mode gets listed here. From here the seller can schedule pickup, mark the orders as shipped, print invoices and shipping label as well.
*Shipped: The Shipped tab will display all the Shipped orders along with their order number and shipping related details.
1.1.2 Fulfilled by 3PL
Fulfilled by 3PL refers to fulfillment of the order by a 3rd party Logistics. Here the inventory lies with any third party logistics company’s warehouse and the order is fulfilled by the 3PL here.
The order gets displayed in 05 different tabs here:
-Confirmed
-Pickup Ready
-Pickup Confirmed
-Shipped
-Disputed
A Regional Distributer (RD) plays an important role in case of One Ship.The below figure shows the work flow in the “One Ship” Mode.
1.1.3 Ship Via FC
Here is the shipment via Fulfillment Carrier option where the order gets sent via FC. This mode displays the list of order fulfilled by FC along with the order image, order number, customer details, Sku Code, Status and much more.
Vendor Self Delivery mode is similar to a Drop Ship model with the exception that in this mode the transporter is decided by the seller itself and there is no intervention from the Marketplace player w.r.t. selection of transporter.
The seller has to track and update the status of the orders all by himself as the trading API’s does not work in this mode. The following will be the status of different orders:
-In-Transit
-Delivered
-RTO
-RTO Delivered
On selecting an order and clicking on the “generate invoice” button, the following screen will appear which will help select a transporter from the drop down list and the system will prompt to enter the AWB number.
1.2 Archived Order List
The Archived Order list contains the list of all the delivered and returned orders.
2. SKU
2.1 Sku Listing
The SKU List gives the list of all the SKU’s linked to a particular seller. There are various filters available like SKU Name, UPC Code, Brands, SKU Code etc. which helps in fetching data quickly from the database. This screen captures all the SKUs linked to the particular vendor.
Seller can also update inventory and view total inventory available in warehouse.
2.2 Update Price/Inventory
From this section the User can help the seller in updating the selling price and quantity of the SKU in bulk i.e. for multiple SKU’s at a time.
The template files are Marketplace defined and can be uploaded to the marketplace after filling all the information. These template files are visible to the seller and can be downloaded to each sub-category. Once the category, sub-category and leaf category is entered, the download template will become active and the template can be downloaded. Once, all the details have been entered it can be uploaded using the upload data file. Seller can also view the status of all the files uploaded by him.
2.3 SKU Import
SKU Import section enables the user to import SKUs & to download them based on their attribute set via CSV.
ASN stands for Advanced Shipping Note. In the case of consignment based purchase, the Seller (Vendor) creates an ASN for the goods which are to be sent to marketplace. All such ASNs are visible in the ASN Enquiry screen in Seller Panel.
Once the ASN is confirmed by Marketplace, the seller can view and print barcodes. Accordingly, the seller pack, stick barcodes and ship the goods to the Marketplace.
3. PROCUREMENT
Procurement section will able to view existing POs and their PO code, status, Location, expected delivery date and more. User can see all the POs and even narrow down results by putting values in search option of PO code field.
User will be able to download results in a report format using Detail Export/ Download option.
Action Button
4. RETURNS
Return section is divided primarily into 02 sections.
4.1 Manage Returns
4.2 Vendor Returns
4.1 Manage Returns: Manage returns section displays all the returns in three different tabs:
-> Returned Initiated: When a return is initiated by the customer online (delivered returns), a Return No is generated. Seller Panel returns screen shows all such returns number with Web Order No, SKU details etc. The below screen depicts the returns initiated by customer.
-> Return To Origin: In case of Un-delivered returns or RTO (Return to Origin), the below screen appears. The data grid shows all the RTO records along with the Return No, Web Order Number, SKU details, any additional remarks etc.
-> Disputed: In case of a dispute between the Seller and the 3PL company, the User can select ‘Mark Disputed’ and give reason for the same. Once the dispute is resolved, the User can confirm the same on ‘Disputed’ tab.
Action Button
Report section enables the seller to generate the manifest sheet and manifest soft data transporter wise based on order type, date wise and other fields.