Custom database solution, within a Joomla component or module.

Project general description: We need a custom database system to be created as a component in Joomla 2.5 (or 3?). This component will have a number of front-end views to display data, enter data and edit data, and a backend interface for basic management of data. All data will be in a separate database to Joomla. Why in Joomla?: We are familiar with Joomla and can easily manipulate the site afterwards to move content and menu items around the data. Use of the system: This database solution will be used to store and manipulate information about incoming “items” coming to a warehouse on “containers”. Items that come in belong to orders, and orders belong to containers that come in each day. This system will help us keep track of each item's status until it has been shipped. Work done so far (We already have the below): CSV import feature- We have a customised CSV import feature working usint the component "Fabrik 3.0" to import bulk data each day from our CSV files directly in to the "Items" database table. Collapsible Table Grouping module- We have a module which shows data with 3 level parent / child grouping that collapses and expands to show items belonging to orders belonging to containers. What we now need (This is what we need you to quote on): 1) Shipping status selection view- We need a component which simply shows all of the warehouse "items" from our database table, filters them by shipping status and groups them by order number or container number (selectable). Then, items in this view can be checked (checkbox) in bulk to be marked as shipped. Also, we need to be able to easily tick an order number (grouped by field) to instantly select each of it's items at once simultaneously. Database requirement- We need a new table in the database containing all the possible shipping statuses that can be selected. Then our "items" database table can be related to this shipping status table by each item's "shipping status" field. Special requirement (shipping log)- Each item needs to have a record of all shipping statuses selected for it by date. A "one to many" database relationship with a shipping status log table may work. I'll leave it up to you, I am open for suggestions here. 2) User access / restrictions on items shown: We need a feature which will allow each item in the database to be made visible (or not) to particular joomla users and Joomla users. Use of this feature- Some Joomla users will be created to allow clients to log in and see their items only. Each item has a "Customer number". Some Joomla users will need to have access to see items that belong to one or more customer numbers. Requirement- We need a component backend feature which brings up a list of Joomla users, and lets you select multiple values from all of the "customer_number" values in the items database. This is how you assign which items belong to which joomla users, by associating Joomla users to one or many of the item "client_ number" values. Database requirement- This data should be stored in a database table (eg, "user_access") and related to the "items" database table ("one to many" relationship, one item to many users). How the filtering might be achieved in the front end As the items data is displayed on the site, the logged in user is detected, and only the items linked to that user will show. (eg. filter results to only show items which the logged in user is related to in the "user_access" table. There may be more paid work once the above 2 features have been implemented. Please quote on providing the above two features and an estimated time-frame that we can expect. We hope not to have to use too much of our budget on these so that we can afford to pay you more later for followup work on this project. We look forward to receiving your questions and quotes.