Krishi Bazaar

Overview of Our Submission

Hey everyone!
So, we have made an online e commerce store for farmers to directly connect with consumers.

There is no available product in the market that proposes a business logic for the farmer to directly sell to the consumer. We have always felt that technology could help small and big farmers to reach remote corners so that they could grow a product instead of a crop and make their own brand.

(The dates used in the video are test dates, currently application is set to current date.)

Submission Category:

• E-Commerce Creation
• Action Star

Link to Code

GitHub Repository

Live link

Live Link https://temp-name-1.herokuapp.com/

• Kindly note : In case registration gives a problem, try loggin in with these credentials: email: vaishnavisdesai@gmail.com password: 123456

Our Goal

KrishiBazaar with its main motto of “Fresh from Farm to Plate” achieves the goal of providing farmers with better opportunities to showcase their produce and pocket a higher remuneration. Its main aim is to do away with the several layers of middlemen between the farmer and the consumer. The project allows farmers to upload details, view product statistics, track various shipments and pickups of orders and receive payment online.

What it does

• There is an absence of an application that connects consumers with farmers in a transparent and direct manner.
• Krishi Bazaar with its main motto of “Fresh from Farm to Plate” achieves the goal of providing farmers with better opportunities to showcase their produce and pocket a higher remuneration. This reduces the cost to end consumer.
• Krishi Bazaar provides farmers with a safe space to educate themselves and receive the appropriate assistance they require. This project aims to help farmers achieve their true potential without the need to be dependent on intermediaries.

Tech Stack

Let's come to the technology.
For building this application, we have used:

• Angular- For building the frontend of the application
• NodeJs - Express - For building backend services and maintaing persistent sessions
• MongoDb Atlas - Used as the application database (Have always been a fan of Json based databases. And its cloud!)
• Atlas Search - For features like autocomplete
• Realm Function and Triggers - For generating a timely (daily) report on the market for analysis
• TimeSeries Collection - For storing the daily reports
• RazorPay API - Because we can't make payment gateways yet
• FontAwesome - Who doesn't want their website to look cool
• Particle JS - Again who doesn't want a bit of confetti.
• PassportJs - For authentication.
• Heroku -For Hosting the application

Okay lets dive a bit deeper into it.

Key Features

- Authentication

We have used the Passport JS library that provides various strategies for authentication. Here we have introduced a local strategy that authenticates with email and password. We are also using the express session, passport session and mongo store to maintain persistent sessions. In simpler terms, the backend sets a cookie in the browser on logging in. The backend also stores this cookie in the database along with the associated user. With every request, the browser sends this cookie back to the backend to validate. The backend validates it with the cookie present in the database and hence persists in the session.
A user can sign up as either of the two roles: Farmer (Farmer + Consumer) or Consumer.

 

- Setting up a store - Register as a farmer

A farmer can set up their own store. This can be
achieved by setting up an identity on the website by registering as a farmer. The farmer can provide details like email address, phone number, name, farmer verification proof and address and create an identity on the website which can now be identified by any other user of the website.

 

- Adding products to the market -

As a farmer the user can add a product to the market. The details include:
Product image, Name, Description, Categories, Discounts and pricing, pickup address. We have used Firebase Storage to store product image and MongoDB Atlas to store other product related information. Once the product is in the database, it is officially on the market!
These products are visible to a consumer user along with the farmer brand. The consumer can also search and filter through all the products in the market. They can also get suggestions for various products based on their purchases and market analysis.

 

- Shipments and Orders -

A farmer can view his shipments on the portal. Shipments are the products that consumers have ordered from the farmer. A farmer can track the shipments till they reach the consumer. After an order is delivered, it gets deleted from the farmer's shipments.
The consumer also stays updated with ongoing orders as well as
has a log of all past orders. All the details of each order including the delivery date, are visible.

 

- The pickup module -

A farmer is also able to view his pickups. Pickups on the portal is nothing but a table showing the schedule of product pickups. It contains details like who is going to pick up from the farmer, what product they are picking up, date, etc.
 

- The logistics -

But who exactly is delivering the products, picking up the product you might wonder? Right now, we don't have a solid logistics in place, but what we do have is a logistics interface.
Logistics interface is a table where all the ongoing orders are listed. Ideally an authorized personal like an employee will be able to access this portal. But for now, we can play around by updating the status of a particular order to 'delivered' or 'picking up' and the status of that order would change accordingly.
 

- Consumer Role Overview-

As a consumer, the user will be able to browse through products, search for a product, etc. Atlas Search has made autocomplete and other searches much simpler and convenient! After landing on a particular product, the user can select the quantity and add the product to the cart. The user can then proceed to checkout by selecting an appropriate delivery address and make payment. After the payment is complete (In the test mode in RazorPay API for now), the order now becomes an ongoing order.
 

- Purchasing a product -

The consumer can add a particular product to their cart as well as edit quantities. The consumer pick the delivery address and makes payment (RazorPay API) through the system.

 

- Review and rating -

A user will be able to comment and rate only after purchasing a product. There are no restrictions on viewing the review and ratings.
All ratings and reviews will be visible on each item’s page along with the average of all ratings as the item’s average rating.
 

- The bidding system -

Another feature that we have implemented is the bidding system. A user can bid on a product. A farmer can see all bids on their product. A farmer can accept bids on their product. After a farmer accepts a bid, an email is sent by the system to the user to directly contact the farmer for acting further on the bid. This feature is developed targeting bulk buyers.
This will help them get products at a cheaper price than the current market price. The farmer can view bids as well as accept a bid. This will help the farmer sell excess produce or gain a good profit owning to bulk consumers.

 

- Market Analysis-

Finally, we have performed some basic analysis of the market. We have implemented some basic Realm triggers and functions to support us with the same. We plan to further improve on report generation of the analysis and statistics of the market to gain an insight into the business strategies that can be used to target a larger audience while maintaining a loyal customer base. This feature will help the company in making informed decisions with the data right in front of them.
 

- Aid-Farmer’s Aid

It's a place where farmers can educate themselves on various current ongoings in the agricultural sector. They can see a variety of information which would help them in making future decisions regarding agriculture.
 

- Search Bar-Search products on the go!

 
Technically speaking, we have developed a bunch of APIs in the backend that perform simple CRUD operations on the database and are consumed by the frontend to send and retrieve data.
 

Wrapping it up, here's everything in a nutshell!

What's next for KrishiBazaar

A lot of features are on our to-do list now! Scaling the applications, testing, and adding more features while also receiving constant feedback is one of our major goals!

Let's KrishiBazaar!🍀

Additional Resources / Info

• PassportJs
• PassportJs Authentication
• Razorpay Resource
• MongoDB Scheduled Triggers
• Atlas Search
• Make a API call in angulare
• Get started with Angular
• Setup an express server
• Setup session
• Perform some CRUD operations
• Deploy app on heroku

Installation

1. Clone the repo ```sh

git clone https://github.com/projecthts/MongodbProj.git

2. Frontend:
```sh


   cd .\FrontEnd\Krishi-Bazaar\
   npm i

1. Backend ```sh

cd .\Backend\NodeJs\
npm i
npm run build
npm run dev

## Made with ❤️ by
- [VAISHNAVI DESAI](https://dev.to/vaishnavi06desai)
- [ISHA GHIRIA](https://dev.to/ishag6)
- [ANIKA TIBREWALA](https://dev.to/anika001)
- [TWINKLE BAGDI](https://dev.to/twinklebagdi)


##### Hope you liked our project. Feel free to reach out in case of any queries - projecthts.16.4@gmail.com