ORDER TRACKING

Order tracking
built for the
AI Agent Era

A tracking page restates the scan the customer already read. KODIF reads it, works out what it means, and tells them first — then fixes what went wrong without a ticket.

  • 100+

    Native ecommerce integrations, all action-capable

  • 9 days

    Contract to resolving delivery issues in production

  • 0

    Engineering tickets to change a coverage rule

Order No. #KD-48291

Delayed at Memphis facility

  1. Carrier scan

    Mon, Sep 23 • 11:41 AM

  2. In transit

    Tue, Sep 29 • 9:30AM

  3. Issue detected

    Tue, Sep 29 • 11:30AM

Customer Notified

exception detected customer notified first carrier trace filed replacement rule armed

END-TO-END AUTOMATION

Own the journey, not just
the tracking number.

Carrier scans are raw events. The agent reads them against the order, the promise date, and your policy — and decides whether the customer needs to hear from you.

LIVE SHIPMENT · ORDER #48156

  1. Label created · Naadam fulfillment
  2. In transit · departed Secaucus NJ
  3. Arrived · Memphis TN facility
  4. No scan for 51 hours — exception detected
  5. Customer notified, trace filed

The customer never wrote in. The agent moved first.

HOWEVER THEY ASK

Chat, email, voice
or your branded
tracking page

“Where is my order?” arrives everywhere at once. Every route reaches the same agent, the same shipment data, and the same resolution policies.

01

Chat

A real answer from fulfillment status and scan detail — not the tracking number read back to them.

9:41●●● ▮

‹ N

NaadamAI agent · replies instantly

Where's my turtleneck? It said Tuesday.

It's stuck at the Memphis facility — no scan for 51 hours, so it's genuinely late rather than just slow. I've filed a trace with UPS.

If it hasn't moved by Friday I'll ship you a replacement automatically. You don't need to chase this.

That's great, Thank you

We're on it

Carrier trace filed · ref 7741-MEM

Replacement armed for Friday 09:00

You'll hear from us either way

No ticket created

ONE HUB

Track, claim, return
one place, one agent.

The tracking page is where customers turn up when something is wrong. Make it the place it gets solved, not the place they discover they need a second portal.

Where is my order

Fulfillment status and carrier scan detail, read and interpreted — including split shipments, partials, and backorders.

  1. Order placed
  2. In transit
  3. Issue detected
  4. Covered

Reroute or hold

Change the address or hold a package in transit where the carrier still allows it, mid-conversation.

Delivered to a different door

Claim approved Replacement ready

Replacement ready

Reship or claim

Lost, or marked delivered but never received: the agent reships or opens the claim on your policy, with the evidence attached.

Freeze Dried In Transit

Order No. #KD-48291

Reroute

Hold Package

Return or exchange

If the issue is the product rather than the delivery, the same agent carries straight on into a return or exchange.

I'd like to return this and get a different size

No problem. I've created a free return label and an exchange for the right size.

  • Free return label
  • Exchange initiated

HOW IT WORKS

From carrier scan
to resolution,
without a ticket.

The agent watches the feed continuously. A problem becomes an outbound message long before it becomes an inbound one.

  1. 01

    The scan lands

    Every carrier event streams in against the order, the promise date, and the service level the customer paid for.

  2. 02

    The agent spots the exception

    Stalled, misrouted, delayed, or delivered-but-not-received — judged against your thresholds, not the carrier's status code.

  3. 03

    The customer hears first

    An outbound message on their channel with the explanation and the options, before they have had to chase anything.

  4. 04

    The fix executes

    Trace, reroute, reship, or claim — carried out on your policy, with the whole thread attached if a human ever needs it.

CUSTOM EDIT RULES

Flexible resolution rules
without complex workflows

Create multiple resolution policies based on order value, customer status, carrier, destination, or how long a shipment has been in transit.

Under $50

Wait 24h, then reship

$50 – $200

Carrier trace, then reship

Over $200

Route to a person

In transit 3+ days late

Notify customer first

GUARDRAILS

AI conversations.
Deterministic execution.

The AI understands the customer, but the resolution engine controls every action according to your predefined policies.

THE AGENT CANNOT

Approve an uncovered order

THE AGENT CANNOT

Exceed a claim ceiling

THE AGENT CANNOT

Settle a repeat claim outside your rules

AI COVERAGE INSIGHTS

Ask your delivery
data anything

Use natural language to understand which carriers and lanes generate the most delivery contacts, where exceptions cluster, and what failed deliveries cost you in reships and refunds.

ASK Which lanes generate the most WISMO contacts?

42% of delivery contacts came from three West Coast metro lanes on one carrier

  • Where are delivery exceptions clustering this month?
  • What share of shipment questions resolved without a person?
  • What did failed deliveries cost us in reships?

Get in touch

Your hardest CX ticket
is our best demo.

KODIF doesn't stop at answering. It identifies the customer, checks policy, takes action, updates systems, creates a test, and turns the conversation into measurable CX intelligence.