Skip to content

Flex ConnectConnect

EDI for logistics and maritime APIs, connected to everyone you work with.

Flex Connect is the maritime API and integration layer on Microsoft Dynamics 365. It links the bookings, voyages, containers and documents in Flex Run with customers, carriers, ports, customs, banks and data providers, through reusable services instead of one-off interface projects.

Flex Connect
  • Customer portal
  • Carriers
  • Ports & terminals
  • Customs · Descartes
  • Banks
  • AIS & data
  • eBL platforms

Flex Run on Microsoft Dynamics 365

REST / JSON, OData / D365 services, Webhooks & events, XML, EDI, SFTP / managed file exchange, Azure integration services, Queues & asynchronous messaging, OAuth / Microsoft Entra, API management & monitoring

What Flex Connect is

The API and integration layer between Flex Run and your partners.

Flex Connect is a set of reusable services: APIs, EDI messages and events. It links the bookings, voyages, containers and documents in Flex Run with customers, carriers, ports, customs, banks and data providers, instead of one-off interface projects.

What it takes care of

  • APIs for portals and partners
  • EDI with carriers, ports and terminals
  • Events when something changes
  • Customs messages
  • eBL platforms
  • Vessel, schedule and reference data

Where it stops

Flex Connect moves data in and out; it does not hold the operation. The record itself lives in Flex Run, and what the data says about your performance is shown in Flex Performance.

Flex Maritime Logistics, layer by layer

  1. Flex IntelligenceAI that reads, checks and flags what needs attention. Your people decide.
  2. Flex PerformanceKPIs and reporting in Power BI and Microsoft Fabric: how are we performing?
  3. Flex ConnectYou are hereAPIs, EDI and events that link Flex Run with customers, carriers, ports, customs and data providers.
  4. Flex RunThe maritime ERP layer: bookings, voyages, cargo, containers and finance in one record.
  5. Microsoft Dynamics 365ERP, CRM, security and the Microsoft cloud
    Finance & Operations · ERPSales · CRM

Each layer builds on the one below. Insight is only as good as the record underneath.

Flex runs only on Microsoft Dynamics 365 Finance and Operations. It is not a standalone system.

Why Flex Connect

Maritime logistics is a network business.

A booking, container, voyage or document rarely stays inside one organisation. Flex Connect gives that exchange a deliberate place, connected to the same operational and financial record your teams run the business on.

  • Customers & portals

    Requests, quotations, documents and shipment status, through the Flex Customer Portal or your customers’ own systems.

  • Carriers & agents

    Schedules, rates, bookings, milestones and shipment status from the service providers you work with.

  • Ports & terminals

    Cargo, container and vessel events and operational status, shared where collaboration needs it.

  • Customs & compliance

    Declarations, messages, statuses and releases, plus approved screening services such as sanction lists.

    Booking vetting and sanctions screening
  • Banks & finance

    Invoices, payments and reconciliation, linked to the transaction they belong to.

  • Data providers

    AIS positions, vessel, schedule and reference data, brought into the operational context.

    AIS data for vessel visibility
  • Documents & eBL

    Shipping instructions, B/L and eBL data, exchanged with document platforms and your DMS.

  • Specialist systems

    TOS, WMS and other best-of-breed platforms stay in place and connect through the same layer.

Connected in practice

Every partner on its own terms.Every answer on the same record.

In practice: at Vollers HoogTij, barriers, weighbridges, OCR, RFID and the silo MES connect to Flex; Seatrade runs container traceability via EDI.

From connection to value

Being connected is the means. Control is the goal.

  • Less re-keying

    Information moves digitally between parties instead of through email, portals and spreadsheets.

  • Better context

    External events and documents stay linked to the booking, voyage, container or invoice they belong to.

  • Ready for insight

    Connected, governed data gives KPIs and exceptions a reliable base.

See Flex Performance

Integration in action

Customs, carrier rates and eBL. Connected end to end.

Three flows where Flex Connect does the work between Flex Run and the outside world. Each one runs out and back again, so the answer lands on the record it belongs to.

Customs integration

Bill of Lading submission and customs responses, routed through Descartes.

Illustrative flow

Out

  1. Flex RunCreates the Bill of Lading
  2. Flex ConnectSends the B/L as XML
  3. DescartesCustoms hub routes the submission
  4. CustomsProcesses the submission

Back

  1. CustomsSends a response
  2. DescartesRoutes the response as XML
  3. Flex ConnectReceives the XML and its disposition codes
  4. Flex RunInterprets the codes, updates status and required actions

Each XML response carries disposition codes that Flex Run interprets. Alerts follow through Flex Intelligence where needed.

Customs integration for bills of lading

Ten end-to-end workflows show where Flex Connect fits.All ten maritime workflows in Flex in Action

Port of Aarhus

“The main reason for our customers to come to Port of Aarhus is the location, the infrastructure and the facilities. For sure the dataflow is very important as well. This was the reason to choose Ultimate Software, it was a strategic choice.”

Henrik Munch JensenAssistant Director, Port of AarhusRead the customer story

APIs, EDI and events

The right technique for every partner.

Flex Connect is not tied to one protocol. The technique follows the partner, the volume, the timing and the security a connection needs.

API-first where practical, event-driven where timing matters, asynchronous where resilience matters, and file-based exchange where the partner requires it.

  • REST / JSON
  • OData / D365 services
  • Webhooks & events
  • XML
  • EDI
  • SFTP / managed file exchange
  • Azure integration services
  • Queues & asynchronous messaging
  • OAuth / Microsoft Entra
  • API management & monitoring

Connect once. Reuse where it makes sense.

Every useful integration should make the next one easier. Recurring connections become documented services in a growing library, so a proven connection is reused or adapted instead of designed again.

  1. 01DefineThe business object and contract: what is exchanged, who owns it and which rules apply.
  2. 02ConnectChoose the pattern, authenticate, validate, map, handle errors and monitor.
  3. 03ReuseAdd the service to the library, so future connections build on it.

For every interface we agree the source of truth, who may call it, which system owns the transaction and what happens when an exchange fails.

Questions

Common questions about Flex Connect.

01

Do we have to replace the systems we already use?

No. Flex Connect is not a promise to replace every specialist platform. Strong systems such as a TOS, WMS, DMS or customs hub stay in place and connect to Flex Run through reusable APIs, messages and data exchange.

02

Which integration standards does Flex Connect support?

The technique follows the partner: REST and JSON APIs, OData and Dynamics 365 services, webhooks and events, XML, EDI, SFTP and managed file exchange, queues and Azure integration services. For eBL platforms the direction is DCSA-aligned exchange; conformance is validated per platform.

03

Does Flex Connect support EDI for shipping partners?

Yes. Shipping EDI, XML, files and SFTP remain part of maritime integration. Flex Connect uses the smallest pattern that fits instead of forcing every partner into the same technical model.

04

Who maintains the interfaces?

Operational ownership is part of every service design. Per interface we agree the source of truth, who may call it, which system owns the transaction, how failures and retries are handled and who monitors it. Reusable services are documented in the library, so changes are made once.

05

How are security and governance handled?

Connections run through authenticated, authorised services, using OAuth and Microsoft Entra, with API management, logging and monitoring. Partners and AI agents get defined services with explicit permissions, never unrestricted access to the ERP database.

Start with the process, not the protocol.

Tell us which systems, partners and decisions need to connect. We look at your integration landscape and show which reusable services fit it.