Get a demo

Flexport SLA reporting

Pull shipment milestone data from Flexport, calculate actual vs target transit times, and flag every missed delivery window by lane and carrier.

Get a demo

The prompt

I want to pull shipment milestone data from Flexport and build an SLA performance report by lane and carrier. Can you build me a flow that calculates actual vs target transit times, measures SLA adherence rates for each lane-carrier combination, and flags shipments that missed their delivery windows as exceptions?

Just copy and paste the prompt into a new Parabola flow to get started.

What Parabola builds

A workflow with seven steps you can edit:

1. Pull shipment milestone data from Flexport. Pickup, departure, arrival, and delivery events for every shipment in scope. API pull or scheduled export from the Flexport portal.

2. Join to the target transit time table. Every lane and carrier combination has a contracted or expected transit window. The flow matches each shipment to its benchmark on lane, carrier, and service level.

3. Calculate actual vs target transit time. Days between pickup confirmation and delivery confirmation, per shipment. Subtract the target. Positive means late.

4. Measure SLA adherence by lane and carrier. Aggregate on-time rate, average days early or late, and percentage of shipments hitting the delivery window. One row per lane-carrier pair.

5. Flag exceptions. Shipments outside the delivery window get labeled with the delay in days, the lane, and the carrier responsible. Sorted by the most overdue first.

6. Roll up to the dashboard view. Summary table by carrier showing adherence rate, total shipments, and trend vs the prior period.

7. Send the report. Emailed SLA dashboard for the weekly logistics review, plus the exception file for the operations team to action.

Why teams stop doing this manually

Flexport's portal shows individual shipment status. It does not tell you which carrier on which lane is missing SLA 30% of the time. Getting to that number means pulling a milestone export, building a lookup table for contracted transit windows, running the delta math, and counting exceptions by lane-carrier combination. By the time the ops lead finishes the export and builds the pivot, the data is three days old and the carrier review meeting has already happened.

The manual version also degrades over time. Transit window tables live in a spreadsheet that gets updated when someone remembers. New lanes get added to Flexport but not to the benchmark file. The SLA report starts reflecting stale targets, and the team stops trusting the numbers. The carrier that looks fine on the dashboard is quietly running at 68% adherence on the eastbound lane.

Operations cannot optimize what it cannot measure consistently. The moment the SLA report runs on a schedule, carrier performance becomes a managed variable instead of a periodic audit.

How it works

Step 1. Paste the prompt.

Open Parabola, paste the prompt in section 2, and let it ask follow-up questions about your Flexport scope, how your transit window benchmarks are stored, and which lanes or carriers to prioritize.

Step 2. Connect your data.

Flexport API or scheduled milestone export, plus your lane-carrier transit window table. The flow reads both on each run.

Step 3. Run it every week.

Weekly before the logistics review, or daily during peak season. New shipments pull in automatically. Updated transit targets take effect on the next run.

Related prompts

FAQ

Does this work with Flexport's API or do I need to export a file?

Both work. If your Flexport account has API access, the flow reads milestone data directly on a schedule. If you are working from scheduled portal exports, the flow reads the file from email attachment or a shared folder.

How do I set the target transit times for each lane?

You maintain a simple lookup table with lane origin, destination, carrier, and target days. The flow joins every shipment to that table. When a contract changes or you add a new lane, update the table and the next run picks it up.

Can the flow handle multiple carriers and modes in one report?

Yes. Ocean, air, and ground shipments can run through the same flow with different transit benchmarks per mode. The output segments by carrier and lane so the team sees performance by the combination that matters.

What if a shipment has missing milestone data in Flexport?

The flow labels those rows as incomplete and surfaces them in a separate tab. Missing milestones are a data quality issue worth tracking alongside the SLA numbers.

How is this different from reviewing SLA in the Flexport portal?

The portal shows individual shipment status. This flow calculates adherence rates by lane and carrier over time, compares to your contracted windows, and flags the specific shipments and patterns that need action. The aggregate view is what the portal does not provide.
Know which lanes and carriers are missing SLA, every week.
Paste the prompt, point it at your Flexport milestone data, and let the SLA report run on its own before the next logistics review.
Start for free