WooCommerce Connector — Installation
This guide walks you through installing and configuring the WooCommerce QuickRelease Connector. You need a WordPress site with WooCommerce active, and administrator access to both WordPress and QuickRelease.
Before you start
- WordPress 6.4 or newer with WooCommerce 8.9 or newer, on PHP 8.1–8.3.
- Your QuickRelease API key and tenant/company ID (ask QuickRelease support if you do not have them).
- The plugin package: wc-quickrelease-1.0.0.zip.
One site, one account
A single WordPress site connects to a single QuickRelease account. If you operate several QuickRelease accounts, use a separate WordPress site for each.
1. Install the plugin
- In WordPress, go to Plugins → Add New → Upload Plugin.
- Choose
wc-quickrelease-1.0.0.zipand click Install Now. - Click Activate.
A QuickRelease menu item appears in the WordPress admin sidebar.
2. Connect to QuickRelease
Open QuickRelease in the sidebar and go to the Connection tab:
| Field | What to enter |
|---|---|
| API base URL | https://api.quickrelease.aero (unless told otherwise) |
| API key | Your QuickRelease API key |
| Tenant / company ID | Your QuickRelease company ID |
| Environment | Production (use Development only for testing) |
Click Save, then click Test connection. A success message confirms the key works and shows how many regions were found. If it fails, re-check the key, ID and base URL.
3. Configure flight import
On the Flight import tab:
- Leave Enable import on and pick an interval (15 minutes is typical).
- Set a Default flight price (used when a flight has no price tag in QuickRelease).
- Choose the product type (usually Virtual) and the sold-out behaviour.
- Pick a Default featured image, and — after the first successful connection — a per-region image for each region (regions are loaded from QuickRelease automatically).
- Save. The first import runs within a minute or two; you can see the result at the bottom of the tab (“Last import”).
Prices you set by hand are respected
If you change a product’s price manually in WooCommerce, the next import will not overwrite it. QuickRelease price tags only apply when a product is first created.
4. Configure the checkout
On the Checkout tab, choose which passenger details to collect per seat (name, e-mail, date of birth, weight, and optionally city/phone) and which are required. Optionally keep one flight product per cart enabled.
5. Configure the booking push
On the Booking push tab:
- Keep Enable booking push on.
- Choose the trigger statuses (for example processing and completed) — the booking is sent to QuickRelease when an order reaches one of them.
- Set the default phone dial code for your country (used to normalise phone numbers), the payment type/status, and the payment amount source.
- Set the order status on failure (default on-hold) and a notification e-mail.
- Save.
6. Vouchers (optional)
On the Vouchers tab:
- To sell gift vouchers, enable Sell gift vouchers and set the voucher product category and default validity.
- To accept vouchers as payment, enable Accept vouchers as payment at checkout.
7. Advanced (optional)
On the Advanced tab:
- Show QR panel on order screen adds a QuickRelease panel to each order.
- Debug logging writes diagnostic entries to WooCommerce → Status → Logs (personal data masked). Turn it off again when you are done troubleshooting.
- Sentry DSN — paste a Sentry DSN to forward technical errors (masked) to your Sentry project. Leave empty to disable.
Verifying it works
- Wait for an import (or trigger one by saving the Import tab) and confirm flight products appear under Products.
- Place a test order for a flight product, fill in the passenger details, and complete it.
- Open the order and check the QuickRelease panel for the booking ID and a link to the booking in QuickRelease.
Troubleshooting
- Connection test fails — re-check the API key, company ID and base URL on the Connection tab.
- No products appear — confirm there are active flights in QuickRelease and that import is enabled; check “Last import” on the Import tab.
- Passenger fields missing on checkout — confirm Capture passenger details is on; both classic and block checkout are supported.
- A booking failed — the order shows the error in its QuickRelease panel and is moved to your configured failure status; fix the cause and change the order status again to retry (no duplicate is created).
- For deeper diagnostics, enable Debug logging and review WooCommerce → Status → Logs.