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 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

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

This post was updated to reflect current trends and information.

Company Overview of Burlington Coat Factory

Burlington Coat Factory is an American national off-price department store retailer and a division of Burlington Coat Factory Warehouse Corporation. The company operated 592 stores located in 45 states and Puerto Rico, inclusive of an internet store and has approximately 40 000 employees.

As per the company’s website, the first store was opened in Burlington, New Jersey in 1972, selling principally coats and outerwear.  Since then company diversified product categories by offering an extensive selection fashion-focused, labeled merchandise acquired directly from nationally recognized manufacturers and other suppliers.

Burlington Coat Factory EDI Standards

For all communications with their suppliers, Burlington Coat Factory use Electronic Data Interchange (EDI) including purchase orders, Advance Ship Notices (ASN), Invoices etc. The company is on EDI X12 v4010 standard.

Burlington Coat Factory EDI Specification

850 Purchase Order

Burlington Coat Factory sends 850 Purchase Orders via EDI, to inform their seller of a product request. A Purchase order 850 may be used to provide distribution requirements for receiving location(s), such as cross-dock, drop-ship, or direct to consumer as would be the case for the Burlington online store.

For each 850 Purchase Order, they indicate a purchase order number, a P/O date, the location of the ship to, provide a delivery time and product pricing.

856 Ship Notice/Manifest

Burlington Stores requires their seller to send an 856 Ship Notice/Manifest via EDI, to be advised of shipment information. The 856 transactions, includes order information, description of goods, types of packaging used, carrier information and more.

For a single purchase order, there can be or more shipments which would be followed by one or more 856 ASN Advance Ship Notice and possibly one or more 810 Invoices.

810 Invoice

The suppliers of Burlington Coat Factory have to comply with X12 810 Invoice to bill Burlington for products and services shipped to their stores.

Using an EDI 810 Invoice, permits Burlington to register payment-request information and update automatically their appropriate systems. The information included in the Invoice 810 provides automated cross-referencing of a purchase order and receiving information. This process is executed without manual intervention, thus eliminating further data entry.

824 Application Advice

Burlington Stores send 824 Application Advice via EDI, to notify the acceptance, rejection or acceptance with change of a trading partner’s transaction. The 824 transaction set contains information such as quantity and monetary amounts, dates, reference numbers, it also provides trading partner information, technical error descriptions in free-form text format.

852 Product Activity

The EDI message 852 Product Activity sent by Burlington to transmit product sales by location to the supplier. These messages inform a supplier about the items sold and items on hand at a store and its level. Burlington sends the EDI 852 message on a scheduled basis (e.g., weekly on Mondays) for input to a vendor’s sales and inventory management system.

997 Functional Acknowledgment

997 Functional Acknowledgment is required by Burlington, when sending or receiving EDI transactions. 997s, are an indication that a trading partner has successfully received a well-formed EDI message. The message Functional Acknowledgments 997 generated automatically for transmission back to the sending party.

Becoming EDI compliant with Burlington Coat Factory

EDI2XML offers full EDI integration with Burlington Coat Factory. From A to Z, a customer’s EDI requirements are handled by our team of EDI experts. We take care of EDI mapping, Trading Partner configuration, Standards maintenance, XML/CSV/TXT translation etc.

For more information Download our EDI2XML Translation Service Pricing Package here 

EDI2XML pricing packages


This post was updated to reflect current trends and information.


Bed Bath & Beyond – Company Overview

Founded in 1971 Bed Bath & Beyond Inc.  is an American-owned omnichannel retailer offering a vast selection of high-quality domestic’s merchandise and home furnishings.

Bed Bath & Beyond (BBB) has an e-commerce platform consisting of various websites and applications. The Company also operates established retail stores in the United States, Puerto Rico, Canada, and Mexico. As of 2021, the company has a total of 1 020 stores and 55 000 employees.

Bed Bath & Beyond purchases its merchandise from 10 800 suppliers, 85% of such purchases are provided by small and medium-sized enterprises. The company’s 10 largest suppliers accounting for only 15% of purchases.

BBB faces growing competition from online stores, such as Amazon. To strengthen its presence on Internet, Company makes acquisitions such as Decorist an online interior design platform. One Kings Lane Inc. – an online home goods retailer which offers an extensive collection of designers. PersonalizationMall.com – online seller of personalized gifts. Of a Kind, is an e-commerce website that offers limited edition items from emerging fashion and home designers.

