Agrevo
Global market in your pocket
The problem Agrevo solves
Farmers frequently encounter low profits, inefficient distribution, and limited access to global markets, resulting in under-compensation and significant food waste. Traditional supply chains fail to directly connect farmers with mass buyers and consumers, restricting their earning potential and increasing costs.
The challenge is to create a solution that enhances farmers' profits, optimizes distribution, and ensures product quality while reducing storage and transportation costs.
The proposed business model creates a marketplace brand that directly connects farmers with mass buyers and individual consumers, ensuring higher profits by purchasing produce at better rates and bypassing traditional middlemen. This platform, featuring an e-commerce section for agricultural products, benefits both large-scale and individual buyers with fresh, locally-sourced goods, while reducing transportation and storage costs.
Farmers are equipped with IoT systems providing real-time insights into environmental factors like humidity, ensuring optimal growing conditions and maintaining high quality standards. Additionally, the brand shares a portion of its profits with farmers at all levels, empowering them financially. Select farmers receive a special company badge, elevating their products to meet global market standards through a unique valuation grade system.
This model fosters a sustainable, efficient supply chain, promoting local produce, and driving success for all stakeholders in the agricultural ecosystem.
Challenges we ran into
Dependency Conflicts in Next.js:
Encountered multiple dependency conflicts when installing certain packages like @radix-ui/react-icons due to React version mismatches. This led to ERESOLVE errors, which were resolved by using the --legacy-peer-deps flag and adjusting dependencies carefully.
Image Handling in Next.js:
Faced issues with the next/image component, specifically with handling external media images. Next.js required configuration of allowed image domains in next.config.js, without which it threw errors. This was resolved by adding 127.0.0.1 to the domains list to handle media files served from Django's backend.
Unauthorized Errors in API Requests:
Experienced 401 Unauthorized errors when accessing protected API routes, particularly after implementing authentication in the Django backend. This issue occurred because session or token-based authentication wasn’t preserved across route changes on the frontend. We addressed this by ensuring proper handling and storage of authentication tokens on the client side.
Django Migration Challenges:
When updating the Product model to include an image field, Django required a default value for existing rows. We addressed this by either providing a one-time default or managing migrations manually to avoid data inconsistencies
Directory Structure for Static Media:
Setting up and managing media files in Django required configuring the project to serve media files in a structured way, ensuring proper URL mapping and storage under the media/ directory. This was critical for image uploads from the frontend and display in the shop page.
Cross-Origin Resource Sharing (CORS):
As the frontend and backend ran on different ports, CORS issues arose when trying to fetch data. We resolved this by configuring Django’s CORS settings to allow requests from the frontend’s origin, enabling seamless data flow.
Button Navigation with Router:
Tracks Applied (1)