Author: Helen Thomas

Accelerated Analytics is very pleased to be sponsoring the Beauty Design Awards. The Beauty Design Awards celebrates the best of design in the Beauty Industry. 2023 is the fourth year of running the award. The award is founded and lead by beauty industry market research specialist Jennifer Carlsson.  Accelerated Analytics’ customers Bubble and Youthforia were finalists for the 2022 award.

To learn more, visit www.beautydesignawards.com.  Product submissions may be made up to August 31, 2023 so hurry to get your brand in the running for the 2023 Beauty Design Awards.  Voting on finalists will be open starting in October as well so be sure to bookmark the site and submit your votes.

The EDI 870 Order Status Report transaction set is commonly used by vendors to report on the current status of a customer’s order. Each status report transaction refers to a customer’s single order but it can involve multiple previously-sent purchase orders. The 870 is replacing what is known as a Paper Status Report, which provides details on where an order is in production. EDI 870 can include but is not limited to:

• Vendor Details
• Order Status Details
• Explanation Of Status
• Reference Identifying The Specific Order
• Details Of Order: Price, Quantity, Item, Etc.

The EDI 870 transaction can be implemented to report complete orders, focusing on line items within an order or selected products/services in that purchase order. It may also be used to update the supplier’s shipment schedule or delivery dates. The 870 could be sent as a result of an Order Status Inquiry (EDI 869 transaction) that’s received from a trading partner. In addition to that, 870 transactions could potentially be used to prearranged schedules but only when inventory is allocated to such an order.

EDI 870 Specifications

This X12 Transaction Set contains the format and establishes the data contents of the Order Status Report Transaction Set (870) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to report on the current status of;

• Purchase Orders
• Purchase Orders For Specific Customers (All or Select)
• Line Items Of The Purchase Order
• Select Products/Services On Purchase Order
• Requirement Forecast

The EDI 870 transaction set can also be used to report on the current status of single or multiple requisitions. The report format allows for the inclusion of “reasons” relative to the status. This transaction set can also be used to provide updates on a supplier’s scheduled shipment or specific delivery dates. This transaction set can result from either an inquiry or a prearranged schedule agreed to by the trading partners.

The EDI 830 Planning Schedule transaction set is really used as an electronic sales forecast. In fact, it can be used in 3 different ways:

• Just as a sales forecast
• As a forecast and an authorization for the recipient to commit to resources
• As a forecast that also includes order release levels

The senders of 830 Planning Schedules are typically manufacturers communicating with their suppliers. The 2 trading partners would represent the buyer (the manufacturer) and the seller (the supplier). The Planning Schedule allows the seller to plan resources, such as labor and material, and to fulfill orders via automation based on a customer’s inventory levels. 830 transactions that do include a Material Release are likely to include specific authorizations, which could be period-to-date cumulative quantities, and shipping or delivery patterns (weekly, monthly or quarterly) requirements. By doing so, it can eliminate the need for a customer to generate separate purchase orders.

This info in a single 830 transaction can relate to all production items sourced from a given supplier site. While the 830 transaction may include shipping information, the main focus is on forecasts. You can use the 862 Shipping Schedule transaction to provide detailed shipping instructions as needed.

EDI 830 Format

ISA*01*0000000000*01*0000000000*ZZ*ABCDEFGHIJKLMNO*ZZ*123456789012345*101127*1719*U*00400*000003438*0*P*>
GS*PS*1234567890 *999999999 *20120126*1211*1*T*004010
ST*830*0001
BFR*00**001*DL*A*19990607*19991029*19990611
N1*SU*STURGIS MOLDED PRODUCTS*92*C84A
N2*STURGIS MOLDED PRODUCTS *70343 CLARK STREET
N3*PO OX 246 *STURGIS, MI 49091
LIN**PC*AA017830-1441*PD*TERMINAL (AN PC )*PO*C01000*RN*001
UIT*EA
PO4*1*96*X4
REF*DK*A22
PER*EX*JOHN DOE*TE*4239827000*****12345
FST*1728*C*D*19990614
FST*1440*C*D*19990615
FST*1440*C*D*19990616
FST*1440*C*D*19990617
FST*1440*C*D*19990618
FST*7392*D*W*19990621
FST*7392*D*W*19990628
LIN**PC*AA017380-2030*PO*C50000*RN*001
UIT*PC
PO4*1*108*X4
REF*DK*A22
PER*EX*JOHN DOE*TE*4239827000*****12345
FST*108*C*D*19990614
FST*108*C*D*19990615
FST*108*C*D*19990616
FST*216*C*D*19990617
FST*108*C*D*19990618
FST*756*D*W*19990621
FST*756*D*W*19990628
CTT*2
SE*31*0001
GE*1*1
IEA*1*000000018

