E-Com BRS 6.5

Design Qandy
DesignQandy E-Com Portal
DesignQandy E-commerce Site

Project/Initiative
March 2021
Version 1.0
Document History
Version Date Prepared by Verified by

1.0 21-March-2021
Contents
...................................................................................3
1 How to Read..................................................................................................................................9
2 About Company............................................................................................................................9
3 Objective.......................................................................................................................................9
4 Abbreviation.................................................................................................................................9
5 Overview.....................................................................................................................................10
6 Portal Authentication and Authorization.....................................................................................12
6.1 Portal user Group\Users......................................................................................................12
6.2 Customer Creation / Login/managementt...........................................................................13
6.3 Vendor Authorization..........................................................................................................13
7 E-COM Portal Header and Footer...............................................................................................13
8 Home Page..................................................................................................................................14
9 Product Listing............................................................................................................................15
9.1 The product listing page would display information............................................................15
9.2 Determining which product to display based on inventory.................................................15
9.3 Out-of-Stock Inventory........................................................................................................15
9.4 The product listing page would provide the following options............................................16
9.5 Product Listing Views...........................................................................................................16
10 Product Detail.........................................................................................................................16
11 Cart..........................................................................................................................................18
11.1 Display the following information and options for each item..............................................18
11.2 Display the following information in summary....................................................................18
12 Abandoned Cart\Failed Transaction.......................................................................................18
13 Checkout or Buy Now.............................................................................................................18
13.1 Sign\Sign Up\Guest Checkout..........................................................................................19
13.2 Address(s)............................................................................................................................19
13.3 Delivery Type(s)...................................................................................................................19
13.4 Personal Purchase or Business Purchase.............................................................................19
13.5 Review Order.......................................................................................................................19
14 Payment..................................................................................................................................20
15 Order Confirmation.................................................................................................................20
16 Inquiry.....................................................................................................................................20
17 Selling from Store\Studio\Ware House..................................................................................20
18 Invoice\Order Cancellation\Return and Refund....................................................................20
18.1 When should the system generate the invoice in the process?...........................................20
18.2 Cancellations........................................................................................................................21
18.3 Return..................................................................................................................................21
18.4 Refund workflow:................................................................................................................22
19 Client Account\Dashboard.....................................................................................................23
19.1 My Profile............................................................................................................................23
19.2 My Orders............................................................................................................................23
19.3 Wish list...............................................................................................................................24
19.4 Shortlisting...........................................................................................................................24
19.5 Gift List *(To be discussed)..................................................................................................24
19.6 My Addresses......................................................................................................................24
19.7 Notification Settings.............................................................................................................24
20 Operations\Dashboard (Admin).............................................................................................24
20.1 Manage Order (Admin)........................................................................................................25
20.1.1 Order Filtering Options................................................................................................25
20.1.2 Order Listing................................................................................................................25
20.1.3 Export Orders...............................................................................................................26
20.1.4 Order Creation.............................................................................................................26
20.1.5 Order Edit.........................................................................................................................26
20.1.6 Order fulfillment team’s responsibility *.....................................................................26
20.1.7 Order Details................................................................................................................26
20.2 Delivery and Invoice.............................................................................................................27
20.3 Order Fulfilment/Inventory/Warehouse..............................................................................27
20.3.1 QC................................................................................................................................27
20.3.2 Packaging Slip..............................................................................................................27
20.4 Raise an Enquiry...................................................................................................................27
21 Purchase Module.....................................................................................................................27
21.1 Purchase + Inventory...........................................................................................................28
21.2 Transaction Management (Finances)...................................................................................28
22 Notifications............................................................................................................................28
22.1 Type of Notification.........................................................................................................28
22.2 Notification Setup............................................................................................................29
23 Admin Functions.....................................................................................................................29
23.1 Users....................................................................................................................................30
23.2 Roles and Permissions.........................................................................................................30
23.4 Customer.............................................................................................................................30
23.5 Vendors................................................................................................................................30
24 CMS.........................................................................................................................................31
24.1 Category and Subcategory...................................................................................................31
24.2 Specification........................................................................................................................31
24.4 Products – (Category/Subcategory/Country of origin)........................................................31
24.4.1 Product Variant............................................................................................................32
24.5 Product Collection...............................................................................................................33
24.6 Banner Ads...........................................................................................................................33
24.7 Featured Product.................................................................................................................33
24.8 Configuration.......................................................................................................................34
24.9 Tax Configuration.................................................................................................................34
24.10 Manage Offers.................................................................................................................34
24.10.1 Coupon...........................................................................................................................34
24.10.2 Discount...................................................................................................................35
24.10.3 Loyalty Point............................................................................................................35
24.11 Commission *(Depending on client type)........................................................................35
24.12 Shipping...........................................................................................................................35
24.12.1 Shipping Zone *(To be discussed)............................................................................35
24.12.2 Shipping Rates..........................................................................................................35
24.13 General Setup..................................................................................................................36
24.13.1 Company..................................................................................................................36
24.13.2 General....................................................................................................................36
24.13.4 Custom Fields Collection..........................................................................................36
24.13.5 Checkout..................................................................................................................37
24.13.6 Order Settings..........................................................................................................37
24.13.7 Order Confirmation..................................................................................................37

24.13.8 Out-of-Stock Items Configuration............................................................................38
24.14 Cancellations....................................................................................................................38
24.15 Pickup from Joints\Warehouse........................................................................................38
24.16 Integration API.................................................................................................................38
24.17 Message Bar.....................................................................................................................39
24.18 Other Configurations.......................................................................................................39
25 ERP integration.......................................................................................................................39
26 Non Functional Requirement..................................................................................................40
26.1 Auditing and Logging...........................................................................................................40
26.2 Implied requirements..........................................................................................................40
1 How to Read
Any person going through this document should go through the following sections.
- Overview
- Abbreviation
- Main heading before getting into the detail of that section
- Non-functional requirement
2 About Company
DesignQandy (“DQ”) is an “Intelligent Technology” based architectural design company. The
company offers a seamless interaction between architects, clients, the world’s best brands, and all
other stakeholders in the ecosystem.
Unlike conventional business practices of increasing the user base through heavy discounting of
both price and quality, the Company is committed to the highest quality standards and
uncompromising value.
DQ is conceived to create customized well-designed spaces for homes / exclusive office spaces /
concept restaurants and boutique hotels. The positive psychological impact of a well-designed
space offers maximum convenience, increased comfort, and an enhanced quality of life.
3 Objective
In his document, we will be describing E-Com portal requirements.
The DQ team is working to create the solution to offer E-Com infrastructure to deliver world-class
furniture and accessories for customers across the world. The proposed portal is planned to work as
an umbrella infrastructure for a variety of stakeholders that would work together to build upscale
homes and cater the clients looking for home furnishing, décor and electronic products.
The DQ’s other arm is working on home design and development projects which typically include
clients, architects, skilled craftsmen, executing teams, and product companies. From the home
design perspective the solution will be focused on creating an ultimate experience for the client by
creating a win-win situation for all other stakeholders. The e-commerce portion of the portal will
enable clients to choose upscale market quality products at ease.
4 Abbreviation
Category Abbreviation Description

