/
Business Requirement Document - Phase 1 - L'azurde

Business Requirement Document - Phase 1 - L'azurde

 

 

 

 

 

L’azurde Main Website

 Client: L’azurde

 

 

Shopdev Technologies L.L.C

Office 13 & 14, Ground Floor, The Iridium Building,

Umm Suqeim Road, Al Barsha 1, Dubai, UAE

 

 


Target release

March 2023

Document status

Final

Document owner

Numan Ahmed 

Date

23rd February, 2023

Document Approvals

Approver Name

Date

Marcelo Da Silva

24th February, 2023

 Rizwan Rajpoot

2nd March, 2023

 

 

Overview

Objective of this project to make L’azurde first ever company that achieve true digital, social commerce and provide the people ease and flawless experience while browsing and shopping through L’azurde’s websites and their retail stores.

At this point of time people want something new with their digital shopping experience. With live selling, social commerce, AR and VR effects where people can try on different products, take informed decision, create customer rings, necklaces, personalize their products, send other people direct gifts will make L’azurde the most exciting company to shop from ultimately having a positive of customer retention, orders and revenue.

Personas

  • Customer

The only User of the Website is the Customer, anywhere the 'user' is mentioned in requirement, it will be the Customer being mentioned.

 

First Delivery Phase

Includes delivery of Waves , Miss L’s and L’azurde’s with following functionalities.

Requirement Category - General Requirements

 

Req. ID

Requirement

Sub-Group

Sub-Req. ID

Sub-Requirement

Priority

Req. ID

Requirement

Sub-Group

Sub-Req. ID

Sub-Requirement

Priority

NEW-001

Multi-Client

Basic Requirements

NEW-MC-001

  • Ability to generate invoices based on the Client legal entities

    • Invoices to have details according to Client’s legal terms of invoicing for e:g

      • Product Pricing

      • Taxes

      • Delivery Details

    • Invoices to be based on the Client subsidiaries

  • Ability to generate invoice for clients based on the country and their legal terms:

    • KSA

    • Egypt

    • UAE

For example: L’azurde KSA will have different Invoicing terms than L’azurde Egypt

Note: Cross border deliveries will require HS Codes for customs

Mandatory

NEW-002

Multi-Tax

Basic Requirements

NEW-MT-001

  • Ability to charge VAT on invoice based on the Store country selected.

  • On the product pages, we show the total price customer will pay (we will not add on a % for tax when they reach the checkout / basket).

  • On the basket and beyond it just shows the price minus the VAT and therefore a line item saying how much of that price is going towards tax - as per the % below

  • UAE VAT: 5%

  • Egypt VAT: 14%

  • KSA VAT: 15%

    • Formula for tax calculation

      • Assume the tax is 15% and selling  price is 2450

         Cost = X 

        Tax = Y  : 115%   

        Selling price = Z : 2450

        Then Cost X =  (2450 *100)/115 = 2130.43  ie   ( Z *100) /Y

Mandatory

OLD-004

QR Code for Electronic invoices

QR Code

NEW-EQR-001

The system requires an ability to view invoice information via QR Code scan. Following are the key requirements:

  • QR Code Integration needs to done on all the Electronic invoices across all the merchants in KSA. On QR code scan invoice related information would be displayed. Electronic Invoice should be sent when an order is delivered.

Mandatory

NEW-003

Multi-Pricing

Basic Requirements

NEW-MP-001

  • Ability for the website to show pricing based on the country selected

    • A KSA store may have different pricing than an Egypt store

    • If a user switches from one country to another, the price to reflect according to the country selected

Mandatory

NEW-004

Multi-Currency

Basic Requirements

NEW-MCY-001

  • Ability to show currency based on the country selected

    • UAE: AED

    • KSA: SAR

    • EGYPT: EGP

  • If a user switches from one country to another, the currency to reflect according to the country selected

Mandatory

NEW-005

Multi-Lingual

Basic Requirements

NEW-MLN-001

Ability for the User to change the website’s language from Arabic to English or vice versa.

  • Every region will have two versions of the website 

    • English

    • Arabic

  • Ability to have the content in Arabic for the following components

    • Website Content

      • Branding

      • Menu

      • Pages

    • Product Information Management

    • Product Listing Pages

    • Pricing

      • Numbers to be in Western Format

      • Currency to be displayed in Arabic

    • Reviews

Mandatory

NEW-007

Multiple Fonts

Basic Requirements

NEW-MFN-001

  • Ability for the website to accommodate both language fonts

    • English

    • Arabic

  • Ability to have Left to Right template alignment for Arabic Fonts and language

Mandatory

NEW-006

Multi-Frontend

Basic Requirements

NEW-MFE-001

  • Ability for the User to switch between different websites which may or may not fall under the same domain.

    • However, each website will have their own look and feel in terms of UI. However, UX will be the same. For instance, in fig-1 we can see that at the top we have GAP, OLD Navy, Banana Republic and Athleta. Simply clicking on them will take the user to that specific website. Brands to appear as categories - Brand identity of every brand will remain unique.

  • Ability to navigate between the following brands:

    • L’azurde

    • Miss’L

    • Waves

 

 

Mandatory

NEW-006

Multi-Frontend

Basic Requirements

NEW-MFE-002

  • Ability for the main L’azurde website to have all brands available on their website whether they have their own website or not.

    • So, L’azurde’s product listing pages(PLPs) will have all the products from brands under their umbrella as in Waves Jewelry and Miss L'.

    • However, L’azurde products will not be available on Waves and on Miss L'.

Mandatory

NEW-008

Responsive Design

Basic Requirements

NEW-RDN-001

  • Ability for the website to have mobile first responsive design approach.

    • Should be responsive according to the device of the customer

  • At least 3 breakpoints (desktop, tablet, mobile) supporting Chrome, Safari, Edge, Firefox & Opera

Mandatory

NEW-010

UAT/Staging  environment

Hosting

NEW-ENV-001

The system requires an environment for Feature Testing with Sample data that needs to be Prod like

Mandatory

NEW-011

Dev environment

Hosting

NEW-ENV-002

The system requires an environment with a server workspace for developers to make changes without breaking anything in a live environment.

Mandatory

NEW-012

QA environment

Hosting

NEW-ENV-003

The system requires an environment with a server with master data (or master data regularly updated) for QA testing

Mandatory

NEW-013

Production environment

Hosting

NEW-ENV-004

The system requires an environment with a server to go live.

Mandatory

NEW-014

Uptime

Hosting

NEW-HOS-001

The system requires the following ability for Uptime:

  • An Uptime (99.99%)

  • Response time SLA Dashboard including Reporting & alerts

Mandatory

NEW-029

User authentication for employees / backend users

Other

NEW-USR-001

The system requires the following ability for User Management:

  • An ability for Employees/Backend User to register into the system

  • A User authentication process for Employees

  • A User authentication process for Backend Users

Mandatory

NEW-030

User Creation -Roles & Permissions

Other

NEW-USR-002

The system requires the ability in the Control panel to Create/Read/Update/Delete of users of the system. Following are the key requirements:

  • Ability to create a Role

    • Standard Roles

    • Custom Roles

  • Ability to Create a user

  • Ability to View a user

  • Ability to update user details

  • Ability to delete user

  • Ability to assign role to a user

  • Ability to define access control for a user on different modules

Mandatory

NEW-031

Audit Trail & logging / change history

Other

NEW-AUD-001

The system requires an ability to track and record every change log that occurs in the system. Following are the key requirements:

  • An ability to store change log in the system log based on the following but not limited to:

    • Order changes

    • Product Catalog changes

    • Inventory changes

    • CMS changes

    • Returns changes

    • User management changes

    • Promotion changes

*More actions can be identified and defined at a later time

Mandatory

NEW-032

Localization & Time zones

Other

NEW-LOC-001

The system requires an ability to configure and run business rules according to the Location and It’s time zone. Following could be considered:

  • Promotions to be set and run based on the Country time zone

  • Invoicing to be done based on the time zone of the Country ordered

Mandatory

 

NEW-033

Analytics

Reporting

NEW-ANL-001

The system requires an ability to provide analytics dashboard (through BI) in the system. Following are the key requirements:

  • Ability to pull all the information from the systems mentioned below and store it in a data lake(Data warehouse)

  • Reporting to be done around the following metrics with the system they reside in, and sync them with the Data Warehouse:

    • Order Number

      • Flow OMS/CEGID

    • Invoice Number

      • Flow OMS/CEGID

    • SKU ID

      • PIM - Plytix

    • Store ID

      • Flow OMS/CEGID

    • Employee ID

      • Flow OMS/CEGID

    • Date

      • Flow OMS/BigCommerce/CEGID

    • Time

      • Flow OMS/BigCommerce/CEGID

    • Brand

      • PIM - Plytix

    • Collection

      • PIM - Plytix

    • Listed Price

      • CEGID/BigCommerce

    • Selling Price

      • BigCommerce/Flow OMS/CEGID

    • Items Cost

      • PIM - Plytix

    • Main Category

      • PIM - Plytix

    • Type

      • PIM - Plytix

    • Metal Type

      • PIM - Plytix

    • Metal Karat Only

      • PIM - Plytix

    • Metal Color Only

      • PIM - Plytix

    • Diamond

      • PIM - Plytix

    • Diamond Carat

      • PIM - Plytix

    • Diamond Shape

      • PIM - Plytix

    • Stone

      • PIM - Plytix

    • Stone Carat

      • PIM - Plytix

    • Stone Color

      • PIM - Plytix

    • Stone Shape

      • PIM - Plytix

    • Payment Method

      • Flow OMS/BigCommerce

    • Delivery Method

      • Flow OMS/BigCommerce

    • Repeat Customer

      • Flow OMS/BigCommerce/Exponea

    • Single Channel / Cross Channel

      • Flow OMS/BigCommerce/Exponea

    • How many purchases has this customer done

      • Flow OMS

    • Customer ID

      • Flow OMS/BigCommerce/Exponea

    • Order Status

      • Flow OMS

    • Promo Code Value

      • Flow OMS/BigCommerce

    • Date Processed

      • Flow OMS/BigCommerce

    • Date Shipped

      • Flow OMS/BigCommerce

    • Date Delivered

      • Flow OMS/BigCommerce

    • Mobile / PC / Tablet

      • BigCommerce

    • Fulfilment Location

      • Flow OMS/CEGID

    • Discontinued

      • PIM - Plytix

    • Returned

      • Flow OMS

    • Returned Reason Code

      • FLOW OMS/BigCommerce My Account

    • Cancellation

      • Flow OMS

    • Cancellation Reason Code

      • Flow OMS

    • Country

      • Flow OMS/BigCommerce

    • Governate

      • Flow OMS/BigCommerce/

    • City

      • Flow OMS/BigCommerce

    • Area within city

      • Flow OMS/BigCommerce

  • Ability to export information based on date ranges

Mandatory

NEW-034

Supports Report delivery format

Reporting

NEW-ANL-003

The system requires an ability to support the reporting in the following report delivery formats:

  • XLS

  • CSV

  • PDF

Mandatory

NEW-035

Reports by channel /Site

Reporting

NEW-ANL-004

The system requires an ability to provide reports based on the following:

  • Reporting by Site

    • An ability to provide reports for Channel/Site based on the following:

      • Report by Country

      • Report by Brand

Mandatory

NEW-036

Standard Operational reports

Reporting

NEW-ANL-005

The system requires an ability to generate reports based on Standard Operational Metrics. Common examples could include:

  • Ability to generate Operations reports by selecting key Operational Metrics and KPIs

    • Inventory Reports

    • Inventory Ageing Reports

      • Ability to store history of Product changes in the Inventory

      • Ability to preserve stock history of Products in the inventory

      • Ability to export Inventory History

      • Ability to perform Inventory audit trail

      • Ability to view all transfer history in the Inventory

    • Ageing SKUs Reports

    • SLA reports

More out of the box reports can be identified at a later time

Mandatory

NEW-037

Order Analysis

Reporting

NEW-ANL-006

The system requires an ability to generate reports based on Order Metrics. Common examples could include:

  • Ability to generate Order Analysis reports by selecting key Order and Sales Metrics or KPIs like the following:

    • Orders by state

    • Orders by Site

    • Orders by Country

    • Sales report by Orders

      *Above Metrics are not final and can be updated at a later time (Full list TBD)

Mandatory

NEW-038

Customer Analysis

Reporting

NEW-ANL-007

The system requires an ability to generate reports based on Customer Analysis Metrics. Common examples could include:

  • Ability to generate Customer Analysis reports by selecting key Customer Metrics or KPIs like the following:

    • Recently Joined Customers

    • Converted Customers

    • Customers by Location

    • Customer Lifetime Value

    • Customer Detail

    • Customer Reports based on RFM
      *Above Metrics are not final and can be updated at a later time (Full list TBD)

Mandatory

NEW-039

Catalog & product reports

Reporting

NEW-ANL-008

The system requires an ability to generate reports based on Catalog and Product Metrics. Common examples could include:

  • Best Selling Products

  • Frequently Bought Together

  • Least bough product

  • Product trends
    *Above Metrics are not final and can be updated at a later time (Full list TBD)

Mandatory

NEW-040

Business performance reporting 

Reporting

NEW-ANL-009

The system requires an ability to generate reports based on Business Performance or Sales Metrics. Common examples could include:

  • Ability to generate Sales reports by selecting key Sales Metrics and KPIs like the following:

    • Sales report by Orders

    • Sales report by Items

    • Sales report by time

    • Sales reports by area

    • Monthly Recurring Revenue

    • Bounce Rate

    • Churn Rate

      *Above Metrics are not final and can be updated at a later time (Full list TBD)

Mandatory

NEW-041

Tab navigation

Navigation

NEW-NAV-001

The system requires an ability to provide Tab navigation on the website for accessibility. Following are the key requirements:

  • An ability to use Tab navigation, navigate through site without using mouse with Tab for people with disability

Secondary

OLD-005

Product Reviews and Ratings.

Order History

NEW-RAT-001

The system requires an ability for the Customer to provide Product review and rating for Orders completed. Following are the key requirements:

  • User will be able to provide product reviews on the PDP page of the product. Product review will include 5 star rating of the product with a written review and one image as-well.

  • Product reviews should only be able to be written once logged in - the user must be logged in.  

  • Ability to send the notification to write the review after 30 days of delivery status confirmed.

In their My Account there will then be a section called “My Product Reviews”.

Mandatory

 

Requirement Category - Customer Account Management

Req. ID

Requirement

Sub-Group

Sub-Req. ID

Sub-Requirement

Priority

Req. ID

Requirement

Sub-Group

Sub-Req. ID

Sub-Requirement

Priority

NEW-077

One Account across all devices

Account creation

NEW-ACC-001

The system requires an ability to have a Unified Account system on the L’azurde Website. Following are the key requirements:

  • Ability to have a same login for all the L’azurde brands

  • Moreover, user would have the same account for logging into any websites that are under L’azurde’s umbrella in the same region

  • Account identifiers :

    • Email Address

    • Mobile Phone

  • So, user will be able to use mobile number with password or email address with password to login to their account.

  • Ability for the user to use social sign in option using following social logins

    • Google

    • Facebook

Note: The Common login will only be valid in the same region, for example One login would only work for UAE region, For KSA Region the user would have a separate account.

Mandatory

NEW-078

Account creation button / link

Account creation

NEW-ACC-002

The system requires an ability to create Account on the L’azurde website. Following are the key requirements:

  • An ability to create an account on the L’azurde website through the My Account Sidebar

Mandatory

NEW-079

Create account before ordering

Account creation

NEW-ACC-003

The system requires an ability to create an Account on the L’azurde website before ordering. Following are the key requirements:

  • An ability to create an account on the Cart (Bag) detail page through the Sign up button

    • Provide information of 10% discount for Member Signup ‘Sign Up And Get 10% Off’

Mandatory

NEW-080

Account creation during order

Account creation

NEW-ACC-004

The system requires an ability to create an Account on the L’azurde website at the time of Order creation. Following are the key requirements:

  • An ability to create an account on the Checkout page through the Sign up button

    • Provide information of 10% discount for Member Signup ‘Sign Up And Get 10% Off’

Mandatory

NEW-081

Account Creation Failure

Account creation

NEW-ACC-005

