Enable seamless B2B EDI Integration—automate data exchange, enhance partner communication, and boost the efficiency of your business.

Tag Archive for: B2B EDI integration

EDI for Specific Industries

EDI – Electronic Data Interchange is a well-established protocol of business data exchange, which has become more and more widespread in recent years among businesses of all sizes and various industries.

Through EDI, companies can exchange business documents that were traditionally communicated on paper or by e-mail.

By replacing the exchange of paper or e-mail documents with EDI, companies save time and eliminate manual data processing, which often leads to errors and costly delays in all business processes.

Companies today use EDI to send all kinds of documents, from orders, and invoices to motor carrier load tender, customs manifest, and more.

The exchange of EDI takes place between business partners who exchange goods or services.

All EDI transactions comply with standards developed and maintained by several organizations including UN/CEFACT, X12, ODETTE, GS1, Peppol, and others.

However, despite uniform standards, each industry can use a certain set of specific EDI transactions. Below we provide some examples of EDI documents for specific industries.

USEFUL: A complete list of documents that can be exchanged via EDI

EDI for Transportation and Logistics Industries

The Transportation industry actively uses EDI and, in addition to standard transactions, this industry use sets of specific EDI documents.

The transport industry includes a huge variety of different types of transportation. It includes marine, air, rail, and motor freight. Accordingly, the EDI transactions used for example in rail transportation will differ from those used by motor freight.

The Most Used EDI Transactions for Transportation and Logistics

USEFUL: You can find a complete list of EDI transportation codes in our article “EDI Integration for Transportation and Logistics”

EDI for the Supply Chain Industry

The supply chain industry includes many processes such as distribution, inventory, purchasing, production planning, sales, supply chain planning, interaction with trading partners and warehouses.

The use of EDI in the supply chain allows the company to quickly exchange documents electronically with all suppliers, exchange prices and catalogs, track information on shipments and acceptance of goods. EDI allows to make the supply chain as transparent and efficient as possible, receiving up-to-date data on the movement of goods and funds in real-time.

EDI Transactions for Supply Chain

Here are some of the most common EDI documents in the supply chain:

  • EDI 810 – Invoice
  • EDI 846 – Inventory Status
  • EDI 850 – Purchase Order
  • EDI 856 – Ship Notice/Manifest
  • EDI 855 – Purchase Order Acknowledgment
  • EDI 820 – Payment Order/Remittance Advice
  • EDI 753 – Request For Routing Instructions
  • EDI 754 – Routing Instructions
  • EDI 816 – Organizational Relationships
  • EDI 830 – Planning Schedule With Release Capability

To learn more about the use of EDI in the supply chain, read our article: Electronic Data Interchange (EDI) in the Supply Chain

It covers the following questions:

– What is EDI?

– Why use EDI in the supply chain?

– How does EDI work?

– Typical EDI workflow process

– Additional and specific types of EDI messages

– Benefits of EDI for Supply Chain Management

– Effective EDI Solution for Supply Chain

USEFUL: EDI for Third-Party Logistics providers (3PL)

EDI for HealthCare and Insurance Industries

EDI is of great value to healthcare organizations because it provides a secure way to electronically exchange sensitive information.

The healthcare industry includes health insurance activities, which are carried out by both commercial and public health organizations.

Most common EDI Transaction Sets in HealthCare

  • HIPAA / X12 270 – Eligibility, Coverage, or Benefit Inquiry
  • HIPAA / X12 271 – Eligibility, Coverage, or Benefit Response
  • HIPAA / X12 276 – Healthcare Claim Status Request
  • HIPAA / X12 277 – Health Care Claim Status Response
  • HIPAA / X12 837 – Health Care Claim (Professional, Institutional, and Dental)
  • HIPAA / X12 999 – Implementation Acknowledgment
  • EDI 273 – Insurance/Annuity Application Status
  • EDI 274 – Healthcare Provider Information
  • EDI 275 – Patient Information
  • EDI 834 – Benefit Enrollment And Maintenance
  • EDI 835 – Health Care Claim Payment/Advice
  • EDI 852 – Product Activity Data (to exchange information between Manufacturers and Pharmacies)
  • EDI 999 – Implementation Acknowledgment (for Health Care Insurance)

To learn more about EDI in healthcare, please read this article: All you need to know about HIPAA EDI compliance in Healthcare

EDI for the Retail Industry

The Retail Industry is a pioneer in the implementation of EDI. Large retailers are actively automating business processes and introducing new information technology solutions to reduce costs and increase sales.

Thus, the use of EDI in retail is a must. Since large retail companies have a huge number of suppliers, they have to exchange thousands of documents every month. It is simply impossible to go through so much documentation manually.

The Most Used EDI Documents in the Retail

  • EDI 810 – Invoice
  • EDI 820 – Payment Order/Remittance Advice
  • EDI 832 – Price/Sales Catalog
  • EDI 846 – Inventory Inquiry/ Advice
  • EDI 850 – Purchase Order
  • EDI 852 – Product Activity Data
  • EDI 855 – Purchase Order Acknowledgment
  • EDI 856 – Ship Notice/Manifest
  • EDI 861 – Receiving Advice/Acceptance Certificate

The use of EDI in retail offers many benefits, ranging from savings in paperwork and avoiding manual data entry errors, to reducing transport and logistics costs and increasing company profits.

If you want to learn more about the use of EDI in retail, please read this article: The Top 6 EDI Documents for Retail Suppliers

Conclusion: EDI for Specific Industries

In this article, we explored the use of electronic data interchange in some industries, however, if you have any questions regarding EDI, you can always contact us for a free initial consultation.

Our more than 21 years of experience in the implementation of EDI for various industries allows us to offer our customers the most profitable and effective EDI solutions.

Free EDI Consultation
/0 Comments

EDI Integration for B2B Exchange to Optimize and Grow your Business

What is B2B EDI? 

B2B (Business-to-Business) Integration, also known as Electronic Data Interchange EDI, is the process of exchanging business documents electronically either internally or amongst external business partners.

Electronic data interchange (EDI) has become a standard data exchange practice in modern business. EDI allows companies to automate their business processes leading to greater efficiency. Automated data exchange allows to avoid errors, reduce order processing time, and achieve accuracy.

What is meant by EDI?

EDI (Electronic Data Interchange) is the process of exchanging documents electronically through secure communication channels from one software information system to another. In other words, from one business partner to another.

In a fully automated process, the exchange of electronic documents (for example, receiving and processing orders), can take place at the application level, without the direct involvement and participation of employees.

Who typically uses EDI?

