Commercial reference data

What the engine can evaluate

• Versioned commercial agreements and applicable amendments.
• Lane, carrier, equipment, commodity and named-account scope.
• Agreement-specific booking-count qualification and documented FEU/TEU conversion policies.
• Source-linked rate applicability and unresolved conflicts.

Onboarding boundary

Customer commercial reference onboarding is not yet a self-service public HTTP API. Agreements, allocations and regional data must be coordinated separately with Foryn.

A missing agreement, unresolved precedence or a booking outside purchased lane coverage produces a distinct response. Purchased coverage does not prove that all bookings were submitted.

Do not invent contract identifiers or attach a synthetic agreementReference unless your source system actually holds that relationship.