EDI Specifications

• Just as a sales forecast
• As a forecast and an authorization for the recipient to commit to resources
• As a forecast that also includes order release levels

• Certification Data
• Inspection Data
• Process Control Measurement Stats

What Is EDI 863 Report Of Test Results?

The EDI 862 Shipping Schedule transaction set is responsible for accounting shipping requirements. These shipping instructions would replace those forecasted in a previous Planning Schedule 830 transaction, though the 862 does not actually replace the 830.

862 transactions are important for supporting Just-in-Time (JIT) manufacturing because they provide detailed shipping requirements more frequently versus EDI 830 Planning Schedule. In the Just-in-Time environment, an 862 can be triggered based on product usage. For example, when a quantity of an item in inventory is below a set restock level, EDI 862 can be used to send a notification to the supplier to replenish that item right away.

Now, the 830 Planning Schedule document works in conjunction with the 862 transaction to support Just-in-Time manufacturing. The forecast data from a 830 can help the supplier manage resources and materials. By doing so, it ensures the on-hand inventory is rightly available when the supplier receives an 862 from its customer with instructions to ship that item. Instructions to ship an item can always change, especially in a real-time. When it does, the 862 transaction can be used, it can provide the changes needed to the previous 862 instructions.

Those changes could include but are not limited to;

• An Increase For Order Quantity
• A Decrease For Order Quantity
• Changing The Shipping Date

Due to this, manufacturers may end up sending numerous 862 requirements, it could be for the same item, it could be on the same day.

EDI 862 Specification

This X12 Transaction Set contains the format and establishes the data contents of the Shipping Schedule Transaction Set (862) for use within the context of an Electronic Data Interchange (EDI) environment.

The transaction set can be used by a customer to relay the exact shipping schedule requirements to a supplier.  The shipping schedule transaction set will contain specific shipping and delivery information transmitted from a previous planning schedule transaction, but it wouldn’t replace the 830 transaction set.

The shipping schedule transaction set would not be used to authorize labor, resources, materials, etc. Also, this transaction set follows best practice of the Just-In-Time (JIT) manufacturing model by giving the customer the ability to issue specific shipping schedule requirements on a more frequent basis, like daily shipping schedules versus weekly planning schedules.

It’s important to note that the shipping schedule transaction can also give the customer location the opportunity to issue shipping requirements independent of other customer locations when planning schedule transactions are issued by a consolidated scheduling organization.

The EDI 867 transaction set represents the Product Transfer and Resale Report. EDI 867 is used to give information on a product that has been relocated to a new location within a company. It can also be used to report sales of a product from multiple locations to an end customer, such as point-of-sale, or POS data. This specific EDI transaction code can also be used to communicate returns from customers to retail locations or distribution centers.

Each 867 document includes the following information:

• Resale Information Or Product Transferred, can include contract details, quantity, purchase order, code types, etc.
• Transaction Totals (Line Items), can include weights, dimensions, other unit measurements.
• Organization Identification Details.

The 867 transaction set can be used in a wide range of different industries. While the retail industry is likely the most common to use it, it can also be used by manufactures, resellers, distributors and wholesalers.

We can give you a quick examples.

Utilities may use an EDI 867 to communicate meter readings, which may include metrics on how much electricity is being used. Wholesalers may use 867 to communicate to a manufacturer about product movements at their wholesale locations.

In many ways, 867 is similar to the EDI 852 transaction set, which is used by the top resellers in the world to provide detailed insights on product inventory and sales levels to the manufacturers of those products.

EDI 867 Format

