Finish development of ecommerce store based on Django

Closed Posted 6 years ago Paid on delivery
Closed Paid on delivery

Complete the development of [login to view URL] based on the Django ecommerce platform Oscar. Currently at 60%. Attached "requirement files" and "current status".

[login to view URL] should be as simple as possible for parents/tutors to shop for their kid’s school supplies, in as little steps as possible.

For a better idea, here’s a brief of the big picture.

Different from other countries, here schools decide which text books (edition and editors) and learning materials they’ll use in each grade. On average, two months (June) prior to the beginning of school year (August) they hand out their lists to parents or post it online.

All parents modify the base list for two reasons: first, they already have one or more of the products (left from prior year like calculators and dictionaries), bought them somewhere else or any other reason; and second, they want to change brands for cheaper of better products.

We get the “lists” from schools that post it online and create those lists in our system for them to easily shop for it, or parents give it to us (email, whatsapp or online attachment) when we don’t have it, so we can create it.

Half our customers have more than one kid, so they should be able to buy for them, but maintaining separate packages (one list is one package). This because a product can be in two or more of the lists being bought and in the shopping cart have to be separate (for example, if buying a list for 10th and 12th grade, both can have the same notebook or a pen, but should be presented separate in shopping cart with respective quantities). In short, when buying more than one list, customer should be able to view each list separate (shown grouped by kids name, not grade) but in the same shopping cart as one transaction. It’s like when you shop Amazon and your order get divided by delivery date or fulfillment center, you end up doing in one transaction, two or more orders.

Common situations:

1. A product in a school list is not available from editors or asked for the wrong edition. If school approves it, we substitute the product in the “list” with the correct one and make a note for the parent (fields used: productID, substitute, substitutedproduct and substitutenote).

2. A product is out of stock from suppliers and won’t have available.

a. We ask customers for approval to change the product if possible.

b. We remove the products from open orders.

In any case, no change to the “list” is done, just the orders.

Inventory:

We do not carry inventory, or the least possible. We buy inventory as orders come in.

Time frame:

July 1, we should start taking orders.

Needless to say, mobile first!

Django eCommerce Python Website Design

Project ID: #9871075

About the project

18 proposals Remote project Active 6 years ago