A fluid systems distributor ships precision fittings, regulators, and tubing across Europe. When a chemical plant in Rotterdam calls asking about a missing carton, the customer service rep has to check SAP for the order, the WMS for the pick, DHL for the tracking, customs for the declaration, and a local carrier for the last mile. Five systems, five logins, fifteen minutes. The customer is on hold the entire time.
Federated order visibility. Sandra doesn't search five systems. She asks one question. ZQL fans out to SAP, WMS, carriers, and customs simultaneously. The correlation engine matches events across systems by time, reference number, and physical markers — including a letter-sequence on carton stickers that lets receiving dock workers spot missing boxes without scanning anything.
This is the Darwinian archetype. Each system evolved independently to solve its own problem well. SAP tracks commercial obligations. The WMS tracks physical locations. DHL tracks shipments in its network. Customs tracks declarations. The local last-mile carrier tracks handoffs. Each system works. None of them talk to each other. And every one of them has a different definition of "delivered."
SAP says "delivered" when the dispatch note is created. The WMS says "delivered" when the pallet leaves the dock. DHL says "delivered" when their driver gets a signature. The local carrier says "delivered" when they hand off to a security guard. The customer says "delivered" when goods receipt is posted in their ERP. Same word. Five meanings. And somewhere between those five meanings, a carton of pressure regulators has gone missing.
Sandra has worked customer service for twelve years. When a customer calls, she doesn't follow a script. She follows a pattern: check SAP first for the order status, then the WMS for the physical pick, then the carrier tracking. If the shipment went cross-border, check customs. If DHL handed off to a local carrier, find the handoff reference. She holds all of this in her head. Stefan, who started last month, doesn't know any of it.
ZQL captures Sandra's pattern — not as a procedure manual, but as a federated query. "For this order, here's which system to ask each question." At order capture, the query registers which "cantons" of knowledge are relevant: this carrier, this customs route, this customer's receiving hours. When the question comes — "where is my stuff?" — the federation already knows where to look.
"Delivered" means four different things in four different systems. That's not a data quality problem. That's operational intelligence. Each definition reflects a real moment in the physical journey. Destroy the variance and you lose the ability to pinpoint where in the chain something went wrong.
The hard problem isn't querying systems — it's correlating events across them. SAP uses order numbers. DHL uses tracking numbers. The WMS uses SSCC barcodes. Customs uses declaration references. The customer uses their PO number. Five different identifiers for the same physical shipment.
ZQL's correlation engine matches events by multiple signals: reference number overlaps, time-window proximity, physical markers, and weight tolerances. When a customer calls about PO-FSAB-2026-12445, the engine traces it to SAP order ARB-2026-00412, WMS pick batch PB-20260120-003, DHL tracking 1234567890, customs declaration CH-2026-EX-78923, and local carrier handoff VDB-20260123-0089. The complete picture — from warehouse pick to customer receiving — assembled in seconds from six independent systems.
The Rotterdam customer received three cartons but expected four. The stickers on the cartons read A, B, D. Where's C? No barcode scanner needed. No system lookup needed. The letter sequence — printed at the warehouse as part of ZQL's visual correlation layer — tells the dock worker instantly what's missing. The regulators. Carton C was separated during a carrier handoff at the Dutch border. Van der Berg Transport picked up three cartons from DHL's Rotterdam hub but the fourth was still in the DHL sort facility.
Without federation: the customer calls, Sandra searches five systems for fifteen minutes, makes two phone calls, and emails the carrier. Resolution: next day.
With federation: the system already knows. The correlation engine flagged the partial delivery when DHL's handoff event showed three cartons against a four-carton shipment. Sandra's screen shows the gap before the customer calls. Resolution: thirty seconds.
Fifteen minutes to thirty seconds. Not because the technology is faster — because the question is already answered before anyone asks it. Federation means the gap between "problem visible" and "someone who can act" collapses to zero.
We'll build a federated WISMO view across your systems — live data, read-only, your actual order flow.
We'll walk through a question from your organisation and show you what federation reveals. Thirty minutes. No slides.
Book a Call