Category: eRetail

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

• By configuring Tally the user will be able to push the sales, sales return, purchase, purchase return data to Tally.
• Lets user to efficiently manage all the accounts, sales, purchases, and much more on Tally with the help of Vinculum eRetail’s data.

NAVIGATION
Masters —> Miscellaneous —> Tally Configuration

CONFIGURATION
Tally Configuration is primarily divided into two parts:

1. Sales and Sales Return
2. Purchases and Purchase Return

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:

• Sales Details
• Sales Return Details
• Sales Ledger Name
• Tax Ledger Name
• Party Name

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:

• Purchase Details
• Purchase Return Details
• Expense Ledger Name
• Tax Ledger Name
• Party Name

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.

Return Management

1. Returns management overview
   Returns management module enables the user to return the items back to the vendor and manage user returns efficiently. For sales order returns, system follows a different process for delivered returns and non-delivered returns.
   This application enables user to return the items back to the vendors. This module supports returns which are with PO and without PO.

Utility

• Raise return request against a PO capturing return types, PO number and return quantity.
• Raise return request for items which are inbounded without a PO capturing return type and other details.
• Application allows quick ship of items which needs to be returned to the vendor.

1.1 RTV Enquiry
Using this screen, one will be able to view RTV requests in a single screen.

Navigation:
Returns –> RTV Enquiry

Utility 

• User will be able to see all the RTV requests in a single screen. The search results can be narrowed using different search fields available in the screen and user may further narrow down the search results using the Advance Search option.
• User may print the search results using the option Export/ Detail Export.
• Screen also allows user to create a new RTV request using this screen.

Lets understand RTV in detail:

• RTV No.: If the user wants to see the record corresponding to a RTV Number, then user may use this field.
• RTV Date: During search user may narrow the search by setting RTV Date to Today, Yesterday, Last 7 days, Last 30 days, This Month, Last Month and also it can be set to custom range. If you set the custom date range, user needs to press Apply action button.
• RTV Type: User may narrow the search results by choosing RTV type: Damage Return, Intercompany move, Normal Return
• PO No.: eRetail will be able to narrow the search results using the PO number.
• Vendor: Search results can be narrowed down using the vendor code.
• Status: Search results can be narrowed using the status of the PO.
• RTV Qty, RTV Amount: Search results can be narrowed using the RTV Qty and RTV amount.
• On Hold: Search results can be narrowed using On Hold as the criteria.Action Button
• Search: Clicking on the search button without entering any filter criterion will populate the list of all the RTV requests based on default filter setting. User can further narrow down the search by using filter options to get a specific information.
• Reset: Reset button will refresh the filter fields to default settings, i.e. to an initial state to start a fresh search.
• Advance Search: This button narrows the search results by adding more search criteria such as site location and SKU Code.
• Export: When this button is pressed, the result set containing all the fields in the RTV Enquiry screen gets downloaded in .xslx format.
• Detail Export: When this button is pressed, details of the records in addition to the fields shown in the RTV Enquiry screen gets downloaded in .xslx format.
• Add New: When this button is pressed a new window will open where user will be able to create a new RTV Request in the system.

1.2 Vendor Return Create/ Edit:
This screen enables user to create a RTV request and modify the existing RTV request.

Navigation:
Returns —> Vendor Return Create/Edit

Utility 

• Initiate RTV request with two options: With PO and without PO.
• Modify the existing RTV request.

Lets Understand the below in detail:

• Vendor Details
• User Defined Fields
• Shipping Details
• Activity and Remarks

Vendor Details tab:
Vendor return request can be created with two options:
With PO
and
Without PO.

With PO option:

• PO Code: User needs to select a PO from lookup. Upon clicking the lookup, a dialog box opens where user can filter for a PO based on PO No., PO Date, Status and Vendor Code. User needs to highlight the PO from the result set and click OK. User may clear the search criteria using Reset button for a fresh search.
• Site Location: On selection of PO Code, Site Location field gets populated automatically.
• Remarks: User may input any remarks about this return request in the field provide.
• Return Type: User may choose return type indicating the reason for return from the following values:
  Normal return,
  Intercompany Move,
  Damage Return.
