Pet Shop Management System In PHP With Source Code

This guide walks you through building a Pet Shop Management System in PHP and MySQL from the ground up, a pet inventory, customer, and sales project complete with source code. Rather than only downloading it, you will understand how each part works: the database schema, how pets and products are managed, how a sale is recorded, and how stock is tracked. That understanding is what turns a downloaded project into something you can explain in a viva, extend for an assignment, or showcase in your portfolio.

1. What a pet shop management system does

A pet shop management system is software a pet store uses to run its day-to-day business: keeping track of the pets and pet products it has in stock, recording sales to customers, and watching inventory so popular items get reordered. At its core it answers a few questions on demand: what do we have to sell, who is buying, what have we sold, and what is running low. Building one in PHP and MySQL is a popular project because it touches every fundamental skill, database design, CRUD operations, relationships between tables, authentication, and stock tracking, in a friendly, relatable context.

The version in this guide includes management of pets and pet products organized by category, customer records, recording a sale, automatic stock updates, basic reporting, and an admin login. That is enough to be a complete, demonstrable project while staying simple enough to fully understand.

2. The database schema

The schema is the backbone of the project, so it is the best place to start. Reading the tables tells you what the system actually models. The pet shop system uses these core tables.

The relationships are the key idea. Each pet or product belongs to a category, a sale links a customer to the item they bought, and stock lives on the pet record. The category_id on the pets table is a foreign key connecting the two tables, which is what lets you group and filter items by type. Understanding this one diagram is understanding most of the project, because every screen reads or writes one of these tables.

3. How pet and product management works

Managing the catalog is straightforward CRUD. The admin can add a pet or product, view the full list, edit details, and remove an item, each operation a small block of PHP running an SQL statement. Adding an item, with values from a form, uses a prepared statement:

// add a pet/product to the catalog (simplified)
$stmt = $conn->prepare(
  "INSERT INTO pets (name, category_id, price, stock, image)
   VALUES (?, ?, ?, ?, ?)"
);
$stmt->bind_param("sidis", $name, $categoryId, $price, $stock, $image);
$stmt->execute();

The prepared statement with bind_param, rather than dropping form values straight into the SQL string, is how you prevent SQL injection, a core security habit in PHP and a detail that marks a project you understand rather than one you copied. To show items with their category name, the listing uses a JOIN between the pets and categories tables, which is how separate tables become a single readable view.

4. How recording a sale works

Recording a sale ties a customer to an item they bought. The admin selects a customer, a pet or product, and a quantity, and the system inserts a row into the sales table with the total calculated from the item’s price times the quantity. Crucially, the same action reduces the item’s stock, so the inventory always reflects what is left.

// record a sale and reduce stock (core idea)
// 1. insert the sale
INSERT INTO sales (customer_id, pet_id, quantity, total, sale_date)
VALUES (?, ?, ?, ?, NOW())
// 2. reduce the item's stock by the quantity sold
UPDATE pets SET stock = stock - ? WHERE id = ?

Because the sale record and the stock update belong together, this is a good place to mention transactions, which group queries so the sale and the stock change either both happen or neither does. Being able to explain why the stock update must accompany the sale shows you understand keeping data consistent, which is a step beyond simply storing records.

5. How stock and inventory are tracked

Stock is just a number on each pet record that goes down as items sell. The value of tracking it is in the reports it enables: a low-stock list, for instance, is a single query that finds items below a threshold so they can be reordered.

// items that need restocking
SELECT name, stock FROM pets
WHERE stock < 5
ORDER BY stock ASC

Other useful reports follow the same idea: total sales, best-selling items grouped from the sales table, or revenue over a date range. Once the schema is right, these reports fall out of simple SELECT queries with WHERE, SUM, or GROUP BY, and understanding that is what lets you add any report your project needs.

6. The admin dashboard and login

The system sits behind a login that verifies a hashed password with password_verify and stores a session every protected page checks. The dashboard is a set of small queries you now understand: total items in stock, total sales, number of customers, and low-stock alerts. Because you know the schema, you can add any new dashboard figure yourself just by writing its query, which is the flexibility that makes the project worth understanding rather than just running.

7. Setup: running it on your machine

To run the project locally you need a PHP environment with MySQL, most commonly XAMPP on Windows or its equivalent on Mac and Linux. The steps are:

1. Install XAMPP and start the Apache and MySQL services.
2. Copy the project folder into the htdocs directory.
3. Open phpMyAdmin, create a database, and import the included .sql file to create the tables.
4. Open the project’s config file and set the database name, user, and password to match your setup.
5. Visit the project in your browser through localhost and log in with the default admin credentials in the guide.

8. How to extend it for your own project

Assignments and portfolios reward what you add, not what you copied. Because you now understand the schema, the sale flow, and stock tracking, here are natural extensions you can build and explain:

• Multi-item sales: add a sale_items table so one sale can include several products, like a real cart.
• Supplier and purchase tracking: record where stock comes from and increase stock when new inventory arrives.
• Pet details and health records: for live pets, store breed, age, and vaccination notes.
• Sales reports with charts: feed a monthly-totals query into a chart library to visualize revenue.
• Customer purchase history: a per-customer view of everything they have bought, using a JOIN on the sales table.

Each of these is a small, well-scoped addition that demonstrates real understanding, exactly what turns a standard download into a project you can defend and be proud of.

Frequently asked questions