For Mews and Mews properties

Plekify for Mews

Talk to us

We're keen to build this. Plekify wants to work with Mews and Mews properties to bring Shopify-grade checkout, discovery and agent-readiness to hotels that run on Mews — on the operator's own domain, with Mews unchanged as the system of record. Nothing below describes something live today between Plekify and Mews. It describes what we want to build together, and an invitation to start.

Keep Mews as your system of record.

We'd add a storefront, checkout and discovery layer in front of it — on your domain, agent-ready, with Mews Payments settling every booking.

The idea

Mews stays exactly where it is: ARI, reservations, folio, payments — the operational core of the hotel. What we'd add sits in front of it: a storefront that reads availability and rate via the Mews Connector API, and writes reservations, folio and a tokenized charge straight back. Mews Payments settles. The guest never leaves your domain. This isn't a third-party OTA page — it's your own checkout, running on infrastructure built for commerce.

For the group / hotel

On-domain checkout. Guests book on your URL, not a redirect, with a checkout built on Shop Pay — 250M+ shoppers with saved details, and up to 50% higher conversion than guest checkout.

Itinerary bundling. For multi-property safari and DMC operators, we'd build bundling across properties into a single checkout flow — one cart, one payment, several Mews properties fulfilling.

Agent-ready booking. As agentic shopping grows — AI-referred orders on Shopify were up roughly 13× year-on-year in Q1 2026 — we want Mews properties positioned to accept agent-initiated bookings, not just human ones. This is roadmap, not shipped.

For Mews

Mews Payments settles. Mews Connector API stays the source of truth for ARI and reservations. Plekify is a tool that sits on top — not a booking engine competitor, not a channel that disintermediates Mews. Every reservation Plekify creates is a reservation inside Mews. We'd want this certified through the Mews Marketplace, built openly, and tested first on a single property before either side commits to anything wider.

Where we are

LIVE today (Plekify, independent of Mews):

Shopify-based checkout infrastructure, PCI-DSS Level 1, 99.9% platform uptime
UCP manifest support (/.well-known/ucp) — the open standard co-developed by Shopify and Google, live since Google added hotel booking to Universal Commerce Protocol in May 2026
Shop Pay checkout for participating merchants

INTENT — what this partnership would add:

Mews Connector API integration (read ARI, write reservations/folio/tokenized charge)
Mews Payments settlement wired into checkout
Itinerary bundling across multi-property Mews groups
Agent-ready booking flows for Mews properties

The ask, in four stages: