FK-PayD Analysis — Non-Linehaul Contracts

East and South regions have completely separate rate cards based on conversion percentage slabs (e.g., East: <=88%, >88-90%, >90% with rates 12-17.5 INR). This performance-linked pricing model for specific regions is absent.

Comprehensive city/region mappings for Tier-I through Tier-IV and SDZ are essential for rate application. Without these definitions (e.g., Tier-I includes Bangalore, Mumbai, Delhi; SDZ includes Leh, Ladakh, Northeast states), rates cannot be correctly applied to shipments.

ANE-SDZ East region has performance-based rates (>75%, >84%, >=90% thresholds) with 'Proposed Final Rate' differing from base rates by up to 3.5 INR. Schema has no mechanism to capture conditional/performance-linked pricing.

Contract contains rates for ODH, MDH, OSH, ANE-SDZ, Biker (grocery), Van, Shopsy, and MDH Pickup - each with distinct rate structures, but the schema assumes only GTNL service type exists

MDH pickup operations have a 2-dimensional rate matrix (4 distance bands: 0-50km to 150+km × 5 volume bands: 0-1500 to >3750) with rates from 1.05 to 12 INR. The schema doesn't support distance-based pricing or pickup vs delivery differentiation.

Separate RVP (Return to Vendor Partner) last mile costs are defined by tier (9-16 INR). Since this hub is in SDZ tier (16 INR RVP cost), reverse logistics pricing is missing from the schema.

ODH-Shopsy is a distinct LOB with modified pricing: 'ODH RC less Rs. 3' for forward, plus conditional Rs. 1 addon if conversion >70%. This LOB-specific pricing logic and conversion-based incentives are completely missing.

LMA LOB has dedicated biker model with standard rates (21-24 INR) and 100% biker model with split payment structure (grocery payment + incentive = 31-36 INR total). Completely different pricing model ignored by schema.

4 distinct SLA parameters with specific targets, thresholds, and 5% billing penalties affect actual payment amounts and vendor performance accountability, not captured in rate-only schema

The MG construct is explicitly valid only for '1st August 2025 to 15th September 2025 (45 Days)', but the schema has no date range fields to capture time-bound contract terms.

5 hubs have special negotiated rates (ranging from Rs 1.25 to Rs 33) that override standard tier rates - these exceptions are contractually binding but completely invisible to a hub-agnostic GTNL schema

Hub special rates are valid only '16th June 2025 to 31st Dec 2025' - the schema has effective_from but no effective_to, making time-bound rate changes untrackable

Separate reverse LM costs by tier (Tier-I: 15, Tier-II: 14, etc.) - return shipment pricing completely missing

ANE-SDZ has separate East region rate card with different volume breakpoints and rates (26-29.5 INR final) vs standard SDZ (25-31 INR). Schema assumes uniform rates per tier.

Schema shows final computed rates (e.g., 32.0) but doesn't capture that these are base tier rates + incremental hub rates, making it impossible to recalculate or audit pricing

Comprehensive city/region mappings for Tier-I through Tier-IV and SDZ are essential for rate application. Without these definitions (e.g., Tier-I includes Bangalore, Mumbai, Delhi; SDZ includes Leh, Ladakh, Northeast states), rates cannot be correctly applied to shipments.

East and South regions have completely separate rate cards based on conversion percentage slabs (e.g., East: <=88%, >88-90%, >90% with rates 12-17.5 INR). This performance-linked pricing model for specific regions is absent.

Three distinct service types with completely different rate structures: HIH Last Mile, CPU Last Mile, and Grocery Synergy. Schema collapses all into generic 'hub_name' losing service type distinction.

All rates are distance-dependent (0-20km, 20-50km, 50-100km, 100-200km for HIH; 0-50km, 51-100km, 101+ for CPU; 1-20km, 21-50km, 51-100km, 101-200km for Grocery). Schema captures only single rate per hub without distance dimension, making rate application impossible.

Extensive penalty structure (RTO penalties at 1-4% of invoice, slot breach penalties, reattempt penalties, fake shipment charges) directly impacts net rates but is completely missing

Biker rate card shows base + incentive structure (e.g., Tier-A: base 23 + incentive 11 = total 34) but schema only captures base rate, missing 32-52% of total compensation