The system requires an ability to display error on Account Creation failure. Following are the key requirements:

  • An ability to display an error message with error reason if the system is unable to create an account

  • An ability to highlight the fields with error

Mandatory

NEW-085

Validate Information

Account creation

NEW-ACC-006

The system requires an ability to validate account information provided by the Customer at Account Creation. Following are the key requirements:

  • Information should be validated to format as per data type (email, name, mobile number) and if incorrect should get an error message to rectify it.

  • If the Email or Phone Number already exists, notify the user of account already exists and allow them to reset their password incase of forgot password

 

NEW-082

OTP Verification

Account creation

NEW-ACC-007

The system requires an ability for the user to provide verification through OTP Code. Following are the key requirements:

  • An ability to keep Phone number as Primary Username

  • An ability to Provide OTP Verification through SMS Code

Secondary

NEW-083

Email Verification

Account creation

NEW-ACC-008

The system requires an ability for the user to provide verification through Email link. Following are the key requirements:

  • An ability to keep Email as Primary Username

  • An ability to Provide Verification through Email Link

Mandatory

NEW-084

Validation expiration

Account creation

NEW-ACC-009

The system requires an ability for the Verification Code or Links to expire. Following are the key requirements:

  • An ability for the Email Verification link to expire after specified time

  • An Ability for the OTP SMS Code to expire after specified time.

  • An ability to specify Expiration time

Mandatory

NEW-086

Existing Magento Accounts

Existing Accounts

NEW-ACC-010

The system requires an ability to keep existing customer accounts from the Magento system in the new system. Following are the key requirements:

  • Customer can sign in using current credentials if already registered as a customer and see personal information.

Mandatory

NEW-087

Existing website History Transfer

Existing Accounts

NEW-ACC-011

The system requires an ability to retain their Information when using old account in the new system. Following are the key requirements:

  • Existing Magento Customer to retain their Account information in the system with the following:

    • All Orders

      • Order History

      • Current Orders

    • Wishlist

    • Items in Basket

    • Reviews

Secondary

NEW-088

Manage profile information

Settings

NEW-ACC-012

The system requires an ability for the User to manage their Profile Information. Following are the key requirements:

  • An ability to add/update Profile information

    • Profile Picture

    • Personal Information

    • Address

    • Add/Remove Payment Methods

  • The User will not be able to update their Username info

Mandatory

NEW-089

Communication preferences

Settings

NEW-ACC-013

The system requires an ability for the User to manage their Communication Preferences. Following are the key requirements:

  • An ability to select/unselect their notification Preferences

Mandatory

NEW-090

Clearly visible Login button / link

Login

NEW-LOG-001

The system requires an ability for the User to login to the website. Following are the key requirements:

  • Ability for the User to login through the Main Website and My Account sidebar

Mandatory

NEW-091

Login during browsing journey

Login

NEW-LOG-002

The system requires an ability for the User to login to the website. Following are the key requirements:

  • Ability for the user to login while browsing at any page through the My Account sidebar or button

Mandatory

NEW-092

Login during purchase journey

Login

NEW-LOG-003

The system requires an ability for the User to login to the website. Following are the key requirements:

  • Ability for the user to login while navigating through the Cart (Shopping bag)

    • The user to be shown login or sign up links on the Cart page

Mandatory

NEW-093

Login failure error message

Login

NEW-LOG-004

The system requires an ability to display error message on login failure. Following are the key requirements:

  • Error message on Incorrect/Invalid Email

  • Error message on Incorrect Password

Mandatory

NEW-094

Automatic login until session expiry

Login

NEW-LOG-005

The system requires an ability to keep the user logged in automatically on the website. Following are the key requirements:

  • An ability for the logged in user through email/phone to stay logged in or log in automatically until the session expires

  • An ability to set configuration rules for session expiry globally

Mandatory

NEW-095,
NEW-096,
NEW-097,
NEW-098,
NEW-099

Social Login

Login

NEW-LOG-006

The system requires an ability for the user to login through social platforms. Following are the key requirements:

  • Ability to login with Facebook and automatically create an account with this corresponding email after authentication of Facebook account.

  • Ability to login with Google and automatically create an account with this corresponding email after authentication of Facebook account.

  • The authentication should be done for 1st time only, then should be logged into my account directly.

  • In case the social login email already has an account:

    • Ability to merge the existing account with social login

    • Considering existing account, sharing the same Email ID with Facebook or Google, user will be allowed to link multiple Social Accounts to sharing the same Email ID. Customer should be able to view linked Social Media Accounts (Google, Facebook). It should be prevented that in the backend multiple accounts are created when the user uses Social Logins with same Email Address.

  • Note: Unlinking accounts not supported for MVP. Users could unlink from Facebook/Google Settings

Mandatory

NEW-101

Option to log out

Log Out

NEW-LOG-007

The system requires an ability for the user to log out of their account. Following are the key requirements:

  • An ability to log out of the logged in account for the following

    • Email

    • Phone Number

    • Social Login

Mandatory

NEW-102
NEW-103
NEW-104
NEW-105
NEW-106
NEW-107
NEW-108

Reset Password

Password Recovery

NEW-LOG-008

The system requires an ability for the user to recover their password in case of error/forgot password. Following are the key requirements:

  • An ability to have forgot password button on the login page

  • Users created with Social Accounts, should also be allowed to create password, using the “Password Recovery” flow.

    • Email for account recovery will be sent to the Email ID of the Social Account.

  • An ability to verify account through the account identifiers

    • Email

    • Phone Number

  • An ability to send password reset link to the registered account identifiers

    • Email

    • Phone Number

  • An ability for the Reset password link to expire after specified time

  • An ability to show password reset success/error message

    • An ability to send notification to the User’s registered Email and/or Phone Number for password reset

  • An ability to require customer to login again with the new credentials

Mandatory

NEW-109
NEW-110
NEW-111
NEW-112
NEW-113
NEW-114
NEW-115

Account Information Update

Account Update

NEW-ACC-014

The system requires an ability for the user to update their Account information. Following are the key requirements:

  • An ability for the user to update the following information of their account:

    • Update First Name

    • Update Last Name

    • Update Email Address

    • Update Password

    • Update Mobile Number

    • Update my favorite city

    • Update communication preferences

  • An ability to require user to provide password before making changes to any of the following:

    • Update First Name

    • Update Last Name

    • Update Password

    • Update my favorite city

    • Update communication preferences

  • An ability for the user to authenticate via registered email to update email

  • An ability for the user to authenticate via registered phone number to update phone number

Mandatory

NEW-116
NEW-117

Add/Update Payment Methods

Payment Methods

NEW-ACC-015

The system requires an ability for the user to View/Add/Update their payment methods. Following are the key requirements:

  • Ability to View Saved payment methods

  • Ability to set a default payment method

  • Ability to Add payment method

  • Ability to edit/delete a payment method

Mandatory

NEW-118
NEW-119
NEW-120
NEW-121
NEW-122
NEW-123
NEW-124
NEW-125
NEW-126
NEW-127
NEW-128

 

Manage Address on Account

Address Management

NEW-ACC-016

The system requires an ability for the user to do Address management on their account. Following are the key requirements:

  • An ability to add address to the account

    • An ability to add multiple addresses to the account

  • An ability to select default address for delivery

    • An ability to update change or amend default address for delivery

  • An ability to select default billing address

    • An ability to update change or amend default billing address

  • An ability to categorize address as Home or office etc. (Secondary)

    • An ability to update the categorization of the address. (secondary)

  • An ability to update all the registered addresses

    • An ability to delete an address from existing address

      • Deleting an address should not impact any order history and the information should remain

  • An ability to set minimum one default address

    • User cannot delete a default address unless they have set another one

  • An ability to autocomplete Delivery Address (Powered by Google) while inputting delivery address. (For KSA)

Mandatory

NEW-100

Opt-in / opt-out notification for marketing

Notifications

NEW-NOT-001

The system requires an ability for the user to have preference for Marketing notifications. Following are the key requirements:

  • An ability to opt in for Marketing notification

  • An ability to opt out of Marketing notifications

Mandatory

NEW-129
NEW-130
NEW-131
NEW-132
NEW-133
NEW-136
NEW-138

Order Details on Account Management

Order History

NEW-ACC-017

The system requires an ability for the user to view their order history. Following are the key requirements:

  • An ability to view Orders list in a listing page

    • Ability to view orders by the following parameters

      • By Order Period

      • By Order Status

  • An ability to view Order details on the listing page with the following

    • Order Status

    • Payment information

  • An ability to view Order information in a detailed page

  • An ability to view Order status for all orders including Cancelled and Returned (including Partial)

  • Ability to view invoices for Order detail

    • An ability to download sales invoices for the record

  • An ability to view all orders placed through any device Email or Mobile App (Secondary)

  • An ability to search Orders in the Orders list

    • Via Order Number

    • Ability to search invoices

 

Mandatory

NEW-139
NEW-140
NEW-141
NEW-142
NEW-143

Requesting for Order Cancellation

Order Cancellation

NEW-ACC-018

The system requires an ability for the user to request cancellation of an order. Following are the key requirements:

  • An ability to display information on how the customer can request a cancellation of the order

    • An ability to request Full cancellation or Partial Cancellation (More details on the Order Flow requirements)

  • An ability to have CTA to call customer support through the Order detail

  • An ability for the customer to receive email confirmation of the Order Cancellation

  • An ability to get automatic refund on order cancellation

    • Automatic process depending on Payment method

  • Order cancellation status to reflect on the Order detail.

    • Show detail if the Order was fully cancelled or Partially

Mandatory

NEW-144
NEW-145
NEW-146
NEW-147

Initiating Account Deactivating request

Account Deactivation

NEW-ACC-019

The system requires an ability for the User to request account deactivation on My Account. Following are the key requirements:

  • An ability to request Account deactivation in My Account section

    • Account deactivation request to be sent to back office to view and execute the account deactivation request

  • Account Deactivation request will only be proceeded after Password verification

  • On Account deactivation, Personal information to be deleted of the user like the following:

    • Email Address

    • Phone Number

    • Payment Information

  • An ability to preserve Order history of the customer even after Account deactivation

Mandatory

NEW-148
NEW-149
NEW-150

Link Social Accounts

Facebook

NEW-ACC-020

The system requires an ability to link social profile to the user’s account. Following are the key requirements:

  • An ability to link following social profiles to their account

    • Facebook

    • Instagram

  • An ability to authorize connection to the account after verification

  • An ability to post content on the connected profiles from the website.

Mandatory

NEW-151

Logic Navigation

Navigation

NEW-ACC-021

The system requires an ability to have a logical navigation on the My Account section. Following are the key requirements:

  • Ability to navigate to my account pages through breadcrumbs (See UI designs)

Mandatory

 

Requirement Category - Website Homepage

Req. ID

Requirement

Sub-Group

Sub-Req. ID

Sub-Requirement

Priority

Req. ID

Requirement

Sub-Group

Sub-Req. ID

Sub-Requirement

Priority

NEW-152

Navigation

Homepage General

NEW-HPG-001

The system requires an ability to have logical navigation on the Homepage. Following are the key requirements:

  • An ability to navigate to different sections and pages through the homepage like the following:

    • Key listing pages

    • Categories

    • Website Static Pages

  • Ability to navigate to different brands under the L’azurde through the homepage

    • Ability for the User to switch between different websites which may or may not fall under the same domain.

      • However, each website will have their own look and feel in terms of UI. However, UX will be the same. For instance, in fig-1 we can see that at the top we have GAP, OLD Navy, Banana Republic and Athleta. Simply clicking on them will take the user to that specific website. Brands to appear as categories - Brand identity of every brand will remain unique.

    • Ability to navigate between the following brands:

      • L’azurde

      • Miss’L

      • Waves

Mandatory

NEW-153
NEW-154
NEW-155
NEW-156
NEW-157
NEW-158
NEW-159
NEW-160
NEW-161
NEW-162
NEW-163
NEW-164

Store Elements on Homepage

Homepage Elements

NEW-HPG-002

The system requires an ability to have store related elements on the homepage. Following are the key requirements:

  • An ability to have top banner on the Homepage with a promotion or an alert with CTA taking to the relevant detail page.

    • Display Promotion floating banners (e.g. Get 15% off)

  • An ability to show collection banners on the homepage

    • Single Collection banners

    • Double Collection banners

    • Multiple slot banners

  • An ability to display Promotional banners with CTA taking to the relevant detail page

  • An ability to display Carousel for New Arrivals

  • An ability to display featured products via widgets or sliders on the homepage

    • Feature products sequence to be changeable

    • Clicking on the featured product will take the user to the Product Detail Page of the Product

  • An ability to display Popular items section on the Homepage

  • An ability to show the live selling section on the Homepage

    • Able to view previous live selling shows and archive after n months

    • CTA to take user to the live selling page

  • Show the Press release section on the homepage

  • Show the Store locator link on the Homepage

    • CTA to take user to the Store Locator

  • Ability to show the Sale widget on the Homepage

  • Ability to display Product offerings on the Homepage

    • Should be able to browse all product offerings category-wise according to the active Taxonomy configured for the current: Channel / Market / Brand. Should be able to navigate to key offers currently active on the website through the homepage.

       

Note: See UI Designs for more details and references

Mandatory

NEW-165

Categories

Navigation

NEW-HPG-003

The system requires an ability to navigate through categories on the homepage. Following are the key requirements:

  • An ability to navigate to any active category page during the browsing journey

     

Mandatory

NEW-166
NEW-167

 

New In and Sales offer

Main Navigation

NEW-HPG-004

The system requires the capability to show ‘New in’ on the category bar on the homepage. Following are the key requirements:

  • An ability for main navigation to include New In showing links to new products under each subcategory

  • An ability for main navigation to include Sale showing links to products on sale under each subcategory

     

     

Mandatory

NEW-168
NEW-169

 

Seasonal Campaign Banner on homepage

Seasonal Campaign

NEW-HPG-005

The system requires an ability to navigate show season campaign banners on the homepage. Following are the key requirements:

  • An ability to show banner for Seasonal Campaigns on the Homepage

    • Banner shown on the homepage taking the user to the Listing Page of the Seasonal campaign

  • An ability to show different Banners per brand and screen size

    • Banner to be displayed according to the design for each brand and screen size.

       

       

Mandatory

 

Requirement Category - Website Dynamic Page

Req. ID

Requirement

Sub-Group

Sub-Req. ID

Sub-Requirement

Priority

Req. ID

Requirement

Sub-Group

Sub-Req. ID

Sub-Requirement

Priority

NEW-170

Category Page

Category Page

NEW-WDP-001

The system requires an ability to show Category Page on the website. Following are the Key Requirements:

  • An ability to display a dynamic page for the Category page

    • Ability to display different products under the Product categories and taking to the PDP of the Products

 

Mandatory

NEW-171

Campaign Page

Campaign Page

NEW-WDP-002

The system requires an ability to show Campaign Pages on the website. Following are the Key Requirements:

  • An ability to display dynamic pages for the Campaigns

    • Ability to display different products under the Campaigns and taking to the PDP of the Products

 

Mandatory

NEW-172
NEW-173

NEW-174

 

Store List

Store Locator

NEW-WDP-003

The system requires an ability to show the Store list on the store locator. Following are the key requirements:

  • An ability to display stores list on the Store locator

    • Should be able to view the list of stores (configurable) for each brand / Market.

  • An ability to show store list details on the store selection

    • Store Details:
      a. Store Location Name

      b. Address

      c. Working Hours

      d. Email Address

      e. Location on the Map

  • An ability for the admin to be allowed to add / edit / remove Stores from

    the Admin panel.

     

Mandatory

NEW-175
NEW-176
NEW-177

FAQ Pages

FAQ

NEW-WDP-004

The system requires an ability to do FAQ page management. Following are the key requirements:

  • An ability to display FAQ link on the Webpage

  • An ability to navigate to the FAQ pages

  • An ability for the admin to create, update and delete FAQ and help pages.

    • An ability to add imagery, audio, video and media content into the FAQ and help pages

    • An ability to to setup SEO URLs and meta tags for FAQ and help pages.

       

Mandatory

NEW-178

Collections Management

Collections

NEW-WDP-005

