The EDI 830 Planning Schedule is how manufacturers tell their suppliers what to build and when, across weeks or months, against a single blanket purchase order. Instead of cutting a fresh 850 for every shipment, the buyer sends a rolling 830 that carries both firm release quantities and forward-looking forecast. Reading it correctly is the difference between shipping on time and either sitting on dead inventory or missing a line-down deadline. For how the 830 splits planning from firm ship instructions, see EDI 830 vs 862.
This guide covers what the 830 contains, how to tell forecast from firm, the segments you will work with, a real example you can open in our renderer, and how a supplier handles inbound 830s even without an ERP integration.
What Is an EDI 830?
An EDI 830 is the Planning Schedule with Release Capability transaction defined by the ASC X12 standards body, used by a buyer to send a supplier forecasted and firm demand for materials over a defined horizon. It is most common in manufacturing supply chains, where an OEM issues a blanket PO and then drives shipments through successive planning schedules rather than individual orders.
Authoritative references for 830 implementation:
- The X12.org Transaction Sets reference defines the BFR, LIN, FST, and SHP segment structure used across 830 implementations
- The EDI Academy 830 and 862 reference explains how the 830 carries forecasting and material-release information, and how the 862 Shipping Schedule supplements it for near-term ship instructions
Who sends it? The buyer (an OEM, assembler, or other manufacturer) sends the 830 to its supplier or contract manufacturer.
When is it sent? On a regular cadence, often weekly or daily. Each new 830 supersedes the prior schedule for the same item and ship-to.
Why does it matter? The 830 is the demand signal that drives production planning and raw-material purchasing on the supplier side. Misreading a forecast bucket as a firm release (or the reverse) leads directly to over-build, stockouts, or premium freight.
Forecast vs Firm: the Distinction That Matters
A single 830 usually carries two kinds of quantity in its forecast (FST) segments, and the whole point of the document is to separate them:
- Firm / committed releases are authorized for shipment. The supplier should produce and ship these to the dated requirements. In X12 these typically carry a forecast qualifier such as
C(firm). - Planning / forecast quantities are a heads-up so the supplier can buy materials and reserve capacity. They are not yet authorized to ship and can change in the next schedule. These typically carry a qualifier such as
D(planning).
Some 830s also carry cumulative (period-to-date) quantities so both sides can reconcile what has shipped against what was authorized. When an 830 is used as an order-release mechanism against a blanket PO, those releases replace discrete 850s entirely.
Key Segments Explained
Here are the segments you will work with in an 830 transaction set:
| Segment | Name | Purpose |
|---|---|---|
| ST | Transaction Set Header | Identifies the start of the 830 and assigns a control number |
| BFR | Beginning Segment for Planning Schedule | Schedule type, purpose, the buyer reference (often the blanket PO), and the horizon start and end dates |
| N1 | Name | Identifies the buyer location (MI), supplier (SU), and ship-to parties |
| LIN | Item Identification | The part being scheduled, by buyer part number and supplier part number |
| UIT | Unit Detail | Unit of measure and, where present, price |
| PER | Administrative Contact | The buyer-side planner or MRP controller responsible for the schedule |
| SDP | Ship/Delivery Pattern | The pattern that ties forecast quantities to dates |
| FST | Forecast Schedule | The dated quantity buckets, each flagged firm or planning |
| SHP | Shipped/Received | Cumulative shipped and received quantities for reconciliation |
| CTT | Transaction Totals | Number of line items in the schedule |
BFR Segment Reference
BFR is the beginning segment of every 830. It sets the purpose of the schedule, whether dates mean delivery or shipment, whether quantities are discrete or cumulative, and the window the schedule covers.
BFR*00*REL-2026-W25*BLANKET-PO-44021*DL*A*20260615*20270615*20260615
| Element | Ref | Name | Req | Value in the example | Meaning |
|---|---|---|---|---|---|
| BFR01 | 353 | Transaction Set Purpose Code | M | 00 | Original schedule |
| BFR02 | 127 | Reference Identification | C | REL-2026-W25 | The buyer's forecast or release identifier |
| BFR03 | 328 | Release Number | C | BLANKET-PO-44021 | Release against a previously placed purchase order |
| BFR04 | 675 | Schedule Type Qualifier | M | DL | Dates are delivery based |
| BFR05 | 676 | Schedule Quantity Qualifier | M | A | Quantities are actual discrete amounts |
| BFR06 | 373 | Forecast Horizon Start Date | M | 20260615 | First date the schedule covers |
| BFR07 | 373 | Forecast Horizon End Date | O | 20270615 | Last date the schedule covers |
| BFR08 | 373 | Date Forecast Generated | O | 20260615 | When the buyer's MRP run produced this schedule |
BFR02 and BFR03 are governed by syntax rule R0203: at least one of the two must be present. BFR09 through BFR12 are optional trailing elements and most automotive implementation guides stop at BFR08. Check your partner's guide before populating them.
BFR01 Transaction Set Purpose Codes
This is the element behind a schedule that arrives and unexpectedly wipes out the previous one.
| Code | Meaning | Effect on the prior schedule |
|---|---|---|
00 | Original | First schedule for this horizon |
01 | Cancellation | Cancels the referenced schedule |
04 | Change | Modifies only the buckets included in this transmission |
05 | Replace | Supersedes the entire prior schedule for the horizon |
22 | Information Copy | Informational only, not authorization to build or ship |
BFR*05 is the one to watch. Replace means the schedule you just received is now the whole truth for that horizon. Any bucket that existed in the previous 830 and is absent from this one is gone, not unchanged. Treating an 05 as if it were an 04 is the single most common cause of a supplier building to stale demand.
BFR04 and BFR05 Qualifiers
| Element | Code | Meaning |
|---|---|---|
| BFR04 | DL | Delivery based dates |
| BFR04 | SH | Shipment based dates |
| BFR05 | A | Actual discrete quantities |
| BFR05 | C | Cumulative quantities |
BFR04 decides whether a date in an FST bucket is the day the goods must be on the buyer's dock or the day they must leave yours. Getting this backwards costs you the transit time, which on an overseas lane is the whole schedule.
FST Segment and Forecast Qualifier Codes
FST carries the dated quantity buckets. It is the segment that actually says what to build and when.
FST*2000*C*W*20260622
| Element | Ref | Name | Value in the example | Meaning |
|---|---|---|---|---|
| FST01 | 380 | Quantity | 2000 | 2,000 units in this bucket |
| FST02 | 680 | Forecast Qualifier | C | Firm, authorized to ship |
| FST03 | 681 | Forecast Timing Qualifier | W | Weekly bucket |
| FST04 | 373 | Date | 20260622 | The bucket date |
FST02 Forecast Qualifier Codes
This is the firm versus planning flag, and it is the most important code in the whole document.
| Code | Meaning | Are you authorized to ship? |
|---|---|---|
A | Immediate | Yes, ship now |
B | Blanket | No, a blanket quantity for the agreement rather than a dated release |
C | Firm | Yes, this is a committed release |
D | Planning | No, plan materials and capacity only |
The practical rule: build to C, buy long-lead material for D, and never ship against D. If you ship a D bucket you are shipping unauthorized inventory and the buyer is under no obligation to take it.
FST03 Forecast Timing Qualifier Codes
FST03 tells you what span the date in FST04 represents. A quantity of 2,000 against a weekly bucket is a very different instruction from 2,000 on a discrete day.
| Code | Meaning |
|---|---|
C | Weekly bucket, Monday start |
D | Discrete, a single date |
F | Flexible interval |
M | Monthly bucket |
Q | Quarterly bucket |
T | Daily bucket |
W | Weekly bucket |
Y | Annual bucket |
Z | Mutually defined |
Partners extend this list. Where your partner's guide and this table disagree, their guide wins.
A Real EDI 830 Example
The example below is an OEM planning schedule for a molded part against a blanket PO. The first three weekly buckets are firm releases (code C); the later buckets are planning forecast (code D). Open it in the renderer to see the parsed structure and plain-English view.
OEM 830 Planning Schedule with Release
OEM-to-supplier planning schedule for a molded part: firm weekly releases (forecast code C) followed by planning-only forecast buckets (code D), with cumulative quantities
Raw EDI (X12)
Human-Readable
Interchange
Functional Group
Transaction 830
Planning ScheduleSegment Detail
Where the 830 Sits in the Order Lifecycle
In a blanket-PO manufacturing relationship, the 830 often replaces the per-order 850:
- Blanket 850 Purchase Order - Buyer establishes the agreement, pricing, and item list
- 830 Planning Schedule - Buyer sends rolling forecast and firm releases against that blanket
- 862 Shipping Schedule (optional) - Buyer sends tighter near-term ship instructions
- 856 Ship Notice / ASN - Supplier notifies the buyer of each shipment
- 810 Invoice - Supplier requests payment
A late or misread 830 ripples through every step that follows, which is why production planners watch it closely.
EDI 830 vs 862: What Is the Difference?
Both carry dated quantities against the same blanket PO. The 830 plans, the 862 ships.
| EDI 830 Planning Schedule | EDI 862 Shipping Schedule | |
|---|---|---|
| Purpose | Rolling demand plan | Near-term ship authorization |
| Horizon | Weeks to months, often 12 to 52 weeks | Days to a few weeks |
| Beginning segment | BFR | BSS |
| Carries forecast? | Yes, firm and planning buckets together | No, firm ship instructions only |
| Authorizes shipment? | Only the buckets flagged firm (FST02 of C) | Yes, that is the entire purpose of the document |
| Typical cadence | Weekly | Daily, sometimes more than once a day |
| Replaces a 850? | Often, as releases against a blanket PO | No, it refines an existing 830 |
| EDIFACT equivalent | DELFOR | DELJIT |
A supplier receiving both should treat the 862 as the authority for what leaves the dock this week, and the 830 as the authority for what to buy and staff for next quarter. When the two disagree inside the near-term window, the 862 wins.
Not every buyer sends both. Many run the 830 alone and rely on the firm buckets for release authority. For a deeper walk through the split, see EDI 830 vs 862 and the EDI 862 Shipping Schedule guide.
Is DELFOR the Same as an 830?
Close, but they are different standards. DELFOR is the UN/EDIFACT Delivery Forecast message and it fills the same role in the EDIFACT world that the 830 fills in X12. If a European OEM asks for DELFOR and your system speaks X12, you need a translation, not a remap of the same file.
| X12 | EDIFACT | Role |
|---|---|---|
| 830 | DELFOR | Rolling forecast and planning |
| 862 | DELJIT | Near-term firm ship instruction |
| 856 | DESADV | Ship notice |
| 850 | ORDERS | Discrete purchase order |
| 810 | INVOIC | Invoice |
DELFOR and DELJIT are not the same message as each other either, and the distinction mirrors the 830 versus 862 split above: DELFOR plans, DELJIT authorizes. A supplier that receives DELFOR only is usually expected to ship against the firm portion of the forecast, exactly as with an 830.
How 830 Releases Drive MRP
The 830 is normally machine output, not a human document. Understanding where it comes from explains most of its odd behavior.
- The buyer's MRP run explodes finished-goods demand through the bill of materials down to your part.
- Netting subtracts on-hand inventory and open receipts, leaving net requirements by date.
- The planning time fence splits the horizon. Inside the fence, requirements become firm and go out with FST02 of
C. Outside it, they stay planning and go out asD. - The result is written to an 830 and transmitted, usually on a fixed weekly cycle.
Two consequences follow directly, and both surprise suppliers the first time:
Quantities move week to week even when nothing was ordered. A forecast bucket is a calculation, not a commitment. If the buyer's own demand or inventory position shifted, your planning buckets shift with it. This is normal and not a signal that the buyer changed their mind.
The firm window is the only thing you can plan production against. Anything outside the planning time fence can and will change. Suppliers who build to D buckets to smooth their own capacity carry that risk themselves.
Cumulative quantities in the SHP segment exist to keep both sides honest across all this movement. For how CUM accounting reconciles what was authorized against what shipped, see cumulative quantity and CUM accounting.
How Suppliers Handle Inbound 830s Without an ERP
Many of the suppliers receiving 830s are contract manufacturers, job shops, and molders that do not run a system with an affordable EDI-capable API. The common (and expensive) advice is to integrate the planning schedule directly into an ERP, but that is not the only path.
OrderSync reads inbound 830s (and arbitrary-format demand like PDF, Excel, and email release schedules) and turns them into a clean, reviewable list of dated release requirements. It separates firm from forecast, collapses weekly grids into dated lines, flags anomalies, and produces valid X12 that drops into the EDI desktop client or folder your trading partner already polls. No ERP read or write is required to get started. When you are ready, the same pipeline can validate releases against your item and ship-to master.
See EDI without ERP integration for the full approach, or try the free EDI inspector to upload one of your own 830s and see it parsed.
Frequently Asked Questions
What is the difference between EDI 830 and EDI 850?
An 850 is a discrete purchase order for a specific set of line items. An 830 is a rolling planning schedule against a blanket agreement that carries both firm releases and forward forecast. In many manufacturing relationships the 830 replaces repeated 850s.
What is the difference between EDI 830 and EDI 862?
The 830 carries the longer-range plan, including forecast that authorizes material and capacity. The 862 Shipping Schedule is a tighter, near-term instruction for what to ship and when. The 862 supplements the 830; it does not replace it or authorize resources on its own.
How do I tell forecast from firm in an 830?
Look at the FST forecast qualifier on each dated bucket. Firm, ship-authorized quantities and planning-only forecast quantities use different codes (commonly C for firm and D for planning). Treating planning forecast as firm is the most common and costly 830 mistake.
What does BFR05 mean in an 830?
BFR05 is the Schedule Quantity Qualifier and it has two values. A means actual discrete quantities, so each FST bucket is its own standalone amount. C means cumulative quantities, so each bucket is a running total from the start of the agreement rather than an increment. Reading a cumulative schedule as discrete inflates demand enormously, because a bucket showing 40,000 means 40,000 to date, not 40,000 more. Check BFR05 before you interpret a single FST quantity.
What does BFR with a purpose code of 05 mean?
BFR*05 is a Replace. The schedule supersedes the entire prior schedule for that horizon. Any bucket present in the previous 830 and missing from this one has been removed, not left unchanged. Compare it against purpose code 04 (Change), which only modifies the buckets it actually contains. Treating a Replace as a Change leaves suppliers building to demand the buyer already deleted.
Which EDI transaction set includes both firm and forecast?
The 830 Planning Schedule. It is the only common X12 demand document that carries both in one transmission, separated by the FST02 forecast qualifier: C for firm and ship-authorized, D for planning only. The 862 Shipping Schedule carries firm ship instructions with no forecast, and an 850 carries a discrete order with no forward plan at all.
Is DELFOR the same as an 830?
They serve the same purpose in different standards. DELFOR is the UN/EDIFACT Delivery Forecast message and the 830 is its X12 counterpart. Neither is a drop-in substitute for the other; moving between them requires translation. The same pairing holds for the near-term documents, where X12 862 corresponds to EDIFACT DELJIT.
Can a supplier process an 830 without an ERP?
Yes. The 830 can be parsed, reviewed, and acted on as a schedule of dated requirements without writing into an ERP. OrderSync ingests 830s and other formats, surfaces the releases for review, and outputs valid X12 to your existing EDI client.