How should the correct ERDs looks like (entity relationship diagram using these information)?

Introduction Camaby Vinyl is a shop in London that sells old vinyl records They act as agents for members of the public as well as selling vinyl singles and albums that they have sourced from auctions and from people who don't need them to act as agents. Currently there is a single store but they have plans to open another branch soon. Details Camaby Viny. (CV), act as a seller for clients who come in to the shop with vinyl records that they no longer want Anyone can come in off the street with a box of records 6 days a week and ask CV to sellthe records for them. (At this point in time they do not allow records to be sent to the store by parcel but they may do this in the future. They agree on a price for each of the records and agree on a commission that CV keep as the seller's fee. The levels of commission are set on a fixed scale, 25%, 35% and 50% for clients, however there is another level of 100% for CV themselves (Commission levels change with larger numbers of records being brought in or for loyal customers). CV buy records at auctions and as part of house clearances and they sell these alongside client's items They receive 100% of the commission CV currently uses a spreadsheet to log all client details, their sales and the records that they have in stock at any one time. When a new record comes into the store the following information is logged: . Client details .Record type (single or album) . Record /sleeve condition (1 5 with t being perfect condition) . Artist or artists on Various Artists collections . Label Date the record is brought in . Date to be sold by (Client can say when they want it back if not sold) . Price to be sold at . Commission level (25 35, 50 100) . Notes (such as good quality record but dodgy sleeve) Requirements CV are looking for a database to replace their current spreadsheet system. They are looking for a system that can be accessed by more than a single member of staff at a often have more than one staff working in the shop at a time as well as considering a second store (We do not have to consider how a second store will access the database) The system must be searchable as they often have customers who come in looking to buy specific albums or singles by specific artists If a customer buys an item and it will not play on their record player, they should be allowed to return it. (The shop is supposed to check each copy before they put it on display but this might not always happen) time as they The store owner wants to be able to run reports, for example, to see which of their clients have sold the most items. The more items sold through CV the lower commission rate CV charges. (We do not know the trigger levels for these changes as the owner does not want to divulge this information at this point in time) CV need certain attributes stored about the items they are selling: Price to be sold at Condition of the item. A notes section that can hold things such as condition of the sleeve. Suitable contact details for the client 14 Date item brought into shop Date it will be taken out of stock and returned IF this is what the client wants