Flutter ERP Project
Budget: $30 – $250 USD
Project Overview:
ERP automation system designed for companies involved in student and personnel transportation. This system allows for the management of income, expenses, and work records, along with live vehicle tracking and route management. The project is utilized by three different parties: the Management Office, the Service Recipient, and the Service Provider.
Tasks to be Completed:
Tally Listing Screen:
This screen is commonly used across multiple other screens. The tally listing screen is shared by both service recipients and service providers. Depending on which user class accesses the screen, the API delivers data specific to that class.
/api/manager/tally/format
/api/contractor/tally/format
/api/factory/tally/format
Each API endpoint can filter data based on three different criteria:
Date
Vehicle
Route
This screen is also utilized in vehicle and route details. When a specific route is selected, the tally records related to that route are listed, and the data can be filtered by vehicles. Similarly, when a specific vehicle is selected, routes are listed and can be filtered by the selected route. The development for this part has already been completed.
In this screen, we need to prioritize the following:
Entry of Tally Records: The ability to enter a tally record and view details related to it.
Details View: The details screen should display:
Vehicle movements during the selected date and time range.
Management of payments received from the service recipient and payments made to the service provider.
Approval status of the service by both parties.
Listing, deletion, and response management for disputes.
Reconciliation Creation:
Reconciliation is the process of mutual approval between the service provider and service recipient regarding the services provided. Reconciliation is managed separately with both the service provider and service recipient.
Only payment and tally records are included in the reconciliation process.
Once the tally is created, it is sent to both the service provider and service recipient.
When both parties approve the reconciliation, it is automatically converted into an invoice and reflected in the cash management system.
Reconciliation Details:
In the reconciliation details, we aim to manage disputes, payments, and tally records. Within a selected reconciliation, we need to:
Add or remove tally records and payment records.
Route Creation and Editing
When creating a new route or editing an existing one, we want to create a path by setting points according to the route's schedule and then assign passengers to these points along the route.
Map Integration: While doing this, we should display all personnel from the factory associated with the route on a map. The personnel who are selected should be marked in red, while those who are not selected should be shown in grey.
This screen is partially completed, and the remaining tasks need to be finalized.
We don't want any design. We want all elements to be developed with standard inputs. All of these are available in the project. We want all operations to be done with FormBuilder whenever possible, and this is how we currently work in our current code. I shared with you the 4 most difficult jobs and the general workflow. If you can give me a budget and time for these 4 works, I can share another tasks
ERP automation system designed for companies involved in student and personnel transportation. This system allows for the management of income, expenses, and work records, along with live vehicle tracking and route management. The project is utilized by three different parties: the Management Office, the Service Recipient, and the Service Provider.
Tasks to be Completed:
Tally Listing Screen:
This screen is commonly used across multiple other screens. The tally listing screen is shared by both service recipients and service providers. Depending on which user class accesses the screen, the API delivers data specific to that class.
/api/manager/tally/format
/api/contractor/tally/format
/api/factory/tally/format
Each API endpoint can filter data based on three different criteria:
Date
Vehicle
Route
This screen is also utilized in vehicle and route details. When a specific route is selected, the tally records related to that route are listed, and the data can be filtered by vehicles. Similarly, when a specific vehicle is selected, routes are listed and can be filtered by the selected route. The development for this part has already been completed.
In this screen, we need to prioritize the following:
Entry of Tally Records: The ability to enter a tally record and view details related to it.
Details View: The details screen should display:
Vehicle movements during the selected date and time range.
Management of payments received from the service recipient and payments made to the service provider.
Approval status of the service by both parties.
Listing, deletion, and response management for disputes.
Reconciliation Creation:
Reconciliation is the process of mutual approval between the service provider and service recipient regarding the services provided. Reconciliation is managed separately with both the service provider and service recipient.
Only payment and tally records are included in the reconciliation process.
Once the tally is created, it is sent to both the service provider and service recipient.
When both parties approve the reconciliation, it is automatically converted into an invoice and reflected in the cash management system.
Reconciliation Details:
In the reconciliation details, we aim to manage disputes, payments, and tally records. Within a selected reconciliation, we need to:
Add or remove tally records and payment records.
Route Creation and Editing
When creating a new route or editing an existing one, we want to create a path by setting points according to the route's schedule and then assign passengers to these points along the route.
Map Integration: While doing this, we should display all personnel from the factory associated with the route on a map. The personnel who are selected should be marked in red, while those who are not selected should be shown in grey.
This screen is partially completed, and the remaining tasks need to be finalized.
We don't want any design. We want all elements to be developed with standard inputs. All of these are available in the project. We want all operations to be done with FormBuilder whenever possible, and this is how we currently work in our current code. I shared with you the 4 most difficult jobs and the general workflow. If you can give me a budget and time for these 4 works, I can share another tasks