How can a single “FOB Shanghai” mismatch derail cooperation on the spot? In non-ocean transport scenarios, casually applying FOB is rarely about convenience; more often, it plants hidden risks. The dispute shared today is a classic case of responsibility misalignment triggered during the inquiry and quotation stage of a rail shipment, where an ocean-shipping FOB term was mechanically applied. Despite the absence of a formal contract and without any actual accounts receivable loss, the misapplication led to a liability dispute.
On the surface, it appeared to be a disagreement over terminology. In reality, the core issue was that the point of origin responsibility was never clearly defined from the outset.
I. Risk Embedded from the Start: Cross-Mode Misapplication of FOB Sets the Stage for Dispute
The spark of this dispute was ignited during the rail transport inquiry and quotation process. The two parties developed fundamentally different interpretations of “FOB Shanghai,” and this divergence fully surfaced after the quotation was confirmed, ultimately causing the cooperation to collapse.
All points of contention converged on one critical question: in a rail transport context, what specific responsibility node does “FOB Shanghai” actually designate?
II. Dispute Breakdown: One FOB, Two Completely Different Interpretations
1. Dispute Over Term Applicability: Industry Practice Extension vs. Scenario Alignment
Creditor Company A asserted:“FOB Shanghai” should be interpreted as meaning that the operating party, Company B, was fully responsible for the entire operational chain from Shanghai onward, including key steps such as empty container pickup and cargo loading.
The core basis for this claim was the commonly observed industry practice of extending FOB usage across multiple transport modes, including ocean, rail, and air freight.
Operating Company B countered:When FOB is applied to rail transport, it should follow the fundamental principle that the shipper is responsible for delivering the cargo to the actual rail departure station.
In this case, B’s practical understanding of FOB was effectively “FOB Xi’an,” meaning that the inland transport costs from Shanghai to Xi’an should be borne by the shipper.
In essence, the core conflict between the two parties was not about pricing, but about the failure to clearly lock in the origin responsibility anchor at an early stage.
2. Dispute Over Quotation Communication: The Ambiguity Trap of “No Hidden Charges”
Core complaint from Entrusting Company A:
During the quotation stage, Operating Company B explicitly committed to “no hidden charges.” However, during execution, B required the shipper to bear the pre-carriage costs corresponding to “FOB Xi’an,” resulting in additional expenses ultimately being passed on to A’s customer. A argued that B used ambiguous wording to mislead the cooperation and secure the order.
Defense from Operating Company B:
B maintained that it had clearly informed the shipper during email communications that pre-carriage trucking prior to rail departure would be the shipper’s responsibility, and had specifically emphasized that FOB in rail transport is not equivalent to FOB in ocean shipping, leaving no room for misrepresentation.
III. Platform Intervention: Thorough Verification to Restore the Full Picture
1. Complaint Initiated: Allegations of Bad Faith and Request for Membership Suspension
Entrusting Company A formally filed a complaint through the JCtrans platform, accusing Operating Company B of dishonest business practices and requesting the suspension of B’s membership.
2. Evidence Review: Key Facts Identified One by One
The platform’s risk control team retrieved and carefully reviewed all email correspondence between the two parties, ultimately confirming three key facts:
- After the quotation was confirmed, the parties immediately developed a significant disagreement over the allocation of origin responsibility between Shanghai and Xi’an, and failed to reach consensus;
- No formal transport contract was signed by either party prior to the dispute;
- The booking for this shipment was successfully canceled, with no actual freight payment made and no accounts receivable or bad debt incurred.
3.Loss Claims: Insufficient Evidence to Substantiate
Entrusting Company A: Provided an invoice showing USD 300 in additional costs incurred due to switching freight forwarders, and further claimed indirect losses such as damage to client relationships and potential profit loss.
Operating Company B: Claimed that booking cancellation resulted in corresponding operational costs, but failed to provide valid evidence proving that such costs were actually incurred or that they should be borne by Company A.
IV. Platform Conclusion: The Core Logic of Risk Control Discretion
After comprehensive assessment, the platform concluded that directly applying FOB terms originally designed for ocean shipping to a rail transport scenario was the fundamental trigger of this dispute. During the inquiry and quotation stage, the parties failed to reach a unified understanding of key responsibility points, and the entrusting party was unable to provide evidence of direct accounts receivable loss in accordance with platform rules.
On this basis, the platform did not support imposing penalties such as membership suspension on Operating Company B.
V. Risk Alerts and Practical Avoidance Guidelines
1. Do Not Use FOB as a Substitute for Operational Scope Description—Details Must Be Clearly Documented
In non-ocean scenarios such as rail, air, and multimodal transport, FOB must never be treated as an operational scope description. Prior to cooperation, four core elements must be explicitly documented in writing:
The specific location for empty container pickup; the specific location for cargo loading; the exact name of the actual departure station; and the inclusions and exclusions of charges, with no omissions or ambiguity.
2. Use the Right Incoterms—Do Not Let “Industry Practice” Become a Risk Loophole
Different responsibility scenarios require precise Incoterms, not vague reliance on industry practice:
If the seller is responsible for delivering the cargo to a designated carrier in Shanghai—apply FCA Shanghai (Named Place);
If the seller is responsible for transporting the cargo to Xi’an Station and bearing the full cost—apply CPT Xi’an Station / CIP Xi’an Station, and clearly state in the contract: “The seller bears all costs incurred prior to delivery of the cargo to Xi’an Station.”
3. The Inquiry and Quotation Stage Is Not a Liability-Free Zone—Ambiguity Equals a Risk Trigger
Every commitment made during the inquiry and quotation stage must be precise. Statements such as “no hidden charges,” “all-inclusive,” or “full process arrangement” must be accompanied by clearly defined responsibility anchors and cost boundaries. Otherwise, from a platform risk control perspective, all ambiguous statements will be deemed invalid commitments and cannot serve as a basis for rights protection.
Conclusion:
The real risk in this case lay not in pricing, but in whether responsibilities were clearly articulated. The platform’s decision-making logic remains consistent: it does not endorse ambiguous statements, does not infer obligations based on customary practice, and does not support accountability claims against members in the absence of actual accounts receivable loss.
For freight forwarders, the true risk does not lie in the mode of transport, but in whether the origin node, operational responsibilities, and cost boundaries are clearly defined and documented in advance. The inquiry and quotation stage is not a liability-free zone, but a risk-definition zone; an unclear commitment is often more dangerous than the price itself.
