Scan Global's OIA Acquisition: How to Protect Customer Service During a Freight-Forwarder Integration

The value of a freight-forwarder acquisition is won or lost shipment by shipment. Customers do not experience a deal through a larger network map. They experience it when a booking is accepted, a customs document reaches the right broker, an exception gets an owner, and an invoice matches the quote.

That makes service continuity the immediate operating priority in Scan Global Logistics' planned acquisition of OIA Global. FreightWaves described the transaction as the largest investment in Scan Global's history. The strategic ambition may be large, but the integration unit that matters is small: one customer, one shipment, one milestone and one accountable team at a time.

Establish the baseline before changing the organization

Integration teams should freeze a pre-close performance baseline before systems, branches or account ownership change. At minimum, measure on-time pickup and delivery, booking response, milestone completeness, customs holds, exception age, claims frequency, invoice accuracy and days to invoice.

Segment those results by customer, mode, lane, branch and service product. A network average can hide a fragile strategic account or a gateway with persistent data gaps. The baseline also needs volume and complexity: shipments per week, countries served, customs entries, special handling, dangerous goods, temperature controls and customer-specific reporting.

Next, inventory every operating promise that lives outside the formal contract. These include preferred carriers, cutoff exceptions, escalation contacts, document naming rules, free-time alerts, invoice references and customer-specific standard operating procedures. During an acquisition, these informal practices are often the first knowledge to disappear and the first source of customer frustration.

Give every critical workflow three named roles: an incumbent owner, a future-state owner and a continuity owner who remains accountable until the handoff passes acceptance tests. An org chart alone is not a handover plan.

Protect shipment data before consolidating platforms

Forwarder integrations typically bring together different TMS platforms, customer portals, carrier connections, customs interfaces and finance systems. Trying to standardize them immediately can create more risk than value. First create a canonical shipment record that both organizations can map to without changing every workflow at once.

That record should preserve:

• customer, shipper, consignee and billing-party identifiers;
• booking, house bill, master bill, container and purchase-order references;
• origin, destination, mode, service and planned milestone dates;
• carrier, routing, equipment and customs-broker assignments;
• document status, customs release, holds and compliance flags;
• quoted charges, accruals, supplier invoices and customer invoices;
• current exception, owner, next action and promised resolution time.

Data mapping deserves executive attention because integration work consumes scarce capacity. A 2026 technology report cited by FreightWaves found that IT leaders spend 36% of their time designing, building and testing custom integrations. The practical response is not to rush migration. It is to prioritize interfaces by shipment and revenue risk, test them against real transaction samples, and reconcile source and target records after every cutover.

Keep immutable cross-reference tables for legacy and new customer, vendor, location and shipment IDs. Without them, teams lose the ability to trace a complaint or invoice back across the two environments.

Run dual controls through the first 90 days

The first 90 days should operate as a controlled transition, not a single go-live. Start with a small cohort of low-complexity accounts or lanes, then promote only after the data, operations and billing controls hold.

For each wave, run parallel checks on booking creation, carrier tender, milestone receipt, customs documentation, exception routing, accruals and invoice output. Sample ordinary shipments and high-risk cases such as rolled ocean bookings, split air consignments, customs exams and accessorial disputes.

Use daily control-room reviews for the first two weeks of each wave. The review should focus on open failures, not presentation slides: shipments without recent events, exceptions without owners, documents approaching cutoff, unbilled completed files and invoices failing validation. Assign one resolution owner and deadline to each item.

Scale also increases the stakes. Reuters reported that DSV's Schenker takeover was valued at €14.3 billion, or about $15.85 billion, illustrating how consolidation can rapidly reshape forwarding networks. Yet network size does not automatically deliver service quality. The operating controls connecting the network do.

Use a customer-facing integration scorecard

A useful 90-day scorecard should include both outcomes and early warnings:

• on-time pickup and delivery by customer and lane;
• percentage of required milestones received on time;
• exceptions acknowledged within the service target;
• average and 95th-percentile exception resolution time;
• customs entries submitted correctly and before cutoff;
• claims and service failures per 1,000 shipments;
• invoices correct on first issue;
• completed shipments not invoiced within the target window;
• customer cases reopened after being marked resolved.

Set thresholds against the pre-close baseline and the contractual target. If a migrated cohort deteriorates, stop the next wave until the cause is corrected. A pause is cheaper than spreading a broken mapping or workflow across the network.

Communicate with customers using the same discipline. Tell them what will change, what will remain stable, who owns escalation and how performance will be measured. Do not promise that integration will be invisible. Promise that every issue will be visible, owned and resolved through a defined process.

Make continuity the proof of integration value

The strongest acquisition program does not treat service preservation as a temporary defensive task. It uses the integration to make ownership, data quality and performance more explicit than they were in either legacy organization.

CXTMS gives freight forwarders a shared operating layer for shipment milestones, documents, costs, exceptions and customer reporting while teams and systems evolve. Request a CXTMS demo to see how shipment-level controls can protect service through a complex integration.