AgroBasket

The idea

By the time fruit and vegetables reach a shop they have usually passed through a wholesaler and one or more traders, and each of them takes a margin out of what the farmer gets paid. AgroBasket puts both ends of that chain on one site, so a farmer can sell straight to the person eating the food.

Two ways in

It's a single Django project split into two apps. Customers use the site root and farmers use /farmer. Each side has its own pages, but both sign in through Django's built-in auth, so there is one user table and one session system to look after.

How the cart works

Four models hold the cart together:

1. 1

   Press Add to Cart

   Each product card carries its id. The click posts that id to /updatecart as JSON, with Django's CSRF token in the header.

2. 2

   Find the open cart

   The server looks up the customer's cart that isn't completed yet, and creates one if there isn't. Each customer has exactly one open cart.

3. 3

   Find the line

   It does the same for the line item: one row per product in that cart. Adding a product that's already there raises its quantity by one instead of adding a second row.

4. 4

   Show the new total

   The page reloads, and the cart's totals are worked out from its line items when the page renders.

Working out the total

The cart doesn't store a total. It adds one up from its line items each time it's asked, so the total can't drift out of step with the items. Changing a quantity box in the cart posts the new number to /updatequantity. A line whose total reaches zero deletes itself.

Where it stopped

Working

Customer and farmer accounts, customer profiles, the product catalogue, and adding, changing and totalling cart items.

Front end only

The farmer upload form and dashboard are built as pages but don't save anything yet. Products are added through the Django admin for now.

Not started

Checkout and payment. The tracking page shows no orders, because a cart can't be completed yet.