EDIFACT PROINQ — Product Inquiry
PROINQ asks for availability, specification, or catalog data for candidate items before formal ORDERS.
✦ What It Does
Response may be PRODAT, PRICAT, or partner-specific message pairs per MIG.
Used in indirect procurement and new product introduction gates.
Often lower volume than transactional messages but critical path for launches.
⚡ When It's Used
- RFP phase before awarding supplier.
- Engineering asks for alternate material data.
- Retail item setup inquiry before assortment listing.
- After recall verifying replacement SKU attributes.
- Cross-reference buyer SKU to supplier article.
Who Uses EDIFACT PROINQ
European retail & brands
Common in EDIFACT-first programs where product inquiry flows between HQ, DCs, and suppliers across the EU and APAC.
Global manufacturers
Automotive, industrial, and CPG companies standardize on EDIFACT for plants and suppliers outside North America.
3PLs & carriers
Logistics service providers consume or produce the message when the contract mandates UN/EDIFACT syntax and directories.
Key Segments & Constructs
EDIFACT uses a hierarchical structure: UNH (message header) opens the transaction; BGM (beginning of message) carries the document name and reference; party data uses NAD; lines often use LIN with QTY, PRI, and MOA. Exact segment requirements depend on the message directory (D.96A, etc.) and your trading partner's implementation guide.
BGM
Inquiry type and reference.
LIN / IMD
Items or families being queried.
QTY
Requested trial quantity when applicable.
DTM
Response due date expectations.
Related Messages
Need Help with EDIFACT PROINQ?
Better EDI maps, tests, and operates EDIFACT alongside X12—same platform, translation when partners use different standards.
Talk to an EDI Expert