Freight and logistics management system in Python/Django
Budget: $250 – $750 USD
Four types of users, shipper, carrier, driver and admin
• A shipper could be a manufacturing company, a small business owner or an individual seller
• A carrier could be a large or small logistics company
• A driver could be an entity that owns multiple vehicles or an individual that owns one single vehicle
• Admin manages the whole system has the ability to modify any information in the system. Admin approves the account creation of other users.
Terminologies of shipping request, delivery request, shipping order, delivery order
• A shipping request is a request initiated by a shipper to look for a carrier to ship packages from one place to another.
• A delivery request is a request initialized by a carrier to look for a deiver to transport packages from one pace to another.
• A shipping request becomes a shipping order once a shipper and a carrier agree on the shipping request
• A delivery request becomes a delivery order once a carrier and a driver agree on the delivery request
• Shipping request, deliver request, shipping order and delivery order have common attributes, such as shipper name and carrier name for shipping request and shipping order (or carrier and driver name for delviery request and delivery order), item name, number of packages, weight, dimension, departure, destination, description field that allows users to fill in more information or requirement, comment field that allows users to leave a comment.
• Comment will be created when an action is taken or status is changed. Each comment should have a timestamp. By default, the comments are hidden or folded as there might be many comments. User can leave comment at any time for shipping request, delivery request, shipping order and delivery order.
• IDs for shipping request (SR), shipping order (SO), delivery request (DR) and delivery order (DO) should be in the format of SRxxxxxxxx, SOxxxxxxxx, DRxxxxxxxx, DOxxxxxxxx. The second part xxxxxxx in the ID names of shipping request, shipping order, delivery request and delivery order for the same shipping job should be identical.
Functionalities
• A shipper, who wants to ship items from one place to another place, publishes a shipping request to the system or sends a shipping request to a specific carrier to look for a carrier to take the shipping task.
• A carrier can receive and view active shipping requests and choose to accept a shipping request while providing a quote for the shipping task.
• A carrier, who then needs to look for driver(s) and vehicle(s) to transport items from source city to destination city, publishes a delivery request to the system or sends a delivery request to a specific driver.
• A driver can receive and view active delivery requests and choose to accept a delivery request while providing a quote and the delivery task.
• Shipping request and order are shared between shippers and carriers.
• Delivery request and order are shared between carriers and drivers.
• Shipping orders can be formed, updated and maintained on the system.
Account
• A user (shipper/carrier/driver) can register to create an account and receive email for confirmation. Account creation needs to be reviewed and approved by admin.
• A user's profile includes business name, phone number, email address, business address, unique ID, user type (shipper, carrier, driver, admin), account creation time, reviews, business partners. The unique ID should be easily differentiate between shipper, carrier, driver and admin, such as starting with a letter S, C, D or A. Clicking "reviews" should list all reviews from its clients as well as a score in [0, 5]. Clicking "business partners" should list all business names of its business partners. A user can also type in credit card and bank account information for making payment and accepting payment.
• Carrier account should have two types of business partners, carriers and drivers.
• Users can update but cannot delete.
• A shipper could be a manufacturing company, a small business owner or an individual seller
• A carrier could be a large or small logistics company
• A driver could be an entity that owns multiple vehicles or an individual that owns one single vehicle
• Admin manages the whole system has the ability to modify any information in the system. Admin approves the account creation of other users.
Terminologies of shipping request, delivery request, shipping order, delivery order
• A shipping request is a request initiated by a shipper to look for a carrier to ship packages from one place to another.
• A delivery request is a request initialized by a carrier to look for a deiver to transport packages from one pace to another.
• A shipping request becomes a shipping order once a shipper and a carrier agree on the shipping request
• A delivery request becomes a delivery order once a carrier and a driver agree on the delivery request
• Shipping request, deliver request, shipping order and delivery order have common attributes, such as shipper name and carrier name for shipping request and shipping order (or carrier and driver name for delviery request and delivery order), item name, number of packages, weight, dimension, departure, destination, description field that allows users to fill in more information or requirement, comment field that allows users to leave a comment.
• Comment will be created when an action is taken or status is changed. Each comment should have a timestamp. By default, the comments are hidden or folded as there might be many comments. User can leave comment at any time for shipping request, delivery request, shipping order and delivery order.
• IDs for shipping request (SR), shipping order (SO), delivery request (DR) and delivery order (DO) should be in the format of SRxxxxxxxx, SOxxxxxxxx, DRxxxxxxxx, DOxxxxxxxx. The second part xxxxxxx in the ID names of shipping request, shipping order, delivery request and delivery order for the same shipping job should be identical.
Functionalities
• A shipper, who wants to ship items from one place to another place, publishes a shipping request to the system or sends a shipping request to a specific carrier to look for a carrier to take the shipping task.
• A carrier can receive and view active shipping requests and choose to accept a shipping request while providing a quote for the shipping task.
• A carrier, who then needs to look for driver(s) and vehicle(s) to transport items from source city to destination city, publishes a delivery request to the system or sends a delivery request to a specific driver.
• A driver can receive and view active delivery requests and choose to accept a delivery request while providing a quote and the delivery task.
• Shipping request and order are shared between shippers and carriers.
• Delivery request and order are shared between carriers and drivers.
• Shipping orders can be formed, updated and maintained on the system.
Account
• A user (shipper/carrier/driver) can register to create an account and receive email for confirmation. Account creation needs to be reviewed and approved by admin.
• A user's profile includes business name, phone number, email address, business address, unique ID, user type (shipper, carrier, driver, admin), account creation time, reviews, business partners. The unique ID should be easily differentiate between shipper, carrier, driver and admin, such as starting with a letter S, C, D or A. Clicking "reviews" should list all reviews from its clients as well as a score in [0, 5]. Clicking "business partners" should list all business names of its business partners. A user can also type in credit card and bank account information for making payment and accepting payment.
• Carrier account should have two types of business partners, carriers and drivers.
• Users can update but cannot delete.