MuktifreshMuktifresh

Muktifresh- Business
RequirementMuktifresh-
Business Requirement
This document contains an overview of the business requirements for developing website
and mobile application (iOS, Android, Windows)This document contains an overview of the
business requirements for developing website and mobile application (iOS, Android,
Windows)

MuktifreshMuktifresh
7/31/20167/31/2016
 Requirements
1. 1.1 End 1.1.1 E- 3 main types of end user should be able to login to the portal-
Website User End commerce 1) B2C customers- main users of the portal who should have
Portal all the functionalities of the portal for order placement/
purchasing. (Will be referred as UserA henceforth)
2) B2B customers- Customers in this space should be able to
see only list of products with price and quantities. UI
should be simplistic in nature. (Will be referred as UserB
henceforth)
3) Corporate customers/Bulk enquiry- This is should be a
simple form for bulk enquiry. Consumers here will not
actually purchase the products, rather enquire about
price and quantity. Necessary information about product,
price, quantity and customer details should be captured
in the form. (Will be referred as UserC henceforth)
1.1.2 Login 1) UserA- Login can be authenticated by conventional
username-password-OTP authentication technique or
directly through fb/google login
2) UserB- Same
3) UserC- Only OTP authentication required for submitting
application
1.1.3 Listing 1) There should be provision of capturing multiple languages
of Products for capturing different names.
2) In individual product page their should be provision for
embedding photos and video
1.1.4 Order 1) UserA should have-
Placement a. User should be able to either pick products and
build their basket or go for a pre-defined basket
b. Customer should be able to choose their delivery
slot. Which will be no earlier than 24 hours from
the order placement time
c. Customers with high order value or
subscription(weekly/ monthly) should be able to
split their basket in 2 different delivery slots
within a span of 2 weeks
d. Max limit on quantity- Limit should be editable by
admin
e. There should be provision for applying coupon
code for customers
2) UserB should have-
a. Users should simply be able to select products
and quantity
b. Min limit should be imposed on quantity- Limit
should be editable by admin
3) UserC- No order placement feature required
4) Customers should have option for order cancellation no
later than 6 hours before the actual delivery. This should

Page 2 of 6
 trigger a red flag against the order ID for the employees
to see and act accordingly
5) Cancelled orders should trigger a workflow for payment
return
6) CART: While user are adding items to their bucket there
would be one dynamic billing note on the right side of the
page showing the total order along with total purchased
value, it will help the customer to know about this orders
and the amount real time. This note pad will be top layer
which will scroll around the page while the user is
scrolling the page.
7) There should be provision for adding coupon code in
cart. A coupon having specific validity should be expired
at the end of specific time period. Any transaction with
valid coupon code should adjust the cart value. Any
transaction of the coupon expired, should not go through
1.1.5 1) UserA-
Delivery a. 3 defined delivery slots should be available for a
single order and the earliest one should be no
sooner than 24 hours from the order placement
time (8-12am, 1pm-5 pm, 6-10 pm). There would
be option so that we can modify the time slot or
deactivate time slot based on our requirement.
b. Weekly or monthly subscribers should be able to
split their products in 2 delivery slots/week
c. There should be 3 separate type of delivery
pincodes in database-
i. List of pincodes where delivery should be
free
ii. List of pincodes where delivery would be
chargeable
iii. For rest of the pincodes- Not yet
delivering. Coming soon
iv. All can be controlled and edited by admin
2) UserB
a. 3 defined delivery slots should be available for a
single order and the earliest one should be no
sooner than 48 hours from the order placement
time (8-12am, 1pm-5 pm, 6-10 pm)
b. There should be 3 separate type of delivery
pincodes in database-
i. List of pincodes where delivery should be
free
ii. List of pincodes where delivery would be
chargeable
iii. All can be controlled and edited by admin
3) Customers should be able to track the order through

Page 3 of 6
 some specific milestones- eg. Order placed collecting