EDI standard and connected technologies are used in a B2B data exchange protocol, of any type of businesses in different industries. These can be large, medium, or small enterprises operating in retail, manufacturing, healthcare, pharmaceutical, or any other industry. EDI is also used in international trade such as air, sea, and road transportation. Not surprising, to see customs in most of the countries using EDI heavily in their cross-border operations.

Experience shows that large retailers such as Walmart, Costco, Kroger, Home Depot, Target, etc. are always the initiators of electronic data exchange. Moreover, almost all retailers, having evaluated the advantages of using EDI, force their suppliers to exchange documents only through EDI.

EDI Integration with Business Systems (ERP/CRM)

EDI integration allows to automate the creation, sending, receiving, and processing of any business documents in electronic format with a trading partner, existing backend business systems, or applications, to provide a greater level of efficiency and complete automation.

With over 21 years of experience in EDI and the integration marketplace, our company EDI2XML has a proven experience in integrating EDI, with the most frequently used systems:

EDI Integrations and eCommerce Businesses  

EDI is also becoming a vital element of the e-commerce business; we are receiving more and more requests for e-commerce integration with EDI.

Especially, requests for connecting online stores running on one of the major e-commerce platforms. The most frequent EDI e-commerce integration are:

  • Shopify EDI Integration
  • Magento EDI Integration
  • BigCommerce EDI Integration
  • Amazon Vendor Central EDI integration
  • Amazon Seller Central EDI integration
  • Walmart EDI Integration
  • And much more…

This means that orders from an online store will be automatically converted into an EDI document (for example X12 EDI 850 Purchase Order) and pushed into a supplier’s business system. This is the most common scenario in an eCommerce dropship business.

However, it is worth mentioning the very common request for e-commerce integration with ERP / CRM systems. This means syncing data between business software systems (SAP, Salesforce, JDE, etc.) with your e-commerce store.

Fully Managed EDI Services to automate data exchange with business partners

Our company offers a fully managed EDI service that includes transformation and connectivity services for companies of all sizes.

Our customers do not need to install any software or hardware because all EDI file conversions and transformations, are done from our side. We carry out all stages of an integration project from project planning to testing with the trading partner.

Our integration platform receives EDI files (for example x12 or EDIFACT) from the trading partner, then converts them into the required format (i.e. XML, CSV, TXT) and sends them to you (see the picture below).

Fully managed EDI Service

EDI2XML platform will sit in  the middle between you and your trading partner to convert, send and collect all EDI documents.

Request Fully Managed EDI Service Pricing Plans HERE for more information.

Benefits of using EDI for B2B exchange

Currently, using the latest technologies, EDI implementation is not so expensive (as many business leaders might think), but the benefits of EDI integration allow companies to significantly speed up document flow and increase sales. Besides, EDI has many advantages, namely:

  • EDI enables companies to optimize all processes in the enterprise, from planning to production management and control.
  • EDI allows increasing the speed and efficiency of data processing. Mandatory use of standards (for example X12 or EDIFACT) helps to avoid errors and improve accuracy.
  • EDI helps manufacturers to quickly respond to the requests of their wholesalers’ customers.
  • EDI document exchange allows retailers and wholesalers to improve the efficiency of logistics and procurement as well as improve inventory management. For example, using EDIFACT messages such as INVRPT, DELFOR, DELJIT, and DESADV allows reducing warehouse storage costs.
  • EDI integration allows companies to reduce the number of employees who enter data into the business system received on paper or by e-mail.
  • EDI increases the accuracy of information processing because as practice shows, errors are inevitable with manual data entry.

B2B / EDI Integration – find the best Solution

EDI2XML offers various EDI integration solutions.

Whether you are a buyer, supplier, manufacturer, retailer, 3PL Warehouses, or Logistics – using our advanced EDI technology, you can exchange data electronically with all your partners quickly, reliably, and efficiently.

We’ve got an EDI solution that really makes your day-to-day tasks easier and faster!

Contact us for a free consultation with our EDI experts.

ORDERS and ORDRSP: The main EDIFACT messages in the supply chain management

This post was updated to reflect current trends and information.

Receiving and processing EDI purchase orders is the most common transaction faced by small businesses. This electronic business document is used to place a commercial order for goods or services by a buyer or business partner.
EDIFACT ORDERS

It’s still possible to use phone, email, or fax between two small businesses, but if you want to collaborate with a large retailer, distributor, or manufacturer, there is a high probability that you must be EDI compatible to receive orders from your B2B partners, in addition to other potential EDI documents or transactions.

What is EDIFACT ORDERS?

ORDERS (Purchase Order) is a type of EDIFACT message that contains requests for the supply of goods or services.

In EDI ANSI ASC X12 standard which is widely used in North America, the ORDERS is referred to as EDI 850 Purchase Order.

Large companies, working with small contractors demand mandatory use of EDI. Requirements for EDI compatibility is specified in contracts or in partners selection criteria.

High competition forces the business to comply, and start exchanging electronic data quickly and accurately, spending minimal time and resources on this business process. Thus, small enterprises must comply with the imposed conditions, in order not to lose a source of profitable purchases.

EDIFACT ORDERS message content

The most important main information contained in an EDIFACT ORDERS message:
  • Order number
  • Required date
  • Delivery date
  • Reference to supply contract number
  • Price and qualifier (including VAT and other taxes)
  • Identifiers of the consignee and sender, delivery location, customer, carrier, recipient
  • Information about the contents of the order (barcodes, quantity, item name, etc.).

EDIFACT ORDERS Processing

After signing the contract, the buyer uses ORDERS to send the seller a list and quantity of goods ordered.

Typically, a buyer creates the order in his ERP system (the most popular are SAP ERP, Microsoft Dynamics, Oracle JD Edwards EnterpriseOne). The created Purchase Order is instantly converted into an EDIFACT ORDERS message which is immediately sent to the seller. The seller must receive the EDIFACT message and quickly process it. He should transmit a Purchase Order Response (ORDRSP) in response to the Purchase Order received.

EDIFACT and ERP/CRM integration

To save time and money by processing the vast amount of information received from business partners, most companies (both retailers and suppliers) choose to integrate their EDI / EDIFACT messages into their ERP systems. Basically, with integration, they connect the received EDI messages and push it directly to their ERP software, through Integration Connectors designed specifically to synchronize and integrate into their ERP systems.

For example, using Magic xpi Integration Platform a company can connect a variety of heterogenous business systems such as ERP, CRM, finance, etc. by implementing out-of-the-box certified and optimized connectors.

You can find useful information on EDI integration with ERP Systems in the following articles:

How to make EDIFACT ordering even easier
EDIFACT ERP integration

As the number of outgoing or incoming orders increase, companies try to optimize the exchange of orders. In case the number of your orders exceeds a couple of hundreds per month, it’s worth thinking about integrating the flow of orders directly into your business software solution and save your company the time and money associated with human errors, delays to deliver, and increase efficiency.

