Filodos

ERP integration overview

Your ERP knows the orders, depots, and customers; Filodos knows where the vehicles actually went. This page tells you what can flow today and how each system connects. Part of the documentation.

What flows today

Every connector below is built on the same two public pieces — the read API and webhooks — so anything your system can do over HTTPS works now; ready-made connectors per vendor follow.

  • Trips and mileage → your system. Completed trips with distance come through trip.ended pushes the moment a trip closes, or through the trips API on your schedule.
  • Arrivals → delivery confirmation. geofence.enter and geofence.exit post zone crossings as visit confirmations with timestamps. Link each vehicle to its zones first.
  • Incidents → your system. alarm.critical fires on SOS, collision, and rollover.
  • Vehicles and drivers. The fleet list and the driver rollups read through the API — match once on plate or driver name, then read on schedule.

With the SoftOne, Entersoft, and SAP Business One connectors, two more flows work: ERP customer and depot sites become zones, and each visit can write a note back into the ERP. See ERP sites and zones and Visit notes in the ERP.

Not flowing yet: order numbers onto trips, and write-back of mileage into ERP fleet records.

Setup path per system

  • Odoo (Community or Enterprise). First in line: a ready-made connector for Fleet, Inventory, and Sales. Until it ships, use the generic path below — Odoo's own API tools map Filodos's trips and visits onto deliveries directly.
  • SAP Business One. A ready-made connector through the Service Layer: customers or warehouses become zones, and a visit can make an activity in SAP. See Connect SAP Business One.
  • SAP S/4HANA, Microsoft Dynamics 365, Oracle NetSuite, Sage. The generic path below, through each system's standard REST or service-layer API. A ready-made connector per system follows.
  • SoftOne and Entersoft (ENTERSOFTONE). Ready-made connectors: an administrator adds the connection on the Organization → ERP page, and managers set up the sites and the visit notes. See Connect SoftOne or Entersoft.
  • Epsilon Net. The generic path below, set up together with your team against your installation. A ready-made connector follows.
  • Any other system. The generic path is the whole integration: an API key with the scopes the feed needs, plus webhook subscriptions for the events. Give the developer reference to whoever builds it.

Where to start

  1. Draw your depots and customer sites as zones and link the vehicles (Geofences page) — arrivals need links before they fire.
  2. Create an API key with devices:read, trips:read, and events:read.
  3. Subscribe your endpoint to trip.ended, geofence.enter, and geofence.exit, and send a test ping.
  4. Match plates and driver names once, then file trips and visits on arrival.

No ERP yet? We can recommend a lightweight setup around Odoo — write to info@filodos.gr.