The primary cost component (₹42,500 for City List I, ₹41,000 for ROI) representing the base monthly fee per vehicle is completely absent from the rate schema which only captures adhoc per-order rates

LMA LOB has dedicated biker model with standard rates (21-24 INR) and 100% biker model with split payment structure (grocery payment + incentive = 31-36 INR total). Completely different pricing model ignored by schema.

ODH-Shopsy is a distinct LOB with modified pricing: 'ODH RC less Rs. 3' for forward, plus conditional Rs. 1 addon if conversion >70%. This LOB-specific pricing logic and conversion-based incentives are completely missing.

Contract lists 100+ specific cities/localities (Dwarka, Saket, Guwahati, etc.) mapped to tiers; schema's generic 'All Zones' loses granular location-to-rate mapping needed for operations

Contract states 'RVP Rates same' as forward rates but reverse logistics has distinct SLA metrics (RVP breach 0.5-5%, reverse fake 0.5%, UD bad 15%) affecting net revenue; schema doesn't distinguish forward/reverse pricing.

Separate last-mile costs (9-16 INR) defined by tier for LMA LOB. Schema misses this distinct cost component that may not be part of hub delivery rate.

Contract explicitly defines different rates for 'Bulky/Heavy (REF/Wash/AC/Cooler/Large Furniture)' vs 'All other items' vs 'Grocery'. Schema has no product/category differentiation, causing complete rate misapplication.

Hub-specific Dexter rates (14.5-15.5 INR) for 10 named hubs show actual hub-level pricing that contradicts schema's assumption of non-hub-specific LMA rates

Named Kirana hubs have specific effective_date (2025-06-16) and end_date (2025-12-31), indicating time-bound pricing. Schema captured only 2 specific hubs but missed temporal validity crucial for rate application periods.

East and South regions have completely separate rate cards based on conversion percentage slabs (e.g., East: <=88%, >88-90%, >90% with rates 12-17.5 INR). This performance-linked pricing model for specific regions is absent.

Comprehensive city/region mappings for Tier-I through Tier-IV and SDZ are essential for rate application. Without these definitions (e.g., Tier-I includes Bangalore, Mumbai, Delhi; SDZ includes Leh, Ladakh, Northeast states), rates cannot be correctly applied to shipments.

ANE-SDZ East region has performance-based rates (>75%, >84%, >=90% thresholds) with 'Proposed Final Rate' differing from base rates by up to 3.5 INR. Schema has no mechanism to capture conditional/performance-linked pricing.

Separate RVP (Return to Vendor Partner) last mile costs are defined by tier (9-16 INR). Since this hub is in SDZ tier (16 INR RVP cost), reverse logistics pricing is missing from the schema.

Contract contains rates for ODH, MDH, OSH, ANE-SDZ, Biker (grocery), Van, Shopsy, and MDH Pickup - each with distinct rate structures, but the schema assumes only GTNL service type exists

ODH-Shopsy is a distinct LOB with modified pricing: 'ODH RC less Rs. 3' for forward, plus conditional Rs. 1 addon if conversion >70%. This LOB-specific pricing logic and conversion-based incentives are completely missing.

MDH pickup operations have a 2-dimensional rate matrix (4 distance bands: 0-50km to 150+km × 5 volume bands: 0-1500 to >3750) with rates from 1.05 to 12 INR. The schema doesn't support distance-based pricing or pickup vs delivery differentiation.

LMA LOB has dedicated biker model with standard rates (21-24 INR) and 100% biker model with split payment structure (grocery payment + incentive = 31-36 INR total). Completely different pricing model ignored by schema.

The MG construct is explicitly valid only for '1st August 2025 to 15th September 2025 (45 Days)', but the schema has no date range fields to capture time-bound contract terms.

Hub special rates are valid only '16th June 2025 to 31st Dec 2025' - the schema has effective_from but no effective_to, making time-bound rate changes untrackable

5 hubs have special negotiated rates (ranging from Rs 1.25 to Rs 33) that override standard tier rates - these exceptions are contractually binding but completely invisible to a hub-agnostic GTNL schema

5% billing penalties for SLA breaches (conversion <78%, P1D <80%, CPD >1%, load-drop <70% over 15-day averages) directly impact payment calculations but are completely absent from rate card schema.

Separate reverse LM costs by tier (Tier-I: 15, Tier-II: 14, etc.) - return shipment pricing completely missing