products from farm Products packagingOut for
Delivery  delivered
1.1.6 Customer should be able to view status of order from order
placement till delivery
1.1.7 4) UserA
Constraint a. Max limit on the quantity they can purchase
b. Min limit on the order value they purchase
c. Single coupon can be applied to single order
d. Any other place in Kolkata than a list of defined
pincode should add a specific delivery charge
(delivery charge will be controlled by admin)
5) UserB-
a. Min limit on quantity they can purchase
b. Max limit on quantity they can purchase
c. Any other place in Kolkata than a list of defined
pincode should add a specific delivery charge
(delivery charge will be controlled by admin)
1.1.8 Story Portal should have a sub-page which should have provision for
Page uploading new contents, video, blog and other articles time to
time. It should have provision for direct upload or embedding
1.2 1.2.1 Login Vendors should be provided admin given username and password
Vendor 1.2.2 1) Admin can place order against specific vendor ID.
End Procuremen 2) Vendor should be able to view list of products, quantity.
t Vendor should be able to update quantity of products and
price for each one of them and submit back to admin.
3) Admin can then confirm the order and raise a final invoice
against the vendor name. (Vendors will be carrying
invoice copy while delivering the order. This process is to
understand availability of items with vendor which are
asked for)
1.2.3 Should have provision to upload and scan final payment
Payment confirmation to vendor page
Payment gateway of CCAVENUE
Cash on Delivery and cash management
1.3 1.3.1 Login 1) Employee should be able to access different part of the
Employee database as per the access/ control given to him by admin
End 2) Employees roles will majorly involve- admin, Finance &
Accounts, Procurement, Order & Delivery, Call center &
complaints handling, HR, Inventory handling
3) Admin should have master control to everything apart
from change in core database or application structure

2. 2.1 End 2.1.1 Mobile app should be applicable for both UserA and UserB. All the
Mobile Users Additional features for UserA and UserB should also be there in mobile app.
App Features Apart from the above features a mobile app should contain-
1. Geo- tagging

Page 4 of 6
 2. Automatic OTP identification for account authentication
or payment confirmation
3.Databa 3.1. OMS 3.1.1 Orders 1. Order should be accumulated in central database in
se & tabular format as per timeline and with details of quantity
back end and delivery address. Employee working on order and
system delivery should be able to pull out a list of orders for
different delivery slots tomorrow (at 6 pm everyday) with
details of products and delivery address
2. Two scenarios-
a. Any cancelled order before 6 pm should be
adjusted with the total demand
quantity(incoming quantity) for tomorrow and it
should reflect in the accumulated order for
tomorrow
b. Any cancelled order after 6 pm should add the
quantity back to stored quantity
Flash Sale 1. There should be options for flash sale for any product of
certain qty. along with other products.
3.2 Other 3.2.1 1. Employees from different department should be able to
Modules Reporting view relevant data
2. Employee in different departments should be able to
download different reports as per requirement
3. Full functional reporting capabilities for different modules
3.2.2 1.Full functional inventory module
Inventories 2. Admin view of inventory should be in tabular format to
capture-
c. Incoming inventories
d. Stored quantity
e. Outgoing inventories

3.2.3 1. A full functional finance module for capturing all the

Financial financial transactions as discussed
Transactions 2. It should be compliant to audit and tax requirements
3. Provision for capturing all ad-hoc expenses with
supporting docs should be there
4. P&L, balance sheet and ledger should be integrated
5. Vendor payment entry.
6. No single admin should be able to override any financial
transaction. It should take at least 2 admins to override
the same
3.2.4Promot Solution should include a full functional promotional module like
ional existing e-commerce websites
Module
3.2.5 1. Employee log registered, Leave, compensation, etc
Attendance 2. Should have capability to attach any document in a
particular employee profile page

Page 5 of 6
 Design should focus more on pictorial representation (Pinterest)
Non-Functional Background color should be either different shades of blue or green
Uniform font should be used across pages
Muktifresh logo should be prominently visible on each page and sub-page

Page 6 of 6