Frequently asked questions

No. Pentangle Connect for Stora is built and maintained by Pentangle. It integrates with the Stora Public API. Stora does not build, own, or operate this plugin.

Three customer-facing products on the same Stora connection: a WordPress plugin or website embed for quotes and bookings, a branded tenant app, and custom flows or CRM work when you need more than the template. Pricing is per site for website booking. The tenant app is POA.

No. WordPress is the self-serve plugin. Wix, Webflow, Duda and similar hosts use an embed we configure with you. The booking journey is the same; only the install path changes.

WordPress 6.4+, PHP 8.2+ with OpenSSL, and a Stora operator account. Your site should use HTTPS if you enable hosted checkout.

No. The plugin uses the Pentangle Connect broker at https://pentangle-connect.com. Stora OAuth credentials are stored on the broker, not in WordPress. Click Connect to Stora in Settings → Pentangle Connect and approve access in Stora BackOffice.

Scopes are requested and managed by the broker during partner onboarding - you do not configure them in WordPress. When you connect, Stora shows the permissions your integration needs (reading sites and units, creating contacts and deals, orders, webhooks, and related access). Approve the request to complete setup.

WordPress stores only an encrypted broker token. Stora access and refresh tokens live on https://pentangle-connect.com and are never written to your WordPress database. This follows Stora's recommended broker pattern for distributed plugins.

Not for a standard install. Broker URL and registration credentials are bundled with the plugin. Overrides in wp-config.php or the Advanced settings tab are only needed for staging environments, key rotation, or agency-managed deployments.

Open Settings → Pentangle Connect → Connection and click Reconnect. Complete the Stora authorisation flow again. Use Disconnect to revoke access entirely.

This usually means the Stora grant was revoked in BackOffice, or the refresh token expired. Click Reconnect and authorise again. If problems persist, try Disconnect, then Connect to Stora, followed by Sync catalog and Test connection. Enable debug logging on the Advanced tab and check your PHP error log for details.

On the Connection tab, click Sync catalog. Deal stages are listed on the Booking tab next to Default deal stage ID. Copy the dstg_… ID for the stage where new web leads should land.

Use the shortcode attribute site_id on location pages:

[stora_booking site_id="site_xxxxxxxx"]

You can also set a Default site ID on the Booking tab, or preselect a site in the Gutenberg block settings.

After syncing the catalog, open the Catalog tab. Hide entire locations with Hide from widget, or check specific unit types to limit what customers can book. Leave all unit types unchecked to show everything Stora marks as bookable.

Yes. On the Form fields tab, set each field to hidden, optional, or required. You can also add a custom questionnaire - answers are saved as a note on the Stora contact.

Use the Appearance tab to set colours, font family, and custom CSS. The widget inherits your theme font when font family is left blank.

Yes, when Stora marks them as bookable. Card layout is controlled on the Catalog tab (price, promotion, dimensions). If a promotion is missing, Sync catalog and Clear cache.

Enable GA4 events on the Advanced tab. The widget then fires step events you can map in GA4. You still need GA4 installed on the host page.

Enable Stora hosted checkout on the Booking tab (or pass checkout="true" in the shortcode). After a deal is created, the customer is redirected to Stora to pay. When payment completes, a webhook updates the deal - optionally moving it to your configured Deal stage after checkout.

Set a cancel page or HTTPS URL on the Booking tab. Stora requires HTTPS for checkout return URLs in production.

Not in the standard plugin. Card payment is Stora hosted checkout so the payment stays inside Stora’s billing. If you need a different payment path, that is custom work.

The contact and deal already exist in Stora from the quote step. They can pay later from Stora, or you follow them up. The widget can send them back to a cancel URL you choose.

Yes. On the Post-submit tab, enable Send quote email and choose the page that contains your booking shortcode (used for the reserve link). You can customise the subject, body, and logo. Placeholders such as {first_name}, {quote_details}, and {reserve_link} are supported.

A Stora contact and deal are created. By default the widget shows an inline thank-you message. You can redirect to a thank-you page instead, or send a quote confirmation email as described above.

Yes, if you have Stora notifications enabled. The plugin quote email is optional and extra - it is for the “here is your quote, tap to reserve” loop back to your site. Turn off whichever side you do not want duplicated.

Sync after connecting for the first time, whenever you add locations or unit types in Stora, or when deal stages change. Day-to-day availability is fetched live; the catalog sync is mainly for admin configuration (stage IDs, unit type lists, and visibility rules).

Use Clear cache on the Connection tab if you see stale pricing or availability during testing. For high-traffic sites, increase cache TTL on the Advanced tab.

Yes. When your Stora account has multiple locations, customers choose a site in the widget unless you preselect one with site_id or hide locations on the Catalog tab.

Same quote journey and Stora connection. WordPress gives you admin screens, shortcode and a block. Other platforms get a snippet we issue; we hold appearance and catalog settings on Connect rather than in wp-admin.

The snippet loads the widget when the booking page is opened. It does not crawl the rest of your site. If a page builder is already heavy, put the embed on a dedicated /book or /units page rather than the homepage.

Yes. They keep the theme and layout. We send the snippet, colours and the Stora connect step. Most agencies paste it in under an hour.

No. It is a branded template: name, icon, splash, colours and feature flags. New screens, custom illustration or a different information architecture is quoted separately. That split is spelled out on Connect for Mobile.

Yours. We list the app under your developer accounts on Apple and Google. We prepare the build and walk you through review.

No. Photos and inventory lists stay in the app. Units, invoices, subscriptions and unlock still use Stora.

The standard app is for existing tenants (access, billing, inventory). New quotes and bookings belong on the website plugin or embed. A book-from-app flow would be custom work.

Per Stora site (location), not per CMS. One WordPress install can serve several sites through the widget; we still bill per site. More than ten sites is a conversation, not a public volume table.

Yes. Both products use the Connect broker against the same operator. They are invoiced as separate lines.

Full setup instructions are in the documentation. For support, contact Pentangle or email hello@pentangle.co.uk.

Yes - try the booking flow on a live WordPress site.