SLA metrics (>88% conversion, >90% first-day pickup, <0.25% CPD breach, load-to-OFD timing) directly impact penalties, performance bonuses, and vendor management. These are likely tied to payment terms but completely missing from rate structure.

ANE-SDZ has separate East region rate card with different volume breakpoints and rates (26-29.5 INR final) vs standard SDZ (25-31 INR). Schema assumes uniform rates per tier.

East and South regions have completely separate rate cards based on conversion percentage slabs (e.g., East: <=88%, >88-90%, >90% with rates 12-17.5 INR). This performance-linked pricing model for specific regions is absent.

Comprehensive city/region mappings for Tier-I through Tier-IV and SDZ are essential for rate application. Without these definitions (e.g., Tier-I includes Bangalore, Mumbai, Delhi; SDZ includes Leh, Ladakh, Northeast states), rates cannot be correctly applied to shipments.

ANE-SDZ East region has performance-based rates (>75%, >84%, >=90% thresholds) with 'Proposed Final Rate' differing from base rates by up to 3.5 INR. Schema has no mechanism to capture conditional/performance-linked pricing.

ODH-Shopsy is a distinct LOB with modified pricing: 'ODH RC less Rs. 3' for forward, plus conditional Rs. 1 addon if conversion >70%. This LOB-specific pricing logic and conversion-based incentives are completely missing.

Separate RVP (Return to Vendor Partner) last mile costs are defined by tier (9-16 INR). Since this hub is in SDZ tier (16 INR RVP cost), reverse logistics pricing is missing from the schema.

MDH pickup operations have a 2-dimensional rate matrix (4 distance bands: 0-50km to 150+km × 5 volume bands: 0-1500 to >3750) with rates from 1.05 to 12 INR. The schema doesn't support distance-based pricing or pickup vs delivery differentiation.

LMA LOB has dedicated biker model with standard rates (21-24 INR) and 100% biker model with split payment structure (grocery payment + incentive = 31-36 INR total). Completely different pricing model ignored by schema.

The MG construct is explicitly valid only for '1st August 2025 to 15th September 2025 (45 Days)', but the schema has no date range fields to capture time-bound contract terms.

Shopsy explicitly differentiates forward vs reverse logistics pricing ('forward: ODH RC less Rs. 3', 'reverse: Original RC') - schema assumes uniform rate regardless of shipment direction

Special hub rates are explicitly time-bound (2026-01-01 to 2026-03-31), but schema lacks date validity fields, so system cannot auto-switch rates or handle overlapping pricing periods

Contract defines rates at individual hub level (e.g., FortHub_MUM, AndheriHub_MUM) not just city/state level - schema forces single Hyderabad rate when contract has 50+ distinct hub rates across zones

Multi-day COD pendency penalties with fixed + variable components (day1/day2/day3) totaling thousands per slab are not captured - direct revenue impact

Eligibility conditions (Availability >=67%, Avg WM Delivered/RVP >=15 shipments/day, Max 26 days capped) determine payout qualification - completely missing from schema

Shopsy has distinct pricing ('ODH RC less Rs. 3' for forward, '+Rs. 1 if conversion >70%', 'Original RC' for reverse) - schema assumes single rate card applies to all LOBs

ODH is a primary LOB with complex 9-slab volume-based pricing across 5 geographic tiers (Tier-I through Tier-IV and SDZ) with rates ranging from 16.75 to 35.0 INR. This represents the core delivery pricing model with 45 different rate combinations based on 15-day cumulative volumes - completely absent from schema.

Shopsy explicitly differentiates forward vs reverse logistics pricing ('forward: ODH RC less Rs. 3', 'reverse: Original RC') - schema assumes uniform rate regardless of shipment direction

MDH pickup has a 2D matrix (4 distance bands × 5 volume bands) with rates from ₹1.05 to ₹12 - this distance-based pickup pricing is entirely missing from the delivery-focused schema

Contract contains 24 detailed SLA metrics (dh_breach_forward_ncd: 0.25%, rvp_breach_cd: 5%, csat_score: >80%, etc.) that likely trigger financial penalties/incentives, but schema captures none of this performance-based pricing dimension

Regional rate cards (East/South/North/West) with conversion-based tiers (₹13-18.5) appear to be separate from the main tier-based structure and include sub-regional breakdowns (Delhi NCR, Punjab/UP, Rajasthan Major, etc.) - schema doesn't capture these regional variations