• Vendor Code: This field is auto-populated on the selection of PO.
• Vendor name: This field is auto-populated on the selection of PO.
• Status: This field captures various status of the return request.
• Edit Return quantity: Here user will be able to modify return quantity in the following format: SKU, Quantity. This detail must be entered row by row and user will be able to enter maximum of 200 records at a time. Once all the records are input, user may click OK which updates RTV Qty as per user’s entry.

Without PO option:

• Site location: On selection of PO Code, Site Location field gets populated automatically.
• Return type: User may choose return type indicating the reason for return from the following values:
  Normal return,
  Intercompany Move,
  Damage Return
• Remarks: User may input any remarks about this return request in the field provide.
• Vendor Code: This field is auto-populated on the selection of PO.
• Vendor Name: This field is auto-populated on the selection of PO.
• Status: This field captures various status of the return request.
• Add SKU: When this button is pressed, a dialog box opens up where user will be able to add a SKU which needs to be returned to the vendor.
• Remove SKU: Added SKU can be removed by the user by highlighting on this SKU line.
• Import: User may choose to add SKUs which needs to be returned by using import option. Here user needs to enter SKUs in the following format one by one in a row: SKU, Quantity. User can add a maximum of 200 records using this option.

ACTION BUTTON

• Add New: When this button is pressed user will be able to create a new vendor return request.
• Save: Saves the record.
• Confirm: This button appears when the RTV request is in Created State.
• Quick Ship: This button appears when the order is in allocated state.
• Side Menu dropdown: This has options using which user will be able to Cancel and hold the request. Also user will be able to print the details of the request by clicking on Print option. Also user will be able mail this information to the vendor using “Send Mail to Vendor” option.

User defined Fields Tab:

This tab has fields UDF1, UDF2, UDF3, UDF4, UDF5 can be entered. These fields are specific user’s requirement which user can use as per his requirement.

Activity and  Remarks tab
This tab has Add Comments tab. User can add his comments related to the RTV request at various stages. Once comment is added, user must press Submit Comments button. When the user adds a comment, it gets added to comments log section where the user will be able to see Date, AddedBy and Status.


1.3 Customer returns
Customer returns overview
This application enables user to manage sales order returns. This module supports two types returns: delivered returns and non-delivered returns efficiently.
This screen enables one to view sales order returns from various channels in a single screen.

Utility 

• User will be able to see all the sales order return requests in a single screen. The search results can be narrowed using different search fields available in the screen and user may further narrow down the search results using the Advance Search option.
• User may retrieve the search results using the option Export/ Detail Export.
• Screen also allows user to create a new sales order return request using this screen.Lets understand in detail
• Return No.: User may narrow the search results using Return Number by entering the number in the field.
• External order No.: This is the external number which will be used to filter the records.
• Order No.: User may enter a specific order number to get the results.
• Order type: This is a dropdown field which will help user to filter return requests having specific order types:
  COD,
  Cheque/DD,
  Consignment,
  JIT,
  Prepaid,
  Not Defined
• Order channel: If user wants to view orders specific to an order channel, he may choose from dropdown.
• Status: User may view return requests for specific status from the following: Cancelled, Closed, Confirmed, Pending Confirmation
• Return type: User may choose to view orders belonging to return types: Delivered Return and Non-delivered Return.
• Return category: User will be able to filter for a specific return category: Credit Coupon, Refund and Replacement.
• Return date: During search user may narrow the search by setting Return Date to Today, Yesterday, Last 7 days, Last 30 days, This Month, Last Month and it can be set to custom range. If you set the custom date range, user needs to press Apply action button.
• Created user: User will be able to filter records based on created user.
• Confirm date: During search user may narrow the search by setting Confirm Date to Today, Yesterday, Last 7 days, Last 30 days, This Month, Last Month and it can be set to custom range. If you set the custom date range, user needs to press Apply action button.
• Return close date: During search user may narrow the search by setting Return Close Date to Today, Yesterday, Last 7 days, Last 30 days, This Month, Last Month and it can be set to custom range. If you set the custom date range, user needs to press Apply action button.
• Delivery No.: User may narrow the search results for a specific delivery number using this option.
• Order date, Amount, Reverse Tracking No., Transporter Name, : This is an indicative field in the screen.
• Delivery Type: User may choose following delivery types: Delivery, No Pick Up, Pick up from the dropdown to narrow down search resultsAction buttons
• Search: Clicking on the search button without entering any filter criterion will populate the list of all the sales order return requests based on default filter setting. User can further narrow down the search by using filter options to get a specific information.
• Reset: Reset button will refresh the filter fields to default settings, i.e. to an initial state to start a fresh search.
• Advance Search: This button narrows the search results by adding more search criteria such as SKU code, Tracking No., Customer Name, Customer Email and Customer Phone.
• Export: When this button is pressed, the result set containing all the fields in the Customer Return Enquiry screen gets downloaded in .xslx format.
• Detail Export: When this button is pressed, details of the records in addition to the fields shown in the Customer Return Enquiry screen gets downloaded in .xslx format.
• Add New: When this button is pressed a new window will open where user will be able to create a new Customer Return Request in the system.
  

  
  1.4 Customer return create/edit
  This enables user to create customer return create/ edit in eRetail.

  Navigation:
  Returns –> Customer return create/edit

