Part of Website and builder
One set of trips for the office and the website
Most Nepal operators keep trips twice: once in the office spreadsheet and once in a WordPress site that a nephew or an agency updates when they have time. The two drift apart. The site still shows last year's price, or a date that sold out a week ago.
In TripNerve the website reads from the same trips, departures and prices the office uses. Add a spring season of Saturday departures to the Everest Base Camp Trek and they appear on the trip page. Confirm a booking for 4 travellers and the seats left on that date drop by 4, everywhere, without anyone editing the site.
What a trip page shows
Every published trip gets its own page, laid out by your theme. You choose which sections appear and in what order once, on the trip page template, and every trip follows it. By default the trip's sections sit in a column beside a booking card that stays in view as the traveller scrolls.
- Photos, key facts, overview and highlights
- Day-by-day itinerary, route map and altitude profile
- Dates with seats left, guaranteed dates and a line for private trips
- What's included, know before you go, packing list and trip questions
- Cancellation policy, reviews of this trip and similar trips
- A booking card with the from price, group prices, next dates, WhatsApp and your rating
Booking requests and enquiries, not online payment
A traveller who is ready presses Book on a date and fills in the booking form: how many travellers of each type, any add-ons such as a porter or an extra night in Kathmandu, a promo code, and their details. The request arrives in Bookings as a request. Nothing is promised and no seats are held until you accept or decline it. When you accept, the traveller gets an email in the language they booked in.
A traveller who is not ready asks a question instead, from the enquiry box, the contact page or a form you build. It arrives in Enquiries with the trip attached, so you can reply on WhatsApp or email and move it along.
TripNerve doesn't take or record payments. There is no card checkout or deposit on the website. You confirm the booking and take payment the way you already do, such as a bank transfer, and you can list the payment methods you accept in the footer.
Trust before the first message
Travellers booking a trek in Nepal from abroad check whether a company is licensed and what other trekkers said. The site shows your licence number and membership logos from the official association files, and licensed Nepali companies also show the Government of Nepal emblem. Tripadvisor and Google reviews appear as sections, as a rating on the trip title and as a floating badge.
The starter site is built only from your own profile and trips. It never invents figures, awards or reviews, so nothing on it has to be taken down later.
Worked example
One spring booking request, end to end
Mero Himal Treks runs the 14-day Everest Base Camp Trek every Saturday from 6 March 2027, at USD 1,450 a person, stepping down to USD 1,290 a person for a group of 6. Kenji Nakamura in Osaka finds the trip on 9 November.
| What the traveller does | Where it lands | What the office does |
|---|---|---|
| Reads the trip page in yen, then switches to USD | Nothing yet | Nothing |
| Asks if Lukla flights are included | Enquiries, with the trip attached | Replies on WhatsApp the same afternoon |
| Requests 2 seats on Sat 13 Mar with an extra night in Kathmandu | Bookings, as a request | Checks seats: 2 of 12 left |
| Gets a copy of the request by email | His inbox, in the language he booked in | Accepts the request on Tuesday 10 November |
| Pays by bank transfer | Outside TripNerve | Checks the bank account as usual |
The question about flights arrives as an enquiry, not lost in someone's phone. When Kenji sends the booking request the next day, the 13 March date still shows 2 seats left. Nothing is held yet, so the office accepts it promptly: the date now shows as sold out on the website and the trip page offers 20 March instead.
The booking keeps the price, add-ons and cancellation policy it was made under. If the office raises the 2027 price in December, Kenji's booking does not change.
Common mistakes
Keeping a second site
Running an old WordPress site beside the TripNerve one means two prices and two date lists. Move the domain over and redirect the old addresses instead.
Leaving requests unanswered
A booking request holds no seats, so another traveller can take the last two while it waits. Confirm or decline within a day.
Hiding the licence
Travellers from abroad look for a licence number before they send money to Kathmandu. Fill in your licence and memberships in the company profile.
Promising card payment
The site doesn't take payments. Say in your confirmation email exactly how and when you want to be paid.

