EDI GATEWAY FOR IN-HOUSE TEAMS

Your system.
Our EDI expertise.

Keep processing orders in-house. Roundhouse handles the VAN connection, document translation and trading-partner mappings—so your team can work with the files it needs, without taking on every retailer’s mapping changes.

Talk to us about EDI Gateway
Hands entering order information at a keyboard beside purchase order paperwork
Your team keeps its workflow. We support the EDI behind it.

In-house processing. Outsourced EDI support.

Roundhouse EDI Gateway connects your trading partners’ EDI documents with the files your business uses internally. We provide Value Added Network (VAN) service and manage the agreed mappings that translate incoming and outgoing information.

Your team continues to manage orders, inventory, fulfillment and invoicing in its own system. Roundhouse handles the agreed EDI exchange and translation around that workflow. This gives your team specialist support without having to maintain each retailer’s document maps itself.

HOW IT WORKS

From the retailer to your system. And back.

We receive and translate incoming documents.

A trading partner sends an order through the established EDI connection. Roundhouse receives the document and translates its information into the file format agreed with your team. We handle the configured technical acknowledgments as part of the agreed workflow.

Your team processes the order.

You import the translated file into your ERP or order-management system and continue your normal business process. Your team controls availability, order commitments, picking, packing and billing decisions. The import method and responsibility for checking successful imports are defined during setup.

We translate your outbound data.

Your team provides the agreed export with shipment, invoice or response information. Roundhouse checks the mapped data against the configured requirements, translates it into the trading partner’s EDI format and transmits it through the established connection. We agree how exceptions are reported and resolved.

A VAN connection is only part of the work.

A VAN carries electronic documents between trading partners. Mapping determines how the information in those documents fits your system’s fields. Translation applies those mappings to produce the required output.

Roundhouse brings these functions together in its Gateway service. Rather than asking your staff to manage a separate mapping for every account, we maintain the agreed trading-partner mappings on our side.

A new retailer field does not have to mean starting over.

Suppose a retailer changes the shipment reference it expects in an ASN. We review the mapping change and how that reference reaches us. If your export already contains the information, the adjustment may be handled in the map. If the information is missing, we work with your team on the necessary data handoff before testing the change.

Mapping can translate the data you provide; it cannot supply an actual carton count or shipping reference that was never captured. That is why a clear exchange with your operations team matters.

The document and the file need to agree.

The following examples show how common wholesale documents fit into a Gateway workflow. Your account requirements determine which transactions, versions and responses apply.

DocumentTypical directionInformation to agree
850 — Purchase OrderRetailer to your teamPO references, item identifiers, quantities, units and destinations in your import format.
860 — Purchase Order ChangeRetailer to your teamHow a change refers to the existing order and how your system applies it.
855 — PO AcknowledgmentYour team to retailerYour approved line responses and business decisions, where required.
856 — Advance Ship NoticeYour team to retailerActual shipment structure, carton identifiers and contents from your packing records.
810 — InvoiceYour team to retailerInvoice references, quantities and approved billing values.
997 — Functional AcknowledgmentAs required by the exchangeTechnical transaction status, kept separate from business acceptance.

Carton-label preparation and other daily processing services can be discussed alongside the Gateway scope. They should be agreed explicitly rather than assumed to be part of file translation.

Start with your system. Define the handoff.

We review your system and version, import/export specifications, sample files and trading-partner requirements. Together we establish:

  • Field mappings, product cross-references and units of measure.
  • How files are transferred, imported and exported.
  • Which team supplies approvals and shipment facts.
  • How errors, duplicate files and corrected records are handled.
  • Test scenarios, production readiness and the transition from an existing connection.

Your ERP vendor or technical team may need to support the import/export work. We confirm compatibility before implementation, including any changes required in your system. An automated ERP import is not assumed simply because a translated file can be delivered.

If you are changing providers, open orders and documents already sent need an agreed transition point. See our trading partner setup service.

Need to connect your business system?

Explore our EDI integration service for the mapping details, import/export decisions and testing that establish a working exchange.

Choose the level of outsourcing your team needs.

EDI Gateway fits teams that want to keep daily processing in their own system while outsourcing connectivity, translation and mapping maintenance.

Fully managed EDI fits suppliers that want Roundhouse to perform the agreed daily EDI work as well, including document preparation, shipment notices, labels and invoices. Explore what we do for that workflow.

If you need temporary processing support or help with a particular document, we can discuss the scope and information needed. We agree the responsibilities before taking over that work.

Whichever service you choose, accurate source data remains essential. Learn how document consistency helps reduce avoidable EDI chargebacks, or explore our trading partner connections.

Understand the connection behind your documents.

Our EDI VAN service page explains mailboxes, routing, acknowledgments and what to consider when moving an existing connection.

Need help finding the source of an EDI problem?

Our EDI consultants review your documents and workflow to identify practical next steps.

FREQUENTLY ASKED QUESTIONS

EDI Gateway, explained.

What is Roundhouse EDI Gateway?

EDI Gateway is Roundhouse’s service for businesses that process orders in-house but want help with EDI connectivity and mappings. We provide VAN service, translate incoming documents into agreed files for your system and translate outgoing data into your trading partners’ required EDI formats.

What is the difference between a VAN and EDI mapping?

A Value Added Network carries EDI documents between trading partners through mailboxes and routing. Mapping defines how information in one document format corresponds to fields in another. Roundhouse’s Gateway service combines the agreed connectivity and mapping work.

Can we keep our existing ERP system?

We begin with your existing system’s import and export specifications, version and sample files. We confirm the supported formats and test the exchange before implementation. Compatibility and any work needed in your ERP are assessed for your particular system.

Do you import the files into our ERP for us?

The standard file handoff gives your team translated files to import into its system. Any automated transfer or import arrangement must be defined and tested during setup; it is not assumed to be included for every ERP.

Who handles trading-partner mapping changes?

Roundhouse maintains the agreed trading-partner mappings. If a new requirement needs information your current export does not contain, we work with your team to identify how to supply it and test the revised exchange.

Does a 997 acknowledgment mean an order has been accepted?

No. A 997 Functional Acknowledgment concerns syntactical processing of an EDI transaction set. It is different from an 855 Purchase Order Acknowledgment and does not itself approve quantities, prices or a shipment.

How is Gateway different from fully managed EDI outsourcing?

Gateway supports a team that continues order processing in its own system while Roundhouse handles the agreed EDI connection, mapping and translation. Fully managed outsourcing also puts the agreed daily document preparation and processing with Roundhouse.

What should we provide to get started?

Tell us your trading partners, ERP or order-management system and version, required documents and current EDI arrangement. Import/export specifications, sample files and a technical contact help us define the mapping and test plan.

LET’S TALK EDI

Tell us about your system.
We’ll talk through the connection.

Bring your trading-partner list and your current workflow. We’ll help define the right level of support.

Discuss EDI Gateway
Hi, I’m Roundhouse’s AI sales assistant.

Please let me know who I’m talking to.