Operating gap
Tour quotations become risky when guest requirements, supplier costs, vehicle assumptions, tickets, VAT, margin and client terms live in separate calculations.
Ahmed Mahmoud
Tour quotations for Amsterdam and Abu Dhabi.
The problem: Tour quotations become risky when guest requirements, supplier costs, vehicle assumptions, tickets, VAT, margin and client terms live in separate calculations.
Who it is for: DMC sales teams, travel consultants and quotation reviewers.
Scope: Amsterdam and Abu Dhabi quotation workflows
My contribution: I structured the quotation journey, commercial calculations, internal controls and separation between cost review and client output.


Tour quotations become risky when guest requirements, supplier costs, vehicle assumptions, tickets, VAT, margin and client terms live in separate calculations.
I structured the quotation journey, commercial calculations, internal controls and separation between cost review and client output.
A controlled quotation workflow that separates the internal cost view from client output while checking break-even logic, margin and readiness warnings.
The demonstration makes pricing assumptions and warnings inspectable before a client-facing quotation is generated.
Use it for new enquiries, custom itineraries, group quotations, supplier-price changes and every pre-approval review before a proposal is sent.
Choose your city to load its catalogue and cost basis: Amsterdam uses native EUR costs; Abu Dhabi retains its AED workflow. Amsterdam includes 25 attraction and route records, 15 dated public price references, four planning templates, age-based admission, service-date availability checks, explicit fare evidence for variable-price products and local operating prompts. Public rates are planning references, not confirmed bookings or supplier net agreements.
The public demo runs on GitHub Pages with browser-local drafts, templates, rates and version history. A separate shared-workspace backend is prepared but not connected. Sample rates still need supplier confirmation; accounting and live booking integrations are outside the demo.
Demonstration boundary: The public demo runs on GitHub Pages with browser-local drafts, templates, rates and version history. A separate shared-workspace backend is prepared but not connected. Sample rates still need supplier confirmation; accounting and live booking integrations are outside the demo.