Please enable JavaScript.
Coggle requires JavaScript to display documents.
Simple Online Shop - Coggle Diagram
Simple Online Shop
User Experience
Order process
The order process needs to be easy to learn and extremely useable. The user needs to be able to purchase what they want easily; the goal of the process is to sell product to the user, hence it should be as easy as possible for them to buy it. Additionally, the user should be provided with full information around the purchase (prices, images, names of items, qtd ect. ect.)
Organization/Search
As this will be a simple shop with only a few items of a few sizes, organisation will be a non-issue. Searching additionally will be mostly redundant as everything the user needs will be either on the shop page or on their purchase history page. Despite this, the shop will need to be kept simple and easy to understand.
Nav
Users need to be able to easily and efficiently navigate between purchase history, the shop, their profile and the various products. Navigation must be simple and easy.
Product Placement
Having recommendations for popular items on the home menu, i.e. encouraging users to buy the most purchased item.
Remember Me (auto log in, credit cards ect.)
Users could be provided with the capacity to enable auto login/'save my card'. They should be able to enable the weboage to save their details such as username, password, email and payment details in order to improve effectiveness.
Data
Products
Product name, cost to produce, sellingp price, any customisation, descriptions, images(?), in house stock
Customers
Username, pswd, full address (for delivery), email, specific purchase history (linked to the individual Cid)
Sales
Purchase History (What, when, price, who, customised how)
Recipt
Receipt number, payment method, billing address, date, customer receipt belongs to
Security
All sensitive data (credit card num, pswd ect.) will be hashed to provide better security. Additionally, any data that doesn't need to be saved will not be harvested.
Devices
-
-
-
Fully accessable to individuals with sight imparements (completely readable to all people + compatability with screen readers).
Functionality
Order history
A full order history will be recorded for administrative purposes and for individual customer record. This should be included to assess sales for the owner of the store and to keep a record of receipts ect. for the user.
Add to cart, remove, view, confirm payment, purchase
-
-
-