A family of Microsoft relational database management systems designed for ease of use.
I'd need to know more about the structure of your database overall, and how you wish to manage inventory. Does your database include purchase and sales orders for instance, and if so how are they modelled? Do you wish to treat each product, regardless of supplier, as a single inventory category, or do you wish to maintain separate inventory data per supplier for each product supplied by more than one supplier?
A fully developed inventory management database is a complex affair, and there are commercial inventory management products available whose functionality would take a lot of time and effort to reproduce in an Access application, even if you have the skills to do so. Unless you only require a simplified system with limited functionality, purchasing a commercial application will often be a more sensible business option than trying to reinvent the wheel.
You'll find an example which illustrates the basic methodologies of a simple inventory management database as Inventory.zip in my public databases folder at:
https://onedrive.live.com/?cid=44CC60D7FEA42912&id=44CC60D7FEA42912!169
Note that if you are using an earlier version of Access you might find that the colour of some form objects such as buttons shows incorrectly and you will need to amend the form design accordingly.
If you have difficulty opening the link, copy the link (NB, not the link location) and paste it into your browser's address bar.
This little demo file is not intended to be a working application, however, but only a starting point to provide some basic guidance in what would be involved in the development of an operational database. It does not include purchase orders, only sales orders, and treats stock acquisition generically, with no supplier data whatsoever. Like all my demos, it assumes that anyone consulting it will have sufficient technical knowledge of Access development to be able to apply and adapt the methodologies to their own requirements.