Generic DQ DesignQandy
Generic Customer Customer who uses DQ E-commerce services
Generic User User refers to all the users in the system from the DQ
side.
Generic Zone Refers to an area within a city
Generic CRUD Refers to an area within a city
Product Category Category or Categories refers to high-level categorization

of products available on the Portal. Also include sub-
categories. For example Furniture is a category whereas
Sofas can be a subcategory
Product Product Type Product Type refers to product type within a category
example Sofas and Armchairs
Product Sub Product Type Refers to an attribute of a product that helps categories
/ Stock Keeping the product type further. They will be very specific to
Unit (SKU) / product type. An example would be the seating capacity
Variant of the Sofa
5 Overview
The proposed E-Com portal is planned to be a controlled multi-vendor serving solution. This portal
will allow customers to select products from various categories based on product name, product
type, area of origin, brand, and application of the products.
1. Curtain raiser page

This page will be the opening page of the DQ portal to enable clients to choose either Design
Services or E-Com portal.
2. E-com portal Home page
 When a customer lands on the portal, the homepage design should have banners,
few rows of trending products listed, header & footer. (Layout details and mood
board will be provided by third party design agency)
 Customers will have ability to search for the specific product through search terms
and predefined filters or they can browse the various categories to find the right
product.
(Details in section 7 & 8)
3. Product listing page

 There should be appropriate filters to narrow down the list to find out required
product(s) list.
 System should also present the product recommendation and similar products.
 On each product there will be similar products (configured in CMS).
 Each product will also have related products (configured in CMS).
 Products from same origin (product attribute)
(Details in section 9)
4. Product details page

 Product description / Name
 Product image(s), videos, specifications
 Measurements
 Variants (color, material)
 Similar products
 Related products
 Recommended products (on previous buying/selection) history
 What Architect thinks (review of the product if available)
 User would choose the product they desire and would be given the following
options:
1. Add to cart.
2. Add to Wish list – Option to create multiple wish list.

3. Shortlist – Shortlisting view is like a wish–list except it displays
selected items on one page. (with option “Move to cart”)
4. Buy Now
5. Add to Compare – Option to add product to compare and compare
product (Logically only similar product should be shown)
(Details in Section 10)
5. Cart Page
 Display carted products.
 Display expected delivery date (calculate using PIN code)
 Provision to enter desired delivery date, later than calculated delivery date and less
than period allowed to keep order booked (This period may change on product
category and availability of the product)
 From the cart, the user can modify quantity or remove the product from the cart.
 Once finalized, the cart can proceed to checkout.
 Abandoned cart / failed transaction.

6. Review Page
 The review order page will be displayed once user clicks on buy now or cart
checkout.
 User would click proceed to buy and user would be prompted to register or login
into system.
 Contact Customer care / “Chat with us’ option can be added to get confirmation
about right product selection and delivery dates and availability of additional
services/ products/ quantities.
 Billing address
o Check if delivery is available at the address selected.
o Cart would move to payment page.
7. Payment & Invoice

 Provision to enter validate and apply Coupon / Promo codes.
 Calculation and display of Shipping charges
 Calculation and display of applicable Taxes
 The online payment options will be presented.
 The client will make a payment and the invoice will be generated.
8. Order Confirmation
 Order confirmation and thank you message display and send to email and/or mobile.
 System may need to push the sales data to ERP or might generate extract.
9. POS sale
Need to have provision for POS sale across stores and with local inventory / delivery from
warehouses.
10. Enquiry
 Customer can send an enquiry to customer care and then customer care executive
can interact with customer and convert the enquiry in order (journey till payment)
 Send payment link for the order.
 Update E-Com portal with payment details
11. Cancel Order

 Customer may be able to cancel order, till it gets further processed in the system
(limited time/ action)
 Contact Customer care / “Chat with us’ option can be added to get confirmation
about right product selection and delivery dates.
12. Refund & Return
 The system should offer return and refund functionality.
(Details in section 18)
13. Order history and management at backend.

 Open Orders, Closed orders, cancelled orders list will be displayed.
 On selecting specific order, Order details will be displayed with Order delivery
tracking.
14. With an e-commerce setup, along comes features like online ordering, order tracking,
assigning delivery partner, payment confirmation, etc.
15. CMS setup to enter product and other portal data.
16. Integration with ERP for Product data, sales data, Inventory, customer data, Invoice and
finance related data.
17. Notification setup
18. Administrative Functions
19. Other Requirements
 Audit Trail
 Implied requirements
6 Portal Authentication and Authorization

6.1 Portal user Group\Users
User management modules to Add/Remove user through Admin.
1. Supper User: - Development team

2. Application Admin: - Responsible for application administration setting
3. IT admin: - monitors health of application

4. CMS Data management team: - Data entry and validation team.
5. Order Management Team: - responsible for order management

6. Fulfillment Team: - Packaging and logistic team
7. Marketing Team
8. Customer support team(s)
9. Reporting management at various levels
10. Vendor(s)
11. Miscellaneous Role(s).
6.2 Customer Creation / Login / management

6.2.1 Types of customers
• Normal website customer

• Architect as a customer
• Design Services (project) as customer
6.2.2 Customer creation and management
Customer would be able to signup and login with either of the following options with
captcha verification.
• Registered mobile number and password.

• Registered email id and password
• Registered mobile number and OTP.
• Registered email id and OTP
• Facebook
• Google
• Instagram (To be decided)
Forget Password.
• The system should offer to reset their password via OTP.

6.3 Vendor Authorization

1. Vendors might require us to create specific login for their different teams. Authorization
process should allow controlled access and ability to define and assign role and permissions.
Vendors in turn can have either of 2 types of VENDOR MASTER account & VENDOR AGENT
account.
2. The access admin would assign specific role (persona) to user. The persons would be given
view, edit, add, delete permissions at screen level.
7 E-COM Portal Header and Footer

Following are just place holders and will be decided by branding team and displayed according to
various scenarios (user logged in or not)
Section Header
Items Logo
Special Offer
Search bar
Find a studio
Notifications
Raise an Enquiry
Wishlist
Currency
Cart icon
Language
Help\Need Help
Account Icon\Sign In\Sign Up\Logout
Category Bar
Category Category Bar represent the main categories the product will fall into The pictorial
Bar representation should be used for subcategories display Mouse hover on any category
will open the subcategory (type of products). The information displayed should get
hidden as soon as the user moves away from the menu
Raise an User can raise an enquiry and mention the question along with quantity they are eyeing
Enquiry for. Enquiries should be available as tickets where the entire conversation along with
timeline will be available. Whenever a ticket is updated a notification (SMS / Email / App
Icon) is sent based on user selected preferences.
Language Content management is one of the critical and time-consuming process when it comes to
multi language support. We will enable multi language support however the content
would always be displayed in English only, the site header, footer and name of menu and
link will be changed to local language.
Section Footer
About Us Buying Guide New and Media Support Generic
About Us\Our Beds & Press Contact Us Careers
Story Mattresses
Show Room & Sofas Videos FAQs Download App
Offices
Associated Upholstery Broachers Website Terms of Use Sitemap
Brands
Newsletters Gift Card
Blog Privacy Policy Gift Registry
Lighting Social media icons Cookie Policy
Storage
Price Promise
Order Cancellation and Return Policy
8 Home Page
Following is just generic requirement and may change with branding and design.
 While the header and footer remain consistent across portal. The section would detail the