Bed Bath & Beyond EDI Compliance

To be among the Bed Bath & Beyond suppliers, you must be able to send and receive documents electronically in accordance with x12 EDI standards.

As a supplier of Bed Bath & Beyond your company may be required to exchange the following EDI business document types:

At any time, we can add additional Bed Bath and Beyond compliant EDI transactions at a customer’s request.

Check up our EDI Document Library

EDI Service Providers for Small Business

EDI2XML offers EDI integration with Bed Bath and Beyond to allow businesses of all sizes to become Bed Bath and Beyond EDI compliant.

Even small companies can trade with Bed Bath & Beyond using our EDI2XML Translation Service. Our services cover all:

  • EDI Mapping
  • Partner Configuration
  • Translation Processing
  • Standards Maintenance
  • XML Translation
  • EDI communication with Trading Partners, etc.

We also work with your team to easily integrate your EDI process with all major ERP systems.


Read: Convert EDI to XML: The Winning SaaS Option


Best EDI for Small Business

With our EDI converter, B2B companies have the ability to exchange essential business documents via EDI without hiring in-house EDI/IT personnel. Our EDI2XML Translation Service is the best EDI solution for B2B. This service is great for any business looking to implement EDI at an affordable price, without any headaches.

If you’re looking to complete an EDI project, Contact us today for your  FREE consultation to evaluate your EDI project.

contact-us-today-to-connect-withbed-bath-beyond-and-other-business-partners

Why use an EDI integration project?

In today’s business world, lots of decision makers are still wondering whether to plunge into EDI integration projects or to hire a couple of new employees to manually enter data received and processed by a third party EDI service bureau.

Which option is much more beneficial for their company and returns the most on their investment?

At a quick glance, hiring data entry clerks might seem appealing for the following reasons:
1) The EDI understanding is still a complex topic to understand by non-technical people;
2) The considerable initial capital investment on integration projects: professional services, EDI consultants, professional services…
3) The ongoing EDI service bureau transactional fees, connectivity fees..
4) The time and effort needed to integrate EDI with their ERP, or Business management software solution, that will be billed by IT consultants, EDI specialists and consultants.

While the above reasons are completely valid, companies stop short from researching about the evolution of the EDI world.

With EDI2XML and its “Software as a Service” model, companies are able to cut over 75% of their EDI integration projects costs and gain efficiency and accuracy within a short amount of time. Just by implementing and using EDI2XML translators, the IT consultant of an SMB, will be able to focus on building the integration between XML data files and the business management software solution in place, since XML is widely used and understood nowadays. EDI2XML is able to generate a readable XML of the EDI file, easily understood by humans and systems. As long as the IT consultant has access to the ERP database structure, he will be able to read the EDI formatted file in XML, and push to the tables, after applying all kinds of business validation. The same applies for outgoing EDI documents. As long as the IT consultant is able to generate an output XML file based on a pre-defined schema, XML2EDI engine will process that file and convert into an EDI file format.

EDI communication protocols are becoming very straightforward today; less complexity and more security. Major retailers and corporations are using AS2 or FTPs secured in order to communicate EDI documents back and forth between business partners. Even better, if a company is not able to handle EDI projects due to lack of budget or expertise, EDI2XML technology is used and empowering erpwizard which is a fully integrated business management software solution offered “as a service” (SAAS) either “on customer premises” or in “the cloud“. Not only is it a fully integrated ERP software solution, but it offers a complete EDI solution.

We have over 15 years in EDI integration in the retail, manufacturing, distribution and healthcare industries. We’ve been very active in Montreal, Canada, where our EDI consultants are experienced at the business level just as much as they are at the technical level.

Read: Free EDI to XML converter: What’s the catch?


Free EDI Demo



This post was updated to reflect current trends and information.


EDI2XML’s Subscription Cost

EDI2XML licensing is affordable since we take the time to listen to our customers’ EDI requirements and price it accordingly. We’ve also ensured that our monthly subscription plans fall within the budgets of companies of all sizes (from small to large). We offer two types of services:

EDI Web Service

Fully Managed EDI Services

EDI Web Service

