Hospitality integration

TUI Group EDI integration

How EDI and API integration with TUI Group typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with TUI Group.

At a glance

TUI Group integration, in three pictures

The industry, the document flow and the outcome for your team. Illustrations only: they show typical practice, not a specific TUI Group program or a customer relationship.

Illustration of a hotel building with a palm tree, representing the hospitality industry that TUI Group operates in.
Industry. Hospitality: where TUI Group operates.
Workflow diagram: your ERP and warehouse systems exchange documents with TUI Group through ECOM. You send 855, 856, 810; you receive 850, 820; 997 acknowledgments go both ways. Your systems ERP · warehouse · finance ECOM integration map · validate · connect · monitor TUI Group 855 856 810 855 856 810 850 820 850 820 997 both ways
Workflow. Documents in each direction. Orange: you send. Blue: you receive. Typical, not confirmed.
Comparison diagram: without integration, documents are re-keyed, files are emailed and rejections are found late; with ECOM, documents are mapped to your ERP, validated and monitored, and exceptions are visible early. Without integration Orders re-keyed by hand Files emailed or uploaded Rejections found late With ECOM Documents mapped to your ERP Every file validated and monitored Exceptions visible early
Outcome. From manual handling to a monitored flow. No figures: results depend on your setup.

Talk to an EDI/API Expert about TUI Group

Tell us which documents you exchange with TUI Group, which ERP you run and when you need to be live. A specialist will outline the connection, mapping and testing plan. This page is a guide based on typical practice; it does not mean ECOM works with TUI Group.

  • Review of TUI Group's requirements with you, once you have them
  • EDI and API integration with your ERP and warehouse systems
  • Monitoring and managed service after go-live, if you want it

Prefer to call? Sales 972-836-7750 or email sales@ecom-specialist.com.

Takes about 30 seconds. Phone and note are optional.

Your request is about

Trading partner
TUI Group

When should we talk?

Times are in your time zone. We use this to schedule the conversation.

We use your details only to respond to your request. See our privacy notice. Prefer to talk? Call Sales at 972-836-7750.

Integration and onboarding

How TUI Group integration fits your systems

Your systemsERP, WMS and accounting
ECOMMapping, validation, connectivity and monitoringAS2 or SFTP · EDI network (VAN) · API or web portal
TUI GroupIts program, documents and requirements
  1. ConfirmConfirm your TUI Group program, role and the documents it requires.
  2. MapMap each document to your ERP fields and business rules.
  3. ConnectConfigure the connection and security the program needs.
  4. TestTest against the applicable specifications and acknowledgments.
  5. Go liveGo live with monitoring, alerts and exception handling.
Typical implementation path. Exact requirements are confirmed against the applicable specifications during onboarding.

Overview

Understanding TUI Group integration

Who this is for: Suppliers of provisions, supplies, equipment and services that serve TUI Group, and their order and finance teams.

Scope: This guide describes typical practice for this kind of trading relationship; TUI Group's own program details are confirmed during onboarding.

TUI Group is a travel and tourism company. ECOM's directory lists it under travel and tourism. Suppliers to travel companies, cruise lines and online travel platforms typically deal with purchase orders for goods and services, provisioning, and invoice and payment processes.

Teams that connect to a travel, cruise or leisure company usually find that onboarding takes longer than mapping, because the rules have to be confirmed first. TUI Group's own EDI or API specification is not part of this guide and no TUI Group document was read: treat what follows as typical practice for a travel, cruise or leisure company, and confirm the documents, X12 version, delivery method and testing steps with TUI Group.

ECOM maps the documents to your ERP and warehouse systems, tests them with the trading partner, monitors every file after go-live and handles partner changes, as software, as a managed service or both.

Business scenarios

Where TUI Group integration gets complicated

Typical requirements—confirm with your trading partner.

Port and venue delivery

Delivery points differ by port, venue or property.

How ECOM helps: ECOM connects shipment and status documents to your ERP, WMS or TMS and shows where each one stands, so late or missing messages are seen early.

