Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Company-Centric Structure: Each company has the autonomy to onboard its own collectors as app users, thereby establishing a dedicated user base within the system.

  2. Customisable Preferences: Companies have the flexibility to define their app preferences, such as specifying premium requirements, configuring app functionality, and setting their preferred products for collection.

  3. External Connections: Companies can tailor their external connections and define the scope of their interactions within the system, granting them control over data flow and integration.

  4. Farmers: All farmers are onboarded or connected to specific companies, fostering a well-organised and efficient ecosystem.

  5. Product Transactions: The flow of product transactions occurs from farmers to the company table, creating a clear linkage between the products collected and the associated payment transactions.

  6. Payment Transactions: Payment transactions, vital for compensation to farmers, flow from the company to the farmer. The verification process is conducted seamlessly through the use of farmer cards.

...

Setup Flow

  • A company is first added/synced to the connect db

  • All the buyers and suppliers are also added/synced to the connect db

  • Company users will get added to the connect db

  • They can access the app after connecting the app to the connect server

  • They can add products under the company from the interface

Data fields

APIs

Mobile app Configurations

...

Standardising data exchangeData structure 

In the connect database structure we focus mainly on two main components, companies and their farmers and their transactions. Additionally, there are database tables to configure and customise the app, set premium payment to farmers and some access control details

On the farmer side, we are collecting the following fields

Transaction files are like this

Premium table

Concept

  • Stand-alone module to handle all the incoming and outgoing data to Trace

  • It will get connected to the mobile app via APIs and fetch data then sync it to trace

  • It will also be connected to a system like PTCAN and then send and receive data

  • It has its own DB and a fronted and possible to self-host

  • There will be a Python lib to manage all the interactions to the standalone module

  • ThisPythonn lib is installedon thee trace server and other systems to push and pull data

  • Users can also do mobile app customizations in the module like custom forms

  • It handles the transactions and connections from a single company perspective.

Flow

...

A company is first added/synced to the connect db

...

All the buyers and suppliers are also added/synced to the connect db

...

Company users will get added to the connect db

...

They can access the app after connecting the app to the connect server

...

Modules

  • Nodes/companies: Module to manage all the companies/farmers. Each company will have many to many relations for suppliers and buyers (self)

  • Transactions: Only external transactions. Each transaction will have a

...