The process of Order creation can be fully automated; it will not require human intervention. To do this first it is necessary to integrate your business system with EDI.

Related article:

Usually, after starting to use ORDERS message, the buyer will most likely request to receive replies to his orders, which means connecting another type of EDI message – ORDRSP. In addition, he can ask you for the dispatch advice (DESADV), and he can send you the delivery advice message. (RECADV).

What is ORDRSP and what are the benefits of using this EDIFACT message

ORDRSP (Order Response) is a type of EDIFACT message in which the supplier confirms or rejects the delivery of goods to the buyer. Using ORDRSP, the supplier can propose amendments, notify of a complete or partial delivery or confirm the entire delivery, before even processing the delivery.

Using UN/EDIFACT ORDRSP improves the logistics chain: the parties save on transportation, reduce returns due to incorrect deliveries of merchandise, increase the accuracy of delivery of the right products.

Through ORDRSP, the supplier can notify the buyer of the lack of certain products, thus avoiding disruption of supplies and maintaining a loyal business relationship. Customer, having this information, can order a similar product from the presented assortment or place an order from another supplier.

The buyer can always understand whether the supplier will deliver the goods on time, or not. He sees preliminary price confirmation and quantity of products, predicts the state of stock based on ORDRSP, and the supplier can automatically book goods for delivery in his warehouse when processing a Purchase Order Response.

What does ORDRSP contain?

ORDRSP has a direct relationship with ORDERS and are complimentary to each other. ORDRSP consists of:
  • Order number
  • GLN numbers of the buyer and seller
  • Order confirmation number
  • Date of planned delivery of goods
  • Scheduled time
  • Item No
  • Quantity approved (To Ship)
  • Price approved
  • Reason of rejection (when parameters are not matching between Order and supplier)

EDI/EDIFACT integration

In EDI/EDIFACT documents exchange, the EDI provider plays a key role. He is the one who ensures the conversion and integrity of message formats and tracking data transfers. For over 21 years now, our company EDI2XML has been successfully helping companies of all sizes switch to Electronic Data Interchange. We help speed up working with orders, shipments, acceptance, inventory of goods and reduce the risks of human errors. We have no hidden fees or confusing rates.

Contact us today for more information and a free EDI consultation.

What is EDIFACT? | UN / EDIFACT Standard Overview

UN / EDIFACT Standard Overview

What is UN/EDIFACT standard?

United Nations/Electronic Data Interchange for Administration, Commerce and Transport (UN/EDIFACT) is the International EDI standard ISO 9735-1987, developed under the UN

The general standard is adopted by national and sectoral standards bodies to better reflect the needs of each industry.

At least twice a year, the standard is updated globally. The reason of this update is to create a new directory of data and messages, in addition to improving the usability of existing EDIFACT messages.

The UN/EDIFACT standard has been developed for trade and transport management. The concept of “trade” was interpreted in a broad sense (orders, deliveries, insurance, payment of goods, customs formalities). Currently, the use of UN/EDIFACT has expanded to include accounting, customs control, pensions, health care, social insurance, judicial practice, employment, statistics, construction, finance, insurance, manufacturing, tourism, trade, freight, and container transportation.

The UN/EDIFACT standard is developed and supported by two international organizations: United Nations Economic Commission for Europe — UN ECE and the International Organization for Standardization. – ISO

EDIFACT Subsets

EDIFACT is predominant outside of North America. Due to its complexity, branch-specific subsets of EDIFACT have been developed. These subsets are subsets of EDIFACT and contain only the functions relevant to specific user groups, such as:

  • EANCOM consumer goods industry
  • ODETTE European automotive industry.
  • CEFIC chemical industry
  • EDICON standard used in the construction industry
  • RINET – the Insurance industry
  • HL7 standard is used in healthcare.
  • IATA air transportation
  • SWIFT banking
  • UIC 912 rail transport
  • EDIFICE electronics, software, and telecommunications industry. EDIFICE has played an important role in the implementation of RosettaNet standards in Europe. EDIFICE became the European RosettaNet User Group.

EDIFACT Messages: Structure and Syntax of the Standard

EDIFACT is a special, structured data language that describes all types of commercial activities, based on information logistics. Using elements and segments of standard informational messages, you can create a description of any document, generate its electronic form and transmit it in open telecommunication networks without fear of interception of private commercial information.

UN / EDIFACT Structure

Any document in UN / EDIFACT standard has a hierarchical structure. The entire electronic document is called a message. A message consists of data groups combined in some way, for example, a data group describing customs payments, a group of data describing the attributes of documents, etc. In turn, the group consists of typical data segments that describe document attributes in more details. The standard provides about 200 different types of segments from which messages are composed. The segments themselves also have a hierarchical structure and consist of data elements that can be simple (data field) and composite (usually 2-3 data fields).

The following is the structure of an EDIFACT transmission:

  • Service String Advice
  • Interchange Header
  • Functional Group Header
  • Message Header
  • User Data Segments
  • Message Trailer
  • Functional Group Trailer
  • Interchange Trailer

EDI Guide

Example EDIFACT

UNA:+.? ‘
UNB+UNOB:2+ XYZCORPORATION:ZZ+COMPANYX:ZZ+190521:1604+906019++++++1′
UNH+1+ORDERS:D:96A:UN’
BGM+220+4500265532+9′
DTM+137:20190425:102′
RFF+CT:CompanyX’
NAD+BY+2010::91′
CTA+OC+2010:G. Smith ‘
COM+044-1010605:TE’
COM+044-1010662:FX’
NAD+SE+0000906300::92′
CTA+SC+0000906300′
NAD+DP+++Consulting Inc St+ Begun + Laval++8003+CA’
CUX+2:CHF:9′
LIN+10++TH300010:BP’
PIA+1+000000000000500807:SA’
IMD+A++::92:HIR0010H12′
QTY+22:1:PCE’
DTM+2:20190423:102′
LIN+20++T0004671:BP’
PIA+1+000000000000501516:SA’
IMD+A++::92:CCGT060204NS LT1110S’
QTY+22:10:PCE’
DTM+2:20190423:102′
LIN+30++T2001171:BP’
PIA+1+000000000000501328:SA’
IMD+A++::92:LTPNG-R20-3.0′
QTY+22:1:PCE’
DTM+2:20190423:102′
UNS+S’
UNT+28+1′
UNZ+1+906019′

Principles and Technologies of Application of the UN / EDIFACT Standard

The EDIFACT Standard has three types of reference books:

The first type is directories that are based on the ISO standards. It includes directories of currency codes, country codes, units of measurement, modes of transport, delivery conditions, and some others.

