Target Architecture

Target view

flowchart LR
    U[Customer]
    W[Webflow experience]
    I[Backend integration service]
    N[Controlled network boundary]
    J[Holiday supplier API]

    U -->|search criteria| W
    W -->|normalised request| I
    I -->|supplier request| N
    N --> J
    J --> N
    N -->|supplier response| I
    I -->|normalised holiday results| W
    W --> U

Responsibilities

Webflow experience

Owns:

• search form presentation;
• customer interactions;
• result-card rendering;
• responsive behaviour;
• onward navigation.

It does not own supplier credentials or SOAP/XML processing.

Backend integration service

Owns:

• request validation;
• supplier authentication/session concerns;
• supplier-specific request construction;
• response parsing and transformation;
• mapping to the website result contract;
• error classification;
• operational diagnostics.

Controlled network boundary

Provides the network path required to reach the external service from an approved integration environment.

Holiday supplier API

Remains authoritative for:

• live availability;
• live price;
• supplier-specific holiday result data.

Internal contract

The website-facing response should be shaped around the customer journey rather than leaking the supplier schema.

That keeps the external contract behind an integration boundary and reduces the impact of supplier changes on Webflow.