Technical Introduction

GrowERP is an Admin Flutter frontend component for Android, IOS and Web using This application is build for the stable version of flutter, you can find the installation instructions at:

Although all screens work on IOS/Android/Web devices, a smaller screen will show less information but it is still usable.

It is a simplified front-end however with the ability to still use with, or in addition to the original ERP system screens. The system is a true multi company system and can support virtually any ERP back-end as long as it has a REST interface.

The system is implemented with state management with the documentation, data models, automated integration tests and a separated rest interface for the different backend systems.

The backend is using the Moqui ERP and framework

The system configuration file is in /assets/cfg/app_settings.json. Select Moqui and for older versions select OFBiz.

The backend Moqui system needs some extra components such as for GrowERP itself, Stripe for payment processor and the PopReststore for the website generated for every company.

For test purposes we can provide access to Moqui or OFBiz backend systems in the cloud.

Additional ERP systems can be added on request, A REST interface is required. The implementation time is 40+ hours.

Data organization

Obviously the frontend is following the backend datamodel to a great extend, however a bit less flexible. Separation by owner is done in the API interface to the backend.

On a user level

All data within an created company and admin is controlled or linked to the ownerPartyId with a special partyTypeId 'owner' .

The major database party (owner/company/user) view used: owner -> (rel) company -> (rel) person -> user account --> sec userGroup |-> postal/telephone etc

When a user logs in, the system can retrieve the above from the user account. The ownerCompanyParty is now the second level, the first level is just an empty placeholder. For convenience the ownerPartyId at the top holds the owner company partyId at the secondlevel.

currently just employees and admins of the owner company can login. Customers can login to the e-commerce website.

A customer user has a single login for all owner websites and will be linked to an new owner when the customer uses a not yet owner website.

other entities

Other entities like products, categories etc use the 'ownerPartyId' field to separate between owners. It contains from now on the

Flutter Module organization

3 layer screen approach

  1. The application
    1. Menu structure
    2. User access
    3. routing
  2. The core screen system
    1. template layout
      1. appBar
      2. navigation rail/left menu selection
      3. top/bottom tab selection.
      4. main menu
    2. screen definitions
    3. registration/login
    4. multi company
    5. employee/admin
    6. supplier/customer/lead
    7. companies
    8. tasks
  3. The package plugins
    1. Marketing
    2. Sales/purchase Order/ Accounting
    3. users/companies
    4. Website
    5. Catalog
    6. Inventory
    7. Chat

The main principle of presenting screens is to show the screen by calling the template with the parameter of the screen name. A screen can be single widget of a screen with tabs which are shown by the template.