I think your design is to cock
you need to read, learn and understand the principles of database design and or normalisation
Fundamentals of Relational Database Design -- r937.com
The Relational Data Model, Normalisation and effective Database Design
are though of as good basic discussions, although no doubtr your course could / should provide other references
ferinstance on your current data model
you define an item list, which is fair enough with a serial number against item list.
it would make moire sense logically and in English to have something similar to:-
suppliers (a table that defines suppliers, organisations or people who supply items)
products (a table that defines products)
orders when your organisation places an order with suppliers
you could replace orders with say deliveries, which defines what products (qty and type) have been delivered on a specific day
deliverydetails which identified the specific serial number of each product that was supplied as part of a delivery
if youy do have to complete this assignement in Access I'd suggest you refine your table and column names so that they make clear sense in your own language (English, French whatever) and that they are as descriptive as they need to be without being longwinded.
there are lists that identify what are acceptable or unacceptable words, characters on names.. do a google for 'Access reserved words'. try to avoid symbols such as @, and avoid using spaces between words. Access does allow you to define a description which can be used on reports or forms.
ferinstance Avoid something like 'Item Brand', use with capitalisation (CamelCase) eg 'ItemBrand' or use underscore eg 'item_brand'
avoid repeating the table name in the column name
so Brand would be better than ItemBrand
don't store derived data
I'd rather be riding on the Tiger 800 or the Norton