The schema captured only the baseline rate (1-3750 volume) but missed that rates decrease across 8 different volume slabs (up to >33000), meaning actual costs vary 20-40% based on shipment volumes - this is fundamental to pricing calculation

Contract has granular per-hub pricing for 50+ named hubs across Maharashtra (Mumbai: 16.91-19.0, Pune: 16.91-18.0), Delhi NCR (Gurgaon: 18.25-19.25, Noida: 17.25-18.25), Gujarat, MP, Rajasthan with base/mid/high tiers - schema only captures volume slabs, missing geographic rate variations

Kirana LOB has dedicated biker grocery rates (₹21-24) with a '100% biker model' that pays ₹23 for first shipment + ₹10-11 incentive for 2nd shipment (total ₹31-34) - this multi-shipment incentive model is completely absent

Shopsy LOB has distinct pricing ('ODH RC less Rs. 3' for forward, 'Rs. 1 if conversion >70%', 'Original RC' for reverse) that is completely missing - this is a separate LOB with its own commercial terms

Biker model includes incentive for 2nd shipment (10-12 INR) separate from base grocery payment, creating total payout structure. Schema captures only single rate value, missing multi-component compensation model.

Separate LM costs (₹9-16) by tier are specified, suggesting a cost component structure rather than a single rate - schema doesn't distinguish between different cost components

Named Kirana hubs have specific effective_date (2025-06-16) and end_date (2025-12-31), indicating time-bound pricing. Schema captured only 2 specific hubs but missed temporal validity crucial for rate application periods.

Contract defines 4 delivery frequency tiers (daily: 5.3-22.4, alternate_2: 5.0-14.5, once_in_3: 4.9-11.9, once_in_4: 4.8-10.6) with 9 rate bands each - completely absent from schema which assumes single rate per volume/zone

Most zones use shipment volume tiers (<=35, <=50, >50 shipments) as primary rate determinant, but schema only captured conversion-based slabs for Hyderabad; this volume-based pricing is fundamentally different pricing logic

Multiple zones (Goa SDZ, Delhi NCR, East Zone, South Zone, North Zone) use conversion percentage bands (<85%, 85-88%, 88-90%, >90%) with different rate structures than Hyderabad's model - schema missed 5+ different conversion-based pricing patterns

Rates vary by 1.5-2 rupees based on conversion performance tiers (e.g., <85%, 85-90%, >90%). Schema captures only base rates, missing the performance-linked pricing mechanism that directly impacts billing.

Rates vary dramatically by 15-day cumulative volume (31 INR at 1-3750 vs 21 INR at >33000 for Tier-I). Schema captures only the lowest slab rate, missing 8 other rate tiers that directly impact pricing by up to 32%.

ANE-SDZ East region has performance-based rates (>75%, >84%, >=90% thresholds) with 'Proposed Final Rate' differing from base rates by up to 3.5 INR. Schema has no mechanism to capture conditional/performance-linked pricing.

MDH Pickup uses two-way distance (0-50km, 50-100km, 100-150km, 150+km) crossed with volume slabs. Rates range from 1.05 to 12 INR based on distance. Schema has no distance dimension.

8 distinct penalty types with specific triggers (15-day averages, state-wise targets) and calculations (2% billing, 1% billing or Rs 10k lower) - schema mentioned penalties exist but missed the trigger logic and calculation methodology

Detailed city-to-tier mappings exist (e.g., Tier-I has 54+ cities listed, Tier-III covers 'Rest of' regions). Schema infers tier from hub name but doesn't capture the comprehensive geography definitions needed for new hub classification.

Minimum guarantee of 30-35 shipments/day with eligibility criteria (>=67% availability, >=15 shipments delivered) and Rs.15/shipment payout - complex conditional guarantees missing

Contract covers ODH, MDH, Grocery Biker, Van, Shopsy, and Reverse logistics - schema assumes single service type per vendor

Completely separate rate structure for grocery delivery with biker payments (21-24 INR), 2nd shipment incentives (10-12 INR), and total payouts (31-36 INR). Different tier definitions (Tier_A/B/C vs Tier-I/II/III). Schema has no grocery LOB representation.

Shopsy has formula-based rates (ODH RC minus Rs. 3, plus Rs. 1 if conversion >70%) with separate reverse pickup rates. Schema has no product/channel differentiation.