items that would be displayed in a home page.
 Sale Banners – Below the header, we will have carousel of banners showcasing any project
or Flash Sale / Clearance. Each banner will be clickable & landing to respective page like
Project / Case Study page or Category Page.
 Product categories/sub-categories and country/area of origin
 Featured Products – Carousel of highlighted products which business / vendor can promote.
Clicking on one will land user on the Product Details Page.

 Product Recommendations – Carousel of recommended products. Recommendations will
vary for unlogged / anonymous user versus logged user. Clicking on one will land user on the
Product Details Page.
 Content – Customer Stories, Blogs
 Product Search: - System search for products should be made on product category, brand,
country or area wise products. Example user can search for Sofa, Muto Sofa from Africa, or
Mexico. Also need to incorporate product related to exhibition & Events.
9 Product Listing
User would land to product listing page because of following action:
o Searched for a product.

o Clicked on product type from Category section.
o Wish list\short listed product.
o Solution design
9.1 The product listing page would display information.
 Name of product type and a brief about the product type.
 A banner\bar with high level sub product types, e.g. Sofa based on seating capacity which
user can choose from and this would apply filter.
 An option to change the currency in which they would like system to display the price (this
option will be available in Header) however the actual payment would always be taken in
base currency. Solution design should consider possibility of opening store outside India and
taking payment in local currency of that country.
 System will display all the products, but it must check the availability of the use location by
pin code. Based on which delivery timeline to be shown to user (Example: An Architect can
pre-book their product based on their timeline and delivery dates)
9.2 Determining which all product to display based on inventory.
User lands on the portal, system should try and determine the city, state, country the user is
browsing site from to decide on the product to be displayed. As of now we are planning for
delivery within country, where we have store(s) however later we would look at options of
delving abroad as well. Few scenarios
 User is from a country/area in country where we have store(s): - System would

display items from store\warehouse based on regional proximity and expanding the
search further to other store across the country.
 User is from a country where we do not have store: - Since system is not in position
to determine which country user want to deliver goods at to start with; system
would display items from store\warehouse which is activated for international
display. Initially base country stock. At checkout users can check the delivery
eligibility.
9.3 Out of Stock Inventory
The product display Out of Stock items; label as per configuration. System would not accept
order for out-of-stock items rather provide following option to user.
 Add to wish list.

 Notify me when it is available.
 An option to raise inquiry. Should have option to specify quantity.
9.4 The product listing page would provide the following options.
 Option to select and change view (Grid\List… To be decided)
 The option for filtering would be based on the following however can change based on
product type.
o Type
o Brand
o Designer (if specified)
o Price
o Design Style (Example of this is modern design from Bali)
o Region
o Category
o Sub-Category
 Option to change the order of the listing by Newest, highest and lowest price, and field
displayed for filtering.
 Since the list of products could be very large, system should provide:
o option to select the number of items to be displayed on the page with the option to
display all. The options will be 25\50\75\100\All. *(To be discussed)
o option to navigate between pages previous page, next page, beginning, end and
specific page.
o System should also display the current page number and the total number of pages.
o Total number of items based on the current filters.
9.5 Product Listing Views
1. Grid View
2. List View
3. Banner View (applicable to mobile only)
10 Product Detail
The user will land of the product detail page when they click on any specific product item in
the portal. The product details page will include the following:
 Option to different images of product as thumbnails, Photo, and full screen

mode
 Ability to zoom in and out in full screen mode.
 Option to Enter PIN Code and Checking Shipping and Assembling Details
 Option to Buy Now
 Option to Add to Cart
 Option to Add to Wish List
 Display Similar Items
 Should include client service and other details.
 Did you find the details you are looking for? This should give a popup with Yes
and No and
 Option to enter comment. The comment goes to Data Admin who corrects the
data.
 Frequently Brought together.
 Expert’s View. This is like user reviews provided by our industry expert or
designers. There
 Option to specify comment, store it and display to user once approved by

admin.
 Explore more.
o More from Category
o The Same Brand
 What you have been Eyeing
The product details will include the following:
 Type
 Brand
 Designer
 Product hierarchy
 Product Name
 By (Designer)
 Area of Origin (e.g., Mexico)
 Similar items (To be discussed) (Example: If user is viewing table category, then
similar item to be shown is chairs and cushions)
 Expert Views (will be added from CMS)
 Related items
 Selling price including Currency Symbol. Prices should be displayed inclusive of
taxes however on product details page we should have the breakup information
available.
 Short Description of the product
 Product Image(s)
 Product Thumbnail(s)
 Product Video(s)
 Detailed description (collapsible)
 Specifications (Dimensions such as height, width & weight)
 Designer documents (CAD files) should be visible only to Architect and Designer.
 Special Instructions
 Specification of material
 Offer Price (Include Tax or Not)
 Only if the Offer price is less then Retail price.
o MRP\Retail Price
o Discount in % or offer.
o Total Savings in Amount
o Offer Duration or Static Text
o Add on Offer\Extra Cash Back.
 Shipping Charges If any
 Easy Instalment and No Cost EMI
 Delivery Time (Preferred date of delivery ** choice to customer)
 Add to Wish List
 Buy Now
 Add to Cart
 Add to compare.
 Display “Out of Stock” as per configuration
 Stock availability
 Viewed
 Last Bought
 Client Reviews
 Detail of the Product\Detailed Description
 Packaging information and instruction for opening a package. It is crucial for
customer to
o understand the sizing and weight of the package to validate the
feasibility of the delivery at
o doorstep.
 Technical Design of Product: - User would get options to see technical design of
the product only if they are registered with us and logged in into the portal.
 Other information is to be display on the page.
o Care and Instruction
o Warranty and Installation Guide
o Client Redressal
o Return and Cancellation policy.
11 Cart
User can click on cart to view the items in the cart.
11.1Display following information and option for each individual item.

 Product Name
 Image
 Date of delivery or Tentative date
 Added quantity.
 Amount with Currency Symbol
 Move to Wishlist.
 Remove
 Option to change quantity.
 Add as Gift > Card with message.
11.2 Display the following information in summary.
 Total No of Items
 Item Total
 Shipping and Handling Fee
 Tax should be inclusive... (but should be displayed to customer in the price)
 Amount Payable
 Discount if gift coupon applied.
