B2BGateway to sponsor NetSuite SuiteConnect EMEA in London

B2BGateway will be sponsoring SuiteConnect EMEA which takes place on October 11^th in the Westminster Park Plaza Hotel in London.

SuiteConnect EMEA is a NetSuite conference for clients and partners located in the European, Middle East and African regions. The conference promises to give attendees insights from NetSuite’s seventeen years of delivering cloud solutions to over 30,000 organizations globally, learn how to stay current with new trends and findings from Frost & Sullivan and to network with over 800 attendees. Guests will also be able to attend dedicated industry vertical breakout sessions as well as visit the exhibition hall to meet with NetSuite partners and their solutions. The keynote address will be delivered by NetSuite CEO, Zach Nelson, who will speak on how modern global companies are thriving in the cloud economy.

EDI (Electronic Data Interchange) has become best business practice in the transfer of electronic business documents such as Purchase Orders, Invoices, Advanced Shipping Notices (ASNs), Inventory Updates, etc., between trading partners and is highly popular in market verticals such as Wholesale Distribution, Retail, Manufacturing, Healthcare, Automotive and Finance.

By integrating with B2BGateway’s cloud based EDI solution the NetSuite user can be compliant in all internationally recognized EDI standards and communication protocols such as EDIFACT, Eancom, Tradacoms, ANSI X12, oioUBL, PEPPOL, VAN, AS2, etc. The B2BGateway EDI solution is built into the NetSuite dashboard and full integration removes the need for the user to re-key data when exchanging electronic business documents with trading partners, leading to greater accuracy, increased labour efficiencies and expediting the ‘order-to-payment’ cash cycle with customers.

For further information on B2BGateway's cloud based, fully integrated EDI solutions for NetSuite please visit https://www.b2bgateway.net/edi-for-netsuite/

EDI transaction sets frequently used in Manufacturing

As EDI becomes more and more popular in many manufacturing verticals and as the thin line between manufacturers and distributors becomes more and more blurred in today’s world of e-commerce transactions, here is a list of some of the more popular EDI transaction sets used in today’s modern world of manufacturing:

§  ANSI X12 810 / EDIFACT INVOIC – Invoice – sent by manufacturers to the customer to bill for goods ordered and delivered.

§  ANSI X12 830 / EDIFACT DELFOR – Planning Schedule/Material Release – provides forecast data for upcoming orders that helps suppliers manage materials and other resources such as labor requirements. Not all 830's, however, can be used to create a Purchase Order, just manufacturers with 830's that have release capabilities.

§  ANSI X12 832 / EDIFACT PRICAT – Price/Sales Catalog – used by manufacturers to provide product information and prices to their supply chain partners in the form of a catalog.

§  ANSI X12 846 / EDIFACT INVRPT – Inventory Inquiry/Advice – used to notify trading partners of on-hand inventory. Becoming a strong requirement from Online Retail trading partners.

§  ANSI X12 850 / EDIFACT ORDERS – Purchase Order – used by manufacturer to purchase materials and/or services from a supplier.

§  ANSI X12 856 / EDIFACT DESADV – Advance Ship Notice (ASN) – communicates the contents of a shipment, sent in advance of that shipment’s arrival, which also provides information on the order, the products, the shipment arrival date and time, etc.

§  ANSI X12 862 / EDIFACT DELJIT – Shipping Schedule – provides detailed shipping requirements and may be triggered by product usage, allowing suppliers to replenish items immediately (similar to VMI), in support of Just In Time manufacturing processes.

§  ANSI X12 940 / EDIFACT INSDES – Warehouse Shipping Order – used to instruct remote Third Party Logistics Providers (3PL) or warehouses to ship orders to customers.

§  ANSI X12 943 / EDIFACT DESADV – Warehouse Stock Transfer Shipment Advice – an advance ship notice to a remote warehouse that a transfer shipment has been made from the manufacturer.