Contract specifies separate 'lm_cost_by_tier' (9-16 INR) which may be additive or informational for cost calculation. Schema doesn't distinguish rate components.

Contract specifies rates for 100+ individual hubs (e.g., FortHub_MUM, AndheriHub_MUM, BanerHub_Pune) with hub-specific pricing, but schema only captured state/zone level for one location

Separate reverse LM costs by tier (Tier-I: 15, Tier-II: 14, etc.) - return shipment pricing completely missing

Shopsy has distinct pricing logic ('ODH RC less Rs. 3' plus conversion-based addon, separate reverse logistics). Biker grocery model has completely different rate structure (23-24 INR base + incentives). Schema treats all ODH products identically.

13 hubs have incremental rates (e.g., ElasticRunDahisarODH_MUM +10.0, ElasticRunKamotheODH_KAM +9.0) added to base tier rates, not fixed rates. Schema treats these as absolute rates, causing incorrect pricing.

Volume slabs use '15 days cumulative volume' for rate determination. This temporal aggregation rule is essential for correct billing but completely absent from schema.

Contract defines CPD breach, escalation, and conversion targets that may trigger penalties or rate adjustments

Distance-based line haul rates (5-22.4 INR) with frequency tiers exist alongside per-shipment rates, representing a completely different pricing model missed by schema

Raw data shows LMA operates across 4 zones (North/South/East/West) with 30+ location-specific rate tiers ranging from 12-18.5 INR, but schema only captures 2 flat rates ignoring geographic pricing

The 87% conversion threshold is the primary determinant of which LMA rate (19 vs 20 INR) applies, making it essential for accurate rate application and invoice validation

Contract lists 100+ specific cities/localities (Dwarka, Saket, Guwahati, etc.) mapped to tiers; schema's generic 'All Zones' loses granular location-to-rate mapping needed for operations

Contract covers LMA, ODH, and Myntra-Dexter LOBs with different rate structures; schema doesn't capture which rates apply to which LOB

Separate rate card exists for grocery LOB (21-24 INR) distinct from LMA rates, indicating multiple service types that schema doesn't differentiate

Contract specifies separate rates for undelivered/RTO scenarios (value 0 for certain conversions), not captured in schema

Hub-specific Dexter rates (14.5-15.5 INR) for 10 named hubs show actual hub-level pricing that contradicts schema's assumption of non-hub-specific LMA rates

Kolkata and Tamil Nadu ROTN models use base_rate + conversion_incentive structure (e.g., 14.5 base + 1 INR for >88%, +2 INR for >90%) - different pricing logic than flat rate slabs

Contract specifies 'Per Shipment Delivered/Picked' as the pricing unit; without this, the rate value (19/20) cannot be correctly applied or invoiced

Most zones use shipment volume tiers (<=35, <=50, >50 shipments) as primary rate determinant, but schema only captured conversion-based slabs for Hyderabad; this volume-based pricing is fundamentally different pricing logic

Multiple zones (Goa SDZ, Delhi NCR, East Zone, South Zone, North Zone) use conversion percentage bands (<85%, 85-88%, 88-90%, >90%) with different rate structures than Hyderabad's model - schema missed 5+ different conversion-based pricing patterns

Rates vary by 1.5-2 rupees based on conversion performance tiers (e.g., <85%, 85-90%, >90%). Schema captures only base rates, missing the performance-linked pricing mechanism that directly impacts billing.

Volumetric threshold at 40 shipments determining CB vs normal rate application. This binary condition fundamentally changes which rate card applies but is not captured.

All rates are distance-dependent (0-20km, 20-50km, 50-100km, 100-200km for HIH; 0-50km, 51-100km, 101+ for CPU; 1-20km, 21-50km, 51-100km, 101-200km for Grocery). Schema captures only single rate per hub without distance dimension, making rate application impossible.

Rates vary significantly by tier (Metro/Tier 1/Tier 2) with 15-30% differences. Schema attempts to capture via hub_name construction but loses the tier as a queryable dimension.

Three distinct service types with completely different rate structures: HIH Last Mile, CPU Last Mile, and Grocery Synergy. Schema collapses all into generic 'hub_name' losing service type distinction.

Extensive penalty structure (RTO penalties at 1-4% of invoice, slot breach penalties, reattempt penalties, fake shipment charges) directly impacts net rates but is completely missing

