Professional Documents
Culture Documents
Website Development SR (Unnamed)
Website Development SR (Unnamed)
Website Development SR (Unnamed)
Technical Solution
The developed website shall be based on the mother company website, such as photos,
font, style and colors, no deviation from design is accepted without granting permission.
1- Frontend Development:
The vendor company should develop front-end website based on the mother
company website.
2- Backend Development
The vendor company should provide two proposed solutions:
1- Full solution development.
2- Using online solution (SHOPIFY, ECWIL, WEEBLY), developer shall as well recommend
the package selection (for financial consideration by client).
Note: if the developer have other preference of online platforms please mention.
SCOPE OF WORK
A- Frontend Website:
1- Users Registration:
- Email
- Google account
- Facebook account
2- Website pages
1. Home
2. Navigation menu
3. Categories List
4. Search box by category, item.
5. Items Details
6. User dashboard
a. My personal info (user profile: email, mobile, birthdate, picture, gender,
cards)
b. My dashboard (canceled, confirmed, paid, history, retune, card, rating,
commants).
7. Contact Us
8. Social media linking
9. Login
3- Language:
Bilingualism Eng/Arabic (right to left language), the admin dashboard will be in
english langauge only.
4- Layout:
- Website should be responsive and easy to convert to mobile app in the
future.
- Website shall be based on the mother company website, such as photos,
font, style and colors, no deviation from design is accepted without granting
permission.
5- Website features
1. In the purchase page below buttons to be introduced
2. button “add to cart” (that will only add the item to the cart without any navigation
to any other pages), with a feedback icon (such as tick if the item is added
successfully to the cart)
3. button “checkout” (that will lead to the final purchase page)
4. the cart count shall always keep the updated count (pressing back shall not undo
the addition)
5. when mouse cursor is kept on the cart an overview of the cart shall be shown or a
small arrow with drop down menu or any other way.
6. Change the quantity at the purchase page without full refresh of the page
7. Link the matching women top or pants on same page for ordering
8. Items with different colors shall be clipped in one page with color selection for
navigation between them
9. The “on Sale” tab shall have a hidden options. where this tap shall only appear if
there is items on sale. And disappear if there is no items on sale.
10. Photos shall be selected by user from the photo’s thumbnails and displayed, the
scroll down shall control the full page.
11. Special task button for ordered items history from which the user can return or
cancel the order or change size, or raise a complaint, with time restrictions of each
function.
12. Policy setting:
13. Cancel order is not permitted after the worker placed a feedback in the system
as shipped.
14. Return/change not permitted after 2 days of delivery
15. Raise complain not permitted after 10 days of delivery
16. Where any item after 10 days of delivery considered fully satisfied
17. Customer loyalty system
a. Based on review submission
i. Each account created shall have a loyalty based on review
submissions, such that the reviews have some sort of badges granted
when they submit a certain amount of reviews, with an automated
email to congratulate them. With the option of getting a credit to use
in their next purchase that can be presented by the admin, when they
reach a certain limit, with explanatory of the levels once the
customers visit hi loyalty badge.
ii. Once the customer reaches a certain level an automated email shall
be sent to congratulate the customer and shows the amount of credit
1
won.
iii. Credit given shall have an expiry period of 4 months and shall be
deleted automatically from the system.
iv. Customers shall be emailed after 3 months to get a reminder to use
the credit, and a second email week before expiry.
Tops
Bras
Sleeveless
Short sleeve
Long-sleeve
Hoodies
Jackets
Sweater
2
Bottoms
Leggings
Pants
Shorts
3. Payments Channels
(A)Credit Card/Debit Card.
(B) Integrate the website to Paypal, Cridimax, and Benefit payment Gateways.
B. Woman
● Shows the items count of purchase in different category as shown below
4
vii. Count of navigation to website
viii. Count of purchase per country
ix. Count of most viewed women items
x. Count of men customer visits using desktops and mobile devices
xi. average items bought by customers as well as the average item
bought
xii. items count (all women items mentioned in table 1.1)
xiii. count of bras purchased
xiv. shows descending/ascending count of all items…etc
xv. count of bottoms purchased
xvi. count of leggings purchased
xvii. shows descending/ascending count of all items…etc
xviii. count of sets purchased
xix. count of bottoms bough without top vs set of same
xx. count of tops bough without bottom vs set of same
● All above mentioned can be viewed with on and off ticks in the same graph
(timeline shall be selected for x-axis as well)
● All above data shall be extractable to excel file if required for further analysis
6- Financial
● Show total amount purchased as per below items (in accordance to table
1.1)
i. Whole items
ii. Men items
● Include all value and count of men subcategory (table 1.1)
iii. Women items
iv. Include all value and count of women subcategory in (table 1.1)
v. Inventory value (at end of selected time category, according to the
sale price keeping in consideration sales value)
vi. Financial analysis
vii. Average value per customer, and total value spent by customer
according to (with the ability to select more than indicator at a time
as the lead KPI)
● Age
● Gender
● Country
● Method of payment
● Total value spent/count according to time
a. Day of week (with subcategories as mentioned in point
3.3.6.1.)
b. Time of day (with subcategories as mentioned in point
3.3.6.1.)
c. Month of year (with subcategories as mentioned in point
3.3.6.1.)
● Automatic financial reports
The automated reports shall be created and emailed to the master accounts emails and shall have the
below information (in pdf format or image)
● Daily report
5
○ Total value of purchases (with gender breakdown)
○ Total count of purchases (with gender breakdown)
○ Total value of sales item purchases (with percentage of
total sales value)
○ Total count of sales item purchase (with percentage of
total sales)
○ Number of items out of stocks
○ Number of items out of stock without restock order (with
reason)
○ Number of Low items on low stock
○ Number of items on low stock without restock order (with
reason)
○ Number of returned items
● Weekly report
○ Total value of purchases (with gender breakdown)
■ Show breakdown of days
○ Total count of purchases (with gender breakdown)
■ Show breakdown of days
○ Total value of sales item purchases (with percentage of
total sales value)
○ Total count of sales item purchase (with percentage of
total sales)
○ Number of items out of stocks
○ Number of items out of stock without restock order (with
reason)
○ Number of Low items on low stock
○ Number of items on low stock without restock order (with
reason)
○ Total number of returned items (with gender
breakdown)
○ Total value of inventory
○ Total value of accumulated purchases from start of
month (with average in brackets)
○ Total count of accumulated purchases from start of
month (with average in brackets)
○ Best 20 most sold items
○ Worst 20 unsold items
○ Total number of loyalty credit given
○ Total number of loyalty credit expired
○ Total number of loyalty credit consumed
● Monthly report
○ Total value of purchases (with gender breakdown)
○ Total count of purchases (with gender breakdown)
○ Total value of sales item purchases (with percentage of
total sales value)
○ Total count of sales item purchase (with percentage of
total sales)
6
○ Number of items out of stocks
○ Number of items out of stock without restock order (with
reason)
○ Number of Low items on low stock
○ Number of items on low stock without restock order (with
reason)
○ Total number of returned items (with gender
breakdown)
○ Total value of inventory (with gender breakdown)
○ Total value of accumulated purchases from start of
month (with average in brackets)
○ Total count of accumulated purchases from start of
month (with average in brackets)
○ Best 20 most sold items
○ Worst 20 unsold items
○ Total number of loyalty credit given
○ Total number of loyalty credit expired
○ Total number of loyalty credit consumed
7- Security
Plan of website security (option for third-party protection), as well as the security
of payment and customers cards.
8- Receipt creation
○ Each purchase shall have a unique receipt number
○ Automated receipt shall be created and saved on website for customer
access (with link in purchased email)
7
○ Creation of pending shipping order with individual sticker print out (in
which at the start of the day the worker can print the list of yesterday
orders and fulfill them along with any unfulfilled orders, with an individual
print receipt)
Note: receipt content shall be discussed with client
9- Shipping
Compatibility with the shipping agent plug-in
○ Calculations of the shipping rates (for each user)
○ Estimated shipping date
○ Show tracking of the shipment (connection with shipping agent)
○ Show tracking of returned orders (connection with shipping agent)
○ API integration with the shipping companies
After order fulfillment the customer shall receive an email confirming the fulfillment
with a link in which the customer can review the order and write a comment, then
the admin shall approve the review for final submission, with the ability of the admin
to post a reply to the comment.
11- Marketing
- Admin controller can have a control over marketing options such as front page
offers, newsletters (mass emailing option), bought together options.
- Facebook and instagram compatibility to link our items to these channels and
have online purchase via these two channels.
- Provide website SEO plan based on expected results.
- Ability to measure the marketing campaign effectiveness key parameters such
as promo codes, and conversion rates
C- PROJECT TIMELINE
9
● The contract should submit a clear milestones for project tasks delivery.
● Clear What-if milestones delay.
Phase
Database
Coding
Testing
Deployment
Weeks 1 2 3 4 5 6 7 8 9
TIMELINE
D- Training plan
● Contractor should submit full training plan for all employees.
● Contractor should submit full training plan for any new employee.
E- Maintenance plan
Provide the maintenance plan with optional price for 2 years maintenance plan:
The plan should contain the following:
○ System troubleshooting
○ Reports manage/create
○ Server maintenance
○ Website performance testing
○ Server Daily backup
F- Documents submissions
Contractor should submit full documentation for the system:
- Admin panel setting.
- Admin panel features.
- How to use admin panel.
- Admin panel FAQ.
G- Coding submissions
- Contractor should submit a DVD with full source code
- Usernames and passwords
10
H- Project Change Control Procedure
Any contract is subjected to expected and unexpected variations and the below are
the guidelines to manage the variations in the below manner
● A Project Change Request (PCR) will be the vehicle for communicating change. The
PCR must describe the change, the rationale for the change, and the effect the
change will have on the project.
● The designated Project Manager of the requesting party will review the proposed
change and determine whether to submit a request to the other party.
● The client shall be eligible for 3 times review of any submission of the developer work
and request of any minor changes without extra fees, and any major changes shall
be subjected to variation policy below as mentioned below.
● Any major variation requested by the client shall be discussed and the developer
shall submit the variation value in number of extra hours and delay in timeline if the
change have a schedule impact as well.
● Note-1: Minor changes definition (any change that doesn’t exceed 6 hours of work)
● Note-2: Developer shall provide price of extra hours fees
● A written Change Authorization and/or PCR must be signed by both parties to
authorize implementation of the investigated changes.
ASSUMPTIONS
● The Contractor agrees to hold all details related to product development for the
Client as proprietary and confidential. No aspect or detail or the product being
developed or any assets or information provided to the Provider by the Client shall be
disclosed to any party without prior written consent from the Client.
● The Contractor is the application source code and application API and database.
● The Contractor has the full right to create his own Apple and Google development
accounts and transfer the full application from Contractor accounts to Client
accounts.
● The Client has the full right to create his own hosting server(s) and transfer the full
application from Contractor account to Client account.
● The Contractor agrees to transfer ownership of all completed work to the Client upon
cancellation of this agreement, once payment has been made pursuant to the terms
of this agreement.
● The Contractor will be responsible for any application update, crashes or database
down with Yearly Full Support and Maintenance.
11