Logistics · freight

Carrier APIs fail all the time. NORTHPIER now fixes the mapping and replays from the failing step instead of re-keying shipments.

31% fewer manual re-keys

4.2M shipments a month

11 carrier APIs

A failed label run waits, we fix the mapping, and replay picks up at step four.

Tomás Reyes

Head of platform

NORTHPIER

NORTHPIER case study cover

Where they started

NORTHPIER books freight across eleven carriers, each with its own API quirks. When a label request failed, operators re-entered the shipment by hand, sometimes creating a second booking.

What they built

A booking workflow validates the address, rates the shipment, books it and generates the label as separate steps. Carrier calls run with a concurrency key per carrier, so one slow API no longer blocks the others.

When a carrier changes a field and every booking starts failing, the runs pause instead of dying. The team ships the mapping fix and bulk-replays the paused runs from the booking step.

What changed

Manual re-keys dropped 31% in the first quarter, and duplicate bookings stopped entirely because every booking call carries the shipment ID as its idempotency key.

Get started

Ship the agent. Keep the receipts.

Free for 50,000 steps a month. No credit card, no separate workers, and your first durable workflow deployed before lunch.

orrindel

Durable runtime for AI agents and automations. Every run, in plain text.

Book a 20-minute demo →
All systems normal
99.99% uptime · last 90 days
90 days agotoday
regions us-east · eu-west · ap-south
soc 2 type ii · gdpr · hipaa (baa)
sdk v4.2.1 · node · python · go
© 2026 Orrindel Labs, Inc.PrivacyTermsSecurityMade in plain text.

Create a free website with Framer, the website builder loved by startups, designers and agencies.