Contract explicitly defines different rates for 'Bulky/Heavy (REF/Wash/AC/Cooler/Large Furniture)' vs 'All other items' vs 'Grocery'. Schema has no product/category differentiation, causing complete rate misapplication.

Biker rate card shows base + incentive structure (e.g., Tier-A: base 23 + incentive 11 = total 34) but schema only captures base rate, missing 32-52% of total compensation

Hub-level rate overrides with specific effective dates (2025-06-16 to 2025-12-31) and commentary ('ODH/MDH RC 2025+1.25', 'Special RC'). Individual hub economics (KelhariMDH at Rs 33 vs others at Rs 1.25) critical for accurate billing but schema has no hub-specific rate capability.

RFK/XRM rate card shows rates vary by volume slabs (0-1300 vs >3901 can differ by 6+ rupees) but schema assumes fixed rate per hub regardless of volume

Contract states 'RVP Rates same' as forward rates but reverse logistics has distinct SLA metrics (RVP breach 0.5-5%, reverse fake 0.5%, UD bad 15%) affecting net revenue; schema doesn't distinguish forward/reverse pricing.

CPU rates are explicitly 'North Zone' specific while HIH rates apply pan-India. Schema conflates zone (directional) with tier (city classification), missing geographical applicability.

Extensive SLA framework with 20+ metrics (DH breach 0.25%, conversion 90%, fake attempt 0.50%, CSAT 97%, etc.) that likely trigger penalties/incentives. Schema has no provision for performance-based rate adjustments.

Bulky vs Non-bulky has drastically different rates (e.g., Metro 1-20km: ₹220 bulky vs ₹90 non-bulky), but schema doesn't distinguish product categories

All rate structures are distance-based (0-20km, 20-50km, 50-100km, 100-200km) with different prices per slab, but schema's single 'rate' field cannot represent this multi-dimensional pricing model

Contract has complex variable and fixed flex premium rates with conditional billing formulas based on minimum guarantee volumes (actual >= MG vs actual < MG), which determines final invoice amount but is completely missing

Flex premium billing formula explicitly depends on comparing actual vs MG volumes to decide between two different rate calculation methods, but MG values are not captured anywhere

Contract covers 7 LOBs (ODH, ODH-GTNL, ODH-Shopsy, LMA, LMA-GTNL, Kirana, Myntra-Dexter) but schema analyzes only 'kirana_rate' - unclear if rates apply uniformly or vary by LOB, risking incorrect rate application.

The contract contains comprehensive rate structures for 6 major zones (West, Delhi NCR, East, South, North, North-East) with 50+ location-specific rates, but schema captured only 1 hub (Hyderabad). This represents ~98% data loss of geographic pricing variation.

Rates vary significantly by conversion performance bands (e.g., <85%, 85-90%, >90% or <88%, 88-90%, >90%) across all zones. Schema treats conversion as single target rather than as a rate-determining variable affecting per-shipment pricing by 10-30%.

Complete penalty framework missing: 2% billing penalties for fake attempts >2%, operational CPD breach >2%, conversion <82%/80%, FAC <83%, and unified CPD breach penalties. These directly reduce vendor payments.

Both LMA and Powerflex use explicit distance ranges (25-50km, 51-75km, etc.) to calculate line haul components, but schema has no distance dimension

7 distinct penalty triggers (fake attempt, conversion, FAC, CPD breach, escalation index, SRTO) with specific thresholds and financial impacts (1-2% of billing) directly affect net revenue but are relegated to 'extra_fields' rather than core rate structure.

The schema captures only single rates but misses that Kirana (and all LOBs) have performance-based tiering where rates vary by FAC% (First Attempt Conversion) - e.g., East Zone Tier A has 3 different rates: 16 (<88%), 17 (88-90%), 17.5 (>90%). This directly impacts billing calculations.

Kirana has dramatically different rates based on shipment volume thresholds: 35 INR for low volume (1-50 shipments Delhi NCR) vs 15.75 INR for high volume (>50 shipments). The schema only captured the high-volume rate, missing 122% price differential.

Contract defines CB (Cash Back) threshold at <=40 shipments with different 'cb_rate' vs 'normal_rate' for >41 shipments. This affects which rate structure applies but schema doesn't capture this conditional logic.

