ПОДПИСЫВАЙТЕСЬ НА НАШ ТЕЛЕГРАМ-КАНАЛ @nemo_travel_official

Order Export

Материал из Центр поддержки системы бронировании
Перейти к навигации Перейти к поиску

Order export is export of order data or orders for various components of the Websky system.

Description

The module allows the external system to obtain order data for further processing.

Export process

The process of order export is schematically presented on the block diagram.

Sofi Nemo export.png

Attention!

  • Order in SOFI format will be exported during synchronization only if there are changes in the order.
  • Order in SOFI format will be exported during cancellation only if the order contains cancelled services.

Settings

Setting up the order uploading process for airline tickets

Order export settings are available via System settings → Integration → Export of bookings.

  • Nemo Backoffice — the possibility to export orders in JSON format, which provides more complete and up-to-date data amount, uses international standards of data format, and is an improved version of data export protocol in Websky format.
  • Address for sending notifications about order changes — if specified, a GET-request is sent to this address when changes are received during the actualization. (Example http://127.0.0.1/?booking_id=ORDER_ID&nemo_id=NEMO_CONNECT_ORDER_ID&locator=LOCATOR). The value format supports variables LOCATOR, ORDER_ID, NEMO_CONNECT_ORDER_ID - (LOCATOR - service identifier in service provider's system, ORDER_ID - Websky order identifier, NEMO_CONNECT_ORDER_ID - order identifier in NEMO Connect).
  • Url of third party script for XML notifications in Websky format — URL to which the data will be uploaded.
  • Url of third party script for XML notifications in SOFI format — URL to which the data will be uploaded.

Websky sends upload files to the http address specified in this field via a POST request (see https://ru.wikipedia.org/wiki/POST_(HTTP) ). The script for processing the received data must be written on the client's side. The script task is to accept the data and process them correctly. All data which can be received through a browser, also are possible to receive via alternative software means (automating export process). It is recommended to use CURL library (see https://ru.wikipedia.org/wiki/CURL). Websky staff does not provide ready-made sample scripts.
If a subagent has a different URL script for export than the root agency URL, the export by order of this subagent will be directed to both addresses. The main agent receives information on all orders of all subagents, the subagent receives the export data only of its orders.

  • Nemo Backoffice export url — URL to which the data will be uploaded.
  • Website code in SOFI — agency ID on the SOFI side. The code is required to connect the agency in SOFI and Websky. If the agency is created in SOFI, its code is specified in this field. Then SOFI will identify orders from specified agency in SOFI unloading.
  • Resending in case of failure — The setting allows you to retry exporting the order at a certain time interval (maximum 3 attempts).
  • A list of addresses for notifications (separated by commas) — This setting allows you to specify one or more email addresses to which a problem order notification will be sent in case all export attempts fail.
  • Export after payment — The setting allows you to additionally export orders after an order payment event.
  • Export order access code — The setting enables you to display the export access code.
  • Send a notification on the need to set a validator code in requisites — The setting allows you to automatically send a notification when an order is exported to SOFI without a validator code.
  • Time zone for dates — The setting allows you to change the time zone in SOFI export.
    "Time zone for dates" setting
    • Use time zone from system settings, through which the time zone specified in "System Settings" will be used.
    • Use time zone from requisites — The time zone is raised individually from each set of GDS connection requisites.
    • Select other time zone enables you to select the time zone independently of other settings.

Order export formats

The system supports order export in formats Websky, SOFI и JSON. It is recommended to use JSON export functionality.

Components supporting order export

Air Tickets Hotels Rail
Websky format + − +
SOFI format + − −
JSON format + + +

Events supporting order export

Авиабилеты Booking Payment* Synchronization** Ticketing Voiding Cancellation*** Exchange/Refund****
Websky format + + + + + + +
SOFI format − − + + + + +
JSON format + + + + + + +
Отели Booking Payment* Synchronization** Ticketing Voiding Cancellation
JSON format + + + − Voiding unavailable +
ЖД Booking Payment Synchronization** Ticketing Voiding Cancellation
Websky format + + + + + +
JSON format + + + + + +

*  A Websky order will be uploaded when paid only if the «Export after payment»' setting is enabled в разделе «Orders» → «Order export».
 ** The order will be exported during synchronization only if there are changes in the order.
***  An order in SOFI format will be exported upon cancellation only if the order contains the cancelled ancillary services.
****  The order will be exported upon exchange or refund when the work with claim is finished (if PNR import is skipped).

Order export statuses

Order export status codes correspond to HTTP status codes. In fact, the last HTTP status code received when uploading data to the address specified in the upload settings is specified. The codes refer to the server to which the orders are exported.

Code Description
0 Unknown response. Export address not available.
200 OK - successful request.
301 The requested document was completely moved to the new URI specified in the Location field of the header.
403 The server has recognized the request, but it refuses to execute it because of the access restrictions to the specified resource for the client.
404 The server has recognized the request but did not find the required resource by the specified URI.
422 Unprocessable Entity - the server has successfully accepted the request, can work with the specified type of data, the XML document in the request body has the correct syntax, but there is some logical error that prevents operation on the resource.
500 Any internal server error.

Order export for the Avia Tickets component

For the «Avia Tickets» component, orders in Websky and/or SOFI formats are available for export (when «SOFI order export» module is enabled).

развернуть

Websky format

развернуть

Websky format for composite bookings (MultiOW)

развернуть

SOFI format

развернуть

JSON format

Order export for "Hotels" component

For the «Hotels» component, order export is available in Websky and/or JSON formats.

развернуть

JSON format

Order export for "Rail" component

For «Rai» component, order export is available in Websky and/or JSON formats.

развернуть

Websky format

развернуть

JSON format

Package order export in Websky format

Order export service allows you to export the necessary samples by orders in XML, XLS(X) format. For example, you can select orders by date of booking and get information on them in the desired format. Export in XLS(X) format will upload a maximum of 1000 orders at a time. If more orders need to be exported (to get complete statistics on all orders), you need to export orders for successive periods.

When you export order data in XLS(X) format, price parameters will be converted into agency currency at the rates recorded at the time of payment for a particular order.

The export panel is always available for managers and experts.

Exporting orders under an authorized user (in a personal account)

Filters for package export orders in personal account

.

The "Show Export Panel" pseudo link opens a form that allows you to export your orders to an XML, XLS or XLSX file format.

The orders of the selected user/company and their subagents/users are uploaded based on the applied filter parameters.

The order data export request will be displayed in the log system with an XML file containing the upload data.

To export postponed orders in XLS(X) format, the "Booking status" parameter must be set to "Postponed" in order filters.

At the moment the limit for the number of single orders uploaded is set to 1000. In case it is necessary to upload more orders (to get complete statistics on all orders), it is possible to do it by uploading orders for certain periods.

Package Export parameters

Parameter XLS - export свернутьXML - export
Ticket number n/a Passengers->Passenger->Tickets->Ticket->Num
Route service_summary OrderInfo
Ticketing date ticketing_date Common->TicketingDateTime
Departure date date_begin OrderInfo->Info->StartDate,StartTime
Fare in the currency of the site (for each ticket) only total for all passengers n/a
Taxes in the currency of the site (for each ticket) только total for all passengers n/a
Fare in the currency of ticketing (for each ticket) n/a n/a
passenger second name (for each ticket) n/a Passengers->Passenger->lastname

Order re-export

If the order export was not successful, the system provides the possibility to export it again. To do this, the manager of the agency needs to go to the page of the problem order in the "Service Information" section, where the link "Re-export order", after clicking on which the order will be re-exported.

Moreover, if the setting of export both Websky and Sophie in the System Settings → Integration → Export of bookings section is enabled, the order will be re-exported in both Websky and SOFI formats.

It is also possible to re-export orders from your Personal Account. To do this, in the "Orders" section, you need to click on the link "Re-export order" for the desired order in the column "Actions".


See also

Источник — https://support.nemo.travel/index.php?title=Order_Export&oldid=17061