Inbound JSON Into OTM – Limitations, Error Handling & Reprocessing

Summary:

Hi All,

We are evaluating the use of JSON payloads for all inbound integrations into OTM (specifically Order Release, Shipment Actuals, and EDI214). While XML has extensive documentation and clear processing behavior, we are trying to understand the functional and technical limitations when switching to JSON for inbound messages.

With XML integrations today, we rely heavily on:

1. Transmission Manager visibility – We can search using the related Object ID and easily see what data was sent to OTM.
2. Error identification & diagnostics – XML errors are logged with clear transmission records and can be retrieved / reviewed.
3. Reprocessing Capability – Failed XML records can be reprocessed from the UI or through integration retry mechanisms.