┌────────────────────────┬─────────────────────────────────────────────────────────────────────────────────────────────────┐
│ Problem │ Evidence │ Cost to Business │
├────────────────────────┼─────────────────────────────────────────────────────────────────────────────────────────────────┤
│ Suppliers prepare │ Logistics managers manually check supplier readiness via email/WhatsApp — 30 min per shipment │
│ cargo before carrier │ (source: user-provided journey map). Late departures discovered only after carrier API fires │
│ handover, but │ post-cutoff — reactive, no warning (source: current GoTrack API architecture). Manual ETA │
│ GoTrack's visibility │ update + customer notification adds 25 min (source: user journey). At 180 shipments/month │
│ starts at carrier │ per customer × 55 min rework × 35 enterprise customers = 5,775 hrs/month wasted across │
│ API — creating a │ customer base (assumption: 180 shipments/customer/month — validate against Q1 2025 shipment │
│ "first-mile blind │ volume data before funding). │
│ spot" that causes │ │
│ late departure │ │
│ surprises. │ │
├────────────────────────┼─────────────────────────────────────────────────────────────────────────────────────────────────┤
│ Solution │ Mechanism │ Expected Impact │
├────────────────────────┼─────────────────────────────────────────────────────────────────────────────────────────────────┤
│ Lightweight supplier │ Suppliers log cargo readiness, upload docs, flag delays in a mobile-friendly portal. GoTrack's │
│ portal integrated │ AI factors supplier-reported readiness into predictive ETA models, surfacing pre-carrier risks │
│ into GoTrack's │ in customer dashboards 24–72 hrs before carrier handover. Replaces email/WhatsApp chase loops. │
│ shipment object and │ 35 customers × 180 shipments/month × 55 min saved × $42/hr blended logistics manager rate │
│ AI-driven ETA engine. │ (source: 2024 Gartner supply chain compensation survey, global avg) = **$2.43M/year │
│ │ recoverable time** (assumption: 180 shipments/customer/month). **Downside case: if adoption is │
│ │ 40% of estimate: $972K/year.** │
├────────────────────────┼─────────────────────────────────────────────────────────────────────────────────────────────────┤
│ Risk │ Probability │ Kill Criteria │
├────────────────────────┼─────────────────────────────────────────────────────────────────────────────────────────────────┤
│ Suppliers don't adopt │ High — requires behavior change at supplier level, not direct customer. If <30% of invited │
│ portal or log data │ suppliers complete onboarding by D30, or if supplier-reported data quality <70% match vs │
│ inconsistently. │ actual carrier handover timestamps by D60 → pause Phase 2 rollout and re-examine incentive │
│ GoTrack's AI trained │ structure. Medium probability that AI model degrades if supplier data is sparse/unreliable — │
│ on carrier API data │ if ETA prediction error increases >15% vs current baseline by D90 → roll back AI integration │
│ may not generalize to │ and revert to carrier-only model. │
│ supplier-reported │ │
│ signals. │ │
└────────────────────────┴─────────────────────────────────────────────────────────────────────────────────────────────────┘```
**The bet:** Supplier visibility is the last unsolved leg in end-to-end shipment tracking. Competitors track container after carrier pickup — we will track cargo readiness before it. The technical risk is moderate (integration with existing shipment object, AI model retraining), but the adoption risk is high: suppliers are not our direct customers, and multi-tier supply chains mean low engagement by default. We mitigate this by embedding the portal into existing supplier workflows (email/SMS links, zero login for one-time updates) and tying customer contract renewals to supplier onboarding rates as a success metric. If we clear 30% supplier onboarding by D30 and see ETA prediction accuracy improve by ≥10% by D60, the feature pays for itself in 6 months via reduced customer support load and improved NPS.
This feature **is** a supplier-facing data entry portal with AI-enhanced ETA predictions visible to GoTrack customers. It is **not** a supplier relationship management tool, a procurement platform, or a replacement for carrier API integrations — carrier data remains the primary truth source; supplier data augments it for early-warning signals only.
---
How competitors solve this today:
┌────────────────────────────────────────────────┬────────────┬────────────┬──────────────────────────────┐
│ Capability │ project44 │ FourKites │ GoTrack (this feature) │
├────────────────────────────────────────────────┼────────────┼────────────┼──────────────────────────────┤
│ Carrier API integration (ocean, air, road) │ ✅ │ ✅ │ ✅ │
├────────────────────────────────────────────────┼────────────┼────────────┼──────────────────────────────┤
│ AIS vessel tracking │ ✅ │ ✅ │ ✅ │
├────────────────────────────────────────────────┼────────────┼────────────┼──────────────────────────────┤
│ Predictive ETA with AI/ML │ ✅ │ ✅ │ ✅ │
├────────────────────────────────────────────────┼────────────┼────────────┼──────────────────────────────┤
│ Supplier readiness portal (pre-carrier data) │ ❌ │ ❌ │ ✅ (unique) │
├────────────────────────────────────────────────┼────────────┼────────────┼──────────────────────────────┤
│ Multi-tier supplier visibility workflows │ ❌ │ ❌ │ ✅ (Phase 1.2) │
├────────────────────────────────────────────────┼────────────┼────────────┼──────────────────────────────┤
│ WHERE WE LOSE: Carrier API breadth │ ✅ (1,400+ carriers) │ ✅ (1,000+ carriers) │ ❌ (350 carriers as of Q4 2024) │
└────────────────────────────────────────────────┴────────────┴────────────┴──────────────────────────────┘```
**Our wedge is supplier visibility** because no incumbent solves the first-mile blind spot, and our existing enterprise customers (pharma, automotive, FMCG) manage complex multi-tier supply chains where this gap causes the most pain. We lose on carrier API breadth — project44 and FourKites have larger carrier networks — but our differentiation is upstream: we see the delay before the carrier does.
---
WHO / JTBD: When a logistics manager at a manufacturing company (pharma, automotive, FMCG) books a shipment, they want to know if the supplier's cargo will be ready on time — before the carrier booking window closes — so they can adjust ETAs, rebook capacity, or notify downstream customers proactively instead of discovering delays reactively after the carrier API confirms a missed cutoff.
WHERE IT BREAKS: Today, GoTrack ingests shipment visibility data from carrier APIs (ocean, air, road) and AIS for vessel positions. But the first mile — from supplier's factory floor to carrier handover (port gate-in, airline cargo acceptance, trucking pickup) — is invisible. Logistics managers chase suppliers via email or WhatsApp to confirm "Is the cargo ready?" Suppliers reply inconsistently: "Yes, almost ready" with no timestamp, or they don't reply at all until after the carrier cutoff. By the time the carrier API fires a "departure delayed" event, the logistics manager has already communicated an ETA to their customer that is now wrong.
WHAT IT COSTS:
┌──────────────────────────────────────────────────────────────┬──────────────────────────────────┐
│ Metric │ Measured Baseline │
├──────────────────────────────────────────────────────────────┼──────────────────────────────────┤
│ Manual supplier follow-up time per shipment │ 30 min avg (source: user journey)│
├──────────────────────────────────────────────────────────────┼──────────────────────────────────┤
│ Time to check carrier portal for booking confirmation │ 20 min avg (source: user journey)│
├──────────────────────────────────────────────────────────────┼──────────────────────────────────┤
│ Reactive ETA update + customer notification after late │ 25 min avg (source: user journey)│
│ departure discovered │ │
├──────────────────────────────────────────────────────────────┼──────────────────────────────────┤
│ Frequency of late departure surprises per customer/month │ 18 shipments (assumption — │
│ │ 10% of 180 shipments/month; │
│ │ validate against Q1 2025 carrier │
│ │ delay event logs) │
├──────────────────────────────────────────────────────────────┼──────────────────────────────────┤
│ Customer support escalations due to unexpected ETA changes │ 2.3/customer/month avg (source: │
│ │ Zendesk ticket tags, Q3 2024) │
└──────────────────────────────────────────────────────────────┴──────────────────────────────────┘```
**Business case math:**
35 enterprise customers × 18 late-departure events/month × 55 min rework (30 min follow-up + 25 min update) × 12 months = 415,800 min/year = 6,930 hours/year.
At $42/hr blended logistics manager rate (source: 2024 Gartner supply chain compensation survey, global average): **$291K/year in direct time waste**.
Add customer support cost: 35 customers × 2.3 escalations/month × 12 months × 47 min avg resolution time (source: Q3 Zendesk data) × $38/hr support agent rate (source: GoComet HR data, 2024) = **$122K/year in reactive support load**.
**Total recoverable value: $413K/year** (conservative — does not account for customer churn risk from repeated ETA misses, which is harder to quantify but referenced in 14% of at-risk customer interviews, source: Q4 2024 CSM notes).
**JTBD statement:** "When I book a shipment, I want to see supplier cargo readiness status in real time alongside carrier booking confirmation, so I can predict delays before the carrier cutoff and communicate accurate ETAs to my customers without manual follow-up loops."
---
Core flow:
Logistics manager books shipment in GoTrack (existing flow, unchanged). Manager enters expected cargo ready date (new required field) and registers supplier contact (name, email, phone).
GoTrack auto-sends portal link to supplier 48 hrs before cargo ready date via email (primary) and SMS (fallback if email bounces). Link format: gotrack.app/supplier/[unique-token] — no login required, token expires after carrier cutoff.
Supplier opens portal on mobile or desktop (responsive web app, no native app). Portal shows: shipment ID, destination, expected ready date, and 3 mandatory fields:
Supplier submits update → GoTrack writes supplier data to shipment object as supplier_readiness nested field (schema: {status, delay_days, reason, submitted_at, documents[]}). Submission triggers webhook to AI model: recalculates ETA confidence interval for this shipment, updates predicted_eta_range field.
Logistics manager sees supplier update in GoTrack dashboard (existing shipment detail view, new "Supplier Readiness" card). If supplier flags delay, dashboard surfaces this as a yellow warning: "Supplier reports delay: [reason]. Predicted ETA adjusted +[X] days." Manager can click through to view uploaded documents or message supplier (opens default email client with pre-filled "Re: Shipment [ID]" subject line).
Carrier API event arrives (existing flow). If carrier confirms on-time pickup, supplier's "on time" status is validated (model learns positive correlation). If carrier confirms delay, supplier's delay flag is validated (model learns predictive signal). If supplier said "on time" but carrier reports delay, model learns to downweight this supplier's future signals (trust score decreases).
Integration points:
Shipment object schema change: Add supplier_readiness nested object:
{
"shipment_id": "SH-2025-00123",
"supplier_contact": {"name": "...", "email": "...", "phone": "..."},
"expected_ready_date": "2025-06-15T00:00:00Z",
"supplier_readiness": {
"status": "delayed",
"delay_days": 2,
"reason": "Raw material shortage",
"submitted_at": "2025-06-13T14:32:00Z",
"documents": [
{"type": "packing_list", "url": "s3://...", "uploaded_at": "..."}
]
},
"supplier_trust_score": 0.85 // 0–1 scale, initialized at 0.9, adjusted by model
}
AI model input feature: supplier_readiness.status and supplier_readiness.delay_days become new input features in ETA prediction model. Model outputs adjusted ETA range (e.g., "June 20–22" instead of "June 18–20" if supplier flags 2-day delay).
Customer dashboard: Existing shipment list view adds new column: "Supplier Status" (icon: green checkmark if on time, yellow clock if delayed, gray question mark if no submission). Shipment detail view adds "Supplier Readiness" card below "Carrier Updates" card.
Notification service: Leverage existing GoTrack email/SMS service (Twilio integration, already SOC 2 compliant). New templates: supplier portal invite, 24-hr reminder, 6-hr final reminder.
Wireframes:
┌───────────────────────────────────────────────────────────────────────────┐
│ GoTrack Supplier Portal [Help] [English]│
├───────────────────────────────────────────────────────────────────────────┤
│ │
│ Shipment SH-2025-00123 │
│ Destination: Hamburg, Germany │
│ Expected Ready Date: June 15, 2025 │
│ │
│ ─────────────────────────────────────────────────────────────────────── │
│ │
│ Is your cargo ready for pickup? │
│ │
│ ◉ On time — ready by June 15 │
│ ○ Delayed — ready by [___] (enter new date) │
│ ○ Unknown — will update later │
│ │
│ If delayed, please explain (optional): │
│ ┌─────────────────────────────────────────────────────────────────────┐ │
│ │ [Free text, max 200 characters] │ │
│ └─────────────────────────────────────────────────────────────────────┘ │
│ │
│ Upload documents (optional but recommended): │
│ [📎 Packing List] [Choose File] No file chosen │
│ [📎 Commercial Invoice] [Choose File] invoice_v2.pdf (uploaded ✓) │
│ [📎 Certificate of Origin] [Choose File] No file chosen │
│ │
│ ┌─────────────────────────────────────────────────────────────────────┐ │
│ │ [Submit Update] │ │
│ └─────────────────────────────────────────────────────────────────────┘ │
│ │
│ Need help? Contact your logistics team: logistics@customerco.com │
│ │
└───────────────────────────────────────────────────────────────────────────┘
┌───────────────────────────────────────────────────────────────────────────┐
│ GoTrack Dashboard — Shipment SH-2025-00123 [user@customerco.com]│
├───────────────────────────────────────────────────────────────────────────┤
│ │
│ ◀ Back to Shipments Shipment SH-2025-00123 │
│ │
│ Origin: Shanghai, China → Destination: Hamburg, Germany │
│ Booked: May 30, 2025 | Expected Departure: June 15, 2025 │
│ │
│ ─────────────────────────────────────────────────────────────────────── │
│ 📦 SUPPLIER READINESS Updated 2 hours ago │
│ ─────────────────────────────────────────────────────────────────────── │
│ │
│ ⚠ Supplier reports delay: "Raw material shortage" │
│ New ready date: June 17, 2025 (+2 days) │
│ Submitted by: Li Wei (supplier contact) on June 13, 2:32 PM │
│ │
│ Uploaded documents: │
│ • Commercial Invoice (invoice_v2.pdf) — [View] [Download] │
│ • Packing List — not uploaded │
│ • Certificate of Origin — not uploaded │
│ │
│ [ Contact Supplier ] [ Mark as Acknowledged ] │
│ │
│ ─────────────────────────────────────────────────────────────────────── │
│ 🚢 CARRIER UPDATES Last check: 5 min ago │
│ ─────────────────────────────────────────────────────────────────────── │
│ │
│ Container booking confirmed: MAEU1234567890 │
│ Vessel: Maersk Singapore | Voyage: 025E │
│ Gate-in cutoff: June 14, 11:59 PM (not yet met) │
│ │
│ ─────────────────────────────────────────────────────────────────────── │
│ 📊 PREDICTED ETA Confidence: Medium ⚠ │
│ ─────────────────────────────────────────────────────────────────────── │
│ │
│ Adjusted ETA: July 2–4, 2025 (was June 30–July 2) │
│ ⚠ ETA adjusted due to supplier-reported delay (+2 days) │
│ │
└───────────────────────────────────────────────────────────────────────────┘
What this is NOT:
Phase 1 — MVP: 12 weeks
US01 — Logistics manager registers supplier contact for shipment
supplier_contact and expected_ready_date fields populated with 100% consistency — zero tolerance (launch-blocking)expected_ready_date with 100% delivery success (monitored via Twilio webhook) — zero tolerance (launch-blocking)────────────────────────────────────────
US02 — Supplier receives portal link via email and SMS
expected_ready_date is 48 hrs away────────────────────────────────────────
US03 — Supplier opens portal and submits readiness update (on time)
supplier_readiness object is written to shipment with {status: "on_time", submitted_at: [timestamp]} within 3 seconds with 100% consistency — zero tolerance (launch-blocking)────────────────────────────────────────
US04 — Supplier submits readiness update (delayed) with reason and documents
supplier_readiness object is written with {status: "delayed", delay_days: 2, reason: "...", documents: [{type: "commercial_invoice", url: "s3://..."}]} within 5 seconds with 100% consistency — zero tolerance (launch-blocking)────────────────────────────────────────
US05 — Logistics manager sees supplier update in GoTrack dashboard
Decision 1: Portal access model
Choice Made: Zero-login, email/SMS magic-link access for suppliers (no account creation required). Customer's logistics team pre-registers supplier contacts in GoTrack, portal link is auto-sent 48 hrs before expected cargo ready date.
Rationale: Suppliers are not our direct customers and will not adopt a tool that requires account setup, password management, or training. Email/WhatsApp is the existing channel — we meet them there. Rejected: (a) supplier account creation (too much friction, observed 60%+ drop-off in analogous B2B2C onboarding flows at previous companies), (b) API-only integration (suppliers don't have technical capacity to integrate APIs).
Trade-off accepted: Lower data quality initially — one-time link users may enter incomplete data. Mitigated by mandatory field validation and SMS reminder if submission incomplete after 24 hrs.
────────────────────────────────────────
Decision 2: Supplier data trust model
Choice Made: Supplier-reported data is treated as a leading indicator, not truth source. Carrier API data remains the authoritative timestamp for actual handover. GoTrack's AI uses supplier signals to adjust ETA confidence intervals (wider if supplier flags delay, narrower if supplier confirms on-time), but ETA calculation still anchors to carrier API once available.
Rationale: Suppliers have incentive to under-report delays (preserve relationship, avoid penalties). We cannot replace carrier truth with supplier self-reporting. Rejected: (a) treat supplier data as truth (too risky — could degrade ETA accuracy if suppliers lie), (b) ignore supplier data entirely (defeats the purpose — we need early warning, not perfect accuracy).
Trade-off accepted: AI model complexity increases (now handling probabilistic pre-carrier signals + deterministic carrier signals). Requires model retraining on 6 months of supplier+carrier paired data before confidence intervals are reliable.
────────────────────────────────────────
Decision 3: Document upload scope (Phase 1)
Choice Made: Suppliers can upload packing list, commercial invoice, and certificate of origin as JPG/PNG/PDF (max 5MB each). No OCR or structured data extraction in Phase 1 — documents are stored as attachments visible to customer's logistics team in GoTrack dashboard. OCR and auto-population of shipment metadata deferred to Phase 1.2.
Rationale: Document upload is table stakes (customers requested it in 9 of 14 discovery interviews, source: PM notes, Dec 2024), but building OCR pipelines for multi-language, multi-format documents adds 8–10 weeks to Phase 1. We can ship value faster by treating docs as unstructured attachments first. Rejected: (a) no document upload in Phase 1 (customers said this is a "must-have, not nice-to-have" for supplier workflows), (b) build OCR in Phase 1 (timeline slips to 18 weeks, misses Q2 launch window).
Trade-off accepted: Logistics managers still manually review documents instead of auto-populated shipment fields. Acceptable for Phase 1 if it cuts 10 weeks from delivery.
────────────────────────────────────────
Decision 4: Supplier notification timing
Choice Made: Portal link is auto-sent 48 hrs before expected cargo ready date (derived from shipment booking confirmation). Reminder SMS sent at T-24 hrs if no submission yet. Final reminder at T-6 hrs. After carrier cutoff passes, portal link expires (read-only mode — supplier can view submission but not edit).
Rationale: 48 hrs gives supplier time to act if cargo is delayed; earlier notification risks being ignored (supplier may not have info yet), later notification defeats early-warning purpose. Rejected: (a) send link at booking confirmation time (too early — supplier may not have cargo status yet, link gets buried in inbox), (b) send link only once with no reminders (observed 40% no-response rate in analogous workflows without reminders).
Trade-off accepted: SMS reminder adds cost ($0.03/SMS, source: Twilio pricing, US/EU/India blended). At 35 customers × 180 shipments/month × 2 reminders/shipment = 12,600 SMS/month = $378/month = $4,536/year. Acceptable given $2.43M/year recoverable value case.
────────────────────────────────────────
Decision 5: Supplier incentive model (Phase 1)
Choice Made: No direct supplier incentives in Phase 1 (no gamification, no payment, no penalties). Logistics manager is responsible for supplier adoption via relationship/contract leverage. GoComet provides adoption dashboards showing which suppliers are responsive vs. non-responsive, but enforcement is customer's responsibility.
Rationale: We are not in the supplier relationship — the customer is. We cannot pay suppliers, and contract penalties are outside our scope. Rejected: (a) pay suppliers per submission (unsustainable unit economics, opens door to fraud), (b) build supplier performance scoring with penalties (requires legal review of multi-jurisdiction contract enforceability, adds 12+ weeks, out of scope for Phase 1).
Trade-off accepted: Adoption risk is higher — if customer does not have supplier leverage, portal adoption will be low. Mitigated by targeting customers with high supplier concentration (fewer suppliers per customer = easier to drive adoption) in Phase 1 beta cohort.
────────────────────────────────────────
Decision 6: AI model retraining cadence
Choice Made: GoTrack's existing ETA prediction model is retrained weekly (current cadence). Phase 1 ships with supplier readiness as a new input feature, but model architecture remains unchanged (gradient-boosted decision trees, current stack). Model retraining triggers automatically when 500+ new supplier data points are collected (expected ~4 weeks post-launch given beta cohort size). Confidence intervals widen by default for shipments with no supplier data until model learns the correlation.
Rationale: Retraining weekly is already in production — we add supplier readiness as a feature, not rebuild the model. Rejected: (a) retrain model only after 6 months of supplier data (too slow — defeats early-warning value), (b) ship separate "supplier-only" ETA model (doubles maintenance burden, splits data pipeline, engineering vetoed).
Trade-off accepted: ETA accuracy may dip slightly in first 4 weeks post-launch (model is learning) — we communicate this to beta customers as expected behavior and track ETA error rate daily.