This Fleet Manager Was Spending 6 Hours a Month on Substitution Disputes. Tidal Brought That to Zero.

Opening

A UK-based bulk carrier operator managing eight vessels across Atlantic, Pacific, and Indian Ocean routes had a persistent problem that the industry quietly accepted as normal: substitution disputes.

A chandler would receive an order for specific provisions, find several items out of stock, substitute with alternatives, and deliver without informing the vessel's superintendent. The superintendent would discover the substitutions at delivery, sometimes during the port call itself, when there was no time to address them, and be left with provisions that did not match what was requested.

Some substitutions were acceptable: a different brand of the same specification, a closely equivalent alternative. Others were not: wrong specification safety equipment that required replacement to maintain SOLAS compliance, provisions that did not meet dietary requirements for crew members, technical stores of the wrong grade for the vessel's engine specifications. In the worst cases, an undisclosed substitution created a compliance problem that required emergency re-sourcing at a different supplier, an expensive and disruptive outcome that was entirely preventable if the substitution had been disclosed before delivery.

The fleet manager was spending 6+ hours per month on substitution dispute resolution: identifying which orders had discrepancies, communicating with chandlers, arranging remediation, and documenting the outcomes. This was time consumed by a problem that the procurement workflow was creating rather than preventing.

Why It Matters

Substitution disputes are the most common source of post-delivery friction between fleet operators and chandlers. Industry estimates suggest 15-25% of orders involve at least one undisclosed substitution. For safety-critical categories, SOLAS-certified safety equipment, pharmaceutical supplies, engine stores, an undisclosed substitution can create a compliance or operational risk that is significantly more serious than the procurement inconvenience.

The root cause is structural. In an email-based ordering process, a chandler who discovers an out-of-stock item at order preparation time faces a decision: disclose the substitution to the fleet operator (requiring communication, possible rejection, delay), or substitute silently and deliver (faster, but creates a dispute risk). The commercial incentive, complete the order, collect payment, favours silent substitution. The fleet operator discovers the problem at delivery, when options are limited.

The solution is not to trust chandlers more. It is to make explicit substitution disclosure a required step in the order confirmation workflow, where the chandler must disclose every substitution before delivery, and the fleet operator must approve or reject each substitution before the order is confirmed.

The Challenge

The eight-vessel fleet called at 14 regular ports annually, using approximately 22 active chandler relationships. The substitution problem was not concentrated in a few suppliers, it was distributed across the chandler base. Even well-regarded chandlers with strong relationship histories were making undisclosed substitutions, not from dishonesty but from the incentive structure of the current workflow.

The fleet manager had attempted to address the problem through explicit instructions in order confirmations: "Please notify us of all substitutions before delivery." The instructions were acknowledged and frequently ignored, not because chandlers were deliberately non-compliant, but because the instruction existed in an email that was easy to miss during busy quoting periods.

The problem required a structural solution, not an instructional one.

The Solution

Tidal's order workflow makes explicit substitution disclosure a system-enforced step, not an optional instruction. When a chandler prepares a quote in Tidal, any item they are substituting must be explicitly marked as a substitution, with the original item, the substitute specification, and the reason noted. The fleet operator sees all substitutions flagged in the quote comparison interface before confirming the order.

If a substitution is acceptable, the fleet operator approves it during order confirmation. If it is not, wrong specification, wrong grade, compliance issue, the fleet operator rejects it and the chandler is notified to source the correct item or remove it from the order. This happens before delivery, when options are available, not at delivery when options are not.

Items that the chandler cannot supply and cannot substitute are marked as unavailable. The fleet operator sees the unavailability during quote comparison and can either accept the gap or seek that item from another supplier. Silence is not an option; the system requires an explicit status for every line item.

Results

Results measured over six months post-implementation:

The 94% confirmed order accuracy figure is the key outcome. The remaining 6% is accounted for by short deliveries (items that were confirmed but could not be sourced in full quantity at delivery), a distinct problem from undisclosed substitution, and a manageable one that shows up in the delivery record.

The three emergency re-sourcing incidents in the prior 12 months, each costing between £2,000 and £8,000 in emergency procurement costs, are the clearest financial expression of what the dispute resolution time represents in real terms.

Key Takeaways

1. Substitution disputes are structural, not behavioural, they arise from a workflow that permits silent substitution and does not require disclosure before delivery.
2. Instructional approaches ("please notify us of substitutions") do not work reliably in email-based ordering, the instruction is lost in the workflow.
3. System-enforced substitution disclosure (Tidal's workflow requires explicit flagging and approval before delivery) eliminates the dispute source rather than managing its consequences.
4. Confirmed order accuracy improved from 72% to 94%, a meaningful operational improvement that reduces crew provisioning risk.
5. Emergency re-sourcing incidents, the most expensive consequence of undisclosed substitution in safety-critical categories, went from 3 to 0 in six months.

FAQ

Q1. How do chandlers respond to the requirement for explicit substitution disclosure?
Initial adoption required some change management. Chandlers who had previously substituted silently needed to adjust their quote preparation process. Most did so without significant resistance, they understood that disclosed substitutions that are approved are less commercially risky than undisclosed substitutions that generate disputes. The explicit disclosure requirement also protects the chandler: an approved substitution cannot be disputed at delivery.

Q2. What happens if an emergency substitution is needed at delivery?
Delivery substitutions, where the ordered item is genuinely unavailable at delivery time, are handled through a delivery confirmation workflow in Tidal that requires the chandler to document the substitution and the fleet operator to acknowledge it. These are logged separately from pre-delivery substitutions and tracked in the order record.

Tidal makes substitution disputes impossible by design. Request a fleet operator demo. Request Demo →