The system requires an ability to manage collections. Following are the key requirements:

  • An ability to create and manage collections

    • Grouping products for marketing purposes

  • An ability to define collections details

    • Configured for each level: Brand / Country Site / Channel

    • Define collection name

    • Define slug

    • Define imagery (banners)

    • Assign products to collection

    • Configure T&C

    • Configure Start date & end date

  • An ability to have landing pages with templates to be used during new collection launches, and promotion periods.

Mandatory

 

Requirement Category - Website Static Pages

Req. ID

Requirement

Sub-Group

Sub-Req. ID

Sub-Requirement

Priority

Req. ID

Requirement

Sub-Group

Sub-Req. ID

Sub-Requirement

Priority

NEW-179
NEW-180

NEW-181

NEW-182

 

Landing Page Management

General

NEW-WSP-001

The system requires an ability to manage static pages on the website. Following are the key requirements:

  • An ability to create, update and delete static content pages (e.g. T&C / Privacy Policy).

  • An ability to add imagery, audio, video and media content into the static content pages.

  • An ability to to setup SEO URLs and meta tags for static content pages.

Note: Static page should be in accordance to the UI designs provided

Mandatory

NEW-183

Show Breadcrumb Navigation on Static Pages

General

NEW-WSP-002

The system requires an ability to have navigation on the static pages. Following are the key requirements:

  • An ability to show Breadcrumb Navigation on Static Pages to make navigation easier for the user

     

Mandatory

NEW-185
NEW-186
NEW-187

Error Handling

Error Pages

NEW-WSP-003

The system requires an ability for error handling in case of error on the website. Following are the key requirements:

  • An ability to show 404 Landing page in case of unavailable pages, page doesn’t exist or access failure.

  • An ability to show error page to handle generic technical errors (Microservice down etc.)

  • An ability to show outage page during outages

    • Traffic to redirect to this page during technical maintenance, system upgrades, release in progress

 

Mandatory

NEW-188
NEW-189
NEW-190
NEW-191
NEW-192

L’azurde Static Pages

L’azurde pages

NEW-WSP-004

The system requires an ability to show static pages related to L’azurde on the website. Following are the key requirements:

  • An ability to create the following static pages with details:

    • About us

      • Details about L’azurde and their business

    • Contact Form

      • Contact form with information to contact L’azurde stores

    • Privacy Policy

      • Details about L’azurde’s privacy policy

    • Terms and Conditions (T&C)

      • Page stating terms and conditions of L’azurde

    • Order & Returns

      • Static page related to Order and Returns

    • Governance and Investor Relations

      • Details about effective communication between the company and investors. with the following pages and stock information coming from Euroland in the following pages

        • IR Home Page

        • Fact Sheet

        • Prospectus

        • Financial Information

        • Stock Information

        • Dividends

        • Announcements

        • Financial Calendar

        • Email Subscription Center

        • Corporate Governance

        • Contact IR

        • In Press



           

Mandatory

NEW-193

Custom Pages

L’azurde Pages

NEW-WSP-005

The system requires an ability to create Custom pages. Following are the Key requirements:

  • An ability to create static custom pages on the website

    • Generic Static Pages based on template (marketing purpose). E.g. Lab Grown Diamond educational page

       

Mandatory

 

Requirement Category - Global Search

Req. ID

Requirement

Sub-Group

Sub-Req. ID

Sub-Requirement

Priority

Req. ID

Requirement

Sub-Group

Sub-Req. ID

Sub-Requirement

Priority

NEW-194
NEW-195
NEW-196
NEW-197
NEW-198

Search preview section

Search Preview

NEW-SRC-001

The system requires an ability to have search preview on the website. Following are the key requirements:

  • An ability to show search preview when the user starts typing or click on the search bar

  • An ability to show search suggestions when the user is on the search bar like the following

    • Products

    • Categories

    • Promotions

  • An ability to provide Auto-correction on the search bar

    • Auto complete, Suggestion for corrections / prevent misspelling

  • An ability to show Categories and Promotion in the search preview while user is on the search bar

  • An ability to show ‘Did you mean?’ while user is typing on the search bar

    • Get suggestions with closest match “Did you mean”

Mandatory

NEW-199
NEW-200
NEW-201
NEW-202
NEW-203

Showing Search Results

Search Result Page

NEW-SRC-002

The system requires an ability to show search result when user performs a search. Following are the key requirements:

  • An ability to take user to the search result page when the user performs a search

  • An ability to show ‘No Results Found’ in case the search doesn’t match any product

  • An ability to apply filters or sorting on the Search results page.

  • An ability to Define relevance criteria for search

    • Search results should match the relevance criteria defined by business

  • An ability to navigate through search results with Breadcrumb navigation

    • Just simple information: Homepage -> Search Results (not a breadcrumb for every search keyword!)

       

Mandatory

NEW-204
NEW-205
NEW-206
NEW-207
NEW-208

Configuring Search Settings

Search Setting

NEW-SRC-003

The system requires an ability define and configure search settings. Following are the key requirements:

  • Sorting Rules

    • An ability to define the sorting rules for a search result

  • Sequencing rules

    • An ability to define the sequencing rules for a search result

  • Exact Match Result

    • An ability to navigate directly to the Product detail page in case of an exact match result

  • Landing Page

    • An ability to assign a landing page to a search term

  • Synonyms

    • An ability to provide suggestions with synonyms

       

Mandatory

NEW-209
NEW-210
NEW-211
NEW-212

Configuring Search Settings

Search Setting

NEW-SRC-004

The system requires an ability define and configure search settings. Following are the key requirements:

  • Configure product per keyword

    • An ability to configure alternate products per keyword.

  • Configure products per product

    • An ability to configure alternate products per product

    • To show alternate products as well as the correct product

    • Showing alternate products in case of no availability of the configured product

  • Phrase Suggestion

    • Searching for product can also show alternative product

  • Search Groups

    • Configuring search groups for search settings

       

       

       

Secondary

NEW-213
NEW-214
NEW-215

Information on No Results Page

No Results Page

NEW-SRC-005

The system requires an ability to show information on a No Results page. Following are the key requirements:

  • Show top sellers

    • In case there are no results that match the search, the system should show top seller products as recommendations

  • Customers also Bought

    • In case there are no results that match the search, the system should also show Links to key categories or customers also bought section

  • Comment function

    • On the no results page, an ability for the customer to leave comments on what they were looking for

       

       

       

Mandatory

NEW-216

Detailed search analytics

Search Analytics

NEW-SRC-006

The system requires an ability to provide search analytics based on search. Following are the key requirements:

  • See detailed search analytics, reporting and conversion Include/exclude products or pages from search

Mandatory

 

Requirement Category - Website Headers

Req. ID

Requirement

Sub-Group

Sub-Req. ID

Sub-Requirement

Priority

Req. ID

Requirement

Sub-Group

Sub-Req. ID

Sub-Requirement

Priority

NEW-217
NEW-218
NEW-219
NEW-221
NEW-222
NEW-223
NEW-224
NEW-225

Navigation and elements on Header

Header

NEW-WHD-001

The system requires an ability to have headers configured on the website based on the Brand. Following are the key requirements:

  • Primary Navigation

    • An ability to have primary navigation bar on the header.

      • Primary navigation bar to have flyout menu

  • Taxonomy

    • An ability to have different L1 & L2 Navigation based on Taxonomy

      • Taxonomy to be configurable for each Brand and Country site

  • Banners

    • An ability to show banners on the Header

      • Banners to be shown based on each brand and country site

      • Banners to be shown as per UI Design

  • Checkout

    • An ability to have a simplified header for Checkout

      • As per UI design

  • Thank you page

    • An ability to have simplified headed for thank you page

      • As per UI design

  • Standard Header

    • An ability to have standard header across all pages on the website other than Checkout and Thank you page

  • Menu Expand Animation

    • An ability for the menu expand to have animations.

      • Menu to be expanded on hover or tap

      • As per UI design

  • Country Switch

    • An ability to allow the user to switch to a different country through the Country switch icon on the header bar

      • On country switch, the website will change according to the country selected

  • Language Switch

    • An ability to allow the user to switch between Languages (English and Arabic) through the Language switch icon on the header bar.

      • On language switch, the content of the website will change from English to Arabic and Vice versa based on the language selected

Mandatory

NEW-226
NEW-227
NEW-228
NEW-229
NEW-230
NEW-231

Elements on the Mini Cart

Mini Cart

NEW-WHD-002

The system requires an ability to show Mini cart on the Header of the website. Following are the key requirements:

  • Item List

    • An ability to see a list of item currently in the cart added by the user

  • Mini Cart View

    • An ability to show the cart in the following views:

      • Collapsed View

      • Expanded View

        • Expanded view to provide the details like
          a. Product name
          b. For slow connections, image loader will be shown to the user (while loading the image assets)
          c. Quantity
          d. Size/Color
          e. Total of Cart

  • Expand View on Adding Items

    • An ability to show expanded view when a User adds item to the cart

  • Item Count Badge

    • On collapsed view, the cart icon should show Badge Item count.

  • Checkout Button

    • Be able to proceed to cart page from mini-cart (cart is always the first step of the checkout)

Mandatory

 

Requirement Category - Website Footer

Req. ID

Requirement

Sub-Group

Sub-Req. ID

Sub-Requirement

Priority

Req. ID

Requirement

Sub-Group

Sub-Req. ID

Sub-Requirement

Priority

NEW-232

NEW-233

 

Actions on the Website Footer

Footer Elements

NEW-WFR-001

The system requires an ability to have element on the footer of the website. Following are the key requirements:

  • Static Pages

    • An ability to display the L’azurde static pages as defined on the footer with the links taking them to to the static pages. Static pages may include:

      • About Us

      • FAQ

      • Contact

      • T&C

      • Privacy Policy

      • Store Location

      • L’azurde World section

  • Login/Sign up button

    • An ability to Sign up or login through the Button located on the footer

      • As per UI design

      • Provide information of 10% discount for Member Signup ‘Sign Up And Get 10% Off’

Mandatory

Requirement Category - Data Model

Req. ID

Requirement

Sub-Group

Sub-Req. ID

Sub-Requirement

Priority

Req. ID

Requirement

Sub-Group

Sub-Req. ID

Sub-Requirement

Priority

NEW-234
NEW-235
NEW-236
NEW-237
NEW-238

Attributes for Customer Data

Customer Data Model

NEW-DMD-001

The system requires an ability to capture Customer attributes. Following are the key requirements:

  • Title/Salutation

  • First Name

  • Last Name

  • Email address

    • Account Unique identifier

  • Phone number

    • Account unique identifier

  • Country Code prefix for mobile numbers

    • Country code to default to browsing country. Could be edited.

  • Date of Birth

    • To be decided if mandatory or optional.

  • Anniversary Date

    • To be decided if mandatory or optional.

Customer Master

  • An Ability to require Customer Master

    • Ability to create a Unique ID that represents a customer across all the systems

Mandatory

NEW-239
NEW-240
NEW-241
NEW-242
NEW-243
NEW-244
NEW-245
NEW-246
NEW-247
NEW-248
NEW-249
NEW-250
NEW-251
NEW-252
NEW-253
NEW-254

Attributes for Product Categories

Category Data

NEW-DMD-002

The system requires an ability to capture Product categories through Category Data. Following are the key requirements:

  • Individual Product Catalogs

    • Ability to create Individual Product catalogs for each brand per Country/Site/Channel

  • Master Catalog Definition

    • Ability to configure Master catalog definition.

      • Have a master product catalog where by Products defined at master catalog level are extendable to any other site

  • Master Catalog Attributes

    • Ability to configure Master Catalog attributes

      • Product attributes and content can be defined at master catalog level and extended to specific site(s)

  • Master Catalog Media

    • Ability to configure Master Catalog Media

      • Product Imagery:

        i. Product image/video/360 view sequencing to be configurable

        ii. Option to control the product image shown in Listing Pages

  • Multiple Taxonomy/Category Tree

    • Ability to assign Multiple categories to a product

    • Ability to create a Category tree

    • Ability to create different taxonomies per market/brand

    • Select default taxonomy per Product catalog

  • A/B test different product taxonomies (Secondary)

  • Changes to the product taxonomy (Quick Publish)

    • Ability to make quick changes to the product taxonomy

      • Ability to show preview before publishing for approval

      • Category updates to be done in real time

  • Hierarchy Levels

    • Ability to create/update/delete Product Categories Hierarchy

      • Create/Read/update/delete product sub-categories to nth level (Child category linked to Parent category )

      • Create multiple layers of child category

      • Associate child categories to parent categories to create Category Hierarchy

  • Bulk Category Assignment

    • Ability to assign Products to categories in bulk through the following

      • Via Interface

      • Via Template (CSV)

  • Logs

    • Ability to create Logs and Review log of successful/failed mapping with reason for failure

  • Default Category

    • Ability to assign default category to a product

      • This category will be shown in canonical links and if product is found via search or other widgets it will be shown in the breadcrumb.

  • Backend Filtering

    • Report/filter option for all the products that are not mapped to any category or mapped to multiple categories

  • Automated category assignment (secondary)

    • Ability to set expiry date for a category (i.e., Black Friday, Clearance, etc.) - category should not be visible after specific date

  • Hide category in navigation

    • Define a category as active but “not visible” on front-end navigation

Mandatory

NEW-255
NEW-256
NEW-257
NEW-258
NEW-259
NEW-260
NEW-261
NEW-262
NEW-263
NEW-264
NEW-265
NEW-266

Attributes for Product Data

Product Data

NEW-DMD-003

The system requires an ability to capture Product Data in Product Attributes. Following are the key requirements:

  • Configure product pricing

    • Manually

      • An ability to configure product pricing manually in the system

        • Configure product pricing manually at country and currency level, for each brand. Individual prices per item

        • Note: Subject to Role Based Access, not all users would be able to configure product pricing manually.

    • Automatically

      • An ability to configure product pricing automatically through the ERP system

        • Configure product pricing automatically at country and currency level, for each brand (updating prices from ERP)

  • Update Product Pricing

    • An ability to update product pricing in the system through the following:

      • Backend Via Interface

        • Updating the product pricing through an interface

      • Backend Via Template

        • Updating the product pricing through uploading a template (CSV)

  • Rich Product Description

    • An ability to add rich description for a product

      • View rich product description (including images, videos and 360-degree images)

  • Product Media

    • An ability to upload product media like the following:

      • Product Images

      • Product Images based on Variations

      • Product Video

      • Product 360 degree Images

  • Additional info on images

    • Ability to add additional info on images related to size/dimension of the product in image

  • Product Features

    • Ability to capture product features and specifications like the following:

      • Product type, dimensions, brand, collection, Karat, metal , needs attributes that result in widgets on PDP

  • Promotion Info

    • Ability to capture any promotional information related to the product

  • Shipping details

    • Ability capture any shipping details related to the product such as shipping options

  • Services (Secondary)

    • Additional service that the product could include such as Gift Wrap, Customization etc.

  • Breadcrumb Navigation

    • Breadcrumb (based on browsing history and/or taxonomy) - canonical link will always be the same per product

  • Out of stock

    • Ability to handle out of stock scenarios of Product

    • Ability to send notification to CDXP if a User subscribes for Notify Me when available option so that, when the product becomes available, CDXP to send email notification to the Customer about Product Availability

Mandatory

NEW-273
NEW-274
NEW-275

Bulk Upload/Download

Import/Export

NEW-DMD-004

The system requires an ability to have bulk upload/download capabilities for Product Catalog. Following are the key requirements:

  • Import / Export Taxonomy / Categories

    • Ability to bulk import Product Categories/Taxonomy

    • Ability to bulk export Product Categories/Taxonomy

  • Import / Export Products mapping to Product Catalog

    • Ability to bulk import products mapping

    • Ability to bulk export products mapping

  • Import Product Attributes

    • Ability to map product attributes in excel and upload to PIM

Mandatory

OLD-003

Cross pollination of products / Products availability on Home/Master website

Product Catalog

NEW-DMD-005

The system requires an ability to have cross pollination of products on the Website. Following are the key requirements:

  • Ability for the main L’azurde website to have all brands available on their website whether they have their own website or not.

    • So, L’azurde’s product listing pages(PLPs) will have all the products from brands under their umbrella as in Waves Jewelry and Miss L'.

    • However, L’azurde products will not be available on Waves and on Miss L'.

  • Ability to share Promotion on a Product across all websites

    • If a Product has promotion for Miss'L, it will be shown with Promo on L'azurde as well

 