12 Abandoned Cart\Failed Transaction

Item should remain in cart and user should be able to initiate the checkout again.
13 Checkout or Buy Now

Once user click on check out user will land on checkout page. Checkout page has 5 major
steps.
13.1 Sign\Sign Up\Guest Checkout

 Sign in or Signup. (refer section for customer signup)
 Users may choose to do a guest checkout.
 Apart from typical registration system should offer login via Facebook, Google and
Instagram
 Users should have an option to do a guest checkout. The user would be prompted to
enter mobile number and verify the same via OTP. We need to check the options
form legal perspective.
 Signup would present option to
o Subscribe for newsletters.
o view and agree T&C and Privacy Policy
13.2Address(s)
 Select or Enter Shipping Details.
o First Name, Last Name, Telephone to be replaced with user profile if blank in
address field.
 Select or Enter Billing Address - Billing address can be of foreign country.
 Select or Enter Shipping Address - Option to specify same as shipping.
 Based on shipping address system would check if this were eligible for delivery to a
particular pin code.
13.3Delivery Type(s)
*(To be discussed in detail requirement)
Provides option to choose from delivery options. If the delivery is free or only one option
system would just display as selected. We would need to define delivery types via
configurations screen based on zone and then link to products. System should display
packaging information on this page.
13.4 Personal Purchase or Business Purchase

User would need to provide the following if user is making a purchase for business.
 GSTIN Number (validation based ON FORMAT)
 Registered Company Name
13.5 Review Order

Review order would offer the following options.
 Apply Coupon Code

 Add Gift Message – Do we need to do this and if yes, the model that you would like
to implement this? Chargeable\Non-Chargeable.
 Delivery Comment
 Select Mode of Payment
 Option to view packaging information and policies.
 Delivery schedule date
*(To be discussed in detail requirement)
14 Payment
The system will display the following options:
 Cash on Delivery if applicable

 List of payment gateway

 EMI Option
 The application would not store credit cards and neither provide wallet facility.
 System should accept payment from foreign credit\debit card.
 The system should make use of billing address to choose between international and
local payment gateways.
 Example of screen if user selects a card payment mode.
 The system should provide multiple payment gateway options.
15 Order Confirmation
Order confirmation screen would display thank you message, order ID, amount, payment
method, message, tentative delivery date (Email, SMS, WhatsApp), icon, etc. along with
option to download copy of order. System should send a courtesy email to customer after an
order has been placed along with packaging details and instructions.
16 Inquiry
*(To be Discussed about company, sales, workflow of session depends on type.)
The user should be offered a dashboard to view the request for enquiry. The team would
review the request received and take necessary action.
17 Selling from Store\Studio\Ware House

 The inventory placed in store will be marked as Store Inventory only and
would not be available for online purchase
 Store manager would have user registered if not already and place order via
online platform for items available online
 The store manager should have option to block items for bulk purchase and
option to sell in store and warehouse items together in single invoice.
 POS system would like to integrate.
18 Invoice\Order Cancellation\Return and Refund

*(To be discussed in detail)
The complete section is very important to read and take a picture in our mind on the
process and then answer the question System would generate a sales order once
client place and order. The order will go to packaging department for processing.
18.1 When should the system generate the invoice in the process?
1. Order place.
2. Order dispatched.
3. Item delivery date.
There are multiple stages during the lifecycle of an order right from order to delivery
and refunds.
We need to define the following:

Typically, their order cancellation is divided into 2 parts: a cancellation and a
return. Till what stage in order processing cycle system has consider order
cancellation request as cancellation and not return?
System behavior for the following case

· If item is yet to be packaged
o Allow client to cancel order and process full refund.
· If item has been packaged
o Allow client to cancel order and process refund/partial refund accordingly.
· If item has been dispatched (in transit or out for delivery; picked up from us
warehouse\store)
o Clients need to raise a return & refund request.
· If item has been delivered
o Clients need to raise a return & refund request.
18.2 Cancellations
*(To be discussed in detail in requirement gathering)
· In what scenario can a client request a cancellation; and would we need to

initiate a specific approval workflow for any specific reason?
o Our client placed an order accidentally.
o Found another product which is better on our portal.
o Found another product which is better on another portal.
· Typical Cancellation workflow
o Request for cancellation within cancellation window
o System generates a cancellation request and cancels an order based on
the condition mentioned above.
 Define cancellation window to which there can be time & action sensitive.
 Cancellation should be flexible, configurable & reversal process.
 There will be cancellation charges applied.
*(To be discussed)
18.3 Return
· In what scenario can a client request a return?
o Damaged Product
o Manufacturing Defect
o Incomplete Product
o Incorrect Product
· Should we add end point delivery scenarios (To be Discussed)
· We would have incurred expenses in packaging or transportation of the product.
Would you like to charge client for the same or would you like to absorb? For
charge back specifically when the payment mode is cash on delivery?
18.4 Refund workflow:

· System opens a refund request workflow for user to choose the reason for
refund.
· System sends the workflow to admin to review and approve.
· Admin checks the eligibility.
o If the order is already delivered
o Send the person to check the issue and submit report.
o If the order is in transit coordinate with the provider for return
· If ok initiate the order pickup and generate a return request to delivery partner.
· Refund would be initiated upon receipt of returned item at warehouse\store
would we be refunding to our wallet or client’s account based on mode of
payment used?
· If not reject refund and initiate communication with client
Scenarios: - The user might have ordered items from different stores in one order which
are sourced either from multiple vendors or available at different warehouses.
Solution: -
 Create a sales order at the time user places an order.
 Order will go to the sales admin dashboard. Sales admin would
o Check the availability of stock across warehouse.
o Accept or reject the order.
o Rejection would trigger notification to user.
o Acceptance would move workflow to packaging manger queue of specific
warehouse\store where item is being stocked.
 User has ordered more than one product in one order from different vendor.
This is more from a marketplace perspective how system would display order
status?
 At each item level the system can display the status depending on the
integration with vendor and delivery partner however over all status will be
the least progressed item status.
 Order management team’s responsibility
o Update the delivery date (in case if delivery is done by platform) or
delivery processed by Vendor other than vendor integrated with
system.
o Warranty Terms
o From when would the warranty of the product will be initiated? The
date from which order is dispatched\invoiced\delivered.
Client Interface: - Refer to My Orders section for user options.
Admin Interface: - Refer to Order Management section for backend options.
19 Client Account\Dashboard
Provide “My account” option on the main screen from where they can access the following
options.
19.1 My Profile
The basic user profile would include the following:
1. First name*
2. Last name
3. Image
4. Email Id*
5. Mobile Number (Verification needed) *
6. Address(s)
7. Date of Birth
8. PAN No./GST No.
9. Gender
They user profile would provide the following options:
1. View Profile
2. Update Profile
3. Open to exercise GDPR right
4. Options to change passwords.
19.2 My Orders
The option would display the list of orders starting from the latest along with the status of the
order. The screen should provide the option to search order based on product name, order id,
SKU number, from date to date and status. The list of order would display the information like
cart with following information:
 Order ID
 Date of order
 Product Detail
 Name of the products
 Delivery date
