The tour catalogue sits outside WooCommerce
Travel themes that also support WooCommerce often leave it unclear whether a listed trip is a product. GoodLayers answers that directly: WooCommerce is supported, but the note attached to that line says the package system is not running on WooCommerce and works independently instead.
So a tour is a Package entry with its own fields and its own browsing presentation, not a product with attributes and a cart. The vendor pairs the Package post type with a package filtering system, which lets visitors narrow the listing themselves before opening a trip.
Read together, that points to a booking-by-enquiry model for tours. If you run a shop as well, it sits alongside the packages rather than underneath them. Decide early which pages the theme's own package templates own, because routing trips through a product-style cart is not what this catalogue is built around.
Two named pieces carry the booking: Contact Form 7 and PayPal
The vendor describes a booking form and notes that it requires Contact Form 7. Version 2.00 added a PayPal payment gateway, recorded as a version entry in the feature list rather than as a described booking engine.
The form and the gateway are listed as separate items, so treat them as separate stages: the form collects the enquiry, and PayPal takes payment. The supplied description makes no claim about availability calendars, deposit rules, seasonal rates or automatic seat counts. If your trips are fixed departures with capacity limits, that accounting is not among the declared features and needs to be planned for before launch.
Naming Contact Form 7 as a requirement also moves some configuration elsewhere. Field layout, spam handling and notification routing live in that plugin's screens, not in the theme's own options.
Six custom post types do most of the structural work
GoodLayers lists six custom post types: Package, Price, Personnel, Testimonial, Portfolio and Gallery. The list matters more for how pages get assembled than for its length.
Price has its own type, so a tariff or price table can exist as a record separate from the package it belongs to, and the theme also lists a price table element. Personnel gives guides or staff a structured home instead of an about page with photos dropped in. Testimonials, portfolio items and galleries supply the proof and imagery a travel site leans on.
Much of a homepage can therefore be built from typed entries rather than hand-written page content. The trade-off is editorial: a new trip means a Package entry plus whichever price, staff and testimonial entries you relate to it, as well as the media that goes with them.
Colours, footers and blog layouts live in theme options
The design controls are options-panel driven. The vendor lists a Live Color Changer tied to the theme customizer, so colours can be adjusted in the front end while you look at the result, plus colour pickers in the admin panel for individual elements.
Beyond colour, the theme offers six footer layouts and three blog styles, each available with a left, right, both or no sidebar. Sidebars are described as unlimited, so pages can carry different widget areas. Sliders run through a drag-and-drop slider manager, with Flex Slider and Nivo Slider named, and each item's thumbnail can be a static image, a slider or a video. The vendor also lists 500+ Google Fonts, a logo uploader, a background uploader and a font uploader for Cufon files.
Because these settings are stored in the theme's options rather than in post content, they belong to the theme rather than to your content. That is worth weighing if there is any chance the site later moves to a different theme.
Translation: a .pot file, WPML, or an admin-panel translator
Tour Package ships a .pot file for localization, is listed as WPML compatible in the marketplace attributes, and includes a Built-in Translator that the vendor presents as an alternative to editing .mo files, with translation handled through options in the admin panel.
Having a built-in translator next to WPML is unusual enough to think through. A single extra language can plausibly stay in an options screen. Selling the same trip across several languages, with per-language package listings, is a different problem, and WPML compatibility is the relevant declaration for it.
All three are vendor statements about translation tooling. They do not establish that translated package content stays in sync, or that every string in the theme is covered by each route.
What the listing declares, and the layered PSD in the file list
The author behind the theme, GoodLayers, offers a video walkthrough of the demo setup and routes questions to its own helpdesk with a stated reply window of about 14 hours outside holiday periods. That describes the advertised support arrangement, not a measured response time.
The marketplace attributes, observed on 3 November 2026, record a responsive two-column layout, widget-ready areas, retina and high-resolution assets, and WPML as the named compatible plugin. The declared WordPress range runs from 6.1.x to 7.0.x, with browsers listed from IE11 through Edge. Because the 6.x branch appears in that range, the theme is not limited to the newest installations. The marketplace's latest version on that date was 2.4.3.
Alongside PHP, CSS and JS files, the ThemeForest file list includes a Layered PSD next to a flat PSD. The layered file is useful if a designer has to restyle the site's chrome and package page furniture before any CSS is touched, and less relevant if the stock look is what you want. Every attribute here is a listing declaration rather than a result from installing the theme against a particular PHP build or plugin set.
Questions & answers
Does the theme sell tours through WooCommerce?
According to GoodLayers, no. WooCommerce is supported, but the package system runs independently of it, so tour listings come from the Package post type and its filtering rather than from WooCommerce products. The Contact Form 7 booking form and the PayPal gateway are the described route from enquiry to payment.
Do I need Contact Form 7 installed?
The vendor's description says the booking form requires Contact Form 7. That makes the plugin a dependency for that form, not necessarily for the rest of the theme.
Can I translate the site without WPML?
The theme includes a .pot file and a built-in translator that works through admin options instead of .mo files. WPML is also listed as compatible, so one extra language and a multi-language catalogue can be handled by different routes.
What does the layered PSD in the file list give me?
A Photoshop source for the theme's design. If a designer prepares layouts before development, working from the layered file keeps comps aligned with the theme's proportions instead of being traced from a live demo.