ISA*01*0000000000*01*0000000000*ZZ*ABCDEFGHIJKLMNO*ZZ*123456789012345*101127*1719*U*00400*000003438*0*P*>
GS*PT*4405197800*999999999*20110127*1719*1421*X*005010VICS
ST*867*0001
BPT*22*ABC123*20120128*01
CUR*SE*USD
DTM*193*20120130
N1*SE*XYZ SUPPLIER*9*1234567890001
N1*DS*ABC DISTRIBUTION*9*9876543210001
PTD*IB***TF*TRANSFER 123
N1*TT*ABC DISTRIBUTION BRANCH 2*9*9876543210002
QTY*78*100*EA
LIN*0001*VC*P-8750*BP*12345
UIT*EA*5*PE
AMT*1*500
DTM*514*20120130
CTT*1*100
SE*16*0001
GE*1*1421
IEA*1*000006638

EDI 867 Specifications

This X12 Transaction Set contains the format and establishes the data contents of the Product Transfer and Resale Report Transaction Set (867) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to:

1. Report Sales Of A Product From One Or More Locations To End Customer
2. Report Sales Of A Product From One Or More Locations And Demand Beyond Sales To End Customer
3. Report Details About Product Being Transferred From One Area To Another

The EDI 861 transaction set is an electronic version of a Receiving Advice/Acceptance Certificate. This EDI transaction can be used to report shipment receipts or it can be used as a formal acceptance for defective items that are being returned. In the case third-party receiving, such as a drop-shipment, the sender may transmit an 861 to report to the purchaser that the shipment was received. Unlike the simple receipt acknowledgement, EDI 861 includes notifications for the disposition of the shipment as it’s received, which can include:

• When a portion or full shipment is received
• When a portion or full shipment is not received
• When a discrepancy in the content receive vs. ordered
• When an item received is damaged

The 861 transaction set is usually used in the retail industry, often used with automatic stock-replenishment programs that are managed by vendors. The use of RFID and encoded ID tags give the ability to track individual cartons. This can include;

• The specific location – As it moves through the distribution center
• Individual store location or number
• Status update – This could be on the sales floor, open box, layaway, reserve stock, etc.

When this type of information can be sent to the supplier via an 861, it allows retailers to provide their vendors with targeted visibility at various points in the supply chain. By doing so, it allows vendors to better manage production schedules, lead times and inventory levels. The 861 can also be useful for initiating proof of delivery and shipment tracking processes, and for carrier performance evaluations.

EDI 861 Format

ISA*01*0000000000*01*0000000000*ZZ*ABCDEFGHIJKLMNO*ZZ*123456789012345*101127*1719*U*00400*000003438*0*P*>
GS*RC*4405197800*999999999*20101127*1719*1421*X*004010VICS
ST*861*1002
BRA*1625791400*20010816*06*8
DTM*003*20010816
PRF*123
N1*ST**21*00KESTJ00
RCD**5*CA
LIN**IN*22970DCXXX493*VC*DB12
RCD**5*CA
LIN**IN*22970DCXXXY493*VC*DB13
CTT*2
SE*12*1002
GE*1*1421
IEA*1*000008638

EDI 861 Specifications

This X12 Transaction Set contains the format and establishes the data contents of the Receiving Advice/Acceptance Certificate Transaction Set (861) for use within the context of an Electronic Data Interchange (EDI) environment. EDI 861 can be used to for multiple business types and sets industry standards relative to the notification of receipt or formal acceptance of goods and services.

The 853 EDI document type is an electronic version of a paper Routing and Carrier Instruction.  The 853 EDI document type is used to wire detailed routing and carrier information relevant to a specific route. Now, EDI 853 doesn’t provide information about shipping events or any type of authorization.

An EDI 853 – Routing and Carrier Instruction document is organized into data and segment elements. For a segment, it can contain at least one data element. Each data element would contain a data field. Data elements can include a number of different things;

• List Of Shops
• Carrier
• Route
• Estimated Time Of Arrival (ETA)

There are an infinite number of possibilities available for a company to include data on an 853 – Routing and Carrier Instruction.

EDI 853 Specifications

This X12 Transaction Set contains the format and establishes the data contents of the Routing and Carrier Instruction Transaction Set (853) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set provides the sender with the capability to transmit detailed routing and carrier information pertinent to a route. This transaction set only provides routing information and does not convey information about a shipping event or provide shipping authorization.