The second type of directories, are the ones included in the EDIFACT standard., by default

The third type of directories is developed by different organizations responsible for issuing codes. Here is the list of organizations 3055 Code list responsible agency code

There are four main components in EDIFACT that are subject to standardization, when preparing documents for exchange between business partners.

  • data elements
  • standard data segments
  • standard messages
  • syntax rules

Data elements are the smallest, non-dividing parts of information, for example, the document date, the name of the destination, the amount of tax. More than 600 data elements used in international trade and transport have been published in a special UNTDID directory.

EDIFACT Standard Principles

The UN / EDIFACT standard is based on the following principal:

1. Standardize data at the segment and element level. Any document intended for electronic exchange should consist of typical segments. This means that the segment of the supplier’s address or delivery address is described by the same elements, regardless of what kind of document it is – invoice, order, declaration, etc. The practice has shown that to describe almost any document, it is enough to have no more than 100 typical segments. The fields inside the segments are standardized the same way, and the ratio of fields to segments is one-to-many, i.e. the same field can be included in different segments.

2. Record the fields used in segments as code. It is assumed that the partners exchanging electronic documents have identical code tables (directories). The composition and content of the reference books is standardized at three levels – international, national and corporate.

3. The independence of standards from the language of communication. The peculiarity of the UN / EDIFACT standards is that more than 90% of the electronic message consists of different codes. Another feature is that only the content of the document is transmitted, without a form. The document form is restored when the message is decoded.

Book a FREE one-on-one EDIFACT consultation session with our in-house experts.

EDIFACT Messages

The EDIFACT standard which provides a set of standard messages has greatly simplified international and multi-branch trade and the exchange of electronic business documents between countries and various industries.

The standard message UN / EDIFACT has a six-letter identifier that reflects the short name of the message, for example:

  • CUSDEC – CUStoms DEClaration
  • CUSRES –CUStoms RESponse

Some of the standard EDIFACT messages with X12 equivalent are listed in the table below.

X12 Transaction Number EDIFACT Transaction ID Transaction name
850 ORDERS Purchase order message
855 ORDRSP Purchase Order Acknowledgment
846 INVRPT Inventory Inquiry/Advice
856 DESADV Shipment Notification ASN
810 INVOIC Invoice
997 CONTRL Functional acknowledgment
860 ORDCHG Purchase Order Change – Buyer Initiated

Due to the independence from the language and the transfer of only the contents of the document, the restoration of the form of the document takes place on the receiving side in accordance with the rules that apply in this place.

Benefits of EDIFACT

EDIFACT benifits

EDIFACT has a competitive advantage that positively affects the efficiency of a company and improves business processes. The main advantages of EDIFACT:

Profitability – reducing the volume of papers to be processed leads to a decrease in personnel and administrative costs.

Efficiency – large volumes of commercial data can be transferred from one computer to another within minutes

Accuracy – the use of EDIFACT eliminates human errors that are inevitable when manually keying in data.

EDIFACT is a key component of a just-in-time strategy that ensures prompt customer satisfaction. EDIFACT in conjunction with the Internet allows real-time electronic transactions and accelerates the interaction between trading partners.

Easy EDIFACT Integration

Our company has many years of proven experience in implementing EDI and EDIFACT projects. We offer our clients Fully managed EDI Service and HTTP Web Service.

Contact us today for a free consultation and we will help you find the best option for your business.

EDIFACT Free consultation

EDI Integration of B2B E-commerce for Small Companies

Navigating B2B E-Commerce: A Small Company’s Guide to Seamless EDI Integration

More and more companies in the B2B vertical, are expanding their business to the web and doing more of what is called today B2B e-commerce. Those companies of all sizes are realizing the importance of automation and the value of exchanging EDI with their business partners, suppliers, and buyers.

For small companies in the B2B market, trading with large retailers such as Costco, Wal-Mart, Target or Home Depot is a great opportunity for their business. However, many small and medium-sized enterprises are missing out on this chance due to the fear of large retailers’ requirement to comply with their EDI rules.

In most cases, EDI is the de-facto protocol to communicate and exchange business documents between big-box retailers and their suppliers.

EDI is used to automate the process of exchanging business documents between trading partners. Essentially, it is the solution for B2B and is quite popular amongst retail, manufacturing, transportation, health care, and other industries. By automating documents exchange process, companies can benefit in many areas.

To those who do not know much about Electronic Data Interchange (EDI), it sounds quite complicated at first. There are different EDI standards, requirements, EDI formats, communication protocols such as AS2, sFTP, VAN, different documents / transactions (i.e. 850, 810, 846 856, etc.) which differ depending on company and industry.

EDI Integration projects seem daunting and expensive, which can explain why many smaller businesses still do not communicate with their trading partners through EDI. However, the key is to find the right EDI provider who can offer solutions and services that are simple, affordable and quick to onboard.

An EDI provider like EDI2XML offers 2 options for EDI integration projects:

Fully Managed EDI

This option is a “turn-key solution” where our team at EDI2XML, takes care of all the project: setup, configuration, testing, certification with your EDI partners …

Our monthly pricing packages are dynamic, they go up and down based on the volume and you are not locked in in any tier. Following is a diagram illustrating the flow of information with our EDI as a service offering.
EDI integration platform

By using our EDI Web Service, you can enhance efficiency, reduce errors, and improve collaboration with your trading partners.

EDI2XML Web Services

This option is meant for companies who got their own technical resources to work with REST API (call and consume HTTP Rest Web services); In such a scenario EDI2XML web services is the way to go for the following reasons:
  • Self-service solution,
  • Low cost,
  • Quick entry: you can be up and running in less than an hour, and it is proven; we provide everything to your developers to get started, a java client with its source code and instructions on how to work with it.
  • We offer the xml schemas (xsd) of the XML format our API expects, and all that you need to do is to format your data according to that format and you will be up and running.
  • We offer 15 days free trial, without any commitment.

Advantages of Using EDI
B2B edi Integration

Integrating Electronic Data Interchange (EDI) into B2B e-commerce can bring significant benefits to small companies. EDI allows for the automated exchange of business documents and data between trading partners, streamlining communication, reducing manual effort, and improving efficiency.

Integrating Electronic Data Interchange (EDI) into B2B e-commerce can bring significant benefits to small companies. EDI allows for the automated exchange of business documents and data between trading partners, streamlining communication, reducing manual effort, and improving efficiency.

With EDI, orders, invoices, and other business documents can be sent straight from your ERP management system to the EDI Provider, where they can process this XML file into EDI format and then sent to the Trading Partner.

