Commerce infrastructure for the travel trade
Retail guests check out with Shop Pay, Apple Pay or card. Trade partners book on account terms. The checkout is fast and PCI-compliant, the pages index on your domain, and remarketing is built in. The guest record and the payment data stay in your store, on your domain.
From the founder of SafariNow.com · R320m peak annual booking value, 2015
SafariNow — Matthew Swart founder profile (archived)
web.archive.org · 2015
SafariNow company page: R320m peak annual booking value (2015).View source
· acquired by Travelstart, 2017
Travelstart acquires SafariNow
Skift · TechCentral · ITWeb · 2017-12
"majority stake", December 2017 — confirmed by three independent outlets.View source
· 25 years in African travel tech
· About the founder ↓
Plekify is how a hotel, lodge or tour operator sells its rooms and trips on its own website and takes payment directly — the guest never leaves your site.
We scripted a real booking — pick dates, choose a room, reach the payment page — and ran it automatically in visible browsers. The score counts every click, form field, page and domain hand-off from property site to payment page (lower is better), under an empirically-grounded formula. Plekify is the only on-domain, Shop Pay checkout — every competitor either pays a domain-handoff penalty or blocks the agent before payment.
Fields counted on the payment page. Shop Pay serves 250M+ shoppers who already saved their card on any Shopify store — those guests complete checkout in one tap, zero fields. The 22-field count is the first-time guest form (email + shipping + card). Competitors have no saved-card equivalent: every guest types the full card form every time.
Reached Mews off-domain booking engine (app.mews.com). Redirects the guest away from the operator's domain. 67% = 2 of 3 valid runs reached the payment page; field count pending re-measure (site-side breakage). Provisional — re-measure on a different day.
Redirects to book.nightsbridge.com (off-domain). Raw wall-clock is similar to Plekify because the guest lands on a lightweight third-party card form — but it carries a domain handoff (6.6x weight) and no accelerated checkout, so its friction is ~2x.
Redirects to direct-book.com (off-domain). Card form only; no express payments. Highest friction of the systems that reached payment. Click count is an average across properties (4.3 avg).
Total time is the relative booking duration, calibrated to Plekify's measured 19 seconds. Every system scales proportionally to its friction score — lower friction finishes first and shows less total time. Plekify's figure is real; competitors are proportional to their measured friction.
Every domain handoff is a place a guest can abandon — and a place the guest record leaves with them. On-domain checkout keeps the booking, the email, and the lifetime relationship on the property's side of the line.
Cart abandonment up to 70%; off-domain redirects a leading cause
Baymard Institute · 50-study meta-analysis
Up to 70% average cart abandonment (Baymard Institute). Off-domain redirects are a leading abandonment cause.View source
Kalibri Labs — direct bookings ~12.5% more profitable than OTA
Hotel Management / Kalibri Labs · 2024
Direct ~12.5% more profitable than OTA — strongest public Kalibri figure.View source
F = C + 6.6H + Fld_excess + P + 9.8I − 3.7A − 5.4AccWhat the test does. A scripted browser (Playwright) walks a real booking flow on each engine: open the property site, pick dates, choose a room, and reach the payment page. It stops there. No real transaction is ever attempted — no card is charged, no booking is completed.
What we count. Every click, every form field a guest must fill, every page that loads, and every time the guest is handed off to a different domain. Lower is better. The friction score combines these under an empirically-grounded formula, with each weight calibrated to a measurable conversion impact (one extra form field ≈ 4.1% relative conversion loss; a domain hand-off is weighted 6.6×, an interruption such as a CAPTCHA or bot-wall 9.8×).
The Shop Pay saved-card difference. This is the one metric where the engines are not directly comparable, and it matters most. Shop Pay (Shopify) saves the card, email, shipping and billing for any shopper who has ever opted in on any Shopify store — a network of 250M+ shoppers. For those returning guests, checkout is one tap: zero fields. For a first-time guest, the full Shopify form renders (the 22-field count shown). Every competing engine offers only the guest card form — there is no saved-card network, so every guest types every field every time. The formula captures this advantage as an accelerated-checkout weight (−5.4); the field count shows both paths for Plekify and the guest-only count for competitors.
Agent-Readiness (the second axis). Agent-Readiness (ARS, 0–3) measures whether an autonomous booking agent can discover and complete a booking on the open web — without a private B2B deal. Plekify is the only system with a live Universal Commerce Protocol manifest (catalog + Shop Pay & Google Pay handlers + an MCP endpoint) and zero bot-walls, scoring 3.0/3.0. The field ranges 0.6–2.0; Booking.com exposes rich structured data but its API is gated and bot-defended; Airbnb's API is closed and login-walled; Expedia hard-blocks automated browsers.
Blocked systems are measured, not hidden. Each run is classified reached-payment, redirected off-domain, agent-blocked or errored. Under Intent-to-Treat, blocked runs take a timeout-penalty floor — so a system that blocks agents is never rewarded with a low score. Cloudbeds is agent-blocked at cart (a React isTrusted guard rejects programmatic clicks); RoomRaccoon and the OTAs are kept as agent-blocked exhibits.
Systems & selection. Plekify + SiteMinder, Cloudbeds, NightsBridge, RoomRaccoon + Mews, Stayntouch, the OPERA ecosystem + Booking.com, Airbnb, Expedia, Travelstart. Properties are matched on tier, region and distribution (Coarsened Exact Matching) so the comparison is like-for-like.
Egress & limitations. Human-friction runs execute from a residential connection; Agent-Readiness from a datacenter (where cloud AI agents run). Single residential geo is a stated, upgradable limitation. The full pre-registered protocol, all code, every per-run JSON and the analysis are open for independent replication at the repository below.
Open repository — github.com/Matthew-Swart/plekify-booking-friction-study ↗
Source:
Plekify Booking Friction Study (open repository, v2 grounded LFI + ARS)
github.com · 2026
Plekify 10.9 / Mews 16.6 / NightsBridge 22.9 / SiteMinder 29.4. Agent-Readiness: Plekify 3.0 (only open-web agent-ready system).View source
Agent-Readiness is scored 0–3 because it is the weighted sum of six machine-checked signals — structured data, robots/bot posture, CAPTCHA/WAF friction, express payments, public API, and protocol adherence — each rated 0 to 3. 3 means an autonomous agent can discover and complete a booking on the open web; 0 means it is hard-blocked. Plekify is the only system with a live Universal Commerce Protocol manifest, so it is the only one an AI booking agent can actually use.
Open-web definition per the Shopify Universal Commerce Protocol.
Each system is scored 0–3 on six signals, each with a published detection method: structured data (JSON-LD LodgingBusiness/Offer or a live UCP catalog); robots/bot posture; CAPTCHA/WAF friction (visible challenge only); express payments (UCP/Shop Pay/Apple Pay/Google Pay); public API (self-serve vs gated); and protocol adherence (a real /.well-known/ucp manifest or A2A agent card). The composite is fully auditable — every raw signal is in the open repository.
This returns a few sample properties from across the demo fleet — not one group's real inventory. It's the fastest way to try the booking flow without an account. For a real group end-to-end, open a demo store below (password: plekify).
The web stack
Most travel brands build their website on WordPress, then add a booking plugin. Shopify is a commerce platform: checkout, payments and customer data are part of the platform. Plekify runs on Shopify Standard. No Plus required.
100% on your domain. PCI-DSS Level 1 by default; 99.9% platform uptime.
Shopify — PCI-DSS Level 1 compliant (all stores by default)
shopify.com · 2026
Level 1 PCI DSS; extends by default; reduces merchant PCI scope.View source
Shopify — 99.9% platform uptime
help.shopify.com · 2026
99.9% platform uptime (99.99% is a scoped Plus checkout SLA).View source
Typically redirects to a third-party booking engine.
Every booking builds a Shopify customer profile — owned, segmentable, marketable.
Records split across PMS, plugin and gateway.
Shopify Email, abandoned-cart recovery, dynamic segments and Flow automations — native.
External CRM required; PMS data rarely flows to email tools.
Agentic Storefronts surface your inventory in ChatGPT, Perplexity, Google AI Mode, Gemini and Copilot. AI-referred traffic to Shopify is up ~8× year-over-year and AI-referred orders ~13× (Q1 2026) — and those visitors have a ~50% higher conversion rate, with +14% AOV.
Shopify Spring '26 — Universal Commerce Protocol + Catalog API
shopify.com · 2026-06-17
Open protocol co-developed with Google; Catalog API clusters inventory for AI agents.View source
Shopify — AI-referred orders ~13× YoY; +~50% conversion, +14% AOV (Q1 2026)
shopify.com · 2026
AI-referred orders on Shopify grew nearly 13× year-over-year in Q1 2026; AI-chatbot referral sessions grew 8× YoY. AI-referred sessions convert at nearly 50% higher rates and carry 14% higher AOV.View source
No structured agentic-discovery layer — invisible to AI assistants.
The Universal Commerce Protocol lets guests ask, browse and buy inside an AI assistant while you stay merchant of record.
Shopify Spring '26 — Universal Commerce Protocol + Catalog API
shopify.com · 2026-06-17
Open protocol co-developed with Google; Catalog API clusters inventory for AI agents.View source
Universal Commerce Protocol — the merchant stays merchant of record
shopify.dev · UCP 2026-04
"The merchant always remains the merchant of record." (UCP carts-and-checkout for agents; specification version 2026-04-08.)View source
No integration path exists.
Deposits, instalments, milestone billing, B2B terms, 130+ currencies, Shop Pay.
Shop Pay — up to 50% higher conversion vs guest checkout
shopify.com · 2026
Up to 50% higher conversion vs guest checkout (Big Three consulting firm, April 2023).View source
Plugin-dependent; typically single-payment flows.
Shopify Markets — localised pricing, 20+ languages, 130+ currencies, hreflang natively.
Plugin-dependent; hreflang and multi-currency require dev work.
Property pages rank on your domain — full HTML, automatic sitemaps, structured data.
Plugin-dependent; structured data and sitemaps need manual setup.
Agent pricing tiers, trade catalogues and negotiated terms — on standard Shopify.
Key B2B features now on Basic, Grow and Advanced
changelog.shopify.com · 2026
Company profiles, payment terms, volume pricing, up to 3 B2B catalogues.View source
Separate systems required.
8,000+ managed apps — no version conflicts, no security patches, no broken upgrades.
Plugin stacks accumulate compatibility risk.
A world-class CDN is included at no extra charge, so galleries, 3D tours and video load fast wherever your guests are.
Shopify — world-class CDN included at no extra charge
help.shopify.com · 2026
"Shopify provides a world-class CDN at no additional charge, ensuring fast global performance." Cloudflare-backed; HTTP/2; automatic image CDN.View source
Hosting and CDN are yours to source, tune and pay for.
Shopify POS unifies gift-shop, spa and front-desk sales with online inventory in one system.
Shopify POS — unified in-person and online inventory
help.shopify.com · 2026
"Shopify POS syncs with Shopify to track your orders and inventory across your retail locations, online store, and other active sales channels."View source
Separate POS system; stock and guests split across tools.
Shopify Audiences delivers up to 2× more orders for every retargeting dollar spent.
Shopify Audiences — up to 2× more orders per retargeting dollar
shopify.com · 2025
"Ad campaigns using the latest version of Shopify Audiences Retargeting Boost lists have generated up to 2x more orders for every marketing dollar spent."View source
Ad targeting rebuilt from scratch in each external platform.
Shopify Functions encode your trade rules, NET-term gating, deposits and discounts directly in checkout.
Shopify Functions — custom checkout, discount, payment & delivery logic
shopify.dev · 2026
Shopify Functions customise the backend logic for discounts, cart/checkout validation, payment and delivery — the surface Plekify uses to encode trade rules and NET-term gating.View source
Booking-plugin checkout is closed; custom rules need bespoke code.
Sidekick answers questions and takes actions in your admin, in plain English.
Shopify Sidekick — plain-English merchant AI assistant
shopify.com · 2026
Sidekick answers questions about your store and takes actions in the admin, in plain English (Shopify Editions Spring 2026).View source
No equivalent merchant AI built in.
Managed Markets handles duties, taxes and compliance for international itineraries.
Shopify Managed Markets — duties, taxes & compliance for cross-border
Shopify Editions Spring '26 · 2026
Managed Markets lets you sell globally with support for duties, taxes and compliance, with localised prices that include duties, taxes and fees (Shopify Editions Spring 2026).View source
Duty and tax compliance assembled plugin-by-plugin.
One checkout, two markets
Your retail guest pays by card. Your trade partner books on pre-arranged net terms. Same Shopify checkout, same database — the direct relationship and the trade relationship, both retained.
Shop Pay, Apple Pay, Google Pay, card. Accelerated one-tap checkout converts up to 50% higher than a guest checkout.
Shop Pay — up to 50% higher conversion vs guest checkout
shopify.com · 2026
Up to 50% higher conversion vs guest checkout (Big Three consulting firm, April 2023).View source
Pre-approved agents book on net terms (NET 15/30/45) against contracted rates. Shopify's B2B features — company profiles, payment terms, volume pricing — now run on the Basic plan; where Basic doesn't support those features (e.g. deposits/split payments), Plekify adds them via custom draft-order terms.
Key B2B features now on Basic, Grow and Advanced
changelog.shopify.com · 2026
Company profiles, payment terms, volume pricing, up to 3 B2B catalogues.View source
Direct and trade don't compete here — one booking record, one guest profile, one folio.
This is a live Shopify storefront on the Plekify fleet, built from Singita’s WETU Pin IDs and running on a real Shopify subdomain. Every lodge, room, activity and 3D tour is a Shopify product on its own page, with live rates and availability from a connected PMS, and consumer and trade checkout on one domain. In production, your site runs on your own top-level domain.
WETU holds the richest property content in African travel — HD photography, 360/3D tours, rooms, activities, dining. Suppliers maintain it themselves, so your site auto-updates, and content entered once is shared across the WETU partner network.
Plekify turns one Pin ID into a complete, SEO-indexed Shopify store on your own domain — every room a product, every activity a page, with structured data and a sitemap.
A guest picks dates, chooses a room, and pays with Shop Pay, Apple Pay or trade-account terms — on Shopify checkout, on your domain. No redirect to a third-party booking engine.
WETU isn't required — but it makes a significantly richer site that updates automatically when WETU content changes. It is our content partner; Plekify makes it bookable.
wetu.com ↗
For WETU users
Already building itineraries in WETU? Plekify publishes a single itinerary UUID as a complete, bookable, agent-readable site on your domain — every stop a page, the journey itself a Shopify product. Bring the UUID; no rebuild.
What one UUID publishes
The journey
A chronological command center — navigate the day plan, read each stop, and drill into any property, room type, activity, restaurant, spa, document, 3D panorama or video, with transfers, flights, maps and day-by-day commentary.
Every stop
A full property page for each accommodation on the route — its own indexable URL, with rooms, imagery and structured data.
Agent-ready
Server-rendered HTML and structured data make every page readable by ChatGPT, Perplexity and Google AI.
Shopify Spring '26 — Universal Commerce Protocol + Catalog API
shopify.com · 2026-06-17
Open protocol co-developed with Google; Catalog API clusters inventory for AI agents.View source
Reference itinerary
Hoffmann Anniversary
Romantic anniversary. Wine estates, soft pacing, no long drives, western routing.
WETU source View the original itinerary on wetu.com
OperationsCalendar, reservations, folios, housekeeping and channel sync — included, with no extra licence. The PMS and the Shopify store share one database, one booking record.
Access is for approved accounts only. Apply below — we'll set you up.
Alternatively — keep yours
Plekify connects as the commerce layer on top. Keep your PMS for operations; Plekify handles the storefront, checkout and guest data on Shopify.
Our adapter framework is open: bring a PMS with an API and we'll build the integration — a commitment, not a pre-built library.
One stack, from checkout to general ledger. Plekify runs the layer that generates revenue — guest commerce and operations — and posts a balanced nightly batch to your general ledger. It integrates with the ERP you already run.
The booking ends at the payment page — the business doesn't. Here's where that payment travels next, and where Plekify fits in the stack you already run.
For lodge operators — and the finance and IT buyers who account for their revenue.
Shopify checkout, Shop Pay, Apple Pay, Google Pay, multi-currency, BNPL, trade-on-terms B2B — on the operator's own domain.
Availability calendar, rate plans, restrictions, nightly rates, line-item folios (room / F&B / spa / tax), payments, voids, close.
General ledger, USALI reporting, accounts payable, owner P&L, business intelligence.
Plekify doesn't write individual reservations into your general ledger — that would bypass your internal controls and inflate ERP consumption pricing. Instead, each day's reservations, folios, taxes and payments compile into one balanced nightly batch that posts to your GL — exactly the night-audit format your ERP already expects. Room revenue, F&B, spa and occupancy tax hit the right accounts; advance deposits land in liability; payments clear to cash.
Out-of-the-box Shopify handles static product quantities, single-invoice orders, one revenue account per product. Hotels need deferred deposits, perishable dated inventory, service-date revenue recognition, and folio-level revenue split. Plekify adds all of this.
| What hotels need | Native connector | Plekify |
|---|---|---|
| Deferred-deposit revenue (ASC 606 / IFRS 15) | Recognises immediately; needs a paid add-on module | Deposits post to a liability, then clear at checkout |
| Dated, perishable inventory | Syncs static quantity counts | Nightly availability + seasonal yield grids |
| Service-date revenue recognition | Whole invoice on one date | Nightly accrual over the stay |
| Revenue split (Room / F&B / Spa) + lodging tax | 1 product → 1 revenue account | Folio line items → distinct GL accounts + tax rates |
The founder
Matthew has worked in hospitality technology for over twenty years. He founded and sold SafariNow, South Africa's accommodation booking platform, before building Plekify.
He trained as a land surveyor (B.Sc. Survey, UCT, 1996) before moving into travel commerce on the early web. In 1998 he built one of South Africa's first online accommodation-booking sites; in 1999 he co-founded SafariNow.com and led it for the next eighteen years — from a borrowed R50,000 to roughly R320 million in annual booking value at peak, four funding rounds (including Tiger Global), and a majority sale to Travelstart in 2017.
Plekify is the next layer of that work: the same direct-booking thesis, rebuilt on Shopify, on the operator's own domain.
Pricing
Plekify is priced in conversation, set against the size of your group and the scope of the work. The fee reflects the number of rooms and properties involved and the complexity of the implementation — a single lodge and a multi-property consortium are priced separately.
Read the open Plekify Booking Friction Study
Plekify Booking Friction Study (open repository, v2 grounded LFI + ARS)
github.com · 2026
Plekify 10.9 / Mews 16.6 / NightsBridge 22.9 / SiteMinder 29.4. Agent-Readiness: Plekify 3.0 (only open-web agent-ready system).View source
Talk to us
We're taking on a small first group of properties and collections who want to shape the product with us. Tell us about your property and your current stack; the founder reads every submission.
