Client database & data collection on our Prestashop site

[samdrp]

We need a set of mySQL tables with interfaces built to work with our existing Prestashop site. These tables will store information about stores on our site and allow them the opportunity to edit this information as needed.

We need 3 sections, which may need to be separated into 3 separate tables. 
Section 1 will include contact information as well as general store info. 
Section 2 will include vendors that each store carries. This involves a many to one relationship where we have many lines tied to one store. (The same line may also be tied to more than one store)
Section 3 will include product categories that each store carries. This also involves a many to one relationship where there are many categories associated with one store. These product categories are standardized, so users of this system will choose from a set list of categories.
** This may require two or more tables to be created depending on whether you are able to add fields to the existing Prestashop table or not. I don’t know if Sections 2 and 3 above will require their own mySQL tables, but that is how our current system is set up. (A common ID ties the tables together)

Stores will need interfaces to access this information on our website and be able to edit their general information, add and delete vendors, and add and delete product categories.

We also need a back office interface for our use that will allow us to do the following:
find listings for specific companies and export their data
send batch emails to specific companies asking them to update their listing info
find out who updated their listing information and when
add/delete product categories

We are located in the US and are on Eastern time. We need candidates who can communicate with us during our business hours when necessary.

[Burhan BVK]

Your requirements should not contain table relations, that is for the developer to work out. When you mix low level design with functional requirements, it makes it harder to understand what you need and is likely to result in errors in the design.

 

I don't see how all these are tied together. How are these information presented in your site? What does a visitor see when they browse the site? Any connection to the products? Or is this only for you to manage stores and vendors? You should provide details on use-cases instead of table relations.