Filatto is a SaaS for micro-mobility based delivery which is able to interact between demand and supply integrating different components

Principles :

• cloud based
• full-API
• modular
• open source

Key components :

• manage, organize, diplay supply
• collect and organize the status of the delivery workforce
• provide to the consumer the option to order
• accept the order and pay
• track delivery status

In this document we present the infra design for the order and delivery

Sketch of the infra suggested

We are going to use the separate components

The suggested ERP for the project is odoo , reason is:

• cloud based
• on prem/Saas
• open source, highly configurable
• huge marketplace of apps with many vendors
• website/e-commerce builder
• full-API

view on odoo apps

In any case the middelware is a separate component and can be integrated with any full-API ERP.

The middelware is the key component of the project and hadles all the requests between the three parties:
* consumer app
* provider app
* delivery app
* ERP

The middelware will receive and map supply and demand

The data storage strategy consists in using different types of DBs to store and query the data.

• Demand and supply will be stored in a relational DB
• Maps and areas as geo shapes in mongo
• Customers preferences as graphs

storage and suggested data bases

An additional service will take care of optimizations:

• delivery availability
• operating areas
• routing: delivery time

Plese refer to infra

deployment of antani

The consumer app is designed following this project intertino .
In short:

• front-end dev using nodejs (react/angular)
• test with ionic
• compile with ionic

The end result will be an android or ios app.

The users of the app will be:

• suppliers
• delivers
• consumers

|company|infra|
|takelocal|??|

|company|infra|
|??|??|

• Restaurants-clients: food delivery
• Shops-clients: grocery delivery
• C2C: parcel delivery

• Definition of shifts: relative restaurants, operating areas, operating time shifts
• Booking rider's shifts from the ERP
• Fleet management: route the request on other fleets in case riders are booked
• Three categories of rider payments: freelance, monthly salary, weekly salary
• Riders availability calendar, booking system, performance reporting, bonus/malus reporting
• Payment system: e-invoice, direct debit