Users would be offered options to view order details. The user would be offered options to
request cancellation or return and refund.
 Order ID
 Date of order
 Total amount
 Mode of payment
 Email ID
 Mobile Number
 Billing Details
 Shipping Details
 Products Summary (Clicking on the product name would redirect the user to product
details page)
 Supplier Name - Clicking on this will redirect the user to vendor detail page.
19.3 Wish list

There should be option to create multiple Wish list. Users can move the product from their
cart to their wish list or add any product from the product search screen to their Wish list.
Users can add ‘n’ number of products to their wish list. Wish list would provide the
following.
- Option to remove product from wish list.

- Option to Buy Product
- Option to Move Product to Cart
- Clicking on one land user on product detail page
- Products in the wish list can be very similar to card displayed in product listing page.
19.4 Shortlisting
Typically, while going through the list of items, the user likes multiple items which they want
to have a look in single window. The only feature that website now a day offers is
comparison of a limited number of items. We will create an option for user to mark item(s)
as shortlisted and open a view of shortlisted items. Users would have option to clear the
entire view or remove items from shortlisting view. This information should be maintained
for the next login as well. This kind of like is different than the normal likes which is used for
rating purposes and kind of option to choose candidate product for their selection.
19.5 Gift List *(To be discussed)

19.6 My Addresses
Option to add, edit and remove and set preferred address(s).
19.7 Notification Settings

Users can on/Off the notification which they are receiving on their email ID, mobile, app etc.
20 Operations\Dashboard (Admin)
The operation dashboard would contain the following components. Users can click on the
items to find more detailed information. Choose the ones which you feel are needed for the
Ops team to effectively carry out their work.
 Order Management
 Items to be packed.
 Items ready to be shipped.
 Items to be delivered – We can look at this in a couple of ways. What would you like
to see?
 Orders to be delivered by store\warehouse.
 Orders to be delivered by delivery partner.
 Items to be invoiced.
 Order Received – new order on which no action have been taken so far… Ideally this
will move to ready to be packed unless we implement order acceptance process.
 Delivered Order – We can look at this in couple of ways. What would you like to see?
 Order delivered by store\warehouse.
 Order delivered by delivery partner.
 Overall stock Quantity – does not make sense to me but some of the
products have.
 We can have Low Stock Items listing or numbers. If number only then user
can click on it and see the list of items falling under this category.
 Refund/Return/Cancel
 Payment
 Purchase/Dispatch/Inventory/Warehouse
 Top selling items list or category… top 5 in the list based on revenue or
number of items?
 List of purchase orders and their status
20.1 Manage Order (Admin)

Would provide the option to view list of orders, status...
Option 1:
 Display Items in different status
 Order received in the last 24 hours.
Option 2:
Create an active working space and past orders.
· Active working space to have 2 options.

o List of order which are open.
o List of orders which are cancelled and an option to acknowledge the
cancelation. This would remove the order from their list and would
only be available in past orders.
· Past Orders
Option 3:
Provide lot of filtering options. Let the user setup those filters and give a name to
report. That creates a tag and display at menu item or tab on the screen.
20.1.1 Order Filtering Options
- The system should offer based on Order Status (Pending Orders, Cancelled
Order, Past Orders...),
- Payment Status (Unpaid, Paid), Refund Status (Partial, Returned, pending...),
Shipping Status.
- (Pending, Ready for delivery, shipped...), order id, client id, name, email
address and mobile number, date and day and sales channel.
- Area wise, Category, Date range, Item wise.
20.1.2 Order Listing
The order information would display the following:
 Order Details (Order ID, Date and Time of Order, Total Quantity and Order
Amount)
 Client Details (Client Name, Email ID, Phone Number and Client ID)
 Order Status (Accepted\Rejected, Ready for Shipping, picked up for Shipping,

Shipped, Out for Delivery, Delivered\Returned, Cancellation Requested,
Cancellation Request Accepted, Cancellation Request Rejected, Refund
Initiated, Refunded)
 Payment (Paid, Cash on Delivery)
 Pickup and Delivery (From City to City)
 Product Detail? An order can be for multiple product or multiple quantity…
would you like to display anything in the list?
Option can be to hover on the product to see the details or you can click on
product id to see complete product details.
20.1.3 Export Orders

Option to handle export orders.
20.1.4 Order Creation

Agents also need ability to create Order on behalf of a customer who might be unable to
place one due to difficulty & platform issue.
20.1.5 Order Edit

Agents also need to be able to edit an order. Suppose the customer accidentally placed
order with wrong quantity or forgot to apply coupon he had or added wrong shipping
address.
20.1.6 Order fulfillment team’s responsibility *

Update the delivery, date (in case if delivery is done by platform)
20.1.7 Order Details

Order details would provide detailed information pertaining to specific order which
user can open by clicking open order id in order management screen. Few views for
your reference. The same view would be leveraged to display order details to the
client. 2 different views for client and ops team
Users can click on Payment\Item Confirmation/Return, or we can create a sequential
display instead of tabular one.
*(need to discuss flow and on sequential or tabular format)
Users can click on more under product list to view detailed breakup of amount or we
can just add one summary section to show the details info on the right just after
client details.
Options to edit details: *(Options to manage at admin level)
 shipping address
 billing address
 Client details
 Shipping and billing address editing function based on delivery channel
capability, integration, or coordination.
Order Details
 Order Details
 Customer Details
 Vendor Details
 Billing and Shipping Details
 Order Item Details with Pricing
 Payment Method
 Order Financial (Subtotal, discount, coupon, delivery charges etc.)
 Delivery tracking
20.2 Delivery and Invoice
To be discussed.
20.3 Order Fulfilment/Inventory/Warehouse

This operation will be handled by Odoo.
20.3.1 QC
· We would like to have stringent control on the quality of the product. Each product’s
quality should be verified before dispatch to customer. For every shipment that we
receive should go through QC process at our end before dispatch to customer.
· Checklist of additional items to be packaged with main product.
20.3.2 Packaging Slip
 Once an order is confirmed the packaging department needs to pick up the order
and package the items. There could be multiple packages for one single order. The
Packaging department would need to generate packaging slips based on the items
packed in one box.
 The system would generate a packaging id and assign a date and display ordered
items. Users would have the option to remove the item from slip or add it back.
 Packaging is a specialized job and would require expertise. As per conversation with
Fed-ex we need to take care of packaging.
 Option to add packaging note.
 Packaging department action can be further optimized by measuring the packaging
box.
 Eg. Consider a group of items (Dining Chair) Cups for example we need to take care.
 The system should provide an option to print packaging slips.
