Summary:
This FAQ article describes the integration of Vendor Mandatory Fields with IMPulse orders and XEDI/EDI.
Table of Contents:
VMF & IMPulse Integration
VMF & IMPulse Integration Automation Limitations
VMF & XEDI/EDI Integration
VMF & IMPulse Integration
The VMF Engine stores vendor‑required data for IMPulse orders. It communicates with IMPulse using shipment‑level flags, which IMPulse uses to track, update, and complete orders. The table below shows the most common flags used between the two systems.
VMF & IMPulse Integration Automation Limitations
Jarvis AI only supports specific fields:
Ship-to phone/email
Reseller phone/email
End-user name/phone/email
MSA number
Quote number
Capture codes cannot be auto-populated. They must be entered manually.
Automation relies on comment line formats with specific separators.
for example, FieldName:Value. Incorrect formatting prevents auto-fill.
Orders are accepted even if VMFs are missing. The order status changes to VR hold. No error codes are returned to customers
VMF & XEDI/EDI Integration
The VMF Engine is built into the XEDI/EDI process to support quotes and orders. The VCAF (Vendor Customer Agnostic Framework) pulls data from purchase orders and CRM quotes, then stores that information in the VMF Engine. The table below outlines the automated tasks performed by the VMF Engine.