§  ANSI X12 944 / EDIFACT RECADV – Warehouse Receipt Advice – acknowledgment of receipt of a shipment (such as may be referenced in an EDI 943 transaction) at the warehouse.

§  ANSI X12 945 / EDIFACT DESADV – Warehouse Ship Advice – used by 3PL or warehouse to let manufacturer know goods have been shipped to customer.

§  ANSI X12 997 / EDIFACT CONTRL – Functional Acknowledgement – customer acknowledges receipt of EDI transaction set from manufacturer.

If your organization would like to know more about how EDI can help improve its supply chain efficiencies, please contact B2BGateway today by visiting our website www.B2BGateway.Net to get a local office number or simply email Sales@B2BGateway.Net

Webinar: EDI for Xero users

 

Webinar: EDI for Xero users. Tuesday, August 25, 12pm Sydney Time. Details and registration here http://bit.ly/1E0fyeH

 

 

B2BGateway continues global expansion with new office in China

B2BGateway, a leading cloud based EDI solution provider continues its global expansion by opening a new office in Jinan, China. The new office will further enhance B2BGateway’s EDI and automated supply chain solutions to clients and trading partners in Asia.

 

B2BGateway is a world recognized EDI solution provider since being established in Boston, USA in 1999. As EDI (Electronic Data Interchange) has become best business practice in data transfer between trading organizations, B2BGateway believes the time is right to further enhance their offerings in the Pacific and Asian regions after recently opening an office in Sydney. B2BGateway’s EDI solutions are used primarily by clients in wholesale distribution, healthcare, retail, manufacturing, automotive, government and non-profit industries.

 

B2BGateway has developed a cloud-based EDI software solution that fully integrates with most ERP or accounting software solutions including SAP, JD Edwards, NetSuite, Microsoft Dynamics, MYOB, Brightpearl, QuickBooks, Sage and Xero to name but a few. As an international company with offices throughout North America, Europe, Australia and now China, B2BGateway can support all recognized international EDI standards and communication protocols that may be required: ANSI X12, EDIFACT, Tradacoms, Eancom, Odette, XML, VAN, FTPs, AS2, etc.. By fully integrating the solution through cloud based technology, B2BGateway is able to remove the need for the client to re-key data. This, in turn, leads to greater accuracy, increased labor efficiencies and it expedites the order-to-payment cycle for the end user.

 

The new B2BGateway Chinese office will be based in Jinan, the capital of the Shandong Province and will be led by Jordan Johnson, who has previously worked with B2BGateway in their Rhode Island, USA offices.

 

For further information on how B2BGateway can help automate and improve your supply chain please visit www.B2BGateway.Net

B2BGateway CEO, Kevin Hoyle, named as a Supply and Demand Chain Executive ‘Pro to Know’ 2015

The leading supply chain publication and industry expert, Supply & Demand Chain Executive Magazine, has named B2BGateway CEO, Kevin Hoyle as a Supply Chain ‘Pro to Know’ for 2015.  

 

Supply & Demand Chain Executive Magazine recognizes Provider and Practitioner Professionals in the supply chain marketplace. The ‘Pro’s to Know’ is a listing of individuals from software firms and service providers who have helped their supply chain clients or the supply chain community at large prepare to meet the significant challenges in the year ahead.

 

Kevin Hoyle founded B2BGateway as a software development organization, Shannon Systems, LLC in Boston in 1999. B2BGateway was the name given to a cloud/SaaS based EDI solution developed by Shannon Systems in the year 2000 that became so popular and synonymous within the industry that the organization now trades as Shannon Systems, LLC dba B2BGateway.

 

Over the past 15 years EDI (Electronic Data Interchange) has become a standard business requirement in the Wholesale Distribution, Retail, Healthcare, Manufacturing, Government, Third Party Logistics (3PL) and automotive industries. B2BGateway is a natural fit for organizations in these industries that require an efficient, cost-effective, cloud based EDI solution to communicate seamlessly with their trading partners.

 