Schema shows only Kirana rates but misses that LMA has separate conversion-based rates (19/20 INR), Grocery/GTNL have tier-based rates (21-24 INR), Dexter has hub-specific rates (15.5 INR), and ODH has regional rates - all different pricing models.

Multiple LOBs use conversion % as primary rate determinant (ODH: <=35%/<=50%/>50%, LMA: >80%/>75%/<=75%, Kirana Hyderabad: <50%/50-80%/>80%, Myntra-Dexter: <90%/>=90%) but schema only captures final rate, not the conversion logic that triggers it

LMA rates are explicitly 'LH + 19/18/16' where LH varies by distance (5.3 to 22.4 based on km ranges), making actual rate a calculated field—schema captures neither the formula nor distance-based LH rates

Kirana has completely different rates for low_density vs high_density (Metro: 12 vs 9, Tier1: 10 vs 7) and self_pickup (2) options—schema has no field to distinguish these service types within same geography

Special hub categories exist (e.g., Mumbai hubs at Rs 16.91-19, Gurgaon milestone hubs at Rs 18.25-19.25, Goa SDZ at Rs 18-21) with 15-25% premiums over standard rates, completely absent from single-hub schema.

8 specific incremental hubs (HanumangarhHub, KukasHub, etc.) have Rs 1 per shipment rate structure, distinctly different from conversion-based pricing, representing alternative pricing model.

8 distinct penalty types with specific triggers (15-day averages, state-wise targets) and calculations (2% billing, 1% billing or Rs 10k lower) - schema mentioned penalties exist but missed the trigger logic and calculation methodology

Contract contains extensive rate cards for West Zone (Maharashtra Mumbai/Pune/Tier-C, Goa SDZ, Gujarat), Delhi NCR (Gurgaon Premium, Noida, Delhi Standard), East Zone (Tier A/B/C, Kolkata), South Zone (Kerala SDZ, Coimbatore SDZ, Bangalore/Chennai, ROI South, Tamil Nadu ROTN), North Zone (Punjab/UP/UK, Rajasthan Tier 1/2, Haryana), and North East (Tier A/B/C) - schema only captured 1 Hyderabad hub from Kirana model, missing 100+ hubs across 6 zones

Contract specifies rates for 100+ individual hubs (e.g., FortHub_MUM, AndheriHub_MUM, BanerHub_Pune) with hub-specific pricing, but schema only captured state/zone level for one location

Kolkata and Tamil Nadu ROTN models use base_rate + conversion_incentive structure (e.g., 14.5 base + 1 INR for >88%, +2 INR for >90%) - different pricing logic than flat rate slabs

Most zones use shipment volume tiers (<=35, <=50, >50 shipments) as primary rate determinant, but schema only captured conversion-based slabs for Hyderabad; this volume-based pricing is fundamentally different pricing logic

Multiple zones (Goa SDZ, Delhi NCR, East Zone, South Zone, North Zone) use conversion percentage bands (<85%, 85-88%, 88-90%, >90%) with different rate structures than Hyderabad's model - schema missed 5+ different conversion-based pricing patterns

The schema captures only single rates but misses that Kirana (and all LOBs) have performance-based tiering where rates vary by FAC% (First Attempt Conversion) - e.g., East Zone Tier A has 3 different rates: 16 (<88%), 17 (88-90%), 17.5 (>90%). This directly impacts billing calculations.

Kirana has dramatically different rates based on shipment volume thresholds: 35 INR for low volume (1-50 shipments Delhi NCR) vs 15.75 INR for high volume (>50 shipments). The schema only captured the high-volume rate, missing 122% price differential.

Contract defines CB (Cash Back) threshold at <=40 shipments with different 'cb_rate' vs 'normal_rate' for >41 shipments. This affects which rate structure applies but schema doesn't capture this conditional logic.

Schema shows only Kirana rates but misses that LMA has separate conversion-based rates (19/20 INR), Grocery/GTNL have tier-based rates (21-24 INR), Dexter has hub-specific rates (15.5 INR), and ODH has regional rates - all different pricing models.

Contract defines 8 SLA metrics (CPD breach <=0.03%, P1D first day pickup >90%, child/women safety ZERO tolerance) that directly impact penalties but schema only captured 3 conversion-related metrics

Each tier explicitly lists covered locations (e.g., East Tier-A: 'Patna, Bhubaneswar, Sikkim, Darjeeling, Siliguri') - critical for operational execution but completely absent from schema

