Freight Claims

Freight claims caught before the window closes.

We encode each carrier’s and co-op’s claim rules against the receiving data you already keep, so claimable events flag inside the window.

  • AI implementation services
  • Per-carrier and co-op claim rules, encoded
  • Claimable events flag inside the window
  • Documentation assembles itself

Built with the leading AI platforms

NVIDIAAnthropic
Peter Enestrom, founder of Zaigo

Led by Peter Enestrom and the Zaigo AI & engineering team

YaleColumbia UniversityMicrosoft

The broken Friday

The claim was lost on the dock, not in the filing.

From operators we have sat with: inventory and pricing managers at multi-store hardware retailers in a national co-op, 19–23 stores on Epicor Eagle-class systems — not shopping for software, drowning between the receiving dock and the inventory adjustment.

  • The missed freight claim window

    Item booked as received 78 days ago, now past the 30-day co-op claim window and over the dollar limit — it ends as an inventory adjustment.

  • The shortage surfaces weeks later

    The damage or shortage shows up at the next count, weeks after the carrier’s claim window closed — by then it is a write-off, not a claim.

  • Return to vendor, returned too late

    Dead stock sits because nobody tracked the vendor’s return window — RTV items age past the deadline and the credit dies with it.

  • Every carrier’s rules are different

    Each carrier and the co-op sets its own window, dollar limit, and required documentation — the rules live in nobody’s head, so nothing gets checked.

  • Landed cost creeps untracked

    Demurrage accruals go untracked and land in landed cost — another recoverable dollar nobody flags before it hardens into the P&L.

What manual costs

An expired window turns a claim into a write-off.

What the manual way looks like at a multi-store retailer where freight claim management is a spreadsheet, a filing cabinet, and one person’s memory. Your numbers will differ — the first store we reconcile puts figures on yours before anything gets built.

Day 30When the claim window closed in one anonymized co-op program — an item received 78 days earlier missed it and the dollar limit
Inventory adjustmentWhere a missed freight claim lands on the P&L when the window closes unfiled
NobodyWho checks each receipt against every carrier’s and the co-op’s claim rules under the manual way

From anonymized engagements — inventory managers at multi-store hardware retailers in a national co-op

How it works

We encode your claim rules.

No new system for your team to learn. The claim rules your best person carries in their head become the catch at receiving.

  1. 01

    Reconcile one store’s receipts

    We reconcile one store’s last quarter of receipts against carrier and co-op claim windows — what was claimable and expired unfiled. That gap starts the rule set.

    First store
  2. 02

    Encode the claim rules end-to-end

    Per-carrier and co-op windows, dollar limits, required documentation, and RTV deadlines — documented against the receiving data you already keep, yours to keep.

    Per carrier & co-op
  3. 03

    Receiving flags the claimable event

    Receipts check against the encoded rules; claimable events flag inside the window with documentation assembled. Exceptions land in a queue with days left shown.

    Every receipt
Not a claims-filing firm

The claim isn’t lost in the filing. It’s lost on the dock.

The claims-filing firms recover a percentage of what you already caught. The software holds the shipment data — it doesn’t hold your co-op’s claim rules. We encode those, so the catch happens at receiving, inside the window.

Our AI does the reading — every receipt, blind-received item, and shortage against your encoded carrier and co-op rules — and your rules do the judging: claimable events flag inside the window, documentation assembled; the rest reaches a person.

Peter Enestrom, founder of Zaigo
Who builds it

Led by Peter Enestrom.

Co-Founder — leads AI & Engineering

Pete Enestrom

Every engagement is led personally by Pete, working with the Zaigo AI & engineering team from the two-week audit through the production handover. The person who scopes the work is the person who builds it.

Education
Yale & ColumbiaGraduate
Background
Microsoft & IntelFormer
Experience
Exited FounderVenture-Backed

Background

Questions

Asked by inventory and pricing managers.

The straight answers, before you book anything.

What’s holding your business back?

A workflow ready for automation. An AI product you want to build. A problem that has sat on the roadmap for years. Let’s talk about what it would take to solve it.

Talk to Zaigo