Requirement Category - Product Listing Page (PLP)

Req. ID

Requirement

Sub-Group

Sub-Req. ID

Sub-Requirement

Priority

Req. ID

Requirement

Sub-Group

Sub-Req. ID

Sub-Requirement

Priority

NEW-276
NEW-277
NEW-278
NEW-280
NEW-281
NEW-282
NEW-283
NEW-284

Displaying Product listing page elements

Product Listing Page Elements

 

NEW-PLP-001

The system requires an ability to display Product listing pages on the website. Following are the key requirements:

  • Product Listing

    • An ability to show the product listing based on the Category selected

  • Sorting and Sequencing

    • An ability to sort and sequence the product listing based on the business rules defined (CDXP driven)

  • Add to Cart

    • Ability to add an item to the cart through the PLP

  • Add to Wishlist

    • Ability to add a product to the Wishlist on the PLP

  • Price/Promotion display

    • Ability to display the price of the product on the PLP

      • Ability to display the promotion on the Product if available

  • Product ribbons/tags

    • Ability to display the product ribbons or tags on the line item of the PLP. for example (New, Online exclusive)

  • Out of Stock (secondary)

    • Ability to display if a Product is out of stock or is not available on the PLP

      • In case a Product gets killed or discontinued, It will not appear on the PLP

        • If a Product is in the User’s Wishlist, they will be able to go to the Product’s detail page but it will show the product is no longer available and recommendations based on the Product would be shown.

  • Breadcrumb Navigation PLP

    • Ability to have breadcrumb navigation implemented based on the Product categories on the PLP

Mandatory

NEW-285

NEW-286

 

Product Images on PLP

Product Images

NEW-PLP-002

The system requires an ability to switch product images in the Product listing page. Following are the key requirements:

  • Switcher from Product view to model view

    • Change Product-view to Model-view and vice versa: for all the products (tab selection) or individual products (pointer hover)

  • Don't keep changes in session

    • Default selection is Product view, change done by user will not be retained when navigating to other categories or page refresh.

Secondary

NEW-287
NEW-288
NEW-289
NEW-290
NEW-291
NEW-292
NEW-293
NEW-294
NEW-295
NEW-296

Sorting functionality on PLP

Sorting

NEW-PLP-003

The system requires an ability to have sorting functionality on the Product listing page. Following are the key requirements:

  • Sorting Options

    • An ability to have the following sorting options

      • Sort by Price High to low

      • Sort by Price Low to high

      • Sort by recommended

      • Sort by Newness

  • Hero Items

    • An ability to have PLP Manipulation based on visual merchandising configuration

  • Default Sorting per Category

    • An ability to apply default sorting per Product category based on configuration. (CDXP Based)

  • Default Sorting business logic

    • An ability to specify default sorting business logic in the system.

      • Default Driven by CDXP

  • Visually order products

    • An ability to visually order the products per category.

      • Driven by CDXP

  • Out of stock

    • An ability to display out of stock items.

      • Out of Stock products (all sizes & variants) listed last as a group, at the end of the listing page

      • Out of Stock products will show a label on the PLP to inform the user about product status.

      • Rule applies to all sorting and filtering combination

      • In case a Product gets killed or discontinued, It will not appear on the PLP

        • If a Product is in the User’s Wishlist, they will be able to go to the Product’s detail page but it will show the product is no longer available and recommendations based on the Product would be shown.

  • Sorting Default Fallback

    • An ability to specify fallback for sorting default according to the following:

      • If there is no default sort order configured per category,

        sorting will default to “Featured Products”.

      • If there is no “Featured Products” configured either, sorting

        will default to “New”

Mandatory

NEW-297
NEW-298
NEW-299
NEW-300
NEW-301
NEW-302
NEW-303
NEW-304
NEW-305
NEW-306
NEW-307

Filter functionality on PLP

Filtering

NEW-PLP-004

The system requires an ability to apply filters on a Product listing page. Following are the key requirements:

  • Filter options

    • An ability to have the following filter options to apply on the PLP

      • Filter by price

      • Filter by Brand

      • Filter by Category

      • Filter by metal

      • Filter by type

      • Filter by Gemstone

      • Filter only NEW

        • Show products on NEW status only. Timeframe of new = TBD

    • An ability to add individual filters coming from the product data model in the future

  • Configure filters per category

    • An ability to configure filters per Product category independently

  • Configure filter groups

    • An ability to configure filters per group of categories

  • Multi-select Filters

    • An ability to configure multiple selection or single selection for any given attribute/criteria

  • 3rd Party Integration

    • An ability to have regular data sync to have up to date filtering and sorting

Mandatory

NEW-308
NEW-309
NEW-310
NEW-311

Configuring Ribbons in the PLP

Ribbons

NEW-PLP-005

The system requires an ability to configure Ribbons in the Product listing page. Following are the key requirements:

  • Ribbon Rules

    • An ability to define business rules to show ribbons on products that are new, on clearance or sale, bestsellers or exclusive

  • Custom Ribbons

    • An ability to define custom ribbons to show on the PLP

  • Ribbon Design

    • An ability to control the look and feel of a ribbon design

  • Apply Ribbons

    • An ability to apply ribbons to products. Ribbons may include the following:

      • New

      • Sale

      • Exclusive

      • Discount

Mandatory

NEW-312

Seasonal Campaigns on PLP

Dynamic Content

NEW-PLP-006

The system requires an ability to configure Season campaigns on the Product listing pages. Following are the key requirements:

  • Configuring Seasonal campaign according to the following:

    1. Products allocated to campaign

    2. Promotion Terms & Conditions

    3. Expiry date

    4. Days to expiry

    5. Last day of promotion should show countdown of time left to buy

    6. Any restriction on the promotion

Mandatory

NEW-313

Lazy Loading

General

NEW-PLP-007

The system requires an ability to show lazy loading on the Product listing pages. Following are the key requirements:

  • Scrolling to the bottom of the page should trigger loading more products.

     

Mandatory

NEW-314

NEW-315

 

Adding to Cart on the PLP

Add to Cart

NEW-PLP-008

The system requires an ability to have adding to cart options on the Product listing pages. Following are the key requirements:

  • Quick buy option

    • Ability to quickly add item to cart and go to checkout

  • Show only available options

    • Options offered to user will be based on stock availability

Note: The above options are only available for Desktop and not available on Mobile.

Mandatory

NEW-316

NEW-317

 

Adding items to Wishlist on PLP

Wishlist

NEW-PLP-009

The system requires an ability to add products to user’s Wishlist on the Product listing pages. Following are the key requirements:

  • Ability to Add products to Wishlist when they are logged in

    • Trigger option to log in if not logged in

Mandatory

Requirement Category - Product Display Page (PDP)

Req. ID

Requirement

Sub-Group

Sub-Req. ID

Sub-Requirement

Priority

Req. ID

Requirement

Sub-Group

Sub-Req. ID

Sub-Requirement

Priority

NEW-267
NEW-268
NEW-269
NEW-270
NEW-271
NEW-272

Handling Product Media

Product Media

NEW-PDP-001

The system requires an ability to handle Product media related to a Product. Following are the key requirements:

  • An ability to handle the following for Product media

    • Carousel

      • View multiple images in a carousel, max images per standard product 4

    • Zoom

      • Ability to zoom into an image of the product

    • 360° Images (Secondary)

      • Ability to view 360° Images

    • Videos (Secondary)

      • Ability to display video of a product

    • Images per variant

      • Ability to select and view images per variant

      • View images in the selected Product color

    • Advanced functionality

      • Ability to perform the following features:

        • Zoom/swipe/multi-touch features for images ( Mobile /touch screen)

Mandatory

NEW-318
NEW-319
NEW-320
NEW-321
NEW-322
NEW-323
NEW-324
NEW-325
NEW-326
NEW-327
NEW-328
NEW-329
NEW-330
NEW-331
NEW-332
NEW-333
NEW-334
NEW-335
NEW-336

Defining PDP page elements

Product Detail Page Elements

NEW-PDP-002

The system requires an ability to display Product detail page of a Product. Following are the key requirements:

  • Product Content

    • Display product content on the PDP as mentioned above

  • Product images & videos

    • Display product images and videos on the PDP as mentioned above

  • Zoom, mouse-hover

    • An ability to enlarge the picture based on the following:

      • Zoom on screen tap

      • Zoon on Mouse Hover

  • Variants (select size, color)

    • Ability to select variants of the Product available

      • can select product variant in stock only

  • Add to cart button

    • An ability to add the product to the cart based on the details selected

  • Product ribbons, tags

    • An ability to display ribbons and tags configured of the Product on the PDP

  • Alternative products if product is sold out

    • Ability to display alternate product in case a product is sold out or not available

      • Definition of Sold out: all variants are sold out

  • Product Recommendations

    • An ability to recommend products to the user based on ML

      • Driven by CDXP

  • Recently viewed Products

    • An ability to display recently viewed products on the PDP based on the following:

      • Product Browsing history

      • Relevant products based on browsing history

      • Configurable based for each brand / Storefront

  • In stock alert

    • An ability to allow user to opt in for in stock alert (In case of Out of stock item) with the following details:

      • When current product is partially or completely out of stock and flagged as replenishable:

        • Users will be allowed to input email addresses and subscribe for Product Availability notifications if they are Logged In users and Email ID is known.

        • After opt-in:

          • User should view a confirmation message

        • Frequency to trigger the notifications will be sent to customer based on configuration (configured from Admin panel by Merchandiser)

        • Guest users will be invited to log in when clicking the link

        • Update the Customer when the item is back in stock

          • This needs to link to CDXP so that email can be sent to the customers from CDXP once the item is back in stock

  • Promotion Display

    • Ability to display promotion related to the Product or store if available

  • Add to Wishlist

    • Ability to add product to Wishlist

      • Trigger login alert in case of Guest user

  • Breadcrumb Navigation

    • Ability to have breadcrumb navigation on the PDP for better navigation

  • Related Products

    • An ability to to see (channel level configuration for each brand and Country) product accessories and related products

  • Bought also

    • An ability to see (channel level configuration for each brand and Country) Customers also bought section on the PDP

  • Product Recommendation in stock Validation

    • All products suggestions should be in stock and available to buy

Mandatory

NEW-324

NEW-336
NEW-337

Defining PDP secondary page elements

Product Detail Page Elements

NEW-PDP-003

The system requires an ability to display Product detail page of a Product. Following are the key requirements:

  • Sound Alert on Add item to Basket

    • Adding an item to the basket should generate a small sound indicating product has been successfully added

  • Configure widgets per device

    • An ability to configure widgets per device.

      • Configurable based on device category (Desktop, tablet, mobile)

  • Social Sharing

    • An ability to allow user to share product on social platforms like the following:

      • Facebook

      • Twitter

      • Instagram

      • Pinterest

      • WhatsApp (Mobile only)

      • Email/Others

         

Secondary

Requirement Category - Wishlist

Req. ID

Requirement

Sub-Group

Sub-Req. ID

Sub-Requirement

Priority

Req. ID

Requirement

Sub-Group

Sub-Req. ID

Sub-Requirement

Priority

OLD-001

Unified Wishlist

Basic Requirements

NEW-WLT-001

The system requires an ability for the User to add products to their Wishlist. Following are the key requirements:

  • User can then view the all the products in their Wishlist and purchase them afterwards. Also, this Wishlist will be unified/common so can have products from different L’azurde’s websites on any given time unless the user changes the region

  • An ability to share Wishlist via share options to others

    • Ability to share Wishlist via Social Platforms

    • Ability to share Wishlist via Email

    • Ability to share Wishlist via Text/WhatsApp

Validation:

The Common Wishlist will only be valid in the same region, for example One Wishlist would only work for UAE region, For KSA Region the user would have a separate Wishlist based on their KSA Account.

Mandatory

NEW-338
NEW-339
NEW-340
NEW-341
NEW-342
NEW-343
NEW-344

Managing Wishlist

Wishlist

NEW-WLT-002

The system requires an ability to add item to the user’s Wishlist. Following are the key requirements:

  • Manage Wishlist

    • Ability to do the following

      • Add to Wishlist

      • Update Wishlist

      • Delete from Wishlist

  • Push Wishlist directly to cart

    • Ability to directly buy from Wishlist

  • Breadcrumb Navigation Wishlist

    • An ability to navigate on the Wishlist page through breadcrumb navigation

  • Push product into shopping cart

    • An ability to push an item from Wishlist to the existing shopping cart

  • One click ease

    • Ability to add an item to Wishlist with a single click

  • Add single item

    • Single item quantities will be added to cart.

  • Option to push complete Wishlist to cart

    • There should be option to push a complete favorites list of shopping cart at once

  • Prompt to login if User is Guest

    • Ability to trigger alert to the user to login if they are adding to Wishlist as a guest user

 

 

Requirement Category - Checkout

Req. ID

Requirement

Sub-Group

Sub-Req. ID

Sub-Requirement

Priority

Req. ID

Requirement

Sub-Group

Sub-Req. ID

Sub-Requirement

Priority

OLD-002
NEW-345

Common Checkout

Checkout

NEW-CKT-001

  • Ability for all the websites to have common checkout and cart meaning a user can add a product from multiple websites by visiting them and checkout all the products all together from any website/store front for that region only

fig-2

As, it can be seen by fig-2 that user have added the product from Athleta’s website and then moved to the Banana Republic’s website. There the user added another product to their cart from the banana republic website website and checking out from the Banana Republic’s website.

Also, we can see that for 100% product penetration we are displacing a logo over the product image of the brand which it belongs to and from which website it was purchased.

Validation:

  • The Common Checkout will only be valid in the same region, for example One login would only work for UAE region, For KSA Region the user would have a separate account and separate checkout.

  • User to only add address of the region of the website they are in for e.g. If a user does checkout from UAE region of the website, they will only be allowed to add UAE address for shipping.

  • Wishlist: The Wishlist will only show products of the region the user is logged in.

  • For UAE, deliveries will be made from KSA 

  • For UAE, there is no cash on delivery available 

  • Shipping fee is only applicable in case of Cash of Delivery for KSA it would be SR49 and for Egypt it will be EP50

  • On the product pages, we show the total price customer will pay (we will not add on a % for tax when they reach the checkout / basket).

  • On the basket and beyond it just shows the price minus the VAT and therefore a line item saying how much of that price is going towards tax - as per the % below

  • UAE VAT: 5%

  • Egypt VAT: 14%

  • KSA VAT: 15%

    • Formula for tax calculation

      • Assume the tax is 15% and selling  price is 2450

         Cost = X 

        Tax = Y  : 115%   

        Selling price = Z : 2450

        Then Cost X =  (2450 *100)/115 = 2130.43  ie   ( Z *100) /Y

  • User can be able to use to avail BNPL option as-well.

    • Valu will be used for Egypt

    • Tabby will be used for KSA and UAE

Mandatory

NEW-346
NEW-347
NEW-348
NEW-349
NEW-350
NEW-351
NEW-352
NEW-353

Displaying Cart elements on Checkout

Cart Element

NEW-CKT-002

The system requires an ability to display cart elements on the Checkout page. Following are the key requirements:

  • Cart Elements

    • Product Thumbnail

    • Product Name

    • Variants selected

    • Product Code

    • Unit Price

    • Quantity

      • Ability to update quantity attribute (Subject to stock availability)

      • Update quantity of an item

        a. Quantity change should reflect on the item subtotal

        b. And the overall cart total

        c. Notify the customer whether the item is available in the requested quantity or not

        d. Ability to configure a maximum quantity that can be added per line item

    • Promotion (if available)

Mandatory

NEW-354
NEW-355
NEW-356
NEW-357
NEW-358
NEW-359
NEW-360
NEW-361
NEW-362
NEW-363
NEW-364

Checkout Details on the Checkout Page

Cart

NEW-CKT-003