Lets understand how we create or edit the customer return:

• Request type: It has two bullet boxes: Request and Request & Inbound.
• If the user selects Request Type: Request, then he/she will be able to use return types: Delivered return and non-delivered return.
• If the user selects Request Type: Request & Inbound, then he/she will be able to use Return Type as Delivered return.
• External order no.: It is a dialog box. Upon clicking this field a dialog box opens up where user will be able to search for an external order number and add it. User return will be initiated against this request.
  The details of the dialog box is given in the following note: User may filter using  External order no., order no, Delivery No/ AWB No, Order Date, Invoice No in the dialog box. After entering the details user need to press Search button. User may press reset for a fresh search. After choosing a particular external order no user has to press OK to create return request.

• Delivery location: This is a dropdown field where user will be able to choose return delivery location for the customer request.
• Return type: This is a dropdown field where user will be able to choose a return type: Delivered return and non-delivered return.
  If the user chooses return type as delivered return, category and delivery type dropdowns fields become active.
  If the user chooses return type as non-delivered return, category and delivery type dropdown fields become inactive and these fields get auto populated with null and Delivery respectively.

• Category: User will be able to choose a category if the user chooses return type as delivered return. User will be able to choose following categories: Credit coupon, refund, replacement
• Delivery type: This field becomes active for delivered returns and for non-delivered returns it is set to delivery by default.

For delivered returns user will be able to choose a type from the following :
Pick up,
no pick up
and
delivery.

• Transporter: User will be able to choose a transporter to fulfil the return request.
• Reference no.: User may insert reference number for keeping more information.
• Remarks: User may insert remarks in this field.
• Refund remarks: User may insert refund remarks in this field.
• Refund status: Check this to know the refund status.
• Refund date: This gets populated with refund date and this is an indicative field.
  

  Action Button

• Add New: User will be able to add a new return request.
• Save: Saves the record. When a new record is saved, the status of the return request changes to Pending Confirmation.User needs to mention return quantities for an SKU. If there is a single SKU in a PO and user creates return request, then automatically return qty will be set to one. In all other cases return qty has to be specified by the user.
• Confirm: User will be able to confirm the return request by pressing this button. The status of the return request changes to confirmed.
• If the return request is in confirmed status, user will be able to inbound returned items.
• Upon inbounding the returned items in the warehouse, the status of the return request changes to Closed automatically.
• Once the PO is in closed status, the user will be able to refund the PO by choosing from the menu option. User needs to input details like Refund Remarks, Refund date for completing refund transaction in eRetail.
• Cancel: By clicking on this user will be able to cancel the transaction.

eRetail POS

Vin eRetail POS
Overview
POS (Point of Sale) is the place where the actual transaction is taking place on a particular time. Vin eRetail’s POS is a cloud based app enabling sellers to manage selling operations at a physical store location.

Dashboard shown in the above screenshot gives the gist of all the transaction’s data in a consolidated format along with the order and revenue graph.
It also consists of the filter for the user to choose the period for which he/she wish to view the data representation.
Lets move further section by section to understand POS.

It is divided into different sections:
-> Sales
-> Return
-> Inventory Management
-> Procurement
-> Reports 
-> eCommerce
-> Admin