EDI2XML Web Service is an HTTP EDI Web Service (REST API) that runs over the internet on EDI2XML’s own platform that takes HTTP requests to translate EDI messages into XML, and XML messages (based on EDI2XML’s proprietary format) into EDI.

You can get started quickly and easily with EDI2XML Web Service. It takes less than an hour to place a first call to the Web Service and sees the response.

EDI2XML Web Service Costs

The EDI2XML charges for using EDI HTTP/Web service calls are based on a very simple pricing system. The prize consists of [2] elements:

  1. The monthly mailbox fee is a “fixed” fee for Web Service Mailbox usage on the EDI2XML platform.
  2. During a calendar month, a “variable” fee is assessed based on the volume of data processed through EDI and XML translations.

Request EDI2XML Web Service Price List

Fully Managed EDI Services

With this SaaS option, all conversions of EDI files are done on our end, leaving you with no installation of software or hardware on your premises.

We offer EDI2XML Managed Services, a fully managed EDI service that includes translation and communication services to businesses of all sizes, in a variety of industries. We drop off and pick up all EDI documents to and from your trading partner’s server and send you email alerts when this is done.

Pricing for these options consist of a one-time affordable setup fee (only determined after a consultation call) as well as a monthly subscription fee, based on volume consumption in a given month (inbound and outgoing EDI transactions).

Don’t worry if your business has EDI documents that aren’t in the list of documents; we can always work with new documents.

We invite you to:

Download the evaluation sheet and fill in the appropriate information

– Once the Excel evaluation sheet is filled in, please feel free to email it to sales@namtek.ca

Download our EDI2XML Service Pricing Package to see the monthly plans we offer.

Within 24 hours someone will be contacting you for a free consultation to discuss your EDI requirements in more depth.

Get A Free EDI Consultation

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

How does EDI2XML work?


In simple terms, EDI2XML is a converter from EDI X12 format to XML format. The result XML format file is based on a pre-defined schema (xsd); we call it our “EDI2XML format”. Here is a very simple graphical description of the EDI2XML engine “in action”.

EDI Platform

Read: What is EDI ?

EDI2XML can work in two directions by changing a little switch when executing the command:

  • Convert incoming EDI X12 files to XML format
  • Convert outgoing XML format files to EDI format
For incoming EDI files, after a raw X12 EDI file is received using communication software and the EDI2XML engine is triggered, the following actions are executed one after the other:
– EDI2XML will verify the structure of the received file to make sure it is a valid raw EDI X12 format file
– If the raw EDI X12 file is valid in terms of structure, it will run another path to eliminate any information not considered part of EDI; for example, some headings and footers sent through the EDI VAN are automatically cleaned as it does not relate to any business information exchanged with the EDI partner
– The engine is smart enough to split a batch of incoming EDI files inside the same physical file, by envelop (ISA) and by ISA id, as a preparation for the conversion to XML, regardless of its EDI standard and revision
– Once all of the above is completed, the engine would generate for each one of the EDI files an equivalent XML formatted file.
The EDI2XML engine works a little differently when converting raw X12 files from an XML format. Once the engine is triggered with the option to convert XML to EDI X12 format, it will do the following actions:
– For each XML file found, EDI2XML will validate its structure and find out if it is well formed, to make sure it is compliant with edi2xml format and schema
– For each valid XML file, the engine will convert from XML to X12 raw EDI format
*It is important to note that the XML file should comply with a pre-defined xsd (or schema). All necessary information related to EDI versions and standards are sent within the XML file. For incoming and outgoing edi2xml formatted files, only files from the “ licensed” partners are being processed. Any EDI or XML file sent from/to an unlicensed partner will NOT be processed at all.

Read: How is EDI2XML licensed ?


Free EDI Demo



EDI Communication and VANs

What is a VAN ?


A Value Added Network (VAN) is considered the “post office” where business partners can collect and sort EDI documents coming through. As of today, a considerable amount of EDI transactions are still going through VANs, however this number is always in constant decline considering the popularity of the internet, its reduced cost as well as the level of security someone can implement with internet communication protocols. Most of the “major players” in the retail industry, have switched to a point-to-point communication of EDI files and transactions using one or many of the following secured communication protocols for a point-to-point EDI exchange:

FTP (not secured – plain text)

sFTP

Https

AS2

AS3

telnet

“bisync modem” to communicate through a value added network (VAN). This is the oldest method of secured communication.