Orders come in as EDI, get translated into XML format and then get sent straight to your ERP system (if integration was done). In most cases where integration to your ERP solution is done, no human intervention is even needed. This saves so much time and effort and finally allows your employees to get a lot more time on their hands for other important tasks, eliminating so much of the manual data entry.

When it comes to EDI, every case is different. It’s all about finding the right EDI provider that can help you with this process and ensure it’s simple and efficient as can be. Automating B2B processes with EDI can help companies stay profitable by letting them keep up with market changes and trends.

Look at EDI2XML, and book a free consultation with one of our EDI experts!
EDI price

What are the differences between RosettaNet, EDI ANSI X12 and EDIFACT

 

This post was updated to reflect current trends and information.


What is RosettaNet?

Rosettanet RosettaNet is a non-profit organization having more than 500 high-tech companies as members. These members create and implement open standards for processing business to business (B2B) transactions, especially at the supply chain level, in their appropriate vertical. The main mission of RosettaNet organization is to generate standard protocols for specific business transactions such as new Product Information, order Management, design registration, request technical data, etc.

These standards define XML schema, thus defining a hundred processes for exchanging information between partners (PIP-partner interface processes).

Founded in 1997 by Fadi Chehadé, RosettaNet is a subsidiary of GS1 US, formerly the Uniform Code Council, Inc. (UCC).

RosettaNet and the high technology industry

RosettaNet includes more than 500 members from companies all over the world. Most companies of this consortium belong to the electronics and semiconductor industry – companies that produce personal computers (PCs), computer hardware, computer software, electronic components, telecommunications equipment, consumer electronics. This organization also includes telecommunications and logistics companies.

RosettaNet includes big companies such as:

RosettaNet has several local user groups. The European user group of RosettaNet for B2B standards is EDIFICE.

The RosettaNet standard

Electronic industry and Rosettanet RosettaNet optimizes existing standards, guidelines, and specifications of open e-business for cross-platform applications and network communications. RosettaNet defines the concepts of e-business (file formats, procedures, implementation, requirements, etc.) and develops standards for ensuring compatibility of business processes. RosettaNet is based on open XML standards.

Primarily oriented in the supply chain areas, RosettaNet also addresses production, product data, and service processes.

As I mentioned above, this standard is widely distributed in the electronic components and semiconductor industries, but also in the logistics and telecommunication industries.

Partner Interface Processes (PIPs)

RosettaNet PIPs are specialized System-to-System XML-based dialogs that define business processes between partners in a value chain. Each PIP comprises a specification founded on the RNIF “RosettaNet Implementation Framework”.

A RosettaNet implementation, requires a message guideline with a PIP-specific version of the Business Dictionary, and an XML Message Guideline document that provides the models and documents.

The different PIPs are divided into clusters (areas), each covering a specific business process area:

  • Cluster 0: RosettaNet Support
  • Cluster 1: Partner Product and Service Review
  • Cluster 2: Product Information
  • Cluster 3: Order Management
  • Cluster 4: Inventory Management
  • Cluster 5: Marketing Information Management
  • Cluster 6: Service and Support
  • Cluster 7: Manufacturing

The actual PIP name is obtained from the clusters and the subsequent division.

RosettaNet PIP 3A4: Request Purchase Order

3 → Cluster 3

A → Quote and Order Entry

4 → Request Purchase Order

To learn more about RosettaNet PIP Classifications learn our previous article: RosettaNet and B2B EDI Integration: All you need to know

How RosettaNet differs From EDI ANSI X12 and EDIFACT

EDI is another standard to exchange EDI (electronic data) messages between trading partners. EDI stands for “Electronic Data Interchange.” There are numerous variations of EDI and each variation is different from the other. The ANSI X12 is the most popular in North America in various verticals, while EDIFACT is popular in Europe.

Useful reading: ANSI ASC X12 Standards Overview

There are many major elements distinguishing RosettaNet from EDI X12 and EDIFACT:

First, RosettaNet is developed principally to support logistics and supply chain interactions in the Hight- technology industry, while EDI is widely used in various industries (Retail, Wholesale, Energy, Healthcare, Pharmaceutical, Manufacturing, Logistics, Government, etc.)

The second difference between RosettaNet and other EDI standards, is that RosettaNet focuses on process and process modeling, while there are no process-focused messages in ANSI X12 and EDIFACT.

Another difference between RosettaNet and EDI is RosettaNet is XML- based while EDI (X12 and EDIFACT) is text-based. There’s a big structural difference between RosettaNet and EDI business document.

A RosettaNet message package contains two main parts: headers that define the source, destination, and purpose of the message package; and a payload (with optional attachments) that transmits the actual business information or operational signals (for example error messages). Both the headers and the payload are encapsulated in XML tags.

In addition, RosettaNet is adopting existing Industry standards, such as JEDEC, UN, the UCC/EAN, NEDA, NIST, and others.

Unlike ANSI X12 and EDIFACT, RosettaNet formed business dictionary and Technical Dictionary (RNTD)

The RosettaNet Business Dictionary (RNBD) identified business attributes to define transactions between trading partners. It defines the meaning of business terms for example “Purchase Order Acceptance” thus the trading partners can be guaranteed the processes interfaced between two businesses are being correctly mapped. The Business Dictionary serves as a central reference and reference work for other standard documents.

The RosettaNet Technical Dictionary (RNTD) provides a common language for the definition of IT products. In other words, it ensures that product information exchanged between business partners uses a common vocabulary even if one of the partners prefer a non-standard intern term.

The EDI community recognized the need for such dictionaries…RosettaNet successfully created and used the dictionaries because it restricted the scope of the dictionaries to first the IT industry, then to the Electronic Component (EC) industry, and the Semiconductor (SM), Telecommunications (TC) and Logistics (LG) industries.

How difficult is to implement RosettaNet?

You will need a good knowledge of XML, as well as some knowledge of supply chain management. Experience with SAP, Oracle Applications, or similar software for enterprise resource planning, manufacturing or supply chain will also be an advantage.

Our team of specialists has many years of successful experience working with RosettaNet and business systems integration, so if you need help or advice or professional advance, please contact us and we will more than happy to assist you!

Fully managed EDI service VS HTTP Web Service: Which is Better for Your Business ?

This post was updated to reflect current trends and information.

Electronic Data Interchange (EDI) and all the services around it are becoming more and more popular, regardless of the industry, for one major reason: EDI transactions are replacing paper documents exchanged between trading partners, and helping companies in their digital transformation projects, for a “greener” planet.

Retail was one of the first industries to fully adopt EDI, and it is still the most active vertical in its usage. EDI is a proven and effective alternative to fax, e-mail, and manually entering or re-entering data such as Invoice, Purchase Order, Inventory and many others…