Some regions combine multiple factors (e.g., Goa SDZ uses both conversion % AND regional classification, Delhi NCR uses hub premium + conversion bands) - schema assumes single rate determinant

Contract covers 6 LOBs (ODH, ODH-GTNL, LMA, Kirana, Myntra-Dexter, EBRC) but schema only extracted Kirana model; unclear if other LOBs use same rate structures or have separate cards

Unified CPD breach, escalation index, and SRTO penalties specify 'lower of 1% billing OR Rs 10,000' - this cap logic affects actual penalty amounts but wasn't captured

Special hub rates are explicitly time-bound (2026-01-01 to 2026-03-31), but schema lacks date validity fields, so system cannot auto-switch rates or handle overlapping pricing periods

ANE-SDZ card includes conversion-based incentives (75%/84%/90% thresholds) and shows current_rate vs base_rate vs final_rate, but schema captures none of this performance-based pricing

The hub-specific rates reference 'ODH/MDH RC 2025+X' addon logic, but schema doesn't capture which tier (I-IV/SDZ) each hub belongs to from annexure_b, making actual rate calculation impossible

Rate card specifies '15 days cumulative' for volume slabs, but schema has no field to capture this critical temporal aggregation rule that determines which rate applies

Some hubs use 'base_rate + addon' (RC 2025+4), others use 'Special RC' flat rates (27.0, 35.0), but schema treats all as flat per_shipment_rate, losing the calculation methodology

Contract distinguishes ODH vs MDH hub types (e.g., GangohMDH_SHP, MiyanGanjMDH_UNN), but schema doesn't capture this, potentially applying wrong rate logic

Tier definitions include exhaustive city/region mappings (Tier-I: 'Vijayawada, Vishakhapatnam...'), but schema has no way to link hub locations to these tiers for correct base rate selection

Hub names suggest parent hub relationships (_KOL, _HYD, _CHN suffixes) but schema only has 'distance_from_parent_hub' without capturing which hub is the parent

Comments reference 'ODH/MDH RC 2025' as base version, but schema has no versioning field to track which base rate card applies or handle future rate card updates

Base rate card has 9 distinct volume slabs with specific thresholds (1-3750, 3751-6000, etc.) that determine rates, but schema has no volume threshold fields

Volume slabs (<35%, 35-50%, >50%) determine rates for Maharashtra Tier B/C and Gujarat/MP, but schema doesn't capture volume as a pricing dimension - it creates pseudo-hubs with volume ranges in names.

Entire penalty framework with 8 metrics (fake attempts, CPD breach, conversion targets, FAC, SRTO, etc.) with triggers and 1-2% billing penalties is completely absent. This directly impacts vendor payments.

CBM (Rs 18-19.5), Grocery (Rs 21-24), Kirana (Rs 5-12 with density/conversion modifiers), Linehaul (Rs 5.3-22.4 by distance) are separate LOB pricing models entirely missed.

Linehaul rates based on two-way distance (7 slabs from <25km to >300km) represent distance-based pricing completely absent from hub-centric schema.

What defines SDZ1 vs Tier_A vs Tier_B/C is unclear. Schema captures tier labels but not the business rules for tier assignment.

The schema treats conversion-based rates as separate hub entries instead of conditional rate structures. Conversion % (85%, 88%, 90%) directly determines rate tiers, but schema creates duplicate 'hubs' for each conversion level rather than capturing this as a pricing rule.

Kolkata uses base_rate + conversion bonuses; ROTN uses base + increments; Kirana varies by density+tier+conversion. Schema flattens these into static rates, losing the calculation logic.

Rates depend on 2-3 variables simultaneously (zone + tier + conversion, or zone + volume + conversion). Schema's single hub_name+rate structure can't natively represent this.

LMA has +2 for South hubs, +1 for North hubs; Kirana has +1/+2 for conversion; Northeast has +1/+2/+3 incentive slabs. Schema doesn't capture these additive pricing rules.

Kerala Special (flat Rs 17), Gurgaon Premium, Delhi Premium, CBM Prime - these special categories have different pricing logic but schema treats them as regular hubs.

'Rest of Bihar', 'ROI South', 'Rest of Bengal' are catch-all categories that apply to unlisted locations. Schema can't represent this default/fallback logic.