What Is an EDI 830 (Planning Schedule with Release Capability)?

An EDI 830 is the X12 Planning Schedule with Release Capability, the transaction set that carries forecasting and material release information from one organization to another, following customary and established business practice.

X12 describes three ways to use it, alone or in combination:

• A simple forecast.
• A forecast with authorization: the buyer authorizes the seller to commit to resources, such as labor or material.
• A forecast that releases orders: the forecast also works as an order release mechanism, with resource authorizations, period-to-date cumulative quantities, and specific ship or delivery patterns for requirements set out in buckets, such as weekly, monthly or quarterly.

X12 adds that an order release forecast can also carry all data related to purchase orders, as required, because the order release capability eliminates the need for discrete generation of purchase orders.

X12's supply chain overview lists planning schedule among the additional processes and transaction sets that support the basic supply chain process for trade items, alongside procurement, request for quote, inventory inquiry and product activity.

Three X12 transaction sets can tell a supplier what a customer needs, at different levels of detail:

• 830 Planning Schedule with Release Capability: forecasting and material release information, from a simple forecast up to an order release.
• 862 Shipping Schedule: used by a customer to convey precise shipping schedule requirements to a supplier. X12 says it is intended to supplement the 830: it supersedes certain shipping and delivery information sent in a previous planning schedule, but it does not replace the 830, and it shall not be used to authorize labor, materials or other resources.
• 850 Purchase Order: the placement of purchase orders for goods and services.

X12 links the 862 to Just-In-Time (JIT) manufacturing, because it lets the customer issue precise shipping requirements more often than planning schedules, for example daily shipping schedules versus weekly planning schedules.

A manufacturer sends its supplier an 830 for one part, in weekly buckets for the next four weeks: 400, 400, 500 and 500 units. The full forecast is 400 + 400 + 500 + 500 = 1,800 units.

In this example the first two weeks are released for shipment and the last two are forecast only. The period-to-date cumulative quantity after week two is 400 + 400 = 800 units released, which leaves 1,800 - 800 = 1,000 units the supplier plans for but does not ship yet.

If the supplier sells B2B on Shopify, a released quantity can become an order for the buyer's company through a B2B draft order.

• Draft orders: Shopify describes a draft order as an order that a merchant creates on behalf of a customer, and lists selling products at discount or wholesale rates among its uses. When a merchant accepts payment for a draft order, an order is created.
• Company buyer: the draftOrderCreate mutation can create a B2B draft order with a purchasing entity, for orders where the buyer represents a company rather than an individual customer.
• What it holds: a draft order can carry customer information, line items, shipping and billing addresses, and payment terms, and it has a field for the purchase order number.
• Stock: by default, creating a draft order doesn't reserve or hold inventory for its items, but the reserveInventoryUntil input can reserve it.
• Access: draftOrderCreate requires the write_draft_orders access scope or the write_quick_sale access scope.

Uncap's guide to Shopify EDI integration describes Uncap Connect as connecting Shopify to ERP systems natively, "so orders created in Shopify from any source move downstream into your ERP automatically without a manual step in between."

• EDI 850
• EDI 860
• EDI 855
• Purchase order
• Material requirements planning (MRP)
• Just-in-time inventory

• X12: 830 Planning Schedule with Release Capability
• X12 Transaction Sets
• Shopify Dev Docs: draftOrderCreate