Jewellery Management System

ABSTRACT

The jewellery management system is a system that can keep track of all your Commercial activity in a jewellery store ranging from small segments to large and very large segments.But maintaining the same quality or improving the present is not an easy task because Quality is the ultimate image of the entire business. The good quality of a product depends on many factors like solid infrastructure, better management controls, etc.

So for optimum quality, Jewellers have to improve materials that affect quality to update them.Content jewellers have to rely on certain types of data. So if the person making the decision.The business wants to control the total business, it must have the knowledge of the entire flow of data and information within the organisation. It can't be done without someone's help like business related software. The jewellery management system can be developed in any language or platform, which can maintain Track all your business activities in a jewellery store, from small to large to very large segments section.

As we all know the jewellery trade can be divided into three major categories i.e.

Retail
Wholesale
Export

Main features of System

Maintaining Purity according to the percentage of alloy.
Maintaining artisans or dealers
Maintain customer details
Maintaining details of stones.

Existing System

Currently, all activities in a transaction are handled manually. Manual data processing systems, which generally provide economy, flexibility, and adaptability to low volumes of data, become more complex as the amount of data increases. As an organisation grows in size and function, a stage is reached where manual processes become inadequate and inefficient. No matter how many employees are employed in one step, it becomes impossible to organise such a large amount of information. What is needed then is an improvement in the ranks of information processing technology.
The current system is not sufficient to contain all the information necessary for processing. Therefore, the library needs a new computerised system, which is very flexible, easy to use and able to maintain the system in a robust way.

Limitation of existing system

There were a lot of reasons for the introduction of the new system. They are mainly due to the drawbacks and efficiency of the existing system.

The delay in information search and retrieval.
Physical volume of the data is very large.
Problems in updating and backup.
Damage of papers containing the information.
Considerable time taken for report generation.
Accuracy of data is very lower in manual system.

Proposed System

The proposed system is very user friendly interface.It is easy to use.We evaluate the existing problem and find the best solution.we are providing menu driven scheme so that user can easily use the given facilities.Our proposed system have following advantages such as:

The proposed system can be utilised for easy documenting and accessing various data carriers such as forms, reports, records etc.
Automation makes the system to be user-friendly and hastily in manipulation and generation of valuable reports providing menu driven facilities.
Accuracy and security of data will be more comfortable for the organisation.
Computerisation will avoids human errors due to inexperience in data entry, manipulation etc.
The paper work occurred in the manual system can be completely avoided.

System Design

Modules of proposed system

User/Customer
- My Account
- Product Details
- Category
- Order
- Order Reports
Admin
- Customer Order Detail
- Product Order Detail
- Category
- Processed Order
- Cancelled Order
- Special Product
- Product Report

Admin Details
- Admin Id
  - Numeric type (Datatype)
  - Primary Key (Constraint)
- Login Id
  - String type (Datatype)
  - Not NULL (Constraint)
- Password
  - String type (Datatype)
  - Not NULL (Constraint)
- Admin Name
  - String type (Datatype)
  - Not NULL (Constraint)
- Address
  - String type (Datatype)
  - Not NULL (Constraint)
- Company Name
  - String type (Datatype)
  - Not NULL (Constraint)
- Company Address
  - String type (Datatype)
  - Not NULL (Constraint)
- Contact Number
  - Numeric type (Datatype)
  - Not NULL (Constraint)
- Fax Number
  - String type (Datatype)
  - Not NULL (Constraint)
- Account created date
  - Date type (Datatype)
  - Not NULL (Constraint)
- last login date
  - Date type (Datatype)
  - Not NULL (Constraint)
Category
- Category Id
  - Numeric type (Datatype)
  - Primary Key (Constraint)
- Category Name
  - String type (Datatype)
  - Not Null (Constraint)
- Final Product
  - Image type (Datatype) depend on database s/w used
  - Not NULL (Constraint)
- Image path
  - String type (Datatype)
  - Not NULL (Constraint)
Customer Detail
- Customer Id
  - Numeric type (Datatype)
  - Primary Key (Constraint)
- Customer Name
  - String type (Datatype)
  - Not NULL (Constraint)
- Occupation
  - String type (Datatype)
  - Not NULL (Constraint)
- Street
  - String type (Datatype)
  - Not NULL (Constraint)
- City
  - String type (Datatype)
  - Not NULL (Constraint)
- State
  - String type (Datatype)
  - Not NULL (Constraint)
- Pin Code
  - Numeric type (Datatype)
  - Not NULL (Constraint)
- Contact Number
  - Numeric type (Datatype)
  - Not NULL (Constraint)
- Mobile Number
  - Numeric type (Datatype)
  - Not NULL (Constraint)
- Email id
  - String type (Datatype)
  - Not NULL (Constraint)
- User Name
  - String type (Datatype)
  - Not NULL (Constraint)
- Password
  - String type (Datatype)
  - Not NULL (Constraint)
- Date
  - Date type (Datatype)
  - Not NULL (Constraint)
Product Detail
- Product Id
  - Numeric type (Datatype)
  - Not NULL (Constraint)
- Product Code
  - String type (Datatype)
  - Not NULL (Constraint)
- Product Name
  - String type (Datatype)
  - Not NULL (Constraint)
- Category
  - Numeric type (Datatype)
  - Not NULL (Constraint)
- Image
  - Image type (Datatype)
  - Not NULL (Constraint)
- Price
  - Decimal type (Datatype)
  - Not NULL (Constraint)
- Weight
  - Decimal type (Datatype)
  - Not NULL (Constraint)
- Weight Unit
  - Numeric type (Datatype)
  - Not NULL (Constraint)
- Short Description
  - String type (Datatype)
  - Not NULL (Constraint)
- Long Description
  - String type (Datatype)
  - Not NULL (Constraint)
- Special
  - String type (Datatype)
  - Not NULL (Constraint)
- Display Order Group
  - Numeric type (Datatype)
  - Not NULL (Constraint)
Purchase Detail
- Category
  - String type (Datatype)
  - Not Null (Constraint)
- Unit
  - Numeric type (Datatype)
  - Not NULL (Constraint)
- Type
  - Decimal type (Datatype)
  - Not NULL (Constraint)
- Item Description
  - String type (Datatype)
  - Not NULL (Constraint)
- Quantity
  - Numeric type (Datatype)
  - Not NULL (Constraint)
- Cost
  - Decimal type (Datatype)
  - Not NULL (Constraint)
- Supplier Name
  - String type (Datatype)
  - Not NULL (Constraint)
- Supplier Address
  - String type (Datatype)
  - Not NULL (Constraint)
- Purchase Date
  - Date type (Datatype)
  - Not NULL (Constraint)
- Purchase Code
  - String type (Datatype)
  - Not NULL (Constraint)
- Amount
  - Numeric type (Datatype)
  - Not NULL (Constraint)
Order Details
- Order Id
  - String type (Datatype)
  - Primary Key (Constraint)
- Order Code
  - String type (Datatype)
  - Not NULL (Constraint)
- Customer Id
  - Numeric type (Datatype)
  - Not NULL (Constraint)
- Processed Order
  - Image type (Datatype)
  - Not NULL (Constraint)
- Cancelled Order
  - Image (Datatype)
  - Not NULL (Constraint)
- Total Order
  - Numeric type (Datatype)
  - Not NULL (Constraint)
- Number of Product
  - Numeric type (Datatype)
  - Not NULL (Constraint)
- Remark
  - String type (Datatype)
  - Not NULL (Constraint)
Employee Attendance
- Employee Id
  - Numeric type (Datatype)
  - Primary Key (Constraint)
- Employee Name
  - String type (Datatype)
  - Not NULL (Constraint)
- Status
  - String type (Datatype)
  - Not NULL (Constraint)
- Attendance Date
  - Date type (Datatype)
  - Not NULL (Constraint)
Employee Advance Detail
- Employee Id
  - Numeric type (Datatype)
  - Primary Key (Constraint)
- Employee Name
  - String type (Datatype)
  - Not NULL (Constraint)
- Advance Date
  - Date Time type (Datatype)
  - Not NULL (Constraint)
- Advance Amount
  - Numeric (Decimal) type (Datatype)
  - Not NULL (Constraint)

Feature Enhancement

The system has been developed in such a way that it can be added without a lot of difficulty. Upgrading the project will increase the flexibility of the system.In addition, the facilities are provided in such a way that the system can also be improved and effective feature programs have been coded in a simpler and more structured way so that Changes can be easily incorporated. The processing time is very less in this system compared to the current system. This system has good flexibility to adapt to any There may be more changes in the future. In this system, data integrity is maintained and the data Redundancy is avoided and increases system efficiency. The database is designed in such a way that it Will also help increase the system.

Conclusion

"Jewellery Management System" manages the processing of purchases and sales of a jewellery shop. This system has been developed to meet all the proposed requirements.The process of recording vendor, item, billing and customer details is simple and easy. The system significantly reduces the risk of errors and maintains the data efficiently.User-friendliness is the unique feature of this system. The system generates reports as follows and as required. The system is highly interactive and flexible for further improvement.Coding is done in a simple and easy to understand manner so that other teams trying to improve the project can do without too much difficulty.Documentation will also facilitate the process as it has also been simplified and short way.

References

www.myntra.com/artificial-jewellery-set
www.mirraw.com/store/jewellery

Jewellery Management System | Project