20.4 Raise an Enquiry
The user should be offered a dashboard to view the request for bulk order. The team would
review the request received and review the availability for the product.
- connect with client to understand the detailed requirement based on if there is a need or
not
21 Purchase Module
ERP to be used for the following.
 List of PO generated under different status.

 Option to generate PO.
 Option to cancel and revise PO.
 List of items to be received in next 24 hours – Provided user adds a tentative date
against each.
 PO item or PO for receipt of items
 List of items to be received based on various filters.
21.1 Purchase + Inventory
 Display a report of low stock items.
 The threshold would be set at each item level.
 The report would display product details, available quantity, and option to select
multiple items and generate POs
 Manage multiple warehouses
 Manage Inventory at stack and aisle level
21.2 Transaction Management (Finances)
*(To be discussed in detail in requirement gathering)
22 Notifications
Notations are divided into 3 major categories:
- On screen Notification
- Email Notification
- SMS Notification
Admin should be offered options to configure notification template for each specific usage.
The template configuration would offer the following field depending on the usage.
- Username
Users should be offered a screen.
- To enable or disable notification.

- To enable or disable notification at each specific category.
- enter notification address for each specific option.
22.1 Type of Notification
On Screen Notification - User would get a notification icon. When clicked on the same user
would be displayed notifications. The user can mark notification as read and notification
would disappear. The notification should provide options to add action buttons. Notifications
would be sorted in the order of their occurrence. Notification would include:
- Icon
- Message
Client Notification
1 Abandoned Shopping Cart Send a recovery link the following day to clients
who've added items to their shopping cart but
didn't complete checkout
2 Order Confirmed Send notification when you confirm an order
3 Order Declined Send notification when you decline an order
4 Order Shipped Send notification when you decline an order
5 Order Delivered Send notification after the order has been delivered
6 Order Cancellation Requested Send notification when a cancellation is requested
7 Cancellation Request Approved Send notification when you cancel an order
8 Cancellation Request Declined Send notification when you decline a cancellation
request
9 Order Return Requested Send notification when a return request is initiated
10 Return Request Approved Send notification containing the return ID when the
client initiates a return
11 Return Request Declined Send notification when you decline a return
12 Order Refund Initiated Send notification after you initiate a refund
Notification
1 Order Placed Send notification when an order is placed by client
2 Order Cancelled When an order is Cancelled
3 Order Returned When an order is returned
Email Notification - Email notification would require custom template.
SMS Notification - An event enabled for SMS notification in the system would trigger
notification based on user settings. There should be an option to configure SMS notification
template.
22.2 Notification Setup

We would need ability to specify email recipient and decided message format (define
template) for each format type.
23 Admin Functions
All administration screens mentioned below will provide the following option unless
specifically advised not to include any. Also, each section would have their own specific
which are documented in the section.
 Delete will be a soft delete (deactivate, nothing should get deleted from database)
 Display list of items in Grid or List View
 Option to choose the number of records to be displayed
 Option to select all and delete
 Option to import from excel file
 Option to export All or Filtered records to excel file
 Sort by recently added or modified and name
 Provide CRUD operation at record level

 Option to search based on id or name
 Option to view and manage
o Dashboard
o Orders
o Products
o Categories
o Collection
o Settings
o Reports
o Address(s)
23.1 Users
There would be different level of access given to different users based on their business
function. The overall applicable administrator will be able to manage other users and take the
following actions.
Search based on business function, user id, username.
- Change business function.

- Create\Delete\Activate\Deactivate User.
- Assign roles.
- Assign vendor(s) the user is going to manage.
23.2 Roles and Permissions

User would be able to search role based on name and recently added. Role would name, id
and name. User with access to this module will be able
- edit name, description, status of role.

- To change the permission assigned to the role.
- View list of users the role is assigned to.
23.4 Customer
Customer Listing
- Ability to filter based on name, mobile number, and email address, name and supplier
id.
- Sort by recently added name email address
- display client id, name, email, phone, last login and use, registration date....
- Possible actions edit, block, delete, activate.
Client Details
1. Client Basic Details
2. Loyalty Points
3. Addresses
4. Orders
23.5 Vendors
Vendor Listing
- Ability to filter based on name, mobile number, email address, name and supplier id
- Sort by recently added name email address.
- Ability to tag Categories and Subcategories.
- Possible actions edit, block, delete, activate.
Vendor Details
Would include Company Name, Display Name, Phone Number, Email, Display Address,
Display Address, Description, Logo, and Banner Image
24 CMS
In addition to generic option mentioned in main section the product administration will offer
the option to search product based on product name, category, subcategory and country of
origin.
24.1 Category and Subcategory

Categories represent a method to group the list of products together. Category can have
subcategory and subcategory can have further subcategories and so on. The screen would
offer the following options:
 Ability to filter based on category name or category code.

 Sort by recently added or name.
 Ability to tag product(s)
We need to capture category id (internal), name, description, image, banner image, show in
menu, show in filter, and banner text for each category.
If admin user tries to delete a category. System should put the request forward for
approval. Once approved system should remove all associations to the product and mark the
category as deleted.
One product can only be tagged to one category or subcategory at same or different level.
24.2 Specification
Specification has 3 types of elements:
 User can create a specification with just specification name and description.
 The data in specification will be organized in groups. A group can be created with group
name and description.
 Name of field and type of value it can hold.
 Every product, category and subcategory will have country of origin.
24.4 Products – (Category/Subcategory/Country of origin)

In addition to generic option mentioned in main section the product administration will offer
the option to search product based on product name, category, sub category and country of
origin.
 Screen should provide option to

 import product,
 add edit and delete product
 change product view (grid, list)

 Search on category and product details screen have the following options to enter
details.
 Generic Details (name, price, SKU, URL)
 Description and details with ability to decorate with feature like MS word.
 Images (Same Image might get tagged to more than one variant)
 Specification – take a specification from the specification configuration and tag it against
product. The moment it is tagged system should prompt user to enter details for the
product.
 Brand – would need an option to assign a brand to a product. A brand management
would be needed.
 Dimension (Weight, Height, Length with option to change measure unit)
 Option to add category would open add category popup. A product can exist in more
than one category.
 Tag: - Provides option to create and associate tag with the product.
 Option to specify if product can be returned by client.
 On Sale – Should show product on sale on the screen to end user
 Additional Items Details
We have to define additional items at product level that would be shipped along with
package. Example pillow, information manual of the product, invoice. System should create
a checklist based on configuration and provide option to modify check list items. The
checklist would be used at the time of packaging process.
- Limit on Number of Items in an Order
 Provide following configuration at item level to control the number of items can a customer
add to a single order.
1. Limited by stock
2. N number of items minimum and maximum
- Inventory Tracking
 If opted to managed inventory within system, the system should offer the feature to specify
initial quantity in product creation screen and option to increase or decrease quantity
subsequently.
There should be option to lock an inventory against a PO where there is no invoice generated yet
locked from selling.
24.4.1 Product Variant

Product can come in different variant. An example would be 3-Seater sofa available in
different color and material and prices can be very specific to variant. Attribute defines the
different variants of a product.
Example: - Combination of color and material can define variants
- Color: Black, Red, Blue

