972-836-7750 Request a demo Talk to an expert
Talk to an expert Request a demo Call sales 972-836-7750

EDIFACT message guide · Travel and tourism

TUPREQ Travel, tourism and leisure data update request

The UN/EDIFACT interactive message a supplier sends to a global distribution system to update rates, availability, policies and general information.

Sent by
Supplier of a travel product or service
Received by
Global distribution system (GDS)
Standard
UN/EDIFACT · Interactive (I-EDI) message
X12 equivalent
No direct equivalent

What is the EDIFACT TUPREQ message?

TUPREQ is the UN/EDIFACT interactive travel, tourism and leisure data update request. The directory defines it as a message sent by a supplier of a product or service to a global distribution system (GDS) to update the receiver's database for rates, availability, policies and general information. The GDS answers with a data update response (TUPRSP).

Suppliers such as hotel chains and car rental companies keep their content in GDS databases so travel agents worldwide can book them. Updates must flow quickly, or agents will see outdated rates and availability.

How the EDIFACT TUPREQ message worksDiagram of the UN/EDIFACT TUPREQ Travel, tourism and leisure data update request message. Supplier of a travel product or service sends it to global distribution system (GDS). It usually starts the exchange. It is usually followed by TUPRSP. Inside the UIB and UIH envelopes, the directory D.21A requires, in the start of message: MSD (Message action details), ORG (Originator of request details) and NUN (Number of units). 5 conditional segment groups are listed by their trigger segment.How the EDIFACT TUPREQ message worksTravel, tourism and leisure data update request: who sends it, where it fits and what the directory marksmandatory1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeTUPREQSENDERSupplier of a travelproduct or serviceRECEIVERGlobal distributionsystem (GDS)USUALLY FOLLOWED BYTUPRSPTravel, tourism andleisure data updateresponse2 WHAT DIRECTORY D.21A REQUIRESInteractive interchangeUIB … UIZMessage TUPREQUIH … UITSTART OF MESSAGEMSDMessage action detailsORGOriginator of request detailsNUNNumber of unitsBODY AND SEGMENT GROUPS+ 5 conditional groups, starting with:TVLMAPITDALSTIFBlue box: mandatory segment group. Conditional groups are listed by the trigger segment that starts them; a group is sent only when its data applies.Conditional segments outside groups are not drawn.Structure: mandatory segments and groups in the UN/EDIFACT directory D.21A listing for TUPREQ. Your trading partner's implementation guide adds itsown requirements.
How the EDIFACT TUPREQ message worksDiagram of the UN/EDIFACT TUPREQ Travel, tourism and leisure data update request message. Supplier of a travel product or service sends it to global distribution system (GDS). It usually starts the exchange. It is usually followed by TUPRSP. Inside the UIB and UIH envelopes, the directory D.21A requires, in the start of message: MSD (Message action details), ORG (Originator of request details) and NUN (Number of units). 5 conditional segment groups are listed by their trigger segment.How the EDIFACT TUPREQmessage worksTravel, tourism and leisure data update request:who sends it, where it fits and what thedirectory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeTUPREQSENDERSupplier of atravel product orserviceRECEIVERGlobaldistributionsystem (GDS)USUALLY FOLLOWED BYTUPRSPTravel, tourism and leisure dataupdate response2 WHAT DIRECTORY D.21A REQUIRESInteractive interchange (UIB … UIZ)Message TUPREQ (UIH … UIT)START OF MESSAGEMSDMessage action detailsORGOriginator of request detailsNUNNumber of unitsBODY AND SEGMENT GROUPS+ 5 conditional groups, starting with:TVLMAPITDALSTIFBlue box: mandatory segment group. Conditionalgroups are listed by the trigger segment thatstarts them; a group is sent only when its dataapplies. Conditional segments outside groups arenot drawn.Structure: mandatory segments and groups in theUN/EDIFACT directory D.21A listing for TUPREQ.Your trading partner's implementation guide adds itsown requirements.

How to read this diagram: the top row shows who sends TUPREQ, to whom, and which messages usually come before and after it. The lower part shows what the directory D.21A itself requires: the envelopes around TUPREQ and the segments and segment groups it marks mandatory. Conditional groups are listed by their trigger segment rather than drawn in full. This is the directory's minimum, not a trading partner's requirement: a message implementation guide usually makes some conditional groups mandatory, restricts the codes and may use an older directory.

Expand diagram Download SVG

When it is used

  • Updating rates in a global distribution system
  • Closing or opening availability
  • Updating policies and descriptive content

Where it fits in the message flow

This message TUPREQ Travel, tourism and leisure data update request
Usually followed by TUPRSP Travel, tourism and leisure data update response

Structure

Mandatory segments in TUPREQ (directory D.21A)

In UN/EDIFACT directory D.21A, the TUPREQ message has 150 segment positions arranged in 42 segment groups. These are the segments and segment groups marked mandatory at message level, in order; a mandatory group is shown with the segment that starts it. Segments inside conditional groups are needed only when the group is used. This is the directory’s requirement, not your trading partner’s: each partner’s message implementation guide names the directory it uses, often an older one such as D.96A or D.01B where the structure can differ, makes some conditional segments mandatory and restricts the codes. This structure comes from one published copy of the directory and has not been independently verified: confirm it before you build a map.

  • UIH
  • MSD
  • ORG
  • NUN
  • UIT

Practical example

TUPREQ in practice

A hotel chain raises its rates for a trade fair week. Its central reservation system sends the GDS a TUPREQ updating the rates for the affected dates and closing availability for one sold-out property. The GDS applies the changes and confirms with a TUPRSP.

Implementation

Implementation considerations for TUPREQ

  • Keep updates in step with the supplier's own inventory.
  • Process confirmations and errors for every update.
  • Prioritize availability changes, which affect bookings immediately.
  • Agree update volumes and rate limits with the GDS.

How ECOM helps

Automate TUPREQ with ECOM

Industry

Hospitality

Procurement, invoicing and supplier integration for hotels, restaurant groups and foodservice suppliers.

Solution

Batch and Real-Time Integration

Scheduled batch processing and real-time, API-driven integration on one platform.

Solution

API Integration

Connect partner and application APIs to your systems and bridge them with EDI processes.

Compare X12 and EDIFACT, or see answers to general questions in the EDI FAQ.

Related messages

Related travel and tourism messages

All 16 travel and tourism messages

Need help with TUPREQ?

ECOM maps, tests and monitors EDIFACT messages for your trading partners and integrates them with your ERP.

Request a Demo Contact us