A plugin you run against a system that's run for you
With WP Travel Engine you own a WordPress site: you choose the hosting, keep WordPress, the theme and every plugin updated, and fix it when an update clashes with something else. Plenty of companies pay a developer to do that.
TripNerve is hosted. There is nothing to install or update, and the website is built from the same trips and departures your team works with, so a sold-out date shows as sold out without anyone editing a page.
Payments
WP Travel Engine can take payment on the site, from PayPal and bank transfer in the free plugin to Stripe and Himalayan Bank as paid add-ons. TripNerve takes no payments. A traveller sends a booking request, your team confirms it, and you collect the deposit as you do today.
If online payment at the moment of booking matters more to you than the office side, WP Travel Engine does something TripNerve doesn't.
What happens after the booking
A WordPress plugin mostly stops at the booking. TripNerve carries on: the enquiry that became the booking, the departure it sits on, the guide and porters assigned, the before-the-trip email, the review request after, and the reports at the end of the season.
- Enquiry pipeline with follow-up dates on Home
- Crew, vehicles and accommodation on each departure
- Traveller emails sent on a schedule and logged on the booking
- Reports on bookings, departures, nationalities and enquiries
When WP Travel Engine may suit you better
- You want travellers to pay online when they book, by card or PayPal. TripNerve doesn't take payments.
- You already have a WordPress site, a developer you trust and content you don't want to rebuild.
- You want full control of the code, hosting and plugins, or need a WordPress plugin that doesn't exist elsewhere.
- You want a GetYourGuide connection, Zapier or webhooks, which are on WP Travel Engine's paid plans.
- You prefer a one-off lifetime licence to an ongoing plan.
When TripNerve fits
- You'd rather not look after hosting, plugin updates and security yourself.
- You want enquiries, bookings, departures and crew in the same place as the website.
- Your site needs several languages without buying and configuring WPML.
- Your team wants to work from a phone, with a native iPhone and Android app.
- You take deposits by bank transfer already and don't need online checkout.
Moving from WP Travel Engine
Trips are entered again in TripNerve or drafted with AI from each trip's name and length, then checked against your WordPress pages. A season of departures is added in one go.
Customers come across with the CSV import, with a preview and a choice to merge or skip duplicates.
Upcoming bookings are added by hand with New booking so they hold their seats.
Add redirects (up to 200) from your old WordPress addresses, such as /trip/everest-base-camp-trek/, to the new trip pages, then connect your domain. The redirects are real 301s, so search engines follow them.
Early-access companies can send us their current site and we'll help move it over.

