Flexport Request-Volume and Freshness Tuning

Overview

Optimize volume and latency against business freshness, not a fabricated per-request bill. Prefer event-driven invalidation plus bounded reconciliation and measured page/expansion choices.

Prerequisites

• Baseline request counts by operation and outcome
• Business-approved freshness and recovery windows
• Metrics for pages read, expansions, cache hits, and reconciliation lag

Instructions

Step 1: Name the outcome

Tie each request to shipment tracking, trade document ingestion, invoice reconciliation, or booking—not generic synchronization.

Step 2: Set freshness classes