What you gain: Teams see current status, and fewer shipments are held up by missing documents.

Hard departure dates

Travel and cruise provisioning runs to fixed departure and opening dates, with delivery to ports and venues.

How ECOM helps: ECOM runs onboarding as a project: we confirm TUI Group's requirements with you, map the documents, build the connection and run test cycles until TUI Group accepts them.

What you gain: A shorter, more predictable path to the first accepted live document.

Platform and partner billing

Billing between platforms and suppliers follows contract terms.

How ECOM helps: ECOM maps invoice, payment and remittance data to your ERP or finance system and matches each document to the order or shipment it relates to, with differences listed for review.

What you gain: Faster reconciliation and cash application, and a clear trail for audit.

Menu or brand-standard changes

Program changes alter items and specifications.

How ECOM helps: ECOM carries each change through to the acknowledgment, shipment and invoice so every document reflects the latest version, and flags changes TUI Group has not acknowledged.

What you gain: Shipments and invoices stay in step with the order after changes.

Workflows

Typical TUI Group business workflows

Typical requirements—confirm with your trading partner. Typical flows in this industry, not TUI Group's published process.

Order to cash

  1. 1Receive 850 purchase order
  2. 2Send 855 acknowledgment
  3. 3Ship and send 856
  4. 4Send 810 invoice

Payment advice

  1. 1Send 810 invoice
  2. 2Receive 820 payment advice
  3. 3Apply cash
  4. 4Reconcile

Documents and APIs

TUI Group documents by program

General guidance. We could not verify TUI Group's EDI requirements from a published source, so these are documents commonly exchanged in this industry, not TUI Group's confirmed requirements. Confirm the list, versions and programs with TUI Group.

DocumentNameDirectionProgramStatusPurpose
850 Purchase Order From TUI Group Not stated General guidance Typically carries the order: items, quantities, prices, ship-to locations and requested dates.
855 Purchase Order Acknowledgment To TUI Group Not stated General guidance Typically confirms an order, or reports changes to quantities, prices or dates.
856 Ship Notice/Manifest To TUI Group Not stated General guidance Typically tells the receiver what is on each shipment, often with carton or pallet label details.
810 Invoice To TUI Group Not stated General guidance Typically bills for what shipped, matched against the order.
820 Payment Order/Remittance Advice From TUI Group Not stated General guidance Typically carries payment and the remittance detail that ties it to invoices.
997 Functional Acknowledgment Both directions Not stated General guidance Typically confirms that each file was received and could be read.

Connectivity

How companies connect

  • AS2 or SFTP

    Many companies exchange EDI files directly over AS2 or SFTP.

    General guidance

  • EDI network (VAN)

    Many suppliers connect through a value-added network that delivers files to and from the partner and keeps an audit trail.

    General guidance

  • API or web portal

    Some programs use REST or SOAP APIs, a supplier portal or a cloud EDI service for some documents. A login is usually required for portals.

    General guidance

Challenges

Common integration challenges

  • Hard deadlines

    Departure and opening dates leave no slack.

  • Delivery points

    Ship-to locations vary. Details depend on your agreement with TUI Group.

  • Documentation

    Delivery documents must match the order.

  • Invoice matching

    Invoices must tie to the order. Requirements vary by program.

  • Program-specific details

    The documents, identifiers, versions and test steps for your program are set by TUI Group. ECOM works from them during mapping and testing.

Automation options for TUI Group suppliers

Four ways to automate. One foundation.

ECOM helps you automate them, meet TUI Group's labeling and ship notice requirements, and see what needs action. TUI Group sets its program's rules; ECOM confirms which options fit yours.

PRISM Supply Chain Automation Foundation

One platform beneath every option. Use one, or combine them for different partners and documents.

Compliance and actionable visibility

Connect order processing, shipping documentation, trading partner requirements, and performance monitoring through one coordinated workflow. These capabilities help teams improve shipment accuracy, reduce manual work, address compliance risks, and respond to exceptions before they affect customers.

