Perfect Orders dropped 3 percent.
Who caused it? ChatKa shows you.

ChatKa shows the real chain:
supplier delays → shortages → substitutions and reveals exactly why Perfect Orders moved and what it cost you, directly inside Microsoft Teams or Slack.

🧩 Perfect Orders • Supplier Delays • Substitutions • OTIF

"Why did perfect orders drop yesterday?"
Answered in minutes.

See ChatKa in Action

Example: Why Perfect Orders Dropped Yesterday (CFC3)

Yesterday, Perfect Orders in CFC3 fell from 64.8% → 58.9%.
ChatKa revealed the exact root-cause chain in minutes without dashboards, exports, or queries.

1. Supplier delays created immediate shortages

Three inbound issues drove most of the drop:

Fastship arrived 10h late to CFC2 and 8h late to CFC3
→ 1,120 eaches affected across 8 chilled SKUs

GreenFields short-delivered
→ 680 eaches across 4 produce SKUs

FreshCo arrived 7h late
→ 1,150 eaches affected across 6 meat SKUs

Total shortages: 1,460 eaches refunded across 13 chilled + produce SKUs.

2. Shortages triggered substitutions across chilled + produce

• Chilled substitutions rose from 6.1% → 9.1%
• ~990 eaches substituted
• 3 produce SKUs went fully out-of-stock by 14:00
• This alone accounted for ~1,000+ order changes.

3. Customer impact escalated quickly

• 184 customer credits issued
• 412 orders refunded
• 40 complaint tickets
• 2 delivery routes pushed near cut-off due to consolidation reshuffle

Estimated margin impact

ChatKa quantifies the real financial effect:

• Refunds: £1,380
• Customer credits: £540
• Substitution margin delta: £315
• Delivery adjustments: £180
• Complaint-driven LTV loss: £260

Total: ~£2,675

ChatKa produced this analysis in minutes — without dashboards, BI queries, or manual reporting.

Traditional analysis:

Hours

ChatKa:

Minutes

See how ChatKa works in Microsoft Teams or Slack

Why did perfect orders drop yesterday for CFC3?
Compare Perfect Orders across all CFCs for last month
Show supplier delays affecting chilled yesterday

How ChatKa plugs into your operation

1

Connect to your warehouse data

Read-only access to your existing data warehouse (Perfect Orders, inbound delays, chilled, substitutions, OTIF).

2

Map your KPIs

We configure 8–10 KPIs: Perfect Orders, Supplier Delays, Substitutions, OTIF, Chilled pick, Cut-off windows.

3

Ask in Microsoft Teams or Slack

"Why did perfect orders drop yesterday?" → ChatKa gives the chain and the financial impact in minutes.

What changes for you

No more Monday firefights

You stop hunting for the cause of KPI drops.

Full visibility on Perfect Order drivers

Supplier → chilled → substitution → cut-off chain in minutes.

Less time wasted in cross-team calls

No more analytics → chilled → inbound → supplier ping-pong.

Protected margin

Real-time view of cost impact from failures.

4-Week Pilot

Week 1
Connect to warehouse data (read-only)
Week 2
Configure Perfect Orders, Supplier Delays, Substitutions, OTIF
Week 3
Run daily questions in Microsoft Teams or Slack
Week 4
Present impact review (time saved, issues identified)

Includes: KPI mapping, Microsoft Teams or Slack setup, 8–10 KPIs, weekly check-ins.

Pricing

Root-Cause Sprint — 4–6 Weeks

1–2 CFCs

  • Covers inbound → perfect order issues
  • Live Chatka instance on your data
  • Weekly insight reviews
  • Outcome: quantified root causes + rollout plan
  • Typical range: low five figures

Network Guardrail — Annual

Covers full CFC + spoke network

  • Full KPI domain pack
  • Daily anomaly explanations
  • Microsoft Teams or Slack for all operational teams
  • 12-month contract
  • Typical range: low-to-mid five figures per year

Security & Access

Read-only data access

No write permissions required

Hosted on Google Cloud

Secure, scalable infrastructure

Uses your warehouse's native permissions

Leverages your existing access control

No PII required

Works with aggregate operational data

SOC2-aligned architecture

Following security best practices

Trusted by operations teams using modern data warehouses

Perfect Orders · Inbound Delays · Chilled · Subs · OTIF · Cut-offs