By fully integrating the EDI solution to the users Accounting Software/ ERP through cloud based technology, B2BGateway removes the need for the end user to re-key data into their system, thus greatly improving accuracy, increasing labor efficiencies and expediting the ‘order-to-payment’ cycle.

 

In addition to supporting the North American EDI standard of ANSI X12, B2BGateway also supports all international EDI standards and communication protocols such as EDIFACT, Tradacoms, oioUBL, Odette, XML, VAN, FTPs, AS2, etc..

 

“It is an honor and a privilege to be recognized as a supply chain ‘Pro to Know’ by industry peers such as Supply & Demand Chain Executive Magazine”, states Kevin Hoyle, CEO B2BGateway, “When I founded the firm in 1999 I had no idea that it would grow so rapidly and now we have clients in over 30 countries operating in 17 different time zones. 2015 is a going to be a great year for B2BGateway as we introduce many great improvements and are currently constructing a new world headquarters in Rhode Island, USA”.

Do you speak my Lingo? A users guide to EDI Jargon!

In a previous post we spoke about common EDI acronyms and what they stood for, now let’s take this one step further and highlight some commonly used EDI jargon terms and what they mean to you the end user.

EDI Standards - EDI standards are formats for EDI documents (transactions sets) that specify what information goes where within an EDI document. Usually your specific industry or trading partners will determine which EDI standard your organization must use. Examples of EDI standards include ANSI X12, EDIFACT, Tradacoms, Odette, oioUBL.

EDI transaction sets – EDI transaction sets are business documents such as purchase orders, invoices, inventory updates, shipping notices, etc.). The EDI transaction set is identified according to which EDI standard it belongs to. For example in the ANSI X12 standard, EDI transactions sets are given a unique 3 digit identifier whereas in the EDIFACT standard, the identifier is made up of groupings of letterings. In ANSI X12 a shipping notice is referred to as an 856 however in EDIFACT it is called a DESADV.

EDI Software – EDI software facilitates sending and receiving EDI transaction sets according to each trading partner’s unique business rules and requirements. The EDI transaction sets are translated and mapped into a form that a user can use, they can be either transported into a web based EDI type portal or they can be integrated directly into the users back end application such as an ERP, Accounting Package, OMS, WMS and so on. Also within the EDI software there should be a translator. The functionality of the translator is that it that converts EDI data into another format.

EDI Mapping – Converting the electronic transaction sets being sent by one system into the format required by the other system. It is the internal programing that changes the files and allows them to process through systems automatically.

GS1/UCC-128 Barcode Labels - A standard way of labelling packages that includes a scan able bar code label that contains the shipping information for the order and is placed on the outer box. Now known as GS1-128 labels, these were formerly known as UCC-128 labels.

Communication Protocol – Is the ability to connect two different computer systems and transfer the data between them. VAN, AS2 and FTP are some of the most popular methods used in EDI.

Value Added Network – Commonly referred to as a VAN is a network that hosts the exchange of EDI data. A VAN transports the data from one system to another.

EDI Standards Version – A segment that identifies a specific release of the ANSI X12 or EDIFACT standards that may be used by the trading partners. Commonly used versions include ANS! X12 version 4010, version 4030, version 5010 or EDIFACT version D96A.

Functional acknowledgement – An EDI transaction set that is sent by the receiver to the sender to let them know that the previous EDI transaction set was received. It may be referred to as an FA or 997 in ANSI X12 terms.

Trading Partner – A business with whom your organization trades or exchanges goods and/or services. For example if an organization was a wholesale distributor its trading partners may be Walmart, CVS, Amazon and a 3PL (third party logistics provider).

EDI Compliant - A client is capable of transmitting data electronic via an EDI provider and meets the standards and requirements for doing so.

For further information and on the various EDI jargon used please feel free to reach out to the B2BGateway sales team at +1 (401) 491 9595 / +353 61 708533 or email Sales@B2BGateway.Net

The essential components required for implementing and running a successful EDI operation.

 

