← Blog
IAGTO25 April 2026 · 4 min read

The IAGTO standard and why we build for it

IAGTO isn't just an agency association. It's an operational standard defining how hotels, courses, and agencies talk in golf travel. We built GolfStay to speak it natively.

Luis Borho · Founder

IAGTO in one line

International Association of Golf Tour Operators. 700+ agencies, 3,000+ associated hotels and courses, 70+ countries. Their annual event is where the entire sector's B2B contracts get signed.


Why it matters to us

When an IAGTO agency works with a hotel and a course, it does so under tacit operational expectations that aren't written anywhere but everyone respects:

  • Confidential net rate between agency and provider, not visible to the end customer.
  • Commission calculated on rack rate, not on net rate.
  • Provider payment on BB30 or BB60 terms depending on contract (Bill Back 30/60 days).
  • Asymmetric cancellation policies: the end customer sees the hotel's, the agency sees the provider's with its specific penalties.
  • Physical or digital vouchers the guest presents at the course.
  • Monthly statements between agency and provider.

Build a B2B golf travel platform without understanding this language and you'll offer the agency a generic retail experience and lose. Same reason agencies don't use Booking or Expedia for their ops: those don't speak IAGTO.


What GolfStay implements natively

  • Rate per agency · provider · product triple, with three modes: flat amount, percentage discount, season override.
  • Configurable commission: on rack, on net, fixed % or volume table.
  • Asymmetric cancellation: the policy shown to the customer differs from the agency-provider operational one.
  • PDF voucher per booking with QR and the course's bookingDetailsId, scannable at the pro shop.
  • Automatic monthly statement with all the agency's bookings + ERP reconciliation.

What it doesn't do yet

GolfStay doesn't natively implement BB30/BB60 — we use immediate Stripe + post-event reconciliation. When a traditional agency needs native BB60, we'll need to build a credit terms module. Most likely: post-Q4 2026.

We also don't talk to legacy tour operator systems (TUI's reservation engine, Thomas Cook legacy connections). If you work with wholesale agencies dragging that stack, let's discuss it in Málaga.


The commitment

If you come from an IAGTO agency and you'll be in Málaga, we want to sit down with you. What we need to know: which three things in your current ops eat the most time, and whether we can close one of them before Q4 2026.