1. SALES

Sales section here in POS provides all the information about sales enquiry, bills generation and refund related transactions.
This section is further divided into:
->Sales Enquiry
->Generate Bill
->Refund

1.1 Sales Enquiry
Sales enquiry section enables the user search and filter the sales enquiry based on various filter available.
Bill No: Bill number is the system generated unique number given to every bill as a identifier.
Order No: Order number is the order number given to an order in the eRetail.
Bill Amount: Bill amount is the total amount of transaction being carried out per order per bill number. User can search any sales entry on the basis of bill amount as well.
Bill Date: User can search and enquire for sales entries on the basis of their billing date. In the POS system their are pre defined fields of periods based on which the enquiry can be searched.
Customer Name: User can search the sales transaction on the basis of name of the customer.
Reprint Receipt: User can reprint the receipt from here.
Email Receipt: User can email the receipt from here.
Location: User can filter on the basis of location of the warehouse.

Action buttons:

1. Search : Clicking on the search button without entering any filter criterion will populate the list of all the sales transaction on default filter setting. User can further narrow down the search by using filter options to get any specific information.
2. Clear Search  : Clear search 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. Advance Search: Advance search further improves the search results of sales enquiry by providing more fields to filter from. Below fields get added for the advance search option of the Sales Enquiry:
->Customer Phone
->Customer Email

1.2 Generate Bill
Generate bills section enables the user to generate the bill from here and proceed with the payment of any transaction. It also enables the user to park the sale of a customer in case customer wishes to recheck the products, and in the meantime user can start the fresh sale transaction and can later retrieve the parked sale.
1.2.1 SKU Search
1.2.2 Add New Customer
1.2.3 Park Sale
1.2.4 Discard Sale

1.2.1 SKU Search
In any POS, to commence a transaction for payment, the first step performed is to search the SKU customer is ordering and then add it for further process.
User can type or scan SKUs bought by the customer. Pressing ‘Enter’ will open “SKU List” pop up. 
Below are fields based on which the SKU can be searched for scanning in POS.
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.
Description: Details provided to each SKU which explains the feature of products.
Size & MRP: User can search & filter the SKU on the basis of size an d MRP(Maximum Retail Price) as well.
Sale Price: User can filter the SKU on the basis of sale price of the product.
Available Quantity: The SKU’s can be filtered on the basis of available quantity to be further selected by the user for POS transaction.

Action Button
1. Search: Clicking on the search button without entering any filter criterion will populate the list of all theSKUs on default filter setting. User can further narrow down the search by using filter options to get any specific information.
2. Clear Search: Clear search button will refresh the filter fields to default settings, i.e. to an initial state to start fresh search.

1.2.2 Add New Customer
Add new customer section is has a great significance as from this section of the POS the user creates new customer or searches for the existing customer to commence the POS transaction.
To create Customer user will have to fill in the below basic details:
Customer Name
Customer Phone
Customer Email

To search for an already existing customer in the system for the transaction, the user can user the below filter/search field:
Customer Name
Customer Phone
Customer Email
Customer Create Date
Customer Code
Extra Info

Action Button
1. Search :Clicking on the search button without entering any filter criterion will populate the list of all the SKUs on default filter setting. User can further narrow down the search by using filter options to get any specific information.
2. Clear Search  :Clear search button will refresh the filter fields to default settings, i.e. to an initial state to start fresh search.

1.2.3 Park Sale
Park sale is an awesome concept of parking the sale for sometime in case of customer wants to add or reduce some products in the current listing, so here user can park this customer in background for the time being and take up the next customer in queue for the transaction and then can retrieve the previous customer on hold.

1.2.4 Discard Sale
Discard sale is the process of removing the sale transaction created before proceeding for the billing. On the events where at the last moment buyer changes the mind about the product or user may have entered the wrong SKU and wants to remove the same, then in such cases discard sale feature can be useful.

2. RETURN
Return section here in POS provides all the information about return enquiry and return request creation.
This section is further divided into:
-> Return Enquiry
-> Create Return