The system requires an ability to display details at the checkout page. Following are the key requirements:

  • List of Items

    • Show all items in the Cart

  • Order Summary

    • Display Order summary with the Order details like the following:

      • Total

      • Discounts

      • VAT

        • On the product pages, we show the total price customer will pay (we will not add on a % for tax when they reach the checkout / basket).

        • On the basket and beyond it just shows the price minus the VAT and therefore a line item saying how much of that price is going towards tax - as per the % below

        • UAE VAT: 5%

        • Egypt VAT: 14%

        • KSA VAT: 15%

          • Formula for tax calculation

            • Assume the tax is 15% and selling  price is 2450

               Cost = X 

              Tax = Y  : 115%   

              Selling price = Z : 2450

              Then Cost X =  (2450 *100)/115 = 2130.43  ie   ( Z *100) /Y

      • Delivery Charge

  • Single Item Removal

    • Ability to remove an item from the cart

      • Removing a single item from cart, Should re-calculate the overall cart total and consider promotions

  • Clear all items

    • Ability to clear all the items from the cart or to empty the cart

      • Clear all items in my cart: Empty cart (remove all items in one go). Clear all the items in my basket. This includes products, services, promo codes … etc.

  • Move to Wishlist

    • Move an item from the current cart to a favorites list in customer account and cart should be updated to reflect the changes including order total, any applied discounts and/or promotions

  • Apply Discount

    • Ability to apply discount on the Cart through promo, voucher or coupon

  • VAT or excl. VAT if international

    • Display VAT information

  • Trust Elements Widget

    • Manage a dedicated content spot on cart page from CMS. UI will show Icons like: Verified by Visa / Mastercard Secure / SSL Secure etc.

  • Checkout Link

    • Proceed to checkout process via Checkout link

  • Back to Shopping link

    • Go back to the previous page in the browsing journey to continue shopping

  • Store Cart at account

    • An ability to store the cart at account level.

      • Shopping Cart to allow cross-channel transactions.

      • Guest user Logging In at a later stage will have the Shopping cart content synchronized to account after log in.

      • Same user will be able to log-in on another device, view and change products added from the previous session and complete the transaction.

Mandatory

NEW-365
NEW-366

Additional Services on Checkout

Cart

NEW-CKT-004

The system requires an ability to provide additional services at checkout. Following are the key requirements:

  • Services

    • Ability to choose services like the following:

      • Gift Wrap

      • Customization

      • Premium Delivery

  • Service Charges

    • An ability to provide service charges on the services

      • Services can be either chargeable or free

        a. Charges can be flat rate

        b. Charges can change based on quantity

        c. Charges can be based on item/basket promotion

Secondary

NEW-367
NEW-368
NEW-369
NEW-370
NEW-371
NEW-372
NEW-373
NEW-374
NEW-375

Promotions on the Checkout page

Promotions

NEW-CKT-005

The system requires to apply promotion or view promotion details on the Checkout page. Following are the key requirements:

  • Promo Codes

    • An ability to apply promo code on the checkout page

      • See whether the promo code has been applied (valid) or not and how much user is saving using the promo code

  • Promotion summary

    • Any type of promotion (buy one get one, cart level discount, promo code etc.) to be highlighted in Shopping Cart Order Summary Section. Discount breakdown to be displayed as per provided design, showing labels (based on admin config) against each discount entry.

  • Promotion Reminder in Cart (Secondary)

    • A prompt should appear in the case of a part-qualification towards a promotion, such as:

      ‘Spend another SAR xx to qualify for free delivery'

      Spend another SAR xx to get SAR yy off

      Shown only in cart ( not in checkout)

  • Product and service level promotions per country

    • Ability to have promotions based on Product/Service according to the Country store

  • Product and service level discounts

    • Ability to have discounts based on Products or service

  • Product based volume

    • Discounts/Promotions based on Product based volume

  • Shopping cart based

    • Discounts/Promotions based on Shopping cart value

  • Time based

    • Discounts/Promotions based on time. For e.g. New Year, Black Friday, Eid etc.

  • Special deals

    • Ability to provide special deals on checkout

    • Ability to generate voucher code as part of customer service resolution . One use promo code that is unique to an end user

    • Ability to report on voucher code usage and redemption

  • Member Sign up Promotion

    • Ability to provide Member promotion on sign up

      • To be displayed on Website footer as well.

  • Voucher Code/Promo Code Usage Sync

    • Ability to sync Voucher code usage in between online and offline (POS) so voucher code usage can be validated. example: A voucher that has been used offline at a POS cannot be used again on an Online order.

Mandatory

NEW-376

Toggle Services in Checkout

Setting

NEW-CKT-006

The system requires an ability to toggle services for checkout. Following are the key requirements:

  • Turn on/off delivery Services at brand / Country / Channel level

    a. Same Day / Next Day

    b. Gift wrapping

    c. etc

Mandatory

NEW-377
NEW-378
NEW-379

Checking out as a User

Checkout Flow

NEW-CKT-007

The system requires an ability to have checkout flow for the users on the website. Following are the key requirements:

  • Ability to checkout on the website as the following users:

    • Registered user

    • Guest User

      • Ability to allow user to create an account at Checkout

    • Social Login User

Mandatory

NEW-380
NEW-381
NEW-382
NEW-383
NEW-384
NEW-385
NEW-386
NEW-387
NEW-388
NEW-389
NEW-390
NEW-391
NEW-392

Configuring Payment options at Checkout

Payment

NEW-CKT-008

