Management Of A Variety Store Has Decided To Implement A Pro

Management Of A Variety Store Has Decided To Implement a Computerized

Management of a variety store has decided to implement a computerized Inventory System to give the store capability to track and record every transaction from the purchase of goods from suppliers, purchases made by customers, available stock, and when to replenish stocks. Management will receive reports daily and monthly summary reports on purchase orders, invoices, customer purchases and stock inventory. Stock levels will be updated immediately that purchases and sales are made to give a clear indication of the amount of stock to be ordered within a timely manner. A Purchase Order is prepared by a Clerk and sent to a Supplier via e-Mail.

The Purchase Order gives the quantity required, a description of the various items, the cost of each batch and the total cost which includes the Value Added Tax (VAT), and the date on which the goods should be delivered. All Purchase Orders are entered into a Purchase Orders database. On receipt of the Purchase Order, the supplier acknowledges receipt via e-Mail as well as confirms that the goods will be delivered on the date requested. If the price of any item is different to that stated on the Purchase Order, the Supplier quotes the correct price on an Invoice which is e-mailed with the acknowledgement. The Clerk uses the supplier invoice to generate several individual invoices in an Invoices database and updates the original purchase order in the Purchase Orders database with updated prices where necessary.

The Clerk creates a separate invoice for each individual item on a Purchase Order. One invoice can be created for the same item on more than one purchase order. Each item in the Stock Inventory database has a unique bar code identifier. When delivering the goods the Supplier delivers a Delivery Notice listing all individual items. On receipt of the ordered goods, one item from each batch purchased is scanned to the system and the Inventory database updated with the quantity purchased.

At the end of stocktaking, a notification is sent to the Accounts Department and to the Supplier on a Delivery Form indicating the quantity of each item of goods received and the items considered ‘unfit for sale’ . The Delivery Form indicates whether or not all goods received were in good order for sale to customers. The Supplier e-mails an updated Invoice to the Purchasing Department and the Clerk updates the individual invoices where necessary. The Accounts Department will make payment to the supplier based on the final invoice received. Each item purchased by a customer is captured in a separate database.

The cash registers are linked to the Inventory System so that when the cashier at the Store scans each item purchased by a customer, the stock level of the item is reduced by the amount purchased. This allows the Purchasing Department to know when to order a particular item and in what quantity. The customer is provided with a receipt when payment is made and all receipts are written to a database.

Paper For Above instruction

Entity-Relationship Diagram and Database Design for the Inventory System

The complex nature of the inventory management system described for the variety store requires careful design of an Entity-Relationship (E-R) diagram and subsequent relational database schema. This section outlines the main entities, their attributes, relationships, and the assumptions used to determine the cardinalities based on the case description.

Entities and Attributes

• Supplier
• Primary Key: SupplierID
• Name
• Address
• ContactNumber
• Email
• PurchaseOrder
• Primary Key: OrderID
• OrderDate
• DeliveryDate
• TotalCost
• VAT
• PurchaseOrderItem
• Primary Key: PurchaseOrderItemID
• Quantity
• UnitCost
• Description
• Invoice
• Primary Key: InvoiceID
• InvoiceDate
• TotalAmount
• InvoiceItem
• Primary Key: InvoiceItemID
• Quantity
• UnitPrice
• Description
• StockItem
• Primary Key: BarcodeID
• Name
• Description
• CurrentStockLevel
• ReorderLevel
• DeliveryNotice
• Primary Key: DeliveryNoticeID
• DeliveryDate
• ItemsReceived
• CustomerPurchase
• Primary Key: CustomerPurchaseID
• PurchaseDate
• CustomerID
• PaymentAmount
• Customer
• Primary Key: CustomerID
• Name
• ContactDetails

Assumptions for Cardinalities

• Each PurchaseOrder can contain multiple PurchaseOrderItems; each item in the PurchaseOrder corresponds to one StockItem.
• Each PurchaseOrderItem belongs to exactly one PurchaseOrder.
• Each StockItem can be included in multiple PurchaseOrderItems.
• Each PurchaseOrder can generate multiple Invoices; each Invoice relates to multiple InvoiceItems.
• Each InvoiceItem is linked to a StockItem, representing individual sale or purchase details.
• Each StockItem can appear in many InvoiceItems and PurchaseOrderItems.
• Each CustomerPurchase involves one Customer, multiple items purchased; each item corresponds to a CustomerPurchaseItem (not explicitly detailed but assumed for completeness).
• Deliveries correspond to PurchaseOrders, with DeliveryNotices listing all items delivered.

Relationships and Tables

Conclusion

This detailed E-R diagram and relational schema facilitate efficient tracking of inventory, purchase orders, sales, and deliveries within the store’s management system. The assumptions above ensure comprehensive modeling of the store’s operations, supporting effective decision-making and timely replenishment of stock.

References

• Casteel, J., & Lee, T. (2020). Fundamentals of Database Systems. Pearson.