To implement and run a successful end to end EDI communication with your trading partners, the following five components are essential:

 
EDI Translation Software: Although the concept of EDI was introduced to have a sole standard for the exchange of electronic data, overtime and across multiple market sectors, many different EDI standards have emerged such as ANSI X12 (predominantly used in North America), EDIFACT (Europe and Automotive sector), Tradacom (UK), Odette and much, much more. In fact within the same standard there are now multiple versions or upgrades, take ANSI X12 version 4010, version 4030 or version 5010 as an example. In order to deal successful and seamlessly with all these standards and versions within standards, it is essential that you have a robust EDI software translator in place.
 
Data Mapping: Data mapping is the converting of 0information from one location to another. In EDI, data mapping converts a user’s application data into the required EDI file format, and vice versa. Mapping outbound data involves establishing what information from the ERP or accounting software goes where in an EDI file. The data must be properly arranged and formatted so that it conforms to both the EDI standard required and the trading partner’s rules and regulations.
 
Communication Network: The EDI transaction sets can be transported between trading partners over numerous different methods such as a VAN (Value added Network), AS2, FTP, FTPs, etc. When trading with multiple customers, you will probably need the ability to handle all of the aforementioned communication protocols as different organizations will use different protocols.
 
Integration: Although there are some stand-alone EDI systems that may suit very small operations or seasonal companies, in order to get the best ROI out of using EDI, any organization should integrate their EDI solution with their back end ERP/Accounting Software/OMS, for example QuickBooks, NetSuite, Sage, SAP, Aptean, Microsoft Dynamics, Brightpearl, Acumatica, etc.. Integration with back end software removes the need to re-key data, thus providing further automation and reducing errors.
 
Support: It is one thing to get a good EDI system in place, but yet quite another to make sure that that system runs smoothly 24/7. Any system that does not run 24/7 or is prone to hiccups could be costing your organization new orders and therefore costing you lost income. Having good support will also keep your organization functioning seamlessly as trading partners require system upgrades or new EDI transaction sets to be introduced.
 
B2BGateway is a full service EDI provider and handles all of the vital components listed above on behalf of thousands of clients worldwide on a daily basis. If you would like to know more about B2BGateway’s full service EDI and automated EDI solutions, please call +1 401 491 9595 (North America)  / +353 61 708533 (Europe) or email Sales@B2BGateway.Net

5 Tips for Successful EDI Implementation.

To implement EDI successfully all organizations must make EDI a part of their overall business strategy with complete buy in from all departments including senior management. Needless to say, good communication between the organization and its trading partners is also an essential component in implementing a successful EDI strategy.

Here are a few tips that should help your organization develop a successful EDI implementation:

1.       Determine where your organization lies in the supply chain.

Is your organization an ‘Initiator’ or ‘Responder’. In other words are you implementing EDI on your own terms to help improve your overall business processes (‘Initiator’) or are you responding to a request from large customers who require you to become EDI compliant in order to secure your contract (‘Responder’). An ‘Initiator’ will be able to determine which rules and regulations suit their business model best, whereas a ‘Responder’ will have to abide by the standards and protocols that have been laid down by their customers or trading partners.

2.       Put in place a dedicated project team.

A dedicated project team is needed to determine your overall business objectives (e.g. remove manual data entry to reduce errors and chargebacks, comply with trading partner requirements, etc.) and to define deliverables over a set time period.

3.       Communicate with Trading Partners.

Ensure your trading partners have full commitment. Ask for a copy of your trading partners agreement and find out which EDI standards (X12, EDIFACT, Tradacoms, Odette, etc.), transaction sets (850, 810, 846, 856, 997, etc.) and communication protocols (VAN, FTP, AS2, etc.) they will require.

4.       Use first implementation as a pilot project and thereafter a stepped approach.

