Operations teams
“A supplier operations team can see partner setup, validation, exceptions, and QuickBooks handoff in one workspace instead of chasing spreadsheets.”
X12 segment reference
PID — Product Item Description
X12 PID segment: free-form and structured product descriptions on PO, ASN, and invoice lines — when partners require human-readable item text.
PID segment facts
- PID is often mandatory when onboarding new SKUs — item master churn makes description loops a recurring compliance task.
- Structured PID (type S) carries attribute pairs some apparel and CPG programs use for size/color validation.
- SignalEDI mapping templates include PID defaults so operators can override description text before send.
What the PID segment does
PID adds descriptive text or structured product attributes to line items. Some retailers require PID for private-label SKUs; others treat it as optional when GTIN is present.
Loop: Under PO1, IT1, or SN1 loops
Key elements
| Element | Name | Description |
|---|---|---|
| PID01 | Item description type | F=free-form, S=structured — partner guides specify. |
| PID05 | Description | Product title or attribute text shown on receiving documents. |
Example PID segment
PID*F****Widget Blue 12oz~
Parse and validate samples with the free EDI validator or send JSON via the JSON→X12 mapping guide.
Common PID errors
- Missing PID when partner mandates description for new SKUs
- Description charset violations
- PID length exceeds partner max
Related reference
FAQ
Frequently asked questions
Depends on partner — many big-box programs require PID for new items without a stable GTIN.
Trust & proof
Built for SMB teams that need API-first EDI, healthcare diligence, and predictable pricing.
SignalEDI keeps the public promise consistent across every route: real-time processing, transparent monthly plans, no per-document fees, QuickBooks-friendly handoffs, and core healthcare X12 workflows on paid plans.
HIPAA-aware handlingBAA path documentedSecure API + webhooksNo per-document fees
Healthcare billing
“837, 835, and 270/271 workflows are explained in plain English, with HIPAA-aware handling and a documented BAA review path for diligence.”
Developer teams
“JSON/CSV in and X12 out, with API docs, webhooks, real-time status, and validation responses that make EDI feel like modern infrastructure.”