There are various types of EDI and several approaches to integrate Electronic Data Interchange in a business community. Each EDI provider can offer a different EDI integration methodology, in order to become EDI compliant. We at EDI2XML, offer two options for to integrate EDI into your company, and make your business “EDI compliant”, while shortening the integration project:

Fully managed EDI service

HTTP EDI Web Service

How to select? What kind of EDI integration solution is a better option for your business?  First, let’s understand both options.

Fully managed EDI service

The EDI2XML service offered as “fully managed”, includes translation and communication service offering to businesses of all sizes, from different industries.

Our team at EDI2XML, takes care of ALL the aspects of the integration project. With this model, we offer a “Turnkey EDI Solution” where we take on our shoulder all setup, configuration, testing, certification with the EDI partners …
EDI Fully Managed Service

In other words, with this option, we take care of everything: all the steps of the project from A to Z. We can even integrate directly into your ERP or CRM system. We provide certified connectors for leading IT systems such as Salesforce, JD Edwards, SAP, Dynamics CRM, Dynamics AX, and more.
EDI integration platform

a) Technical Details

A setup phase is mandatory for all new Trading Partners and/or EDI document implementation. This stage includes the project analysis, setup of Trading Partner accounts, configuring Partner specs and platform, defining the transfer file structure, building and setting up all required connectivities and communication protocols. It also includes an end-to-end full cycle data testing and certification.

To learn more about EDI service, download our free introductory guide here

b) Pricing

As for the pricing, it is based on pre-defined monthly service packages, including a pre-defined volume of data processed. All our packages are billed monthly based on the entry level plan (Business Light) at the beginning of each month. Subsequent month billing will include the basic plan fee PLUS the difference between the plan we billed initially (Business light) for previous month, and the plan that we were supposed bill for the previous month based on real volume of data processed for that month.

All this to say, our monthly pricing packages are dynamic, they go up and down based on the volume of data we process and integrate, and our clients are not locked in in any of the packages.

For more information about pricing – fill out a form: EDI2XML Translation Service Pricing Package

HTTP EDI Web Service (REST API)

EDI2XML Web Service, is an HTTP service running over the internet, on EDI2XML own platform that is capable of receiving HTTP requests to translate EDI messages to XML, and XML messages to EDI (based on EDI2XML’s proprietary format).

EDI2XML Web Service is much more cost effective, and meant for companies who got their own technical resources to work with REST API (call and consume HTTP Rest Web services)

The principles of the mechanism of EDI2XML Web Service is schematically illustrated in the below diagram.
EDI Wed Service

a) Advantages

EDI2XML Web Service is the way to go for the following reasons:
  • Self-service solution
  • Low cost
  • We offer a 15 days free trial, without any commitment.
  • Get started with less than an hour
  • There is no contract, no commitment.
  • Payments are month to month; Cancel anytime with a 30 days’ notice.
  • A very simple and dynamic pricing scheme
  • Availability and reliability
  • Based on proven technology in the field for over 18 years now
  • Outstanding technical support

b) Technical Details

Implementation time: Getting started with EDI2XML Web Service, is very simple and quick. Within less than an hour, you can issue the first Call to the Web Service and see the response. Our HTTP EDI Web service is very clearly documented, and we provide instructions with each subscription.
  • Quick entry: you can be up and running in less than an hour, and it is proven; we provide everything to your developers to get started, a java client with its source code and instructions on how to work with it.
  • We offer the schemas(xsd) of the XML format our API expects, and all what you need to do is to format your data according to that format and you will be up and running.

c) Pricing

EDI2XML API service fee to use the HTTP / Web Service calls, has a very simple pricing scheme. The price consists of two elements:
  1. Monthly mailbox fee: a “fixed” monthly fee for the Web Service Mailbox usage on EDI2XML platform. It is a nonrefundable fee.
  2. Data processing fee: a “variable” fee based on the volume of data processed and translated between EDI and XML, during a calendar month. The volume of data processed is computed in both directions:
  • Incoming, and
  • Outgoing

Click here to request EDI2XML Web Service Price List

d) How to get started with EDI2XML API

To get started with our EDI Web Service three steps you need to follow:

1. You need to provide us the list of documents/transactions you want to be activated under your trial account.

2. We will simply set you up with a 15 days trial account, without any commitment from you. Just let us know when do you want to kick off, and we can take care of setting you up on a trial account.

3. We provide a Java client and its source code. You can get started with less than an hour, this will allow you to try and see the results by your own.

? Watch the Video and discover which solution aligns best with your business needs and goals.

Compare key features of Fully managed EDI service and HTTP EDI Web Service

key feature

Fully managed EDI service

HTTP EDI Web Service

 Type of EDI solutionFull serviceSelf service
 Contract YesNo
 Commitment24 monthsNo
 Implementation time   (approximately) 2 weeks1 hour
 Real-Time ConnectionYesYes
 Free Trial account No15 days
 Data processing feeBased on the appropriate plan. It works in both directions: when the volume goes up and  when the volume goes down.  “Variable” fee based on the   volume      of data processed     and translated         between   EDI    and XML, during a         calendar    month.
 Need for internal   resourcesNoYes
 Need for in-house EDI expertiseNoNo
 Technical SupportYesYes
 Hardware Installation  RequiredNoYes
 Software Installation RequiredNoNo
Communication with the trading partner: setup and testing in both directionsYes

No

Free edi consultation

We, at EDI2XML, provide an EDI integration solution for every type of business. Contact us today for a free consultation and we will help you find the most appropriate option for your business.

Magic xpi and EDI2XML HTTP web service: the best EDI software option

This post was updated to reflect current trends and information.

More and more questions related to EDI software, systems integration, EDI, best EDI software are being raised every day by our contacts and clients. I decided to tackle those questions in this post, hoping it will help consultants, as well as companies looking for the most suitable EDI software solution.

Automation via EDI software

It does not matter which industry a company is part of be it sales, manufacturing, or service delivery at some point, every company seeks to automate its internal processes, increase efficiency and eliminate human errors.

A very common situation is the automation in e-commerce, namely – online eCommerce stores. Typically, there are several people who will work on order processing, after an order is keyed-in and entered by the consumer:

  • Operators who manually transferred orders received from the e-commerce site to the internal system.
  • A warehouse worker who will ship orders.

In an environment where EDI is implemented in such a company, and systems eCommerce and on-Premises systems are directly integrated, the need for operators to enter orders, disappears as the order is automatically transferred to the internal system of a company.

As a result, the persons in charge of shipping orders can prepare the goods for dispatch without the help of operators. So, operators are not needed at all.

The company saves money by reducing staff, eliminating errors due to human factors, moreover, the company will be able to quickly ship and deliver orders in a short window of time, which improves greatly its customer service experience.

