Questions

Question List

1. Can a vendor user buy, comment or rate other products, or does he need to open a customer account to do these?

Vendor and customer registrations are separated. Users should choose customer-user or vendor-user while logging in. But one e-mail address can be used for both.

2. Which categories should the program support or can the category tags be designed by vendors themselves? (this causes a big category pool generation and also lots of repetition)

Vendors cannot edit categories.

3. Can a vendor direct message another user (customer or vendor or admin)? Or just can reply?

A vendor can start a conversation with a customer during an active order. A vendor can communicate with admins anytime.

4. Can a guest user add products to the cart and buy without an account?

A guest user can add a product to the cart and buy without an account. The system asks for an email to send a tracking code. The messaging system is also available temporarily between the guest user and the vendor.

5. What should be the permissions of admin?

An admin can delete and ban the users and the products. Also, he/she can add a category to the system. Products are controlled by the admin before the selling.

6. In what kind of situations vendors might communicate with platform admins?

Vendors and admins can communicate. If there is something inappropriate, the vendor can get in contact with the admin.

7. What kind of notifications might be done (especially for vendors)?

The notifications about the details of the shipment are obligatory. The notifications in case of sales are optional.

8. What is the desired performance in terms of response time?

It is up to us.

9. Is there any preferred encryption algorithm to store passwords?

There is no preferred option, but passwords should be private and well-protected.

10. In which versions of Android should the product work?

Android 8+

11. In which web browsers should the product work? (And its versions)

The last versions of chrome, safari, opera should be supported.

12. What should be the least uptime percentage?

It is up to us.

13. Should there be maintenance on a regular basis? If so, what should be the frequency? What should be the duration of the maintenance?

Once in a month is enough.

14. What should be the language of the product? English, Turkish or both?

English is mandatory, others are up to us.

15. What is the expected number of users that use the product? How many people could be able to use the product at the same time without a problem?

It is up to us.

16. What is necessary while registering other than an e-mail address and password (name, surname)?

Location for a vendor is necessary.

17. Will customers have a profile page?

No need for a public profile page for a customer. In private, it should contain 'change address', and 'change password' sections. If a customer deletes its account, his/her info can store in the database anonymous. Besides, when a user registers in the system, he/she should complete a form that contains this information.

18. What will be available on the vendor's/customer's page to be seen?

Vendors have a public profile page. It contains the name, locations, products, ratings, and comments of the company.

19. Will it be a local website or global?

Global.

20. Will the sold products 2nd hand(used) or brand new?

Brand-new products

21. Can a guest user rate a product?

A guest user can rate only the product that he/she buys.

22. Should vendors be able to see the total amount of money they gained on the platform?

Yes, it would be nice.

23. Is semantic search mandatory or a preferable?

Yes, it is mandatory. If the user chooses, we can apply an exact search.

24. What is the return policy? Is cargo charge on the customer? If not, is a cargo code OK?

There will be a button for return. After clicking, one will receive a cargo code to return the good without extra cost.

25. Will return reason be asked?

No reason will be asked for return in 14 days.

26. Is this kind of notification possible: New arrivals that match a set of properties: category, color, size.

Yes.

27. Vendor: is the name of the person necessary?

Yes.

28. Validation of requirement 1.1.4.1.

29. Validation of requirement 1.1.7.3.

30. Validation of requirement 1.1.7.5.