2.1 Create Return
User can create the return of product purchased by the customer.
Below are fields which the user needs to fill in order to raise the return.
Bill Number: User will search and enter the bill number of the order /SKUs which needs to be returned. Entering the bill number will fetch the details of the products ordered in that bill. User will then select the products to be returned as per customer’s requirement proceed.
Return Category: Category of return needs to be defined by the user as per customer’s requirement. Below are the three types of return out of which one can be processed.
-> Credit Coupon: it is a receipt given by a the user/POS to a customer who has returned goods, which can be used by the customer against future purchases (may be valid upto a certain period)
-> Refund: User/POS returning the amount paid by the customer against the SKU returned.
-> Replacement: Customer replacing the SKU he wants to return with some other SKU that he wish to purchase by adjusting the previous amount paid here.
Reason: POS user will be entering the reason of return by asking the same from the customer.
Enter Return Quantity: Once the bill number is fetched for the return, and SKU is selected from that order then the user will be entering the quantity to be returned by the customer and click on Confirm Return.

ACTION BUTTON
New: To raise a new return request.
Confirm Return: After filling in all the details, user uses confirm button to confirm the return request.

2.2 Return Enquiry
Return Enquiry section enables the user to search for the existing returns already raised by POS user. This section will be helpful in data analysis of all the returns created in the POS system.
Below are the fields based on which the returns requests can be searched, filetered & viewed.

3. INVENTORY MANAGEMENT

3.1 Inventory View & Adjustment
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 Code & by SKU IMEI.


3.1.1 Inventory view by SKU
In inventory view by scan user can search or filter SKU’s on basis of few fields, lets understand them in detail.
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 filter and search the SKU on the basis of description given to it.
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.
Inv Bucket: Inv bucket shows the status of the products in inbound and accordingly to be assigned the bucket. User will have to select the most suitable one out the given options.
Total Quantity:Total quantity of the SKU
Available Quantity: Actual available quantity of the SKU.
Brand Code:User can filter and search the brand code on the basis of brand code given to it .
Site Location: User’s selected warehouse location for the Inventory view will be getting displayed here. This field is automatically fed once the user logs in.

ACTION BUTTON
a) Search : Clicking on the search button without entering any filter criterion will populate the list of all the SKU code on default filter setting. User can further narrow down the search by using filter options to get any specific information.
b) Clear Search  : Clear search button will refresh the filter fields to default settings, i.e. to an initial state to start fresh search.
c) Download  : To download the filtered or searched result in CSV format which is displayed in the data grid.
d) Add Stock  : By this action button user can add the stock to any particular SKU. Once this is clicked the user gets a form to fill in order to increase the stock.
SKU* : Enter the SKU name here in order to increase its inventory.
SKU Desc : Enter the SKU description.
Adjustment Qty*: Enter the Increased or adjusted quantity.
Reason*: Enter the reason for adjustment. For example: Order Shipment, Stock Take etc.

3.1.2 Inventory view by IMEI
In inventory view by IMEI user can search or filter SKU’s on basis of IMEI as well. Rest everything will be same as inventory view by SKU code but here the inventory can be viewed by IMEI as well.

3.2 Manage Inbound
Overview
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 enquiry can be carried out by filtering the below data:
Inbound no: Inbound number is the unique identification system generated number given to every inbound created in the system.
STO no: User can search the inbound enquiry and can narrow down the search results by using STO no. as a filter.
ASN no: User can search the inbound enquiry and can narrow down the search results by using ASN no. as a filter.
PO no: Inbound can be searched with respect to the PO number generated for the same.
GRN no & Date: Inbound enquiry can be carried out by using the Goods Received Note and date.
Inbound Type: User can filter the inbound numbers based on their types and categories.

Invoice no: The inbound can be filtered on the basis of invoice number as well.
Vendor: User can filter the inbound enquiry by the vendor name as well.
Status: The inbound can also be searched with the status of the inbound entered in the system.
The Status based on which these inbound can be filtered are:
-> Cancelled
-> Confirmed
-> GRN in Process
-> GRN in QC
-> Pending Confirmation
->QC Done
Inbound Location: User can search and filter the result on the basis of inbound location.

3.3 Manage Stock Transfer

• This section will enable the POS user to enquire and search an already existing STO’s and STO details. User can refine the search further by using filters as per requirement/s. Fields on the basis of which the Stock Transfer Orders can be searched:

• STO number- Date- Type
  STO number is the system generated unique ID given to the STO & from the filter option the STO’s can be searched using STO as well.
  STO Date is the date on which the STO is created.
  STO type filter consists of two type STO, one is NORMAL STO which is created in case of normal transfer from one location to another & other type of STO is RETURN where the sales transfer order is created in case of order returns. STO can be filtered /searched on these bases as well.

Ship & Delivered Date
Ship Date & delivered date are the dates on which the STO was shipped and delivered respectively. The user can narrow down the search results by entering the ship date or delivered date.

Origin & Destination Site
User can also search the STO by entering the origin and destination site for the STO. And all the STO’s corresponding to that origin will be displayed as search result.

Status
STOs status changes at every stage with respect to the user’s action and STOs processing cycle.
The status through which an STO goes through is:
-Created: When the STO is created.
-confirmed: When the STO is Saved and confirmed.
-Allocated: When the STO is allocated for the WH location.
-Part Allocated: When not all the SKU’s of the STO but few are allocated for the WH location.
-Part Picked: When from an confirmed STO few SKU’s are picked and not the whole STO, then this is the part picked status of an STO.
-Pick Complete: When an STO is completely picked.
-Part Shipped: When from an STO few SKU’s are Shipped and not the whole STO, then this is the part Shipped status of an STO.
-Shipped Complete: When an STO is completely picked.
-Delivered: When the STO is delivered to destination then the status changes to delivered.
-On Hold: User can put the STO on hold if he wants, and in the search criterion the same can be treated as a parameter to narrow down the STO search results.

Action buttons

1. Search: Clicking on the search button without entering any filter criterion will populate the list of all the STO 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/Download: To download the filtered or searched result in CSV format which is displayed in the data grid.
4. Advance Search: Advance search further improves the search results of STO by providing more fields to filter from. Below fields get added for the advance search option of the STOs.
5. Add New: To add a new STO to the database.
below tabs are present to capture all STO related information while creating it.
-> STO Order Detail
-> UDF
-> Outbound Delivery
-> Comment History
-> STO Order Tag

 STO Order Detail:
From STO order detail section the user will enter all the details for creating an STO and adds the SKU for STO from here.

Ext. STO No:
External STO number is the number given by the user OR order No provided by the sales channel/platform from where STOs are pulled into eRetail

STO Type:
There can be two type of STO, one is NORMAL STO which is created in case of normal transfer from one location to another & other type of STO is RETURN where the sales transfer order is created in case of order returns.
From Site:
The ‘from site’ is the warehouse location from where the SKU will be picked up.
To Site
The ‘to site’ is the warehouse location to where the SKU will be inward.
Reason
User will have to mention the reason for Stock transfer being done from one location to another.
Priority
User can set the priority while creating the STO as low priority or high priority based on the priority options.
On Hold Status:
User can put the STO on hold if he wants, and in the search criterion the same can be treated as a parameter to narrow down the STO search results.
Remarks:
User can mention the remarks for the STO being sent for the receiving warehouse to know about the same.
Status:
STOs status changes at every stage with respect to the user’s action and STOs processing cycle.
The status through which an STO goes through is:
-Created: When the STO is created.
-confirmed: When the STO is Saved and confirmed.
-Allocated: When the STO is allocated for the WH location.
-Part Allocated: When not all the SKU’s of the STO but few are allocated for the WH location.
-Part Picked: When from an confirmed STO few SKU’s are picked and not the whole STO, then this is the part picked status of an STO.
-Pick Complete: When an STO is completely picked.
-Part Shipped: When from an STO few SKU’s are Shipped and not the whole STO, then this is the part Shipped status of an STO.
-Shipped Complete: When an STO is completely picked.
-Delivered: When the STO is delivered to destination then the status changes to delivered.

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.
Outbound Delivery
Outbound delivery number shows the details of order like from which Warehouse it has been shipped, the Shipping detail or ASN number.
The transporter can be changed for the order from this section.
STO Order Tag
User can enter the order tags which are nothing but important information about the STO order which also acts as the searchable keywords for those STOs.

Action buttons
1. Add New: To add a new STO to the database.
2. Save: Save the created the STO.
3. Confirm: To confirm the created STO.