Carriers and third-party logistics providers publish shipment status through APIs and EDI messages. Lima reads tracking events, proof of delivery and exceptions from DHL, UPS, FedEx, XPO and others through their APIs (polling and push) and through EDI 214 and 856 messages, so on-time-in-full can be measured from the carrier's own record.
Each method has a job. The first load uses the bulk method; the daily run uses the incremental or change-capture method; write-back uses the interface the system itself uses.
| Method | What it does | When it is used |
|---|---|---|
| Carrier APIs | Polls and receives tracking events. | Near real time. |
| EDI 214 / 856 (X12) and IFTSTA / DESADV (EDIFACT) | Reads status and dispatch messages. | Partners on EDI. |
The objects are the tables, views or records Lima reaches through the methods above. The patterns say how a copy is made and kept current.
| Object | Plain meaning |
|---|---|
| Shipments and tracking events | status by shipment |
| Proof of delivery | delivered on time, in full |
| Pattern | Supported |
|---|---|
| Full load | Yes |
| Incremental | events since the last poll |
| Change capture | — |
| Streaming | push where the carrier offers it |
| Write-back | — |
The prerequisites are what the team that runs 3PL and carrier APIs (DHL, UPS, FedEx, XPO) grants. The four steps are the same for every connector.
Incoming data = valid records + exception records. A row that fails a check is kept, routed to the person who owns it with a deadline, and replayed once fixed. The load carries on with the valid rows and the report says exactly what was held back. How exceptions work →
Lima connects from outside through the interfaces listed above with credentials your administrators grant. Where a vendor requires its own agent or add-on for a method, the prerequisites say so.
Parallel reads are capped and the cap is agreed with the team that runs the system. Large reads run inside an agreed run window. Change capture keeps the daily volume small.
A report per run: rows in, rows out, control totals and variance per table, the exceptions held back and who owns them, and whether the deadline was met.
Yes. Most estates start with one source, one target and one dataset, then add tables and patterns on the same connection.
A trial connects this system, runs a first load and ends with a reconciliation report. Your administrators see the prerequisites before anything is installed.