Discuss Your Trading Partner Requirements

Connect TUI Group documents to your ERP

ECOM connects the documents you exchange with TUI Group to your ERP and warehouse systems, so orders post without re-keying and ship notices and invoices come from the data you already hold.

Industry

Hospitality

See how ECOM supports hospitality suppliers and operators.

Solution

Procure-to-Pay Automation

Automate purchase orders, receipts and invoices on the buyer side.

Service

Fully Managed EDI

Have ECOM run your EDI connections, monitoring and partner changes.

General EDI flow

How EDI with TUI Group typically works

The documents, their order and the timing are TUI Group's to set; this is the general sequence most programs of this kind follow.

  1. 850 Purchase Order

    From TUI Group to you

    Typically carries the order: items, quantities, prices, ship-to locations and requested dates.

  2. 855 Purchase Order Acknowledgment

    From you to TUI Group

    Typically confirms an order, or reports changes to quantities, prices or dates.

  3. 856 Ship Notice/Manifest

    From you to TUI Group

    Typically tells the receiver what is on each shipment, often with carton or pallet label details.

  4. 810 Invoice

    From you to TUI Group

    Typically bills for what shipped, matched against the order.

  5. 820 Payment Order/Remittance Advice

    From TUI Group to you

    Typically carries payment and the remittance detail that ties it to invoices.

  6. 997 Functional Acknowledgment

    Both directions

    Typically confirms that each file was received and could be read.

Need help with the specification?

Tell ECOM which program you are in and what the partner has given you. We help you read it, confirm the applicable requirements, map them to your systems and test against them. Do not send passwords or EDI identifiers with your request.

Next step

Get help with your TUI Group program

Each request goes to an ECOM EDI specialist with TUI Group's name attached, so the reply starts from your program.

  • Review TUI Group's requirements

    Send us TUI Group's guide or your program details; we explain the documents, rules and options for meeting them.

    Request a requirements review
  • Connect TUI Group to your ERP

    Orders in, ship notices and invoices out, from the ERP and warehouse systems you already run.

    Discuss ERP integration
  • Testing and certification

    Build, test and certify each TUI Group document, then go live with monitoring from the first file.

    Plan testing and certification
  • Shipping labels and ASNs

    Labels and ship notices that match TUI Group's rules, to help avoid receiving problems and compliance deductions.

    Review shipping compliance

TUI Group integration FAQs

Does TUI Group use EDI with suppliers?

Travel and leisure companies buy through procurement systems that may accept EDI or portal orders. This page does not describe TUI Group's program.

Can ECOM help with provisioning orders?

ECOM maps orders, ship notices and invoices between a customer's format and your ERP and monitors each file.

Which EDI documents are typical for a travel, cruise or leisure company?

Typical documents are 850, 855, 856, 810, 820, 997. That is general practice, not TUI Group's published list.

How does onboarding with TUI Group usually work?

Typically you get the specification from the trading partner, agree the connection, map to your systems, test until the partner accepts the documents, then go live with monitoring. Timing depends on TUI Group's requirements, test cycles and your ERP.

Does this guide mean TUI Group endorses ECOM?

No. This is an independent integration guide. It does not indicate an endorsement, partnership or approval by TUI Group.

Sources and accuracy

This guide summarizes publicly available information as of November 2026. TUI Group sets its own requirements and can change them at any time; your TUI Group implementation guide, supplier portal or account contact is the authoritative source for your program.

  • ASC X12: transaction set reference (standards body) Standards reference
  • TUI Group: company description Background, not checked against a company source The one-sentence description of TUI Group comes from general public knowledge and was not checked against TUI Group's own website for this page.
  • TUI Group: no company document read Background, not checked against a company source No TUI Group supplier, customer or integration document was read for this page. Everything shown is typical practice for this type of company.

Request TUI Group integration assistance

Tell us about your TUI Group program, documents and ERP. We will outline the connection, mapping and testing plan.