If you have many trading partners to communicate thru EDI, use your first implementation as a pilot project, one that you can tweak and make improvements to as you move forward. Many organizations make the mistake of trying to add too many trading partners at once. This is a huge drain on your resources and can make trading relationships go sour very fast. A stepped or phased approach may be better. Decide which trading partner relationships are a priority and implement accordingly over a phased basis.   

5.       ‘Inhouse’ or ‘Outsourced’ EDI

At this stage you need to determine if you have the internal capabilities and resources to successfully implement your own EDI department or do you outsource your EDI requirements to a 3^rd party EDI provider. A 3^rd party EDI provider will act as your own EDI department and will take away the hassle, constraints and complexities of using EDI with many trading partners. However, if your organization is very large and you have a large IT department there may be advantages to operating your EDI needs inhouse.

If you would like further information on how B2BGateway’s fully outsourced EDI solutions can help your organization achieve successful EDI implementation please call +1 (401) 491 9595 or email Sales@B2BGateway.Net 

Drop Shipping and EDI

Drop shipping is a supply chain management technique in which the retailer does not stock or take possession of the goods, but instead transfers customer orders and shipment details to either the manufacturer or wholesaler direct. It is the manufacturer or wholesaler who then ships the goods directly to the customer.

Some drop shipping retailers may have example ‘not for resale’ items in store, so that customers can inspect an item similar to those that they can purchase. Other retailers may provide only a catalogue or online listing of their products e.g. Amazon.

Drop shipping reduces inventory, warehousing, packaging, labor and shipping costs for retailers by enabling them to pass orders and ship to information along to the manufacturer or wholesaler direct. EDI can help drop ship trading partners, by not alone providing integrated order, invoicing  and shipping solutions, but by also providing the EDI 846 transaction set otherwise known as the Inventory Inquiry/Advice (INVRPT in EDIFACT). The EDI 846 is used by manufacturers and wholesalers to notify retailers and trading partners of stock and inventory levels so that the retailer doesn’t commit to sales where not enough stock is available.

For further information on how you can use B2BGateway’s EDI solutions to further automate your drop shipping requirements please call (401) 491 9595 or email Sales@B2BGateway.Net

What is an ASN?

An ASN (Advance Ship Notice) is an electronic document that provides a detailed notification of a pending delivery. It is a commonly used EDI transaction set known as the EDI 856 under the ANSI X12 standards or the DESADV (Despatch Advice) under EDIFACT standards. The purpose of an ASN is to notify the customer when shipping occurs and provide physical characteristics about the shipment so the customer can be prepared to accept delivery to their warehouse or store.  

The ASN which ties back to the original Purchase Order (PO) sent can be used to list the contents of a shipment of goods as well as additional information such as when an order will be shipped, which items are being shipped, how many of each item is being shipped and physical characteristics about the shipment such as the shipment’s weight, the number of boxes and a description of how the shipment units are packaged. An ASN also tells the customer which mode of transportation is being used for shipping and provides carrier information.

Retailers have found that having an ASN requirement as part of their overall EDI compliance structure leads to greater accuracy, greater flexibility and an overall reduction in costs.

If you would like to know more about the ASN and how B2BGateway can help you implement this EDI transaction set please call (401) 491 9595 or email Sales@B2BGateway.Net

EDI 846 - Inventory Updates

An EDI 846 transaction set (EDIFACT: INVRPT) is an inventory inquiry/advice or an electronic version of inventory update. It is used by trading partners to communicate inventory levels and whether there is enough stock of goods on hand to be sold electronically. It has become particularly important for online retailers such as Amazon to have this information at hand, particularly when drop shipping. Online retailers cannot reliably offer goods to consumers without having up to date information regarding a supplier’s inventory of goods.

 

EDI can help solve this problem through the EDI 846 transaction set and most large online retailers now insist that their suppliers are capable of sending them the EDI 846 transaction set. The EDI 846 can be sent multiple times a day or a few times a week depending on the needs of the trading partners. Typically an EDI 846 transaction set includes:

·         Inventory Amount

·         Committed Inventory

·         Quantity On Order