- Material: Fabric, Leather
The moment attributes are added variant are created and inventory management moves at
variant level except the details mentioned in category, tags, specification. Images added to
the main product would then have to be selected to make it specific to variant.
The system would provide the option to upload images, video, 3D models. Business can
choose want information that want to upload and showcase to customer. The videos will be
supported with Transcripts.
SEO Details will be product specific as well.
24.5 Product Collection

We would like the ability to create collections and display pages. Example Balinese design
collection. By default, one single collection would be created with no filters and that would
be default collection like “All Products”.
Product Collection Listing System should present list of collection and ability to edit
collection details and tag product, categories, subcategories.
Product Collection would have a title, URL, description and ability to create collection-based
conditions and filters. We need image and banner for collection which can be displayed to
the user.
Condition
1. A single condition
2. All the condition
3. Any of the condition
Filters
1. Price (>, <, <=, >=, = , <>)

2. Name (=, <>, starts with, ends with, contains, does not contains)
3. Brand
4. Tag
The system will show list of matching products, the moment collection condition are set.
These would the product that will be tagged to collection.
24.6 Banner Ads

Banner management screen should provide CRUD operation. The system should offer ability
to
- Configure banners based on zone

- Change the order of the banner
- Option to specify Alt text for banner
Each banner should have the following option:
- Name\Title
- Text
- Banner Image. Should define size or ability to size for different display.
- Banner Image for Mobile.
- Redirection URL
- Restrictions
o Country, State, Pin Code
o Specific Category of Users
o Logged in users could have different banner.
24.7 Featured Product

Featured products are product that would be displayed on home page when a new user
visits the web site. Admin will search for product based on name, category, sub category and
mark them as featured. (for first page and search page) How many product should admin
mark at max? What is user select more than max limit? System will not allow user to finalize
and save selection if the selected product are more than specified limit.
24.8 Configuration
To be discussed on billing and display currency Option to define a base currency. Exchange
rates are updated every day. The currencies that you add will get displayed in the home
page of your published site. Client can choose the currency in which they want to view your
products. The checkout will take place only in the base currency. Display multiple currency
on home page.
24.9 Tax Configuration
*(To be discussed with finance consultant which will be part of ERP/Odoo module)
The tax configuration will be defined at country level as taxation rules differs. A generic tax
rate can be defined at Category level however can differ from product to product. At high
level tax configuration would provide following options
 Tax Rate on Shipping (Yes\No)

 GSTIN
 Tax code \type
 Option to configure if system product price entered is inclusive of Taxes. In which tax is
calculated with the formula:
Tax = (tax rate * tax-inclusive price) / (1 + tax rate) Example: If the final tax-inclusive price is 100,
at a 10% tax rate, then the tax will be 9.09. 90.91 (Base price) + 9.09 (Tax) = 100 (Final price)
24.10 Manage Offers

Coupons, Loyalty point and Cash Back are programs to incentivize user or increase sales.
24.10.1 Coupon
The system should provide following options and also display no of times a coupon has been
used.
 Code (Auto generated coupon code)

 Name
 Description
 Discount fixed value or percentage where percentage is of
o Subtotal or
o delivery charges or
o based on past purchase amount defined in validity section
 Coupon Restricted To
o All Orders
o Client (All, Registered, Home Design)
o Shipping Zones
o Products
o Categories
o Collections
o Use of Coupon in Number (Limit, limit per day, limit per client per day, limit to per
client, unlimited)
o Validity period date and time
o Subtotal range of this order
o Delivery charges exceeds x amount
o Amount range of past x days with minimum order amount x per day starting from x
day
o Can be combined with all or selected coupons
o Coupon type (hidden, public, show in client account)
o Status
o Dependency on client type.
24.10.2 Discount
Discount would have configuration like coupon. The only difference is it will reduce the base
price of the product. Example: 10 % discount on every product on Christmas.
Discount can be added on all products.
24.10.3 Loyalty Point

Loyalty Points configuration has typically an earning criterion, redemption option, criteria,
expiry duration etc. The point configuration should be as flexible as coupon configuration is.
This would be needed in next phase not as of now.
24.11 Commission *(Depending on client type)

Commission setup enables us to act as a marketplace for other vendors. There can be tier
wise (based on volume) or generic condition Excluded for next phase.
Example: Architect can get a commission
24.12 Shipping
Shipping mode would include self-managed, or third party managed. Shipping is defined by
creating zones and creating different shipping rates for that zone based on different criteria.
24.12.1 Shipping Zone *(To be discussed)

Shipping Zone would require a title and list of regions (country, state, city, pin code) to be
included or excluded. You can create multiple regions under one shipping zone with
following information.
 Country
 State(s)
 Ship only to selected zip codes option would let the product eligible for shipment to very
specific Zip code. Zip code should have SQL like feature.
24.12.2 Shipping Rates
Shipping mode would include self-managed or third party. Shipping mode would require
following:
 Shipping Name
 Estimated Delivery Time
 Shipping Rate: - it can be a flat rate or may vary based on different parameter
 Variable Rate Configuration can be defined on parameter like order value, order quantity,
order weight and a combination of these
 Each rate would have minimum and maximum unit condition and rate applicable to
condition.
o Rate can be for overall value or on an item basis. Should be able to define multiple
conditions.
24.13 General Setup
System should have at least 2 level of validation for any change. Workflow definition
configuration option to be created.
24.13.1 Company
1. Organization Name
2. Store Configuration
3. Business Address(s)
4. Primary Email Address
5. Secondary Email Address
6. Company ID Type and Number
7. Tax ID Type and Number
24.13.2 General
1. Allow client to access their GDPR rights
2. Time Zone
3. Time Format
4. Date Format
5. Language
6. Currency
7. Currency Formatting
8. Fiscal Year
9. Weight Unit
10. Dimension Unit
11. Distance Unit
12. Terminology
24.13.3 Product Search
Show Smart Recommendation
21. Number of Product to Display

22. Out of Stock Configuration
23. Enable Serial or Batch Number Tracking
24. Show Product Specification
25. Show Sorting Options
26. Show Search Bar
24.13.4 Custom Fields Collection
1. Field Label
2. Field Type (Data Type, Control Type, Field Type)
a. Text Box (Single Line)
b. Text Box (Multi Line)
c. Alpha Only
d. Numeric
e. Alpha Numeric
f. Specific Char
g. Email
h. URL
i. Phone Number
j. Number
k. Decimal
l. Amount
m. Percentage
n. Date
3. Make this field visible to client
4. Is this an input field for client?
5. Is this field mandatory?
6. Show this field
7. Pattern for validation
24.13.5 Checkout
1. Allow Guest Check out → Yes
2. Outstanding Payment (should charge from next order or?) N/A
3. Enable Payment Options
a. Cash on Delivery
b. Pay Later N/A
c. Payment Gateway(s)
4. Cash on Delivery Setup: - Cash on delivery to be restricted to specific product, area and
amount. Also need to consider the dependencies on logistic partner
a. Area they delivery to
b. Maximum Cash we can accept etc.
5. Allow Delivery\Order Note or Additional Comment in Checkout Page (discuss option with
delivery partner and give hint to customer)
6. Show Link to Terms & Condition in Check out Page
7. Ask user to accept Terms and Condition in check out page – Yes\No.
8. If answer to above is no should system display standard message “By clicking next you are
agreeing to T&C...” - Yes\No
9. Option to configure message.
24.13.6 Order Settings