With the growth of the business, a new need arises – the necessity for interaction between various business partners who use different systems. Nowadays many companies have realized that EDI (Electronic data interchange) along with integration of its business applications, helps enterprises and qualitatively changes the work of employees.

Grow your potential with EDI web service solution

Today, there are many EDI software solutions in the market that allows you to trade electronically with your business partners. Before making a decision and choosing an EDI software, you should pay attention to:

  • the possibility of modernization and scaling
  • the simplicity of EDI implementation
  • ability to send and receive a variety of EDI documents
  • ease of use and feature-rich
  • ability to integrate with other solutions

one important trend in the tech industry today that is very popular, is the use of web services. It is a trend as a technology and as a business methodology.

If you what to know more about web services technology read our article: Seamless EDI implementation through Web Services

Our unique EDI software includes a combination of EDI2XML EDI Web services, and Magic xpi, the code free integration platform, with drag and drop visual aping, simple to use. This combination will reduce the complexity of EDI development, allowing organizations to quickly reap the benefits of this powerful technology, quickly on-board its partners, and most importantly, fully automate and integrate its own ERP or CRM system in a matter of days.

EDI2XML Web Service, is an HTTP service running over the internet, on EDI2XML own private platform that is capable of receiving HTTP requests to translate EDI messages to XML, and XML messages (based on EDI2XML’s proprietary format) to EDI.

EDI2XML HTTP services provide technological and business benefits which include:

  • Application and data integration
  • Versatility
  • Cost savings (no contract: pay as you go)
  • Very simple and dynamic pricing scheme
  • Quick start of using (you can start with less than an hour)
  • Availability and reliability
  • Based on proven technology in the field for over 18 years now
  • Outstanding technical support

Who is EDI2XML web service for?

EDI2XML Web Service, is for developers and businesses, interested in building their own EDI (Electronic Data Interchange) integration flows and programs. Normally, these individuals, are capable of interacting with external API and Web Services to translate EDI to XML and XML to EDI, and have the resources and expertise to work with Web Services and HTTP requests in order to achieve their goals. EDI2XML web service, is the premier choice for IT people as a reliable service to accomplish such Integration projects.

Getting started with EDI2XML Web Service, is very simple and quick. Within less than an hour, you can issue the first Call to the Web Service and see the response.

EDI2XML Web Service currently, supports the EDI transactions as listed on our website. In case a transaction you are looking for is not on the list, we can simply just add it within 24 hours.

Increase competitive power through integration EDI software

Often, companies are already using different business applications such as CRM or ERP systems, which they are quite satisfied. But the question is: can they work in harmony with each other, and integrate together? What is the best way to integrate EDI software to them?

Have you ever thought that EDI software can improve your business by integration all of your business applications and organizing a new way of transferring data and processes through your CRM, ERP, WMS, SCM, finance, third-party applications, and other outdated or cloud-based system?

As mentioned above our EDI software include EDI web service and Magic xpi integration platform;  this technology combination can cover all your business needs. Before we review what is Magic xpi integration platform, let’s see what integration is.

Integration (from the Latin. Integratio – “insert”) – the process of inserting parts into something. Depending on the context, it may mean:

  • Web integration – the integration of heterogeneous web applications and systems into a single web-based environment.
  • Data Integration – Data integration involves combining data residing in different sources and providing users with a unified view of them. (definition from Wikipedia)

I would add this Wikipedia definition as follow: The integration of software systems and products is the exchange of data between systems with possible subsequent processing. The point of integration is that the data entered by the user (or directly injected by another application or API) into one system is automatically migrated to another.

Magic xpi – efficient integration for any business and any system

Magic xpi makes integration fast and uninterrupted due to pre-built components, proven and certified connectors as well as code-free, visual approach.

Using Magic xpi Integration Platform you can connect a varied business application and systems and improve the capabilities of your ERP, CRM, finance, and other enterprise systems.

Unlike other integration platforms that use complex point-to-point coding, Magic xpi have easy to use, code-free, drag and drop visual data mapper. You can manage the performance of your system at all times thanks to comprehensive monitoring and management tools. Magic xpi has incomparable connectivity including 100+ prebuilt components, certified and optimized adapters for leading IT systems, and a Connector Builder for all your needs.

Magic xpi Integration Platform

Start with the best EDI Software solution

We do offer EDI projects consultancy. We help companies plan, deploy, test and integrate EDI projects. You can simply call us (450) 68-3009 Ext 223 or write us sales@namtek.ca if you need any EDI consulting work. We have a proven 20+ years of experience in EDI and integration projects.

Seamless EDI implementation through Web Services

EDI is used almost everywhere regardless of industry or company size. The most extensive use of EDI is in the retail industry. EDI compliance is mandatory in order to trade with big retailers such as Target, Costco, Walmart,… even giants of electronic commerce like Amazon are heavy users of EDI.

There are a lot of different types and approach of implementing EDI in your company. It can fully managed EDI service, or gaining popularity lately EDI Web Service, because, service architects and developers want EDI to be easy to implement, maintainable, extensible, and scalable.

What is web service?

Web service is a network technology that provides inter-program interaction based on web standards. More specifically, it’s client and server application that communicate over the World Wide Web’s (WWW).

The W3C consortium defines a web service as: “A Web service is a software system designed to support interoperable machine-to-machine interaction over a network”.

Thus, the web service is identified by a URI string. The Web service has a User Programmatic Interface (UPI) that is represented in WSDL format. Other systems interact with this web service by exchanging SOAP or REST protocol messages. HTTP Hypertext Transfer Protocol is used to transport the messages. The description of Web services and their APIs can be found by UDDI.

♦ WSDL (Web Services Description Language) – is an XML-based interface definition language that is used for describing the functionality offered by a web service.

♦ UDDI (Universal Discovery, Description and Integration) – is an XML-based registry for business internet services

Web services are rich in functionality and extensibility, as well as their machine-readable descriptions through the use of XML. Web services can be combined to achieve complex operations.

web service diagram

The diagram above shows a very simplified view of how a web service works. The client invokes a web service call by sending a request to a server which hosts the actual web service, then get the response from the web service.

What are different types of web services?

Web services can be deployed in several ways. The following web-services are the most commonly used http web services:

♦ SOAP (Simple Object Access Protocol) — in fact, it is a triple of standards SOAP/WSDL/UDDI

♦ REST (Representational State Transfer) – quite often called as RESTful API (Application Program Interface that uses HTTP requests to GET, PUT, POST and DELETE data) or RESTful web service – is based on (REST) technology.

Actually, SOAP originated from XML-RPC (XML Remote Procedure Call) and is the next generation of its development and evolution. While REST is a concept, based on an architectural style.

