<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>OnArrival Field Notes</title>
    <link>https://www.onarrival.com/blog</link>
    <description>Ideas for building useful, resilient travel products.</description>
    <language>en</language>
    <atom:link href="https://www.onarrival.com/pages/blog/rss.xml" rel="self" type="application/rss+xml" />
    <lastBuildDate>Mon, 03 Aug 2026 00:00:00 GMT</lastBuildDate>
    <generator>OnArrival file CMS</generator>
    <item>
      <title>Build vs. buy: where should your travel infrastructure end?</title>
      <link>https://www.onarrival.com/blog/build-vs-buy-travel-infrastructure</link>
      <guid isPermaLink="true">https://www.onarrival.com/blog/build-vs-buy-travel-infrastructure</guid>
      <description>A practical build-versus-buy framework for travel products, covering supply, booking, servicing, payments, ownership, and the right architecture boundary.</description>
      <category>Business</category>
    </item>
    <item>
      <title>Embedded travel for fintechs: turn a transaction into a relationship</title>
      <link>https://www.onarrival.com/blog/embedded-travel-for-fintechs</link>
      <guid isPermaLink="true">https://www.onarrival.com/blog/embedded-travel-for-fintechs</guid>
      <description>How fintechs can design embedded travel around payments, rewards, trust and post-booking service without turning travel operations into the core business.</description>
      <category>Product</category>
    </item>
    <item>
      <title>Give the travel agent tools, not open-ended authority</title>
      <link>https://www.onarrival.com/blog/agentic-travel-mcp-guardrails</link>
      <guid isPermaLink="true">https://www.onarrival.com/blog/agentic-travel-mcp-guardrails</guid>
      <description>A practical guardrail model for AI travel agents: typed MCP tools, scoped credentials, spend limits, idempotency and audit traces. See how agents book safely.</description>
      <category>AI and agents</category>
    </item>
    <item>
      <title>NDC, GDS or LCC direct? The wrong answer is choosing one</title>
      <link>https://www.onarrival.com/blog/ndc-gds-lcc-comparison</link>
      <guid isPermaLink="true">https://www.onarrival.com/blog/ndc-gds-lcc-comparison</guid>
      <description>Compare NDC, GDS and low-cost carrier direct connections across content, coverage, servicing and integration complexity, and how to choose your mix.</description>
      <category>Comparison</category>
    </item>
    <item>
      <title>The travel API is not the architecture</title>
      <link>https://www.onarrival.com/blog/travel-api-architecture-control-plane</link>
      <guid isPermaLink="true">https://www.onarrival.com/blog/travel-api-architecture-control-plane</guid>
      <description>A practical architecture for normalising travel supply, maintaining one order lifecycle and servicing bookings after checkout. Where the boundary belongs.</description>
      <category>Technical architecture</category>
    </item>
    <item>
      <title>Checkout is the midpoint: designing the travel order lifecycle</title>
      <link>https://www.onarrival.com/blog/travel-order-lifecycle</link>
      <guid isPermaLink="true">https://www.onarrival.com/blog/travel-order-lifecycle</guid>
      <description>Design a canonical travel order across offer recheck, payment, confirmation, changes, disruptions and refunds, with state transitions you can audit.</description>
      <category>Product engineering</category>
    </item>
    <item>
      <title>How we solved room mapping</title>
      <link>https://www.onarrival.com/blog/how-we-solved-room-mapping</link>
      <guid isPermaLink="true">https://www.onarrival.com/blog/how-we-solved-room-mapping</guid>
      <description>Inside OnArrival&apos;s mapping pipeline: normalisation, geohash and trigram blocking, calibrated matching, human review queues and drift control.</description>
      <category>Data and supply</category>
      <pubDate>Mon, 03 Aug 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>One booking, many money movements</title>
      <link>https://www.onarrival.com/blog/unified-payments-refunds-reconciliation</link>
      <guid isPermaLink="true">https://www.onarrival.com/blog/unified-payments-refunds-reconciliation</guid>
      <description>A technical and operational guide to unifying travel collection, supplier settlement, refunds, FX, ledger design, and booking-level reconciliation.</description>
      <category>Technical</category>
    </item>
    <item>
      <title>One hotel, five names: the quiet craft of hotel mapping</title>
      <link>https://www.onarrival.com/blog/hotel-mapping-deduplication</link>
      <guid isPermaLink="true">https://www.onarrival.com/blog/hotel-mapping-deduplication</guid>
      <description>How to resolve duplicate hotel listings, map rooms, merge content and rank supplier rates without erasing meaningful differences. A practical guide.</description>
      <category>Data and supply</category>
    </item>
    <item>
      <title>Post-booking is the trust product</title>
      <link>https://www.onarrival.com/blog/post-booking-is-the-trust-product</link>
      <guid isPermaLink="true">https://www.onarrival.com/blog/post-booking-is-the-trust-product</guid>
      <description>A practical guide to designing travel post-booking service around order state, disruptions, self-service, support, refunds, and customer trust.</description>
      <category>Operations</category>
    </item>
    <item>
      <title>The cart is the hardest problem in travel</title>
      <link>https://www.onarrival.com/blog/the-travel-cart-problem</link>
      <guid isPermaLink="true">https://www.onarrival.com/blog/the-travel-cart-problem</guid>
      <description>Why a multi-supplier travel cart is a distributed-systems problem: hold TTLs, price re-validation races, saga commits, idempotency and currency rounding.</description>
      <category>Technical architecture</category>
      <pubDate>Mon, 03 Aug 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>When should you add travel as a product?</title>
      <link>https://www.onarrival.com/blog/when-to-add-travel-as-a-product</link>
      <guid isPermaLink="true">https://www.onarrival.com/blog/when-to-add-travel-as-a-product</guid>
      <description>A practical readiness framework for deciding whether, why, and how to add travel to a fintech, loyalty program, marketplace, or digital product.</description>
      <category>Strategy</category>
    </item>
    <item>
      <title>Why NDC will not solve your immediate problems</title>
      <link>https://www.onarrival.com/blog/why-ndc-wont-solve-your-immediate-problems</link>
      <guid isPermaLink="true">https://www.onarrival.com/blog/why-ndc-wont-solve-your-immediate-problems</guid>
      <description>A technical look at NDC certification levels, schema drift, servicing gaps and interline limits, and why supply belongs behind one offer abstraction.</description>
      <category>Technical</category>
      <pubDate>Mon, 03 Aug 2026 00:00:00 GMT</pubDate>
    </item>
  </channel>
</rss>
