Validating vendor XML before it breaks your integrations

If your business depends on XML from partners — orders, claims, listings, product feeds — you have felt this: an integration that worked for months suddenly fails, and the root cause is a payload that changed shape without anyone telling you.

The spec said one thing; the wire said another. Validating against reality, not the documentation, is what keeps integrations alive.

Contract drift, in practice

• A required element is renamed or moved under a new parent.
• A namespace prefix changes, breaking every hard-coded XPath.
• An attribute your parser depends on is dropped for some records.
• Cardinality shifts: a field that was always singular starts repeating.

Validate the shape, then watch it

Start by capturing the real structure of known-good payloads: their namespace-aware node paths, attributes, and sample values. That becomes your baseline.

Then, every time a new payload arrives, compare it against the baseline. Added and removed paths surface new or missing fields; changed occurrence counts reveal cardinality shifts. This catches drift the moment it appears rather than at the next failed import.

Keep the evidence searchable

The teams that handle integrations well keep a searchable vault of redacted sample payloads and the quirks each partner exhibits. When something breaks at 2am, the on-call engineer can search for the path in question and see exactly what changed and when.