1. Delivery Mode
a. Pickup from Store
b. Pickup from Joints – option to specify joint address where user can pick product
from
c. Home Delivery
2. Delivery Partner Charges Integration API
3. Default Delivery Charges. We need to discuss this. Should be via shipping rate
configuration.
24.13.7 Order Confirmation

1. Order ID Format (Prefix, Order ID and Suffix)
2. Invoice Number Format (Prefix, Order ID and Suffix)
3. Client Support Email ID for Order Page
4. Client Support Phone Number for Order Page
24.13.8 Out of Stock Items Configuration
 Generic Configuration
o Should display out of stock items (Yes\No)
o Should display out of stock item indicator(s) on product listing page
 Labe
 Icon
 both
o Option to specify label for out of stock item
 Product level configuration
o An option to customize the display that system display information in one of the
following formats
 date (date by which item will be back)
 day (item will be back in n number of days)
 don't display
o An option to define from which date on-wards customer should get an alert based for
items expected back in stock and items back in stock. There should be configuration
similar to outlook recurring meeting invitation to control and configuration number of
notification system should generate, interval and when.
o An option to specify the date by when are we expecting an item back in our stock
(internal use only). This can be linked and extracted based on procurement process or
can be manually updated.
o An option to specify the date by when are we expecting an item back in our stock (for
customer display). There can be following option
 Same as internal date
 Days +- internal date
 specific date
o An option to specify the date from which user would see the item back in stock
information
24.14 Cancellations
Option to define cancellation reasons, activate, deactivate, eligible for client selection,
internal selection, text for client, text for internal, and define cancellation policy ( till when
can a customer cancel an order, no cancellation, changes applicable on cancellation (full,
partial, %)
24.15 Pickup from Joints\Warehouse

Would require static address configuration which has more to do be vendor setup locations
where client can pick up stuff from.
24.16 Integration API

Request and Response Configuration for third party API
 Request URL
 Parameter Configuration
 Account key
Configuration would be required for the following with ability to enable disable and add
profile
· Delivery partner
· Payment Gateway
· Social Profile
Social Share Configuration
 Can user share details on social media?

 Option to track sharing.
24.17 Message Bar
The bar would appear on the top once and once user clicks on button it will disappear. The
option would let user enable disable bar, add content, option to specify button
acknowledgment only, accept, position, theme (colour) etc.
24.18 Other Configurations

Moderation SEO
Manager
Site Map
Redirection URL
Layout Option
25 ERP integration
We are looking for Bi-directional sync ERP integration pattern to unite multiple datasets
from multiple different systems, to behave as one system while allowing them to recognize
the existence of different datasets.
We want to discuss decide and integrate following Odoo ERP apps with our Magento E-com
Portal for better integration and live data update.
 Odoo Website
o Blogs
o Live Chat
o Appointments
o Events
 Odoo Accounting
o Accounting
o Invoicing
o Expenses
o Spreadsheet BI
 Odoo Inventory
o Inventory
o Purchase
 Odoo Marketing
o Email Marketing
o SMS Marketing
o Social Marketing
o Marketing Automation
 Odoo Sales
o CRM
o Point of Sale (POS)
o Sales
 Odoo Shipping
o DHL Integration
o FedEx Integration
26 Non Functional Requirement

26.1 Auditing and Logging
 Each record creation and modification date and time along with username and id
 Delete will be a soft delete. Information will only be marked as deleted except where user
exercise its rights to be forgotten.
 System should maintain a history of changes and should offer feature to see historical
changes to data in descending chronological order.
Admin Audit log view
1. Activity Date and Time
2. Activity Info
3. Activity By
4. Activity Category
26.2 Implied requirements
 PCI Compliance
 CDN usage
 Security Plugins
 SSL usage
 Platform update mechanism
 Data Backup
 Server Security
 Payment Gateway Security
 Search engine Optimization
 Google Address Registration
 Search engine friendly URL’s
 URL rewrites by admin
 Meta-information for products, categories and content pages
 Auto-generated site map for display on site (Dynamic XML Sitemap)
END OF DOCUMENT

E-Com BRS 6.5

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

E-Com BRS 6.5

Uploaded by

Copyright:

Available Formats

Design Qandy

DesignQandy E-Com Portal

DesignQandy E-commerce Site

Version Date Prepared by Verified by

24.13.7 Order Confirmation..................................................................................................37

- Main heading before getting into the detail of that section

Category Abbreviation Description

Product Category Category or Categories refers to high-level categorization

1. Curtain raiser page

3. Product listing page

4. Product details page

2. Add to Wish list – Option to create multiple wish list.

 Abandoned cart / failed transaction.

7. Payment & Invoice

(Details in Section 16)

11. Cancel Order

13. Order history and management at backend.

6 Portal Authentication and Authorization

1. Supper User: - Development team

3. IT admin: - monitors health of application

5. Order Management Team: - responsible for order management

6.2 Customer Creation / Login / management

• Normal website customer

• Registered mobile number and password.

• The system should offer to reset their password via OTP.

6.3 Vendor Authorization

7 E-COM Portal Header and Footer

Clicking on one will land user on the Product Details Page.

o Searched for a product.

 User is from a country/area in country where we have store(s): - System would

 Add to wish list.

 Option to different images of product as thumbnails, Photo, and full screen

 Option to specify comment, store it and display to user once approved by

11.1Display following information and option for each individual item.

12 Abandoned Cart\Failed Transaction

13 Checkout or Buy Now

13.1 Sign\Sign Up\Guest Checkout

13.4 Personal Purchase or Business Purchase

13.5 Review Order

 Apply Coupon Code

 Cash on Delivery if applicable

 List of payment gateway

17 Selling from Store\Studio\Ware House

18 Invoice\Order Cancellation\Return and Refund

We need to define the following:

System behavior for the following case

· In what scenario can a client request a cancellation; and would we need to

18.4 Refund workflow:

19.3 Wish list

- Option to remove product from wish list.

19.5 Gift List *(To be discussed)

19.7 Notification Settings

20.1 Manage Order (Admin)

· Active working space to have 2 options.

 Order Status (Accepted\Rejected, Ready for Shipping, picked up for Shipping,

20.1.3 Export Orders

20.1.4 Order Creation

20.1.5 Order Edit

20.1.6 Order fulfillment team’s responsibility *

20.1.7 Order Details

20.3 Order Fulfilment/Inventory/Warehouse

 List of PO generated under different status.