Itineraries and rooms become bookable Shopify products — with Shop Pay, abandoned-cart recovery, 130+ currencies, and AI discoverability. Your checkout. Your customer data. No domain handoffs. No OTA commission.
Select dates below to search live availability and pricing from the PMS. Results load automatically — no search button needed. Click Book Now on any result to reach Shopify Checkout in one step. The guest never leaves the operator domain.
Kruger National Park
De Kelders
Franschhoek
O.R. Tambo
Hoedspruit
Bantry Bay
Outside
Franschhoek
Kruger National Park
Matetsi Private Game Reserve
Tswalu
Karen
Karen
Nyarugenge
Watamu
Mara Naboisho Conservancy
Mara Naboisho Conservancy
Bantry Bay
Bantry Bay
Hoedspruit
Franschhoek
Franschhoek
Stellenbosch
Kapama Private Game Reserve
Kruger National Park
Mara Naboisho Conservancy
Mara Naboisho Conservancy
Mara Naboisho Conservancy
Mara Naboisho Conservancy
Mugie Wildlife Conservancy
Arcadia
O.R. Tambo
Summerstrand
Sandown
Waterval City
Bantry Bay
Westdene
Sandown
Isandovale
Bantry Bay
Summerstrand
Bantry Bay
Sandown
Sandown
Sandown
Umhlanga Ridge
Durban Central
Johannesburg International Airport
This is the flow running today at a live storefront. The guest never leaves the operator's domain — search, availability, selection, and payment all resolve in one place. There is no redirect to a third-party booking engine, no email form, no new tab. See it yourself at simbavati.myshopify.com.
The guest enters dates and party size in a search widget embedded in the operator's Shopify storefront (the Travel Search app extension). Live availability returns from the PMS — no page handoff.
Available rooms appear with live rates in the guest's currency. The guest picks a room and reviews the total — taxes and the full price shown before any commitment, not revealed at the final step.
A provisional hold is placed against live PMS inventory and a Shopify draft order is created. The room is held; nothing is charged yet.
Shopify Checkout — Shop Pay, Apple Pay, Google Pay, or card. On payment, the order is confirmed and the PMS reservation is written back as confirmed, with a folio opened.
The same store, the same checkout, the same customer record handles an itinerary booking. One platform, both products.
Wetu is the standard for building and presenting itineraries — more than 3,000 operators use it. But Wetu does not take payment, does not index in Google, and cannot be read by the AI assistants that increasingly plan trips. When a guest clicks "Book Now" on a Wetu itinerary, they get an email form. Meanwhile, thousands of lodges and boutique hotels still confirm rooms by manual availability check and email — a structural exclusion from a travel economy that now expects instant booking.
Most booking engines send the guest off the operator's brand-name site to a third-party payment domain in a new tab. That redirect is where trust fractures: jarring redirects cost 15–22% of entry-point traffic, and 23% of abandoners leave because they do not trust an off-domain page with their card. [DR1] Travel already abandons at 80.8% on average — higher than retail's 70.2% — and every handoff makes it worse. [H1] Shopify's abandoned-checkout recovery can win some of that back; that recovery is structurally impossible when the checkout lives on someone else's domain.
OTAs and trade intermediaries take 15–30% of a booking — and for remote safari lodges, 25–45% through DMCs, leaving the lodge 40–55% of the gross after all fees. [OTA1] Direct bookings cost 2–5% blended and are worth more: a direct booking averages $516 against an OTA's $312, and cancels at 10.6% versus 21.8%. [SM1] The commission is not a marketing cost. It is a room given away.
Plekify closes the gap between the content that sells the trip and the checkout that books it — on the operator's own domain.
The established property management systems were reluctant to integrate Shopify-first, so we built a lean PMS of our own. You do not have to adopt it. Plekify works with any PMS that exposes a documented API — open, or accessible through a commercial agreement. Either way, your storefront, checkout, and customer data run on Shopify, on your domain.
A lean, modern, built-for-purpose property management system runs your operations: calendar, rooms, rates, guests, folios, housekeeping. Availability feeds your Shopify storefront directly; bookings and folios are created automatically on payment. One vendor, one data model, fastest path to live.
Your PMS stays the system of record. Plekify connects to it through its API and adds the Shopify commerce layer on top — storefront, Shop Pay, recovery, AI discoverability — without changing how your team works. Provisional holds and confirmed reservations write back to your PMS.
| Path A — Plekify PMS | Path B — Your PMS | |
|---|---|---|
| System of record | Plekify PMS | Your existing PMS |
| Operations surface | Plekify PMS (12 modules) | Your PMS, unchanged |
| Storefront & checkout | Shopify, your domain | Shopify, your domain |
| Shop Pay / accelerated checkout | Yes | Yes |
| Abandoned-cart recovery | Yes | Yes |
| 130+ currencies (Shopify Markets) | Yes | Yes |
| AI discoverability (Catalog, metaobjects, llms.txt) | Yes | Yes |
| Requirement | — | Documented API: open or via commercial agreement |
The PMS is a choice. The Shopify advantage is the constant.
Provide your Wetu credentials. Plekify reads every PIN and itinerary UUID and builds a complete, structured Shopify catalogue — each surface a standalone, SEO-indexed page with its own URL, schema.org markup, and wetu.* metafields. A single PIN typically generates 10 or more indexed pages. Re-sync at any time: change detection runs on a content hash, so only modified records write back to Shopify, and day-count integrity checks prevent a partial sync from corrupting a live itinerary.
| Surface | What it becomes |
|---|---|
| Property | Primary product page — gallery, narrative, location, structured data |
| Rooms / units | One product per room type (no variants), with live rates |
| Activities | Bookable activity products |
| Dining | Dining venues and experiences as indexed pages |
| Spa | Spa and wellness treatments as indexed pages |
| Travel documents | Visa, health, and pre-departure information pages |
| Rates | Rate tiers exposed as structured pricing |
| Videos | Embedded property and experience video |
| 3D panoramas | Interactive 360° / 3D room and lodge views |
Accommodation operators without a Wetu portfolio populate the same storefront directly from the PMS: room types, rates (ZAR / USD / EUR / GBP), availability, and restrictions flow into Shopify products and the live search widget. The website is built from the system of record, not maintained by hand.
Listings that carry interactive media — 3D tours, 360° views — report materially higher booking conversion and far longer dwell time than static photos. [IM1] Fact-dense, structured pages are also what AI engines cite: structured content earns 30–40% higher citation rates in generative search than unstructured copy. [GEO1] One PIN, correctly synced, is simultaneously a conversion asset and an AI-discoverability asset.
We ran two studies with Python/Playwright browser automation, from the guest's first click to the payment page. We separated them on purpose: comparing an OTA's consumer checkout to a property's PMS booking engine in one table mixes two different things. Every number traces to a row in a published spreadsheet, and Plekify is itself a subject of the study — the methodology is open for independent re-running.
| Platform | Friction Score | Clicks | Handoffs | Fields | Accelerated checkout |
|---|---|---|---|---|---|
| Plekify | 3.0 | 4 | 0 | 7 | Yes (Shop Pay) |
| Airbnb | 4.0 | 5 | 0 | 6 | No |
| Booking.com | 6.5 | 7 | 0 | 7 | No |
*¹ Plekify Booking Friction Study, March 2026. ² Shopify.
| Platform | Friction Score | Clicks | Handoffs | Fields | Accelerated checkout |
|---|---|---|---|---|---|
| Plekify | 3.0 | 4 | 0 | 7 | Yes (Shop Pay) |
| Legacy regional PMS engine | 18.5 | 8 | 1 | 9 | No |
| RoomRaccoon | 27.5 | 11 | 2 | 15 | No |
*Source: Python/Playwright automation, March 2026. Scripts, raw CSV, and timestamped screenshots published. The "legacy regional PMS engine" row is a real measured result; the provider is not named.
The high-friction engines redirect the guest to a separate booking domain — sometimes twice, once more to a payment processor. Each handoff adds 3.0 to the score and is where 23% of abandoners leave over payment trust. Plekify: zero handoffs.
Plekify reaches payment in 4 clicks; the heaviest engine required 11. Baymard: 22% of shoppers abandon a checkout that is too long or complicated. [C1]
The heaviest engine asked for 15 fields. The average checkout collects 11.3 when only 8 are needed; forced account creation alone costs 19% abandonment. [C4] Plekify inherits Shopify's optimised checkout.
Only the front-end consumer platforms and Plekify support accelerated checkout. Shop Pay converts up to 50% higher than guest checkout and is 4× faster on mobile. [B1] No regional PMS booking engine offers it.
Don't take our word for it. The Playwright scripts and raw data are published. If the numbers are wrong, run them yourself. Read the full study →
| Capability | Copy |
|---|---|
| Shop Pay | Accelerated, one-tap checkout for 100M+ pre-saved buyers. Up to 50% higher conversion than guest checkout; 4× faster on mobile. The 5% lower-funnel lift from its presence alone is conversion no PMS booking engine in this market can match. [B1] |
| Abandoned checkout recovery | Automated recovery for guests who start but do not finish — the 80.8% of travel sessions that abandon are partly winnable. [H1] Structurally unavailable when checkout runs on a third-party domain. |
| 130+ currencies — Shopify Markets | Localised currency, language, and tax by geolocation. 92% of consumers prefer to pay in their own currency and 33% abandon a USD-only price; localisation lifts international conversion up to 40%. [CUR1] |
| PCI DSS Level 1 | The operator never touches raw card data. Shopify manages the full payment lifecycle at the highest compliance tier, with fraud analysis on every transaction. |
| AI discoverability | Each itinerary and room is a structured Shopify product — Catalog API, metaobjects, schema.org, and llms.txt / agents.md theme templates — readable by ChatGPT, Gemini, and Perplexity. AI traffic to Shopify stores is up 7×, AI-driven orders up 11×, since January 2025.
[A1]
|
| Structured data for GEO | Generative engines cite facts, not prose. Dense, structured product data earns 30–40% higher citation rates in AI search, and feeds the long-tail attributes (amenities, accessibility, location) that itinerary engines parse. [GEO1] |
In March 2026, OpenAI discontinued Instant Checkout after roughly five months. Walmart reported in-chat conversion roughly 3× lower than its own channels; only about a dozen merchants ever integrated; the scraping-based model could not verify live inventory or compute tax across jurisdictions. [D1] When OpenAI announced the wind-down, the share prices of the large OTAs rose ~10% — the market understood that AI is a referral layer, not a replacement checkout.
The Universal Commerce Protocol — co-developed by Google and Shopify in early 2026, backed by Visa, Mastercard, Stripe, Adyen, Target, Walmart and others — lets AI agents query live inventory and complete purchases against real merchant systems. Crucially, the merchant remains the Merchant of Record. [UCP1] Shopify syndicates structured product data to ChatGPT, Copilot, Gemini, and Google's AI Mode through Agentic Storefronts.
56% of travellers used AI to plan a trip in the past year, up from 24% — but only 8% trust it "almost always," and half click through to a source site to verify. [T1] The behaviour is settled: travellers research with AI and complete the purchase on a domain they recognise. Plekify positions your itineraries and rooms to be found by the agent and booked on your Shopify checkout.
Shopify lets you serve dedicated machine-readable templates — llms.txt, llms-full.txt, agents.md — so AI crawlers read a clean, high-density catalogue of your properties, rates, and policies. Generative Engine Optimisation replaces keyword SEO: the goal is to be the cited, recommended answer, not the tenth blue link.
Travel designers spend an average of 22.5 hours every month formatting proposals, sourcing images, and rebuilding the same content. That is seven working weeks a year that never reach a client. Plekify rebuilds that workflow as a governed pipeline — consultant-authored, AI-assisted, bookable on the operator's own domain.
| When a guest… | Wetu today | With Plekify on Shopify |
|---|---|---|
| Clicks "Book Now" | Email sent to consultant — no online payment | Shopify checkout with deposit or instalment payment |
| Views the itinerary | wetu.com subdomain — not the operator's domain | Operator's own branded domain |
| Asks about pricing | Static price display only — no booking capability | Static display plus live checkout when PMS is connected |
| Google crawls the page | Nothing — JS iframe, not indexed by search engines | Full HTML, structured data, automatic sitemap |
| Asks ChatGPT to plan a trip | Invisible — Wetu content cannot be discovered by AI assistants | Your itinerary appears in the AI conversation — with pricing, images, and a direct path to checkout |
| Abandons without booking | No recovery possible | Automated Shopify abandoned checkout recovery |
| Browses property detail | Description and images | Rooms, dining, activities, spa, rates — each browseable |
| Wants to book accommodation | No booking capability — presentation tool only | Live availability, real-time pricing, on-domain checkout |
| Requests another language | Some itinerary translation; wider site does not translate | 20+ languages across the entire storefront via Markets |
| Wants local currency | Static display only — no currency conversion | 130+ currencies, localised pricing at checkout |
The Western Cape and Kruger account for more than three-quarters of inbound Southern Africa revenue. Every operator knows the strategic case for selling the Waterberg, the Wild Coast, the Eastern Cape, KwaZulu-Natal — but the commercial infrastructure has not kept up with the ambition. Itineraries for secondary destinations built in Wetu live on wetu.com, where they cannot rank in Google, are invisible to ChatGPT, Perplexity, and Google AI, and offer no way for a guest to book without leaving the operator's brand.
Plekify republishes those consultant-authored itineraries as full HTML pages with structured data and automatic sitemaps — indexed by search engines, discoverable by AI assistants, and routed through a governed pipeline with human sign-off before they ever appear to a guest. When a traveller asks an AI to plan a trip to the Eastern Cape, only operators with structured, queryable inventory appear in the answer. Geographic spread is not just a policy ambition. It is a commerce problem, and it requires commerce infrastructure to solve.
Plekify operates its own massive-scale travel intelligence store, continuously tracking over 428,000 verified locations across 16 African nations. We use Google Maps data as the baseline for global discovery, and then enrich it through our own proprietary pipeline—deeply crawling websites and cross-referencing over 70 million traveler reviews to extract nuanced details.
Our database holds unprecedented density across the continent: over 193,000 indexed properties in South Africa alone, supported by comprehensive coverage in Kenya (58,000+), Tanzania (36,000+), Uganda (26,000+), and Madagascar (13,000+), alongside tens of thousands more across Zambia, Namibia, and Zimbabwe. This includes over 54,000 distinct accommodation properties, 58,000 dining venues, and 10,000 activities.
For operators, Wetu acts as an elective connection to synchronize specific media and property details. But every recommendation in a Plekify itinerary is ultimately grounded in our own live, independent data store—letting us verify accessibility, validate dietary protocols, and match precise guest constraints with unmatched accuracy.
Plekify integrates with existing workflows, from simple sync-to-Shopify publishing to full brief-to-bookable design.
An itinerary authored by a consultant in Wetu is synced to Shopify without modification. The AI structures the commercial layer — deposit collected at checkout, balance scheduled — and publishes it as a bookable product the consultant signs off on.
Sync & publish · Commerce layerThe AI evaluates every property selection against the Plekify Intelligence Layer—surfacing better-matched alternatives, improving routing, and freshening narrative—then uploads the improved version back to Wetu.
Enhancement pipeline · On behalf of clientA natural-language brief is the only input. The pipeline handles constraint detection, candidate discovery, route validation, and direct upload to Wetu—then sync to Shopify as a bookable product.
Try the brief interface → Full pipeline · 14 agentsA ZAR 2.8M itinerary for seven guests across three generations. Coeliac dietary protocol with chain-of-custody handover to every kitchen. Mobility constraints that dictate room allocation and vehicle type. A secret proposal the lodge manager knows about — the parents do not.
One JSON file holds the brief, the constraints, the pricing, and the narrative. From that single source, the pipeline generates four distinct outputs: the client view, the operator dossier, the ground ops brief, and the pre-departure pack. Each tab below traces a complex brief through extraction, gating, ranking, and these four live delivery views.
This is not a prompt sent to a chatbot. It is a governed, gated pipeline — each stage validated before the next begins.
This sequence shows how Plekify turns a conversational brief into a governed, bookable itinerary package.
Runs left-to-right on desktop, stacks vertically on mobile.
Voice dictation or typed notes arrive as an open brief instead of a rigid form.
Dates, budget signals, accessibility needs, pace rules, and emotional intent are structured into context.
The Wetu universe narrows through geography, dates, budget, and specialist fit before ranking begins.
Candidate properties are scored against the brief and sequence logic, then elevated into a coherent shortlist.
A consultant reviews the shortlist, checks special conditions, and confirms the package is publishable.
One validated itinerary fans out into audience-specific surfaces without changing the underlying travel logic.
The Brief
"Seventeen-day South Africa journey. Celebrating 25th wedding anniversary. Interest in wine estates, fine dining, no children on this trip. Prefer shorter drives, nothing over 3 hours. Cape Town as anchor. Budget around R450,000." Hoffmann Anniversary · Extracted from intake brief
| Constraint | Value | Gate Impact |
|---|---|---|
| Duration | 17 days | 14-21 day itineraries |
| Occasion | Anniversary | Romance tag required |
| Interest | Wine estates | Winelands region priority |
| Interest | Fine dining | Dining score 4.5+ |
| Travel | Short drives | Max 3hr between stops |
| Anchor | Cape Town | Arrival/departure point |
| Budget | R450,000 | Per-night within range |
| Party | Adults only | No family-focused properties |
The Brief
"This is Gloria's 60th birthday, a milestone celebration. We're bringing three generations: Gloria and her husband, their two adult children with spouses, and three grandchildren ages 8, 11, and 14. Three weeks across Southern Africa. Must include Victoria Falls and Cape Town. One grandchild uses a wheelchair, accessibility is critical. Budget flexible but looking around R2.8 million for the full party." Osei Milestone · Extracted from intake brief
| Constraint | Value | Gate Impact |
|---|---|---|
| Duration | 21 days | 18-24 day itineraries |
| Occasion | Milestone birthday | Celebration tag |
| Party size | 11 pax | Group accommodation capacity |
| Ages | 8-75 years | Multi-generational suitability |
| Accessibility | Wheelchair required | Accessibility score 4+ |
| Must-see | Victoria Falls | Zimbabwe/Zambia inclusion |
| Must-see | Cape Town | Western Cape inclusion |
| Budget | R2.8M total | Per-night total within range |
This is a new, lean, built-for-purpose property management system. It is fast and modern, and it is optional — Path A for operators who want one vendor and the fastest route to a live Shopify storefront. It is not a 20-year-old platform, and we do not claim it is the deepest system on the market. It claims one thing the incumbents do not: it was designed from the first commit so that a guest can search, hold, book, and pay on your domain without a handoff.
| Module | Function |
|---|---|
| Today | Arrivals, departures, stayovers, available rooms, pending holds, KPI cards |
| Calendar | Availability and rates by room type, seasonal rates, restriction badges, inline editing, hold creation |
| Bookings | Reservations table — search, filters, detail, cancel, room assignment, folio link |
| Guests | Guest CRM — profiles, preference tags, VIP flag, stay history, deduplicated by email |
| Guest Bills | Folios — line items, charges, payments, voids, tax breakdown, close |
| Messages | Guest communications |
| Housekeeping | Room-status grid, 7 statuses, bulk actions, auto transitions, cleaning log |
| Room Pricing | Rate plans — multi-currency (ZAR/USD/EUR/GBP), default toggle, deactivate |
| Special Offers | Promotional rate and package management |
| Reports | Occupancy, ADR, RevPAR, revenue by plan and room type |
| Activity Log | Audit trail |
| Property Setup | Property, room type, and configuration management |
We built the database for commerce, not commerce on top of a legacy database. That is the whole difference — and it is offered, not insisted upon.
Checkout, Shop Pay, abandoned-cart recovery, Markets, Catalog
Our own lean property management system
Itinerary sync to bookable Shopify products
Planned integration via documented API
Planned integration via documented API
Planned integration via documented API
We work with any PMS that has a documented API which is open or accessible through a commercial agreement. The adapter framework already exposes the hooks — provisional holds, confirmed reservations, and two-way availability sync — so onboarding a new PMS is an integration, not a rebuild.
| OTA channel | Plekify + Shopify Payments | |
|---|---|---|
| Nightly rate | R3,500 | R3,500 |
| Per-night cost | R525 (15% commission) | ~R107 (2.9% + R5.50) |
| Occupancy | 70% — 256 nights/yr | 70% — 256 nights/yr |
| Annual cost per room | R134,000 | R27,000 |
Annual saving per room: R107,000. That is not a feature. That is a salary.
The arithmetic is worse for remote lodges. Through DMCs and trade, distribution runs 25–45%, and after concession fees, levies, taxes, and commissions, a lodge keeps only 40–55% of the gross. One worked example: a R10,000 rack rate nets roughly R486 in retained profit after everything. [OTA1] Shifting a single booking from OTA to direct is worth about $246 in net margin, and a direct guest is worth ~1.73× an OTA guest over two years. [SM1]
Direct is not only cheaper — it is better business: $516 average booking value versus $312, and 10.6% cancellation versus 21.8%. [SM1] Plekify moves bookings to the channel that costs less and earns more.
Operators managing 50–300+ properties who publish through Wetu but collect payment by invoice. Plekify turns the itinerary link into a checkout, and the portfolio into an indexed, AI-discoverable storefront.
Operators who want direct bookings on their own domain instead of redirecting guests to a third-party engine. Keep your PMS, or run the Plekify PMS — either way, the booking happens on your brand.
Groups with fragmented stacks across member companies. One Shopify commerce layer, shared infrastructure, individual brand identity per property.
Properties standing up operations for the first time can adopt the Plekify PMS and a Shopify storefront together — one vendor, the fastest path from zero to a bookable, indexed site.
Book a setup call and see a live demonstration with your inventory: a Wetu PIN becoming an indexed Shopify storefront, or the four-click booking flow against live PMS availability. Or run the Booking Friction Study against your current engine — the scripts are public.
Matthew Swart co-founded SafariNow.com in 1999 and led it for 18 years — to R320 million in annual booking value and 150 employees — before selling a controlling stake to TravelStart in 2017. Plekify is the commerce infrastructure SafariNow needed and did not have.