Of course, there are other types of web services, but since they are not widely used, we will focus on these two in this brief review: SOAP and REST.

A Quick Overview of SOAP Web Services

SOAP stands for Simple Object Access Protocol. It is an XML-based protocol for accessing web services.

It is platform and language independent. It means that by using SOAP, you can interact with other programming language applications.

Initially, SOAP was primarily intended to implement a remote procedure call (RPC). Now SOAP is used to exchange arbitrary messages in XML format, not just to call procedures.

Like any text protocol, SOAP can be used with any application layer protocol: SMTP, FTP, HTTPS, etc., but more often SOAP is used over HTTP.

All SOAP messages are structured as an envelope (is the root element in every SOAP message), including the following elements:

  • Message ID (local name)
  • Optional Header element
  • Mandatory Body element (message body)

Structure of SOAP message:

SOAP message structure

The expanded list of SOAP message elements is shown in the data schema (for SOAP version 1.2).

A Quick Overview of REST Web Services

REST stands for Representational State Transfer. As it was mentioned above, REST is not a protocol but an architectural style built on existing standards that are well known and controlled by the W3C consortium, such as HTTP, URI (Uniform Resource Identifier), XML and RDF (Resource Description Format).

In a REST services, the emphasis is placed on access to resources, and not on the execution of remote services; this is the fundamental difference from SOAP-services. However, the remote procedure call is also applicable to REST. It uses the PUT, GET, POST, and DELETE methods of the HTTP protocol to perform tasks. The cardinal difference between REST and SOAP is that REST remains an HTTP request.

According to many developers, SOAP is cumbersome and difficult to use. REST is an easy alternative.

REST is using the URL approach. Often, to make a request, REST relies on a simple URL Instead of using XML.

Advantages of REST Web Services

REST is more flexible and easier to use for the most part. There are following advantages when:

  • Agile: Unlike SOAP, there is no strict specification for REST Web services and it consumes less bandwidth and resources, thus, REST Web services are very fast.
  • Language and Platform independent: REST web services can be written in any programming language and run on any platform.
  • Can be used with different data format: REST web service permits different data format such as Plain Text, XML, HTML, and JSON.

SOAP vs REST what to choose?

SOAP is more applicable in complex architectures where interaction with objects is beyond the scope of the CRUD model. In applications having the CRUD model, it can be quite applicable to REST due to its simplicity and transparency.

In fact, if any objects in your service do not need a complex relationship than: “Create”, “Read”, “Update”, “Delete” (usually in 99% of cases is enough), it is possible that REST will be the best choice.

In addition, REST compared to SOAP can be more productive because it does not require parsing complex XML commands on the server (regular HTTP requests are performed — PUT, GET, POST, DELETE).

EDI2XML HTTP service

EDI2XML Web Service, is an HTTP (based on REST) service running over the internet, on EDI2XML private cloud platform that is capable of receiving HTTP requests to translate EDI messages to XML, and XML messages to EDI (based on EDI2XML’s proprietary XML format). Advantages of using EDI2XML HTTP service:

⇒ You can start with less than an hour

⇒ No contract: pay as you go

⇒ Very simple and dynamic pricing scheme

⇒ Availability and reliability

⇒ Based on proven technology in the field for over 18 years now

⇒ Outstanding technical support

Our EDI Web Service solution solves developer’s problem because we have over 18 years of expertise in EDI, that is difficult for every developer and integrator to acquire quickly.

You can start with the free 15 – days trial of EDI2XML Web Service to see how real-time translation services works.

EDI Web Service for edi integration

Related Posts:

What is EDIFACT? | UN / EDIFACT standard overview

EDI ANSI ASC X12 Standards – Technical Overview – 2020

EDI Integration of B2B e-commerce for small companies

Why EDI 846 is important to do business with big-box retailers

, ,

Many vendors these days want their products to be sold at Big-box store  such as Target, Walmart, Home Depot or Costco. If you want your product on their shelf, you should be complying with their EDI requirements. EDI (Electronic Data Interchange) is the standard electronic messaging between two business partners.

B2B Integration Matters to Business Success

connect-to-large-retails-with-EDI2XML

Nowadays, big box retailers work exclusively with companies that are capable of complying with their EDI requirements, and there is a good reason for it.

Large stores move a huge amount of goods, so all that they track in their inventory systems, must comply with a variety of requirements. This means that your inventory data must be properly formatted and transmitted on time and in accordance with their requirements.

Before starting EDI Integration, you must to identify the trading partners you want to do business with. The reason for this is that each trading partner you deal with, has his own unique requirements. One of the most popular EDI document in demand these days for big-box retailers is the EDI 846 Inventory Inquiry / Advice.

What is the EDI 846 and how is used?

Based on the ASC (Accredited Standards Committee) X12 format, the transaction set Inventory Inquiry/Advice (EDI 846) could include vendor number, products, and quantity in stock. 846 documents can be used by manufacturer or supplier in the following ways:

  • for a vendor of goods and services to provide inventory information to a prospective purchaser, with no obligation to the purchaser to acquire these goods or services;
  • for a seller’s representatives of goods and services to supply inventory information to that seller;
  • for one location to supply another location with inventory information;
  • for an inquiry as to the availability of inventory with no obligation on the seller of goods and services to reserve that inventory.

 Benefits of EDI 846

There are benefits of 846 Inventory Advice to both business partners as for the supplier and for the purchaser. Some of the benefits:

  • Enable the supplier to advise when product is out of stock or no longer being manufactured
  • Allows better management of manufacturing and logistics
  • Communicating to the purchaser when the item will be available again if out of stock
  • The purchaser is able to better plan warehouse and store ordering
  • Supports the ability to order non-stock items or make some special orders

How to send/receive an EDI 846?

For the most part, the transmission of EDI is carried out via the Internet or Value-Added network (VAN). To make EDI more accessible, today most of the EDI data is carried out via the Internet using AS2 or a secure FTP. This eliminates the need for expensive VANs. The file is protected by encryption to ensure data security.

 Need to know more about EDI? View our SlideShare Presentation on EDI in the Business World

Connect to large retailers with EDI2XML

Don’t miss your opportunities to trade with big chains, because of their requirements of EDI. Using our service, even small companies can get the opportunity to trade with large stores and send 846 documents.

Delegate EDI to a third party and focus on running your business. We are well-qualified EDI-as-a-Service provider and we produce results rapidly while avoiding common errors that can endanger business operations and trading partner relationships.

If you need EDI Integration, let us show you what our popular translation and communication service EDI2XML as a Service can do for your business. Don’t give up big retailers, Contact us today!

cta_edi2xml