·         Backorder quantity

·         Inventory in transit

·         Returns

 

The EDI 846 transaction set can be used in the following ways:

(1) The seller of goods and services can provide inventory information to a prospective purchaser, with no obligation to the purchaser to acquire these goods.

(2) A representative of a seller of goods can supply inventory information to that seller

(3) For one location to supply another location with up to date inventory information

(4) An inquiry as to the availability of inventory or stock with no obligation on the seller of the goods to reserve that inventory.

For further information on how B2BGateway can help your organization set up and handle the EDI 846 inventory update with your trading partners please call our sales team today on (401) 491 9595 or email Sales@B2BGateway.Net  

Louisa Gooding is Director of Sales & Marketing at B2BGateway.Net

The differences between EDI X12 and EDIFACT

 

Question: Hi Roger, we recently got a contract to supply an organization in Germany which will require EDI. This would normally be no problem to us as we have been doing EDI with our North American trading partners for over four years; however, our new German contract requires us to use EDIFACT rather than X12 as their preferred EDI standard. Could you highlight the main differences between X12 and EDIFACT and suggest what I should do?

 

Answer:  In 1979 the American National Standards Institute (ANSI) chartered the Accredited Standards Committee (ASC) X12 to develop uniform standards for inter-industry electronic exchange of business transactions – now known commonly as Electronic Data Interchange (EDI). These transaction sets, abbreviated to X12, are the predominant EDI standards used by organizations in North America today.

In 1986, the United Nations Economic Commission for Europe (UN/ECE) approved the acronym "UN/EDIFACT," which translates to United Nations Electronic Data Interchange for Administration, Commerce and Transport. UN/EDIFACT is an international EDI standard designed to meet the needs of both government and private industry. EDIFACT is the most popular worldwide EDI data standard outside of North America.

Here is a brief list of some of the different names given to documents in the X12 and EDIFACT transactions sets. You will notice that X12 assigns numeric values to documents whereas EDIFACT lists names or abbreviations.

TRANSACTION SET/DOCUMENT	X12 SET	EDIFACT
PRODUCT/PRICING TRANSACTIONS
Price Sales Catalog	832	PRICAT
Price Authorization Acknowledgement/Status	845	ATHSTS
Specification/Technical Information	841	PRDSPE
Request For Quotation	840	REQOTE
ORDERING TRANSACTIONS
Purchase Order	850	ORDERS
Purchase Order Acknowledgement	855	ORDRSP
Purchase Order Change	860	ORDCHG
Purchase Order Change Acknowledgement	865	ORDRSP
MATERIALS MANAGEMENT TRANSACTIONS
Planning Schedule/Material Release	830	DELFOR
Shipping Schedule	862	DELJIT
Production Sequence	866	--
Ship Notice/manifest (ASN)	856	DESADV
SHIPPING/RECEIVING TRANSACTIONS
Shipment Information (Bill of Lading)	858	IFTMCS
Receiving Advice	861	RECADV
Non-conformance Information-Disposition Transaction, Cause/Correction	842	NONCON
INVENTORY MANAGEMENT TRANSACTIONS
Inventory Inquiry/Advice	846	INVRPT
Product Transfer and Resale Report	867	SLSRPT
FINANCIAL TRANSACTIONS
Invoice	810	INVOIC
Freight Invoice	859	IFTMCS
Payment order/Remittance Advice (EFT)	820	REMADV

There are many differences between an X12 and an EDIFACT document and I would recommend that if you do not have the capabilities to do EDIFACT in house that you outsource to a strong global EDI solution provider who can handle both data formats. At B2BGateway, we have offices located in North America, Europe and Pacific/Asia regions and can handle all internationally recognized EDI data formats including not only X12 and EDIFACT but many, many more (Tradacoms in the UK for example).

For further information on B2Bgateway’s international data standards capabilities please visit www.B2BGateway.Net or call (401) 491 9595. 

Roger Leyden is Director of Global Business Development at B2BGateway.