The system requires an ability to have payment options at checkout. Following are the key requirements:

  • Payment Options

    • Payment options to be configurable . Following are the payment options that could be configured and activated/deactivated:

    • Pay on delivery (COD)

      • Toggle Payment Option in Checkout per Country / Website.

    • Card Payment credit/debit (Visa, Master Card)

      • Toggle Payment Option in Checkout per Country / Website.

      • For payment with new Card, a form should be displayed that include fields like:

        a. Card Holder Name

        b. Card Number

        c. Expiry Date

        d. CVV

    • Mada Card

      • Toggle Payment Option in Checkout per Country / Website.

      • Ability to Pay in KSA through Mada Card

    • Apple Pay

      • Toggle Payment Option in Checkout per Country / Website.

      • Available in KSA&UAE. Unavailable in Egypt

    • BNPL - Buy Now Pay later

      • Toggle Payment Option in Checkout per Country / Website.

      • BNPL options may include Tabby (KSA only) Valu and Tamara, Forssa (EGP)

  • Multi-Payment (Split Payment)

    • Ability to use multiple voucher code/gift card + one other payment type e.g. credit card.

  • Save Payment Method

    • Ability to save Payment method (Debit Card/Credit Card used by the Customer (only logged in user) to be used next time

  • Payment Rules

    • Ability to configure and set payment rules

    • Available payment options are dependent on business rules such as Country, product type, international delivery, fulfilment source, delivery proposition, order type … etc. e.g. COD max order limit

  • Add fees per payment

    • If a customer chooses Cash on Delivery, an additional fee should be displayed if applicable (Configurable value)

  • Default Payment Method

    • Default payment method should be preselected if configured by the user form My Account section.

  • Save Card

    • Ability to save the card for future use

      • Logged in users paying with new cards, should have the option to Save the card for future payments

  • Choose existing cards

    • Ability for the user to choose existing card that were saved during previous order

      • Logged in users having cards previously stored in their account, should be allowed to choose one of the stored cards as payment method.

  • Real time payment approval

    • An ability to verify payment at real time

  • Payment failure information

    • If the payment fails a payment declined page should be displayed informing the customer the order unsuccessful

Mandatory

NEW-393
NEW-394
NEW-395
NEW-417
NEW-418
NEW-419

 

Thank you page on Checkout after Order placed

Thank you Page

NEW-CKT-009

The system requires an ability to display order confirmation at the time of successful order placement. Following are the key requirements:

  • Order confirmation details

    • Show order confirmation details at the time of successful checkout

      • Confirmation page should include details like:

      a. Order Number

      b. Order Date/Time

      c. Name of Customer

      d. Delivery address in case of Home Delivery

      e. Expected delivery/collection date/time for Home Delivery

      f. Summary of the purchased items with details like:

      i. Product thumbnail

      ii. Product name

      iii. Product code

      iv. Unit price

      v. Subtotal

      vi. discounts/promotions

       

  • Account signup for Guest checkout

    • Ability for an account to be created for all the customer even if they don't register with Username and Password

    • Trigger an email to the customer about account creation

  • Guest Registering Option

    • In case of guest checkout, user could signup with Social Connect or using a form to allow the user to set a password and create an account.

    • When user choose to create an account, their history as a guest should carry forward into new user account including order history, personal information, delivery address … etc.

  • Marketing Messages

    • Ability to send Marketing messages to the customer

  • Content Widget

    • A content spot should be displayed for the user as a marketing shout that can be configured by business

Note: Klaviyo tool to be used for Email messaging

Mandatory

NEW-396
NEW-397
NEW-398
NEW-399
NEW-400
NEW-401
NEW-402
NEW-403
NEW-404
NEW-405
NEW-406
NEW-407
NEW-408
NEW-409
NEW-410
NEW-411
NEW-412
NEW-413
NEW-414
NEW-415
NEW-416

Details for Checkout on the Checkout page

Checkout

NEW-CKT-010

The system requires an ability to configure checkout details. Following are the key requirements:

  • Checkout Availability check

    • When moving from Shopping Cart to Checkout ATP check should be triggered

  • Guest Checkout

    • An ability to checkout as guest

      • In case of Guest checkout, email address is mandatory

  • Registering in Checkout

    • An ability for the customer to create a L’azurde account at the time of checkout

      • If the customer chooses to register a new account, he/she should be redirected back to checkout once registered.

  • Social Login Checkout

    • An ability to login through social account at the time of checkout

      • Use Facebook/google account to login on the site and complete checkout journey without the need to create a password

  • Log In Checkout

    • An ability to login at the time of checkout.

      • If the customer chooses to login, he/she should be redirected back to checkout once logged in.

  • Exception Case Guest -> Login

    • Guest becoming Logged In scenario:

      a. Existing items in the Account related DB Shopping cart

      i. Account related Cart (from previous sessions) will be prompted to the user to take action:

      1. Move old items to Wishlist

      2. Update cart with old products

      3. Dismiss the old products

  • Pre-filled Personal Information

    • Ability to load Personal information for logged in user at the time of checkout

      • See personal information pre-filled with the ability to edit them

  • Address Book

    • Ability to choose saved address (logged in user) for delivery

  • Default Address

    • Ability for Previous (default) address to be displayed and selected by default on delivery page

  • Edit Addresses

    • Ability to edit saved addresses or add new address

    • An ability to autocomplete Delivery Address (Powered by Google) while inputting delivery address. (For KSA)

  • Default Payment Method

    • Ability for the default payment method to be pre-selected (if any)

  • Delivery Address

    • New Delivery details should be filled in with an auto completion assistance and include information like:

      1. Name

      2. Type of location: business, residential (Drop Down List)

      3. Street name

      4. Building name

      5. City (Drop Down List) (middle east specific)

      6. Area (Drop Down list) (middle east specific)

      7. Country (Drop Down List)- Default to browsing country

      8. Phone number

      9. Google map pin drop

      10. Zip code

    • An ability to autocomplete Delivery Address (Powered by Google) while inputting delivery address. (For KSA)

  • Delivery Options

    • Ability for the customer to select delivery options

      • Delivery options available to the selected delivery address displayed with selection

      • Cost and delivery details (expected delivery date) of every delivery option is displayed to the user

      • Delivery options available dependent on the business rules that takes into consideration Country Site, delivery address, product type, fulfilment source and whether the product requires service. It should also consider the cut-off times for delivery. e.g., Same Day /Next Day

  • Checkout Summary

    • Ability to show the basket summary before finishing checkout

      • Basket summary showing thumbnail, product name, color, size, quantity, stock status (i.e., warning if low stock), line total, shipping cost and order total

  • Back to Basket link

    • Ability for the user to edit cart before proceeding to checkout

      • Edit Link should be displayed as part of order summary to allow the user to go back cart if needed

  • Edit Billing Address

    • If a registered user, saved billing addresses should be displayed with the ability to edit or add new billing address

  • Services

    • Ability to show services to the Customer at the time of checkout

      • Services shown to users will be based on eligibility / business rules configuration for each brand / Country and Channel.

      • Services: Gift wrapping, Pricing will be calculated and shown to the user based on configuration.

  • T&C / Privacy Policy links

    • Ability to show T&C and Privacy policy links before proceeding to checkout

      • To comply with the International Market regulations, T&C / Privacy Policy links to be shown to the user before placing the order. Links will be only displayed; the user is not required to tick the checkbox for acceptance before submitting the Checkout form.

  • Checkout Item reservation

    • During checkout: Should temporarily block the inventory. soft reservation for 30 min to allow time for completion , if not completed inventory is released and a new ATP check is triggered if the customer comes back to complete checkout

    • Payment Success scenario:

      • If payment is successful, order status should be automatically updated and inventory should be updated.

    • Payment Negative scenarios:

      • In case of payment gateway response timeout OR payment declined, inventory should be released - after a time interval configured in the Admin Panel. ( 30 min )

  • Guest Checkout Analysis (secondary)

    • Can see customer by email address and identify related orders and purchase history

    • Can export information to be used for marketing /CRM purposes

 

Note: Checkout.com to be running the checkout process

Mandatory

 

Requirement Category - SEO

Req. ID

Requirement

Sub-Group

Sub-Req. ID

Sub-Requirement

Priority

Req. ID

Requirement

Sub-Group

Sub-Req. ID

Sub-Requirement

Priority

NEW-420
NEW-421

Robots.txt configuration

Robots.txt

NEW-SEO-001

The system requires an ability to configure Robots.txt for SEO. Following are the key requirements:

  • Robots.txt

    • Ability for the robots.txt to be:

      • Allowed

      • Disallow

  • Configure which URLs can and cannot be crawled by Google

  • Ability to add XML sitemaps to
    robots.txt file

  • Ability to update Robots.txt file from
    the BigCommerce backend

Mandatory

NEW-422
NEW-423
NEW-424

Sitemaps configuration on the Website

Sitemaps

NEW-SEO-002

The system requires an ability to configure sitemaps on the L’azurde website. Following are the key requirements:

  • Sitemap XML Categories

    • Create specific sitemap for Homepage, CLPs & PLPs - split by market and language

  • Sitemap XML PDPs

    • Create specific sitemap for PDPs - split by market and language

  • Sitemap XML CMS Pages

    • Create specific sitemap for content pages - split by market and language

  • Ability to automate the XML sitemap when new products/brands/landing pages are added/removed

  • No dynamic URLs should be included in the XML sitemaps (Optional)

  • The sitemap should contain href lang tags for all URLs (For eg - A PLP in KSA EN should have all its variations listed in other markets and language) (Optional)

     

Mandatory

NEW-425

Href-Lang

Href-Lang

NEW-SEO-003

The system requires an ability to configure Href-lang on the L’azurde website. Following is the requirement:

  • Create file to direct Google to appropriate country/language

  • All indexable pages on the website should contain the href lang tags in the HTML (For eg - A PLP page on the website should have all its variations basis market and language should be listed in the HTML)

Mandatory

NEW-426

Canonical URLs

Canonical URLs

NEW-SEO-004

The system requires an ability to configure Canonical URLs on the L’azurde website. Following is the requirement:

  • Rules & implementation required to guide Google on which URLs are canonicalized to which (duplicate indexation prevention)

  • All indexable URLs should contain self referencing canonical tags by default. [Except dynamic/filter pages these will have canonicals to the respective category or brand page]

  • The system should have the ability to manually overwrite the canonical tags for the pages.

Mandatory

NEW-427

Page Title

Page Title

NEW-SEO-005

The system requires an ability to configure Page Title for SEO configuration on the L’azurde website. Following is the requirement:

  • Ability for the Page title to be generated automatically AND self editable. Page Title should be template driven with the ability to customize each one individually (<meta name="title" content="xxx/>)

  • Following templates are required -

    • Brand [Eg - Miss L]

    • L1 categories [Eg - Jewelry]

    • L2 categories [Eg - Shop By Metal]

    • L3 categories [Eg - Rings]

    • PDP [Eg - Product Title]

    • Country [Eg - Egypt]

    • Page Number [For paginated pages]

  • Systems ability to overwrite tags by
    a csv upload

Mandatory

NEW-428

Meta Description

Meta Description

NEW-SEO-006

The system requires an ability to configure Meta Description on the L’azurde website. Following is the requirement:

  • META Description should be template driven with the ability to customise each one individually (<meta name="description" content="xxx/>)

  • Following templates are required -

    • Brand [Eg - Miss L]

    • L1 categories [Eg - Jewelry]

    • L2 categories [Eg - Shop By Metal]

    • L3 categories [Eg - Rings]

    • PDP [Eg - Product Title]

    • Country [Eg - Egypt]

    • Page Number [For paginated pages]

  • Systems ability to overwrite tags by
    a csv upload

Mandatory

NEW-429

Alt-Text for Images

Alt-Text for Images

NEW-SEO-007

The system requires an ability to configure Alt-text for images on the L’azurde website. Following is the requirement:

  • Images should be named appropriately (descriptive names rather than file numbers) and ALT text should replicate the image file name

  • System should add the product title as the “alt” automatically

  • For multiple images, system should append a number [For Eg - 18K Gold Diamond Drop Earring - 2]

Mandatory

NEW-430

<h>-headlines

<h>-headlines

NEW-SEO-008

The system requires an ability to configure <h>-headlines for text based content on the L’azurde website. Following is the requirement:

  • Heading Tag structure to be implemented (H1 - H3) based on site designs

  • By default all page headings should have <h> tags [basis design] -

    • Page title - <h1>

    • Sub headings - <h2>

    • Sub-Sub headings <h3>

    • All PDP titles on PLPs - <h3>

  • Ability to add and modify a heading tag on any heading present on the page

  • Ability to configure tags from H1 - H4

  • No irrelevant heading tags placement (eg: On elements from footer of website, sign up, add to cart etc.)

Mandatory

NEW-431

Domain structure

Domain structure

NEW-SEO-009

URL Structure to be implemented based on the instructions in:

https://docs.google.com/spreadsheets/d/1Qqh2ITTQr_peKZHsESZ4b9W6yuclX-LK3t6zwJQFCxs/edit#gid=1250074119

Mandatory

NEW-432

Automatic URL Rewrites

Automatic URL Rewrites

NEW-SEO-010

The system requires an ability to configure Automatic URL Rewrites on the L’azurde website. Following is the requirement:

  • URL structure should be clean and driven by taxonomy naming conventions

Mandatory

NEW-433

Custom URL 

Custom URL 

NEW-SEO-011

The system requires an ability to configure Custom URL for SEO on the L’azurde website. Following is the requirement:

  • An ability to configure Custom URL for SEO configuration

Mandatory

NEW-434

NEW-435

Miss L' URL Takedown

Redirects

NEW-SEO-013

The system requires an ability to redirect Miss L' to L’azurde once it’s taken down. Following are the key requirements:

  • Miss 'L Jewelry website is currently a standalone website. However, it will be taken down and it will be come under L’azurde website / domain. However, it will still have its own UI.

    The domain name of Miss L Jewelry and will 301 redirect directly to Miss L within the L’azurde platform. Example: Going to Miss L Rings would 301 redirect the user to Miss L rings on L’azurde website

Mandatory

NEW-434

NEW-435

 

Redirection of Existing URLs

Redirects

NEW-SEO-012

The system requires an ability to configure redirects for existing URLs. Following are the key requirements:

Mandatory

NEW-436

Design Review

Design

NEW-SEO-013

Wireframes and site designs to be reviewed to ensure SEO friendly (ie. heading tags, on page content, internal linking)

SEO team will also review the HTML on staging along with the backend for items mentioned in this document

Mandatory

NEW-437

Filtering

Filters

NEW-SEO-014

The system requires an ability to configure Filters for SEO configuration. Following is the requirement:

  • Rules to be created in order to account for filtered URLs and multi-select attributes across one or more filter types

  • Display the filters applied separately for the user to understand what filters are currently applied while
    allowing the user to remove filters when needed.

  • The filter bar needs to be sticky and follow the user scrolls through the page.

  • Filter dynamic URLs should contain canonical tags to the main page

Mandatory

NEW-438

Schema Markup

Schema

NEW-SEO-015

The system requires an ability to configure Schema for SEO Configuration. Following is the requirement:

  • Schema markup required across various page types with key information (ratings/reviews, price, availability, product attributes)

  • Additional schema to be integrated apart from product schema

    • Breadcrumb schema

    • Organization schema

    • Local Business schema

  • Ability to manage schema codes from the backend at a template level homepage, categories and PDPs

Mandatory

ENH-001

Content Placeholder

SEO Content
[Text]

NEW-SEO-016

The system requires an ability to have content placeholder for SEO Configuration. Following are the key requirements:

  • Adding an HTML content placeholder on the category and homepage. This will be place above the footer section

  • Ability to implement and configure heading tags (H1, H2, H3), integrate texts in HTML

  • Ability to add links in the content to other pages

  • A read more tab will be present to
    expand the content on mobile and
    desktop

Secondary

ENH-002

Internal Links

Links on
Extended Footer

NEW-SEO-017

The system requires an ability to have internal links for SEO Configuration. Following are the key requirements:

  • A “popular search” section to be placed under the main footer section for internal linking. This can
    be in an accordion

  • Ability to implement/customize new anchor text and hyperlinks as suggested by SEO team on the
    footer section on main L'azurde website, Miss L and other brand pages.

  • Ability to implement/customize popular searches section across the website which hyperlinks to
    relevant pages.

Secondary

ENH-003

Pagination

Scrolling

NEW-SEO-018

The system requires an ability to have Pagination scrolling for SEO Configuration. Following are the key requirements:

  • Replace the numbered pagination to a ‘load more’ button

  • Webpage to have static URL on “load more” click (rings/page-2) instead of dynamic URL (rings/?page=2)

  • Implement noindex, follow meta directives onto paginated pages

  • Implement rel next and rel prev directives on paginated pages

  • Implement self referencing canonicals on paginated pages

  • Main page’s meta title to be appended with page number

Secondary

ENH-004

Navigational Links

On PLPs

NEW-SEO-019

The system requires an ability to have Navigational Links on PLPs for SEO configurations. Following are the key requirements:

  • Create a new placeholder under the breadcrumb of PLP pages to link important pages
    Example:
    On the rings category page the placeholder can include hyperlinks to static pages for ‘Engagement
    ring’, ‘Cocktail rings’ or any other new landing page that we may create

  • Ability to manually add links and anchors to these tabs

Secondary

ENH-005

Breadcrumb

Across the
Website

NEW-SEO-020

The system requires an ability to have Breadcrumb across the Website for SEO Configuration. Following are the key requirements:

  • All levels of page hierarchy to be displayed on the breadcrumb.

  • On the PDP page level, product title should be the last level without the link

  • Ability to change “Home” in the primary level of breadcrumb to respective brand name

  • Breadcrumb schema implementation to be automated

Secondary

ENH-006

Image Optimization

Image
Compression &
Format

NEW-SEO-021

The system requires an ability to have Image optimization for SEO Configuration. Following are the key requirements:

  • All images to be compressed and resized to fit the container.

  • Images should be in the webp format for optimal compression. (100kb or less per image)

Secondary

ENH-007

404 Page
Management

Page Redirects

NEW-SEO-022

The system requires an ability to have 404 Page Management for SEO Configuration. Following are the key requirements:

  • Ability to redirect the 404 product/category to the parent category automatically. [For eg - 14K Diamond Drop Earring if 404ed should redirect to/jewelry/earrings]

  • Ability to manually overwrite the automatic redirect to a custom 200 OK product URL

  • Ability to upload a csv for bulk overwrites of automatic 404 redirects

Secondary

ENH-008

Discontinued
Product
Communication

PDPs

NEW-SEO-023

The system requires an ability to have Discontinued Product Communication on PDPs for SEO Configuration. Following are the key requirements:

  • Ability to add a “permanently out of stock” message on selected products

  • Ability to add a widget for similar products on such pages

Secondary

ENH-009

Store page

URLs

NEW-SEO-024

The system requires an ability to have Store Page URLs for SEO Configuration. Following are the key requirements:

  • Each Store to have a unique URL on click with separate meta directives

  • Automation of schema implementation on store pages

Secondary

ENH-010

Meta directives

Meta Robots

NEW-SEO-025

The system requires an ability to have Meta Directives and Meta Robots for SEO Configuration. Following are the key requirements:

  • All pages we would like to get indexed should contain a “index,follow” meta directive

  • Ability to manually change meta directives of pages on the CMS

Secondary

ENH-011

CDN

Image Hosting

NEW-SEO-026

The system requires an ability to have CDN Image Hosting for SEO Configuration. Following are the key requirements:

  • Ensure that your images are always hosted on your own domain.

  • Ensure that CDN is enabled on your own domain rather than any third party domain so that all link
    equity that you get through image links should be passed on to your main domain.

Secondary

ENH-012

Core Web Vitals

Website
Performance

NEW-SEO-027

The system requires an ability to have Core Web Vitals (Website Performance) for SEO Configuration. Following are the key requirements:

  • We (Incubeta) will be reviewing the website on staging while it's being developed to share recommendations related to core website vital issues like - CLS, LCP
    and FID etc.

Secondary

 

Requirement Category - Notifications

Req. ID

Requirement

Sub-Group

Sub-Req. ID

Sub-Requirement

Priority

Req. ID

Requirement

Sub-Group

Sub-Req. ID

Sub-Requirement

Priority

NEW-439

NEW-445
NEW-446
NEW-447

Registration Confirmation

Email

NEW-NOT-002

The system requires an ability to send Account related notification for Registration. Following are the key requirements:

  • Individual Confirmation Mail Template

    • An ability to send Email confirmation for Successful registration

    • Content and information in the registration email will be provided by design teams.

  • Account Creation

    • An email notification to be sent on successful Account creation

      • Successful registration should send confirmation email with customer details to registered email address

  • Email Verification

    • An email notification to be sent for Email Verification

  • Password recovery

    • An email notification to be sent for Password recovery

Mandatory

NEW-440
NEW-441
NEW-442
NEW-443
NEW-444

Order State Notifications

Email

NEW-NOT-003

The system requires an ability to send Order state notifications to the customer. Following are the key requirements:

  • Order Confirmation

    • Ability to send Order Confirmation notification on the Email

      • Order details to be sent in the Order Confirmation

      • A confirmation Email notification should be triggered once the user reaches Thank You page

  • Order Dispatch

    • Ability to send Order dispatch notification on the Email

      • Notification to be sent when the order has been dispatched for delivery

      • with tracking link to 3PL site- automatically populated to show customer delivery status

  • Order Delivered

    • Ability to send Order delivered notification on the Email

      • Notification to be sent when the order has been delivered to the customer

  • Order Cancelled

    • Ability to send Order cancelled notification on the email

      • Notification to be sent for Order cancelled

        • Notification to be sent based on the order being partially cancelled

  • Order Return/Refund

    • Ability to send Order Return/Refund notification on the email

      • Notification to be sent based on the order being returned or refunded

        • Notification to be sent for Order partially Returned/Refunded

Mandatory

NEW-448

NEW-449

 

Subscription Notifications

Email

NEW-NOT-004

The system requires an ability to send notification related to subscriptions. Following are the key requirements:

  • Opt-In-confirmation to new subscriber

    • Ability to send email notification as opt-in confirmation for being a new subscriber

  • Notify Me: Availability Notification

    • Ability to send email notification when a user subscribed for an out of stock/unavailable becomes available

    • Update the Customer when the item is back in stock

      • This needs to link to CDXP so that email can be sent to the customers from CDXP once the item is back in stock

Mandatory

NEW-450

Cart Abandonment

Email

NEW-NOT-005

The system requires an ability to send Cart abandonment notifications. Following are the key requirements:

  • Cart Abandonment

    • Generate a notification for a Cart that was abandoned by the Customer and didn’t proceed to checkout

      • An email notification to be sent with Cart details in order to recover the cart from being abandoned

Mandatory

NEW-451
NEW-452
NEW-453
NEW-454

Notifications via SMS

SMS

NEW-NOT-006

The system requires an ability for the Customer to receive notifications via SMS. Following are the key requirements:

  • Order states notification via SMS

    • An ability to send SMS notification to the Customer for the following order states

      • Order confirmation

        • A confirmation SMS notification should be triggered once the user reaches Thank You page

      • Order Dispatch

        • With tracking link to 3PL site- automatically populated to show customer delivery status

      • Order Delivered

  • Account related notification via SMS

    • An ability to send SMS notification to user for the following account related actions

      • OTP Password for Sign up Verification

      • OTP for Password Recovery

      • OTP for Phone number change

         

Mandatory

NEW-455
NEW-456
NEW-457

Configuring Push notifications on Account

Push Notifications

NEW-NOT-007

The system requires an ability to generate push notification on the Web. Following are the key requirements:

  • An ability to generate Push notifications for the following:

    • Marketing Messages

    • Order Dispatch

    • Cart Abandonment

Mandatory

NEW-481

NEW-482

 

Survey Notifications

Web Layer

NEW-NOT-008

The system requires an ability to generate Survey notifications to the Customer. Following are the key requirements:

  • Post Purchase Customer Survey

    • An ability to generate Survey notification once the customer has purchased a product or completed an order

  • Browser Customer Survey

    • An ability to generate Survey notification for the customer who are browsing through the Website and yet to make a purchase

Note: These surveys are currently enabled by Exponea

Mandatory

 

Requirement Category - Marketing Notifications

Req. ID

Requirement

Sub-Group

Sub-Req. ID

Sub-Requirement

Priority

Req. ID

Requirement

Sub-Group

Sub-Req. ID

Sub-Requirement

Priority

NEW-458

Abandoned Carts configuration

Cart Abandonment

NEW-ACB-001

The system requires an ability to generate marketing notification for Cart Abandonment. Following are the Key requirements:

  • Cart Abandonment Storage

    • An ability to generate a notification for an Abandoned Cart stored.

      • Definition of Abandoned Shopping Cart: A cart created or updated recently without completing checkout within a given time.

Mandatory

NEW-459
NEW-460
NEW-461

Cart Abandonment Triggers

Cart Abandonment

NEW-ACB-002

The system requires an ability to configure Cart Abandonment rules. Following are the key requirements:

  • Configuring Cart Abandonment

    • An ability to configure Cart Abandonment for the following:

      • Cart Abandonment Time

        • Time to qualify a cart as abandoned (to be configured via CDXP)

      • Cart Abandonment Mail Triggers

        • Triggers to send the Abandoned Shopping Cart notification should consider if another notification was sent recently (to be configured via CDXP)

      • Cart Abandonment Mail Frequency

        • Abandoned Shopping Cart notification frequency (to be configured via CDXP)

           

           

Secondary

 

Requirement Category - Immersive Experience

Req. ID

Requirement

Sub-Group

Sub-Req. ID

Sub-Requirement

Priority

Req. ID

Requirement

Sub-Group

Sub-Req. ID

Sub-Requirement

Priority

NEW-475

AR solution via Tangiblee

Virtual Try On

NEW-IEX-001

The system requires an ability to have integration of Virtual Try on in the website. Following are the key requirements:

  • Ability to Integrate Virtual Try on Feature from Tangiblee to enable VTO experience 

  • Ability for the Customers to see what a product will look on themselves without leaving the product page.

Mandatory

NEW-476

Live Selling  

Bambuser

NEW-IEX-002

The system requires an ability to have Live selling of the products on the website. Following are the key requirements:

  • Integration with Bambuser for Live selling on the website

    • Ability to have 1-to-1 and 1-to-Many Live sessions on the Website

  • Ability to include streaming on Social Media platforms in real time as well as Website

Mandatory

NEW-477

Subscription service

TBC

NEW-IEX-003

Ability to enable a subscription model for customers to try new jewelry based on business rules 

Secondary

NEW-478

Marketplace

TBC

NEW-IEX-004

Ability to integrate with 3rd party marketplaces for product feeds, inventory management and purchase/customer information 

Secondary

NEW-479

Augmented Reality 

TBC

NEW-IEX-005

Ability to provide real time AR features for customers on any device 

Secondary

NEW-480

iPad sales in store 

Omni Channel Sales 

NEW-IEX-006

Ability to process sale and payment via tablet in store for products not available in that store

Mandatory

NEW -483

Cross Border eCommerce

Cross Border

NEW-IEX-007

Ability to ship cross border from KSA to other GCC countries including Qatar, Kuwait & Bahrain. Requires customs duty calculation and shipping integration with customs invoice

Note: Cross border deliveries will require HS Codes for customs

Secondary

 

Requirement Category - Interfaces

Req. ID

Requirement

Sub-Group

Sub-Req. ID

Sub-Requirement

Priority

Req. ID

Requirement

Sub-Group

Sub-Req. ID

Sub-Requirement

Priority

NEW-049
NEW-050
NEW-051

eCommerce Interfaces

eCom

New-IFC-001

The system requires an ability to have an ecommerce interface for Product Information Management. Following are the key requirements:

  • An ability to display the following on the feed:

    • Products & Catalogs

      • Online Assortment including Master Data and Catalog information

    • Ability to make eligibility check on SKU level for Voucher codes and Promotions.

      • A checkbox to apply on Product to let the system know if the Product is eligible for Vouchers and Promotions

Note: PIM to be done by Plytix

Mandatory

NEW-052
NEW-053
NEW-054
NEW-055
NEW-056

NEW-058

Order Interfaces

OMS

NEW-IFC-002

The system requires an ability to have interface for Order management. Following are the key requirements:

  • Delivery Options

    • Available delivery options for a particular product or an order ( e.g. Backorder(Made to Order) vs standard delivery)

  • Stock

    • Stock Movement/Updates

  • Availability/ATP

    • API/Real-time Call for ATP (available to promise)

  • Order Status

    • Orders Status Update- Accepted, dispatched, delivered, cancelled etc..

  • Order/Return data

    • a) Captured orders (via batch or API call), including price, discounts, items, qty, services

      b) Delivery details including name, address

      c) Items purchased and any associated services

      d) Payment information Pre-Paid/COD/BNPL

      e) Selected scheduled/planned delivery (date/time) for an order

      f) Channel ID

      g)Fulfilling site

  • Return/Refund

    • Get Return order and receiving return items/refunds - ref business process flows

Note: Order Management to be carried out through FLOW OMS

Mandatory

NEW-072

Placeholder for image assets

CDN

NEW-IFC-002

The system requires an ability to have placeholder for image assets. Following are the key requirements:

  • Loading image assets will show a generic animation while loading the image assets is in progress, placeholder image in same size, maybe low quality picture or just same loading animation for all

 

Mandatory

NEW-074
NEW-075
NEW-076

CMS management

CMS

NEW-IFC-003

The system requires an ability to manage CMS. Following are the key requirements:

  • CMS Content

    • In scope: workflow for CMS Content: Any labels, messages, text elements shown by each Country Site and brand should be editable in their appearance.

  • CMS Workflow

    • Workflow for content and translation Review, Approval, Publishing to Target environment:

  • General

    • Content should not be hard coded. Content needs to be exchangeable

       

       

Mandatory

NEW-073

Preview feature

CMS

NEW-IFC-004

The system requires an ability to have Preview feature for CMS. Following are the key requirements:

  • Schedule publishing any site content (Taxonomy, Campaign, Product Mapping, Product Content, Static Content, etc.).

  • Above mentioned content should have a start date and end date configuration that will allow automatic publishing and unpublishing.

  • Preview site based on date selection (i.e.: promotion preview after start date)

Secondary

 

Requirement Category - Customer Order Management

Req. ID

Requirement

Sub-Group

Sub-Req. ID

Sub-Requirement

Priority

Req. ID

Requirement

Sub-Group

Sub-Req. ID

Sub-Requirement

Priority

NEW-466

NEW-467

 

Home Delivery Dispatch 

OMS

NEW-OMS-001

The system requires an ability to process Home delivery dispatch. Following are the key requirements:

  • Customer places an order

  • OMS to Add orders to Order well (Order Queue)

    • Data for Customer delivery sent to schedule 3PL delivery based on Customer Promise

    • OMS to send Order information to CEGID about Order Creation

  • OMS to Generate Picklist

    • Alert needed. Rules needed to prioritise picks for Customer Order and match the ‘Customer delivery date’

  • OMS will notify to Pick Order

    • Ability to print or use App and scan to order

    • Ability to pick by order or SKUs required

  • Check Availability of Items

    • In case All Items are available

      • The order status will be updated to
        Ready for Dispatch on OMS

      • OMS will Trigger AWB (Airway Bill) Creation

    • In case there are Items Unavailable

      • Mark Scratch item(s) and fulfill order

        • Mark as scratch pick &
          re-routing logic invoked
          Rule based on fulfillment
          locations

    • Order cannot be fulfilled as the item is not available in any location

      • In case an order cannot be fulfilled, The CSR will contact customer to advise of change and cancel the Order.

  • OMS to Generate AWB (Airway Bill)

    • Send Delivery Data

    • Should contain tracking link,

    • Tracking ID will direct to 3PL site

    • If order in blocked status due to cancellation, then alert to ensure physical dispatch prevented

    • System will decide 3PL

    • Tracking URL and data sent to OMS

  • Once the Order is Ready for dispatch, the order is sent for dispatch

    • OMS to update Order status to Dispatched

      • OMS to handover stock ownership to 3PL

        • Ability to scan AWB to auto dispatch or bulk dispatch of orders

      • Triggers email to customer with tracking link

      • Send Dispatch SMS via OMS with tracking link

      • Information sent to CEGID for Goods Dispatched

        • Goods dispatch trigger inventory & Sales posting in ERP for pre-paid orders in CEGID

 

 

Mandatory

NEW-466

NEW-467

NEW-468

 

Home Delivery Dispatch - HD to Customer

OMS

NEW-OMS-002

The system requires an ability to track delivery to Customer. Following are the Key requirements:

  • 3PL to collect customer order from the Fulfilling and attempt to deliver to the Customer

  • Delivery Attempt Successful - In case of successful delivery attempt

    • 3PL to obtain Customer signature and Update status

      • 3PL to collect cash incase of COD

    • 3PL to update L’azurde about successful delivery

    • OMS to receive order status delivered

      • OMS to send order status delivered to CEGID

        • Assume near real time update.
          Delivered status update will trigger revenue recognition for COD orders

    • Send Delivered Email to the Customer

      • Tax invoice via Link in Account

  • Delivery attempt Unsuccessful - In case of unsuccessful delivery attempt

    • 3PL to make multiple attempts as per contract

      • In case of successful delivery on later attempts, successful delivery flow to be repeated

    • If the delivery still fails

      • OMS to receive delivery status Failed

      • OMS to provide instruction to return order to Fulfilling Site

        • Return process flow to start from here

      • OMS to create Return order and update CEGID

      • OMS to send email to Customer of failed delivery

 

NEW-466

NEW-467

NEW-470

 

Home Delivery Dispatch - Fulfillment through Multi Site - Split Shipment

OMS

NEW-OMS-003

The system requires an ability for the order to be fulfilled through Multi site. Following are the key requirements:

  • Picking up Items from Multi Site(s)

    • OMS to create Stock Order request

      • SO created per fulfilling site. OMS to select consolidating site and fulfilling sites based on sourcing logic

      • OMS to send Order detail to CEGID about Order created

        • Order detail should include respective fulfilling sites in order create

    • OMS to pick item(s) from the site

    • Print Delivery Note for shipping, pick on hand held device ( scan ). May also be email received

    • Item availability check - All items available

      • In case all items are available - OMS to Update order to ready to dispatch and Generate AWB

        • Tracking Link per shipment to be created

      • Stock ownership to be handover to 3PL

      • OMS to

        • Dispatch Items

          • Dispatch by scanning barcode to auto dispatch on system. Trigger dispatch notification to customer with tracking link.

        • Send information to CEGID that goods are dispatched from Site inventory

          • Goods dispatched from site inventory
            Invoice & sales recognition per
            fulfilling site. Need to reference original order for reconciliation , sales posting.

    • Item availability check - All items not available

      • Mark Item(s) as scratch on OMS

        • OMS , user will mark as scratch pick & re-routing logic invoked

      • In case order cannot be fulfilled CSR will advise customer of change and Order will be cancelled

      • In case the order can be fulfilled, OMS will add the order into the order well and repeat process as mentioned above.

    • Delivery process followed as mentioned in NEW-OMS-002

Note: Split billing assumed per fulfilling location under the original order ID

Mandatory

NEW-471

Made to Order

OMS

NEW-OMS-004

The system requires an ability to have Made to Order (Back Order). Following are the key requirements:

  • An ability for the customer to make Back orders (Made to Order)

  • Review order and send to production coordinator

    • As per Master data created by finance including weight of MTO

  • SC Planner to create Stock Order in system for MTO

    • As per Master data created by finance including weight of MTO with agreed tolerance

  • Production Order is created in system by BAN and Production team starts working on the product

  • Once the Product is manufactured, it is sent to Quality control

  • Once QC is passed, CEGID sends the product to Fulfilling Site

    • Product is sent directly to Fulfilling Site

  • Once the product is received at Fulfilling Site, CEGID updates the system that product is at Fulfilling Site and communicates to OMS

  • OMS Picks and packs order

  • OMS updates the status to Ready to Dispatch

  • OMS then generates AWB and handover stock ownership to 3PL

  • Once the Order has been collected by 3PL, OMS updates the order status to Dispatched and updates CEGID about Order dispatched

    • Invoice and sales recognition is also done

  • Delivery process followed as mentioned in NEW-OMS-002

Secondary

NEW-472

Click & Collect 

OMS

NEW-OMS-005

The system requires an ability to have Click and Collect order on the website. Following are the key requirements:

  • Click and Collect Order

    • The customer to be able to select Click and Collect order type while placing order and be able to select Store location.

    • On successful order placement, System notifies CEGID about Order created

    • OMS adds the order to the Order queue and produces pick list

      • Alert via OMS App on handheld device. Picking via OMS App

    • OMS picks order and checks for item availability

      • Print pick Note for May also be email received OMS led activity.

    • Check Items Availability - All items available

      • OMS to check if the order is part of Multi site fulfilment.

        • In case yes, OMS will create STO (Stock transfer order) to fulfilling site(s)

          • Follow Multisite fulfillment process in NEW-OMS-003

      • In case, the order is not part of Multi site fulfilment, OMS will pack order and have it sent to dedicated area

      • OMS to update Order status to ready to collect and send dispatch/SMS confirmation email

        • SMS and Email notification to contain QR code for in-store collection

    • Check Items Availability - All items not available

      • Follow Multisite fulfillment process in NEW-OMS-003

      • Once the order has been collected in the Consolidated area, OMS will update status to ‘Ready to Collect’ and send notification to customer.

  • Collection in Store

    • Customer enters the store and notifies Store operator about the Click and collect order

    • Store operator to find order details by scanning QR code or manually input Order number/customer information. This would pull order detail onto POS

    • Store operator will retrieve the item from location

    • Based on SOP the Store operator may or may not allow the customer to try on the product

    • Store operator will try to attempt to upsell more items to the customer

      • In case they become successful in upselling items, the store operator will scan items to order

      • Adding items to C&C order will update original order value /items purchased

    • Store Operator to transact the order on POS

      • Take additional payment (in case of upsell) if required and completed transaction receipt generated in store

    • OMS to update order status to collected

    • OMS to send Order collected status to CEGID and CEGID to send collected email/SMS to customer with tax invoice link

      • CEGID to Goods dispatch trigger inventory & Sales posting in ERP.
        Sale is posted to collection store

    • Customer wants to make return

      • In case a customer wants to make a return of the order, the store operator will trigger the return flow (See Return flows) and CEGID will send return email/SMS to customer

Customer hasn’t collected Order yet:

Ability to add a rule alert if order is not collected within 48 hours of ready to collect notification to trigger alert to store & Ops for tracking and follow up, system generated alert also to be sent to the customer for reminder.

Mandatory

NEW-473

Reserve & Collect

OMS

NEW-OMS-006

The system requires an ability to have Reserve and Collect order on the website. Following are the key requirements:

  • Reserve and Collect Order

    • The customer to be able to select Reserve and Collect order type while placing order and be able to select Store location.

    • On successful order placement, System notifies CEGID about Order created

    • OMS adds the order to the Order queue and produces pick list

      • Alert via OMS App on handheld device. Picking via OMS App

    • OMS picks order and checks for item availability

      • Print pick Note for May also be email received OMS led activity.

    • Check Items Availability - All items available

      • OMS to check if the order is part of Multi site fulfilment.

        • In case yes, OMS will create STO (Stock transfer order) to fulfilling site(s)

          • Follow Multisite fulfillment process in NEW-OMS-003

      • In case, the order is not part of Multi site fulfilment, OMS will pack order and have it sent to dedicated area

      • OMS to update Order status to ready to collect and send dispatch/SMS confirmation email

        • SMS and Email notification to contain QR code for in-store collection

    • Check Items Availability - All items not available

      • Follow Multisite fulfillment process in NEW-OMS-003

      • Once the order has been collected in the Consolidated area, OMS will update status to ‘Ready to Collect’ and send notification to customer.

  • Collection in Store

    • Customer enters the store and notifies Store operator about the Reserve and collect order

    • Store operator to find order details by scanning QR code or manually input Order number/customer information

    • Store operator to import order details on POS and retrieve the item from location

    • Based on SOP the Store operator may or may not allow the customer to try on the product

    • Store operator will try to attempt to upsell more items to the customer

      • In case they become successful in upselling items, the store operator will scan items to order

      • Adding items to R&C order will update original order value /items purchased

    • Store Operator to transact the order on POS

      • Take Payment for R&C Order Receipt from Till showing order number (Online)

    • OMS to update order status to collected

    • OMS to send Order collected status to CEGID and OMS/Klaviyo to send collected email/SMS to customer with tax invoice link

      • CEGID to Goods dispatch trigger inventory & Sales posting in ERP
        Sale is posted to store. Channel is eCom , Profit Centre is Store
        For items added to basket, split sales posting to show upsell items vs original Online Order

    • Customer wants to cancel

      • In case a customer wants to make a cancellation of the order, the store operator will trigger the cancellation flow and OMS/Klaviyo will send cancelled email/SMS to customer

Customer hasn’t collected Order yet:

Ability to add a rule alert if order is not collected within 48 hours of ready to collect notification to trigger alert to store & Ops for tracking and follow up, system generated alert also to be sent to the customer for reminder. For a Reserve and Collect order, set a rule to auto-cancel the order after x number of days if the Customer hasn’t collected the order.

Secondary

NEW-469

Order Cancellation 

OMS

NEW-OMS-007

The system requires an ability for the Customer to request cancellation for their order. Following are the key requirements:

  • Order Cancellation

    • The customer will contact Call center to request cancellation of Order

      • Full Cancellation

      • Partial Cancellation

    • The CSR to check order status on OMS

    • If the order is in Pick/Pack status, the CSR will process Return flow (See Return flows)

    • If the order is not in Pick/Pack status yet, the CSR will Cancel an Item or Order on the OMS

      • Partial order cancellation triggers
        order recalculation
        Item(s) cancelled, stock released

    • OMS will trigger refund to customer of value cancelled

      • In case of COD, the CSR will capture Bank details of Customer and process refund

    • OMS to receive order status update

      • Partial order cancellation triggers order data update including amount
        to be collected if changed

    • OMS to send Cancellation Email/SMS to the Customer

      • If partial, should show only item cancelled and order updated on my account

    • OMS to send order cancellation update to CEGID

      • Partial cancellation needs to update Sales order value to ensure accurate invoice

    • CEGID to inform WH team of the cancellation

    • CEGID to release Order Cancelled
      Inventory to ATP

Mandatory

NEW-469

Order Cancellation - Out of stock order cancellation via Call Center

OMS

NEW-OMS-008

The system requires an ability to cancel orders that are out of stock. Following are the key requirements:

  • Fulfilling Site to identify Out of stock shortages

  • Check if the Order is unable to fulfill

    • Order able to Fulfill

      • Repeat flow mentioned in NEW-OMS-001 for HD Dispatch

    • Order Unable to Fulfill

      • Fulfilling Site to notify Call center about out of stock order

      • Call center to contact customer to advise about the order

      • Call center to cancel order on OMS

        • Partial order cancellation recalculates order value Item(s) stock released

      • OMS to trigger refund to customer of Value cancelled

        • Refund process of Card

      • OMS to receive Order status update

        • Partial order cancellation triggers
          order data update including amount to be collected if changed

      • OMS to send cancellation email to customer with details

      • OMS to send information to CEGID of Cancel order or item from order.

        • CEGID to release cancelled Inventory
          to ATP and instruct Fulfilling Site to put away stock.

Mandatory

NEW-474

Sourcing logic and business rules

OMS

NEW-OMS-009

The system requires an ability to source logic and business rules for OMS. Following are the key requirements:

  • Minimize split for single order (cost)

    • Value: Highest

      • Configurable maximum number of splits allowed for each order. For cross border, we will split shipment

  • Closest Location to customer (Experience)

    • Value: High

      • Geographical location to delivery. Will source from closest location to
        meet customer promise

  • Highest Inventory(cost)

    • Value: Medium

      • Prioritize sources by stock availability

  • Shipping Zone

    • Value: Low

      • Where we may wish to only ship from specific region e.g. for Western province, only choose stores in Western region

  • Order capacity

    • Value Medium

      • Configure Max orders per day by site and re-route orders once capacity reached to alternative site based on above rules.

Mandatory

NEW-484

Online Sale In-Store

OMS

NEW-OMS-010

The system requires an ability to process Online sale in store. Following are the key requirements:

  • Store colleague creates an order on the website , via a tablet/mobile device.

  • Store will login to website to identify store creating order.

  • At point of purchase, they will select ‘In store payment’ as a payment method.

  • Order is created in Cegid/OMS as pending payment ( like a Reserve & Collect order)

  • Store colleague imports the order to POS . ( Using order number )

  • Store colleague takes payment using available payment methods in store via POS.

  • Order is updated in Cegid , OMS & eCom platform as paid and will follow the normal dispatch & delivery process.

    1. Include store where transaction was made in order data from eCom to POS/Cegid/OMS

    2. Includes capture of payment & method as well as all other expected order details ( name , address etc.)

    3. Order should be blocked until payment has been made

Secondary

 

Requirement Category - Returns Management

Req. ID

Requirement

Sub-Group

Sub-Req. ID

Sub-Requirement

Priority

Req. ID

Requirement

Sub-Group

Sub-Req. ID

Sub-Requirement

Priority

NEW-462

Remote returns

Website

NEW-RET-001

The system requires an ability for customer to process returns from the Website. Following are the key requirements:

  • Returns via Website

    • Customer to be able to process returns for an order through the My Orders section on My Account

    • OMS will check for Return Eligibility of the Product (30 days from the Product Delivered date)

      • In case the Product is eligible the Website will show Return Products link

      • In case the Product is not eligible the Return Products link will be disabled

    • Product is Eligible for Return

      • OMS will create Return Order for Item(s) selected and Update CEGID

        • Customer selects item(s) and
          reason for return. Customer selects pick up date

      • CEGID to create RO against original Order

      • OMS to create return via 3PL

        • Return data to schedule collection
          Manual creation of AWB irequest

      • 3PL to schedule pick up of item from Customer’s location

        • 3PL will bring RAWB on collection for tracking 3PL to send tracking link to OMS

    • Product is Not Eligible for Return

      • Customer to contact Customer Support

  • Receive Return Item in Fulfilling Site

    • Fulfilling Site to receive good from 3PL

    • Fulfilling Site to check if the order was a failed delivery

      • Not a Failed Delivery

        • Send the Item for QA check

          • QA check pass

            • Fulfilling Site to receive against RO on OMS

          • QA check Fail

            • Update the Call center about rejected Return

            • Call center to contact Customer and provide explanation

            • OMS to arrange returns for Customer

            • OMS to Cancel RO

            • CSR to Cancel RO on OMS

            • OMS to send Cancel return information to CEGID

      • Failed Delivery

        • Receive against Return order

          • AWB contains original SO to identify order if List of failed deliveries available in OMS

    • OMS to update inventory on CEGID for Return

      • Should post to Blocked
        location until disposition of
        stock determined

    • CEGID to trigger sales reversal

    • OMS to check Original Tender type

      • Cash

        • System trigger via email to
          alert CS to initiate call to
          obtain bank details

        • Initiate Bank transfer

      • Card

        • OMS to Trigger refund

      • BNPL

        • OMS to notify BNPL scheme provider to refund and or stop additional payments

      • OMS to return email and invoice to customer

 

Mandatory

NEW-463

Remote returns

Customer Service

NEW-RET-002

The system requires an ability for the Customer to initiate return request via Call center. Following are the key requirements:

  • Customer calls the call center to initiate return request

    • Product is Eligible for Return

      • CSR to create RO for items selected on OMS

        • Capture reason for return

      • CSR to create Return via 3PL

        • Access 3PL calendar to schedule
          confirm requested pick up date for
          customer

      • OMS to schedule pick via 3PL

      • 3PL to pick up item from Customer’s location

    • Product is Not Eligible for Return

      • CSR to explain options to Customer

  • Product is received in Fulfilling Site

    • Fulfilling Site checks if Product came for QA or Return

      • Return

        • Fulfilling Site receive against STO on CEGID

          • Step for STOs from Fulfilling Site
            where return already
            accepted in Fulfilling Site and stock
            being returned to WH

        • CEGID updates inventory based on return

      • QA

    • Fulfilling Site perform QA Check on the item.

    • Fulfilling Site sends products to specialist to Authenticate

      • QA Fail

        • Fulfilling Site inform Call center about Rejected Returns

          • Fulfilling Site put item aside as unreturnable

        • Call center contact customer
          to explain

        • Return Item via Fulfilling Site to Customer

        • Call center cancels Return order on OMS

      • QA Pass

        • Fulfilling Site check for re-stocking fee

          • Re-stocking fee eligible

            • Fulfilling Site notifies call center about restocking fee

            • Call center calls Customer to explain

            • If Customer accepts restocking fee, Fulfilling Site update order status to return on OMS based on restocking fee applied. Move to check Original Tender Cash point

            • If Customer doesn’t accept Re-stocking fee, return the item via Fulfilling Site to the customer and update Cancel Return Order on OMS

          • Re-stocking fee not eligible

            • Fulfilling Site update order status to return on OMS based on restocking fee applied.

            • OMS updates inventory on CEGID

        • OMS to check Original Tender type

          • Cash

            • System trigger via email to
              alert CS to initiate call to
              obtain bank details

            • Initiate Bank transfer

          • Card

            • OMS to Trigger refund

            • For BNPL, alter to provider
              to amend or refund amount. Refund always via original
              payment tender type

          • OMS to return email and invoice to customer

Mandatory

NEW-464

In Store returns 

Via POS

NEW-RET-003

The system requires an ability for the Customer to return items in store via POS. Following are the key requirements:

  • Returns Items in Store via POS

    • Customer engages with Store Op to return an item

    • Store to check if Customer have Proof of Receipt

      • No

        • Store OP to Invoke receipt
          not present SOP

      • Yes

        • Store OPs to check customer order details

          • Validate vs returns policy
            Order or Mobile number search to Online order - Displays order details( Import Order)

          • Accept / return based on returns policy. Exceptions to return policy managed locally at store. Detailed SOP required. Exchange via Return & Re-Order Bundle rules to be applied

        • Store OPs to determine if QA check is required

          • Diamond product authentication may require product to be sent to HQ before refund approved
            Manual process - SOP based

        • QA Required

          • Fulfilling Site Ops to create RO on CEGID

            • Inventory posted to receiving site and placed in blocked location pending STO to factory

          • CEGID to Create RO for QA against original order on OMS

            • CEGID to create STO to WH if necessary

            • Business rule to return all
              ecom items to WH. System generated delivery note for items being returned.
              SOP for daily returns TBC

          • RO to indicate QA required

          • Repeat steps mentioned in ‘Product received in Fulfilling Site flow in NEW-RET-002’

        • QA Not Required

          • Store OPs to create return &
            process partial or full refund

            • Process against original
              online order Business Rules for refund including restocking fee

          • POS to check Original Tender type

            • Cash

              • Cash refund from Cash Register

            • Card

              • OMS to Trigger refund to original card payment

            • BNPL

              • OMS to notify BNPL scheme provider to refund and or stop additional payments

          • OMS to return email and invoice to customer

Mandatory

NEW-465

Failed Deliveries from 3PL Returns

Fulfilling Site

NEW-RET-004

The system requires an ability to cater Failed Deliveries from 3PL Returns. Following are the Key Requirements:

  • Fulfilling Site to check if the order was a failed delivery

    • Not a Failed Delivery

      • Send the Item for QA check

        • QA check pass

          • Fulfilling Site to receive against RO on OMS

        • QA check Fail

          • Update the Call center about rejected Return

          • Call center to contact Customer and provide explanation

          • OMS to arrange returns for Customer

          • OMS to Cancel RO

          • CSR to Cancel RO on OMS

          • OMS to send Cancel return information to CEGID

    • Failed Delivery

      • Receive against Return order

        • AWB contains original SO to identify order if List of failed deliveries available in OMS

  • OMS to update inventory on CEGID for Return

    • Should post to Blocked
      location until disposition of
      stock determined

  • CEGID to trigger sales reversal

  • OMS to check Original Tender type

    • Card

      • OMS to Trigger refund

    • BNPL

      • OMS to notify BNPL scheme provider to refund and or stop additional payments

    • OMS to return email and invoice to customer

Mandatory

 

Requirement Category - Website Tools

Req. ID

Requirement

Sub-Group

Sub-Req. ID

Sub-Requirement

Priority

Req. ID

Requirement

Sub-Group

Sub-Req. ID

Sub-Requirement

Priority

NEW-033

Analytics

Reporting

NEW-ANL-002

  • An ability for the system to be integrated with the following:

    • Power BI

    • Google Analytics (GA-4)

    • Facebook ADs Manager

    • Google AdWords

Mandatory

NEW-042

IP Redirection

IP Forwarding

NEW-IP-001

The system requires an ability to provide IP redirection to the Users. Following are the key requirements:

  • User to be automatically redirected to the related country Site Redirection (Based on IP) on the first visit.

  • Country site change by user (from Header Navigation) will be stored at cookie level.

  • Future visits will redirect to the site selected by the user (if different than default).

Mandatory

NEW-043

GDPR Cookie Policy Banner

Cookie Consent Manager

NEW-COK-001

The system requires an ability to require cookie consent. Following are the key requirements:

  • An ability to track cookies and request customer cookie consent through GDPR Cookie Policy Banner

Mandatory

NEW-044 & 045

GA-4 Integration

Google Analytics 4

NEW-GA4-001

  • Ability to integrate GA-4 into the L’azurde Website and GA-4 tagging to cover flow end to end

  • Ability to track the following:

    • User attributes (logged / not logged)

    • Logging Banner Impressions

    • Measuring Product Impressions on the: PLP / CLP, Search Results (search string), Recommended products widgets, Shop the look

    • Logging product click from Listing Page to Product Details Page

    • Measuring a view of the Product Details Page

    • Measure adding a product to shopping cart

    • Measure removing a product from shopping cart

    • Checkout steps

    • Purchase

      • Abandoned Cart Restore

Mandatory

NEW-046

Facebook/Instagram JS

Snippets

NEW-FBI-001

The system requires an Ability to integrate Facebook/Instagram JavaScripts into the L’azurde Website. Following components are required:

  • Integration of Facebook/Instagram JS at the following components

    • Product Catalog

    • FB Pixel

Mandatory

NEW-046

Product Feed

Snippets

NEW-FBI-002

The system requires an ability to integrate Facebook/Instagram JavaScripts for Product feed into the L’azurde Website. Following are the key requirements:

  • Integration of Product Feed to Social Media Platforms

    • Facebook

    • Instagram

    • Snapchat

    • Google

Template to be provided

Mandatory

NEW-047

Snap Chat JS

Snippets

NEW-SCT-001

The system requires an Ability to integrate Snapchat JavaScripts into the L’azurde Website.

  • Integration of Snapchat JS at the following components

    • Product Catalog

Secondary

NEW-048

OG Tags

Snippets

NEW-OGT-001

The system requires an ability to integrate OG Tag into the L’azurde Website. Following are the key requirements:

  • HTML Headers to include og:tags specific to Social Share:

    • Image on the aspect ratio required for Facebook share

    • Product Title

    • Product Description

    • Price

    • URL

Mandatory

 

Requirement Category - Non Functional Requirements

Req. ID

Requirement

Sub-Group

Sub-Req. ID

Sub-Requirement

Priority

Req. ID

Requirement

Sub-Group

Sub-Req. ID

Sub-Requirement

Priority

NEW-009

Data Retention and Disaster Recovery

Backups

NEW-DRD-001

The system requires an ability to accommodate Data retention and Disaster Recovery

  • An ability to restore the system to last backup in case of disaster or system failure

  • An ability to periodically backup the system

  • An ability to accommodate data retention policy to preserve data from loss

Mandatory

NEW-015

Communication Protocol – SSL/Encryption

Hosting

NEW-HOS-002

The system requires to set the following communication protocol to transmit and exchange data:

  • SSL Encryption

Mandatory

NEW-016

Performance and Load Balancing

Hosting

NEW-PAL-001

The system requires the following capabilities for Performance and Load Balancing:

  • Peak users/Site traffic/Page views

  • Concurrent users/connections support

  • Max concurrent transaction Requests

  • Catalog size

  • Average time on site

  • Page load times < 2 seconds

Mandatory

NEW-017

Peak scalability

Tech

NEW-TEC-001

The system requires the following capability for scalability in peak timings:

  • All system need to scale up quickly in cases of traffic peaks

Mandatory

NEW-018

Modern Caching Approach

Tech

NEW-TEC-002

The system requires the following capability for caching approach in the system:

  • A modern caching or no-caching approach

Mandatory

NEW-019

CSS & JS Bundling

Tech

NEW-TEC-003

The system requires the following capability:

  • Performance optimized handling of CSS and JS files

Mandatory

NEW-020

OWASP Top 10

Data Protection & Security

NEW-DPS-001

The system requires the following capability for Data protection:

  • OWASP TOP 10

Mandatory

NEW-021

GDPR

Data Protection & Security

NEW-DPS-002

The system requires the following capability for Data protection:

  • Compliant with GDPR

Mandatory

NEW-022

PCI Compliance

Data Protection & Security

NEW-DPS-003

The system requires the following capability for Data protection and security:

  • The system to be PCI Compliant via payment gateway / Storefront passing encrypted Cardholder Data to the Payment Gateway

Secondary

NEW-023

SOX

Data Protection & Security

NEW-DPS-004

The system requires the following capability for Data protection and security:

  • Compliant with SOX

Mandatory

NEW-024

ISO 9000

Data Protection & Security

NEW-DPS-005

The system requires the following capability for Data protection and security:

  • Compliant with ISO 9000

Mandatory

NEW-025

ISO 27001

Data Protection & Security

NEW-DPS-006

The system requires the following capability for Data protection and security:

  • Compliant with ISO 270001

Mandatory

NEW-026

ISO 27017-18

Data Protection & Security

NEW-DPS-007

The system requires the following capability for Data protection and security:

  • Compliant with ISO 27017-18

Mandatory

NEW-027

Testing

Development

NEW-DEV-001

Testing methods that needs to be done:

  • Functional Testing (Sprint wise, and End to End)

  • System Integration Testing

  • Performance Testing

  • Support for UAT

  • Vulnerability/penetration testing

Mandatory

OLD-007

NEW-059
NEW-060
NEW-061
NEW-062
NEW-063
NEW-064
NEW-065
NEW-066
NEW-067
NEW-068
NEW-069
NEW-070

Third Party Integrations

Integrations

NEW-INT-001

The system requires an ability for the website to integrate with third party integrations. Following are the key requirements:

Mandatory

 

Process Flows

Customer Order Management Flows

Home Delivery Dispatch

 

Order Dispatch - Home Delivery to Customer

Home Delivery Dispatch - Fulfillment through Multi Site

 

Made to Order

Click & Collect - Fulfill Order

Click and Collect - In Store Collection

 

Reserve & Collect

Reserve and Collect - In Store Collection

Order Cancellation - Via Call Center

Out of stock order cancellation via Call Center

 

Sourcing logic and business rules

Return Management Flow

Remote Returns - Website

Remote Returns - Website - Receive Item in Warehouse

Remote Returns - Via Call Center

Remote Returns - In store via POS

In store Return - Receive item in Warehouse

Failed Deliveries from 3PL Returns

 

Related content