Everything you need to know about the Clover WooCommerce Integration plugin. New here? Start with the setup guide or explore all features. Can't find your answer? Email us at support@cloverwoo.com.
Yes. You need to create an app in the Clover Developer Dashboard to get your App ID, App Secret, and PAKMS key. This takes about 5 minutes. The developer dashboard is free to use.
After purchase, you receive a separate email from support@cloverwoo.com (sent by our license server, separate from your Stripe receipt) containing your license key plus a private download link for the plugin. The license key has the format CLV-XXXX-XXXXXXXX-XXXXXXXX-XXXXXXXXXXXX. Paste it into the plugin's Settings page under the License section.
Most merchants are up and running in 15–30 minutes — the time accounts for creating the Clover developer app, completing OAuth, and configuring sync settings. Our setup guide walks you through every step.
Yes. You can switch between Sandbox and Production environments in the plugin settings. We recommend testing in Sandbox first before going live with your production Clover account.
Products (names, prices, descriptions, images, SKUs), inventory stock levels, orders, customers, categories, tax rates, modifier groups, and discounts. All data types support bidirectional sync.
Clover sends webhook events to your WordPress site whenever data changes (inventory updates, new orders, item modifications). The plugin processes these events instantly. You can also set up an hourly cron sync as a fallback.
You choose your conflict resolution strategy in settings: Clover wins (POS data takes priority), WooCommerce wins (online store data takes priority), or Newest wins (most recently updated record wins). This applies to all entity types.
Yes. WooCommerce variable products map to Clover item groups. Product attributes map to Clover options. Each variation syncs as a separate Clover item within the group.
Yes. You can filter sync by categories or exclude specific products. The selective sync feature lets you control exactly which data moves between platforms.
The plugin generates a hash of each record’s data and stores it. On subsequent syncs, it compares hashes to identify which records have actually changed. Unchanged records are skipped, dramatically reducing API calls and sync time.
The plugin reads stock from one configurable Clover location and syncs it to WooCommerce. WooCommerce core doesn't natively support multi-location stock, so the plugin keeps Woo aligned with whichever Clover location you designate as your online-fulfillment source.
It can. The Clover payment gateway supports all standard WooCommerce payment features including saved cards, refunds, tipping, and subscriptions. You can also run it alongside other gateways.
Yes. Card data is tokenized via Clover’s hosted iframe — card numbers never touch your server. This is the same PCI-compliant tokenization used by Clover’s own checkout system.
Yes. Customers can save payment methods for faster future checkout. Card tokens are stored securely by Clover. This is fully compatible with WooCommerce Subscriptions for recurring billing.
You can process full or partial refunds directly from the WooCommerce order screen. Refunds are automatically sent to Clover and reflected on the customer’s card statement.
In auth-only mode, the plugin places a hold on the customer’s card without actually charging it. You can then capture (charge) the payment later from the order admin screen. This is useful for restaurants, pre-orders, and made-to-order businesses.
Yes. You can show customizable tip options (preset percentages or custom amounts) at WooCommerce checkout. Tips are included in the Clover charge and appear on POS receipts.
Yes. When an order is placed on your WooCommerce store, it’s sent to Clover as a new order. If you have auto-print enabled on your Clover device, the order prints immediately on your kitchen or receipt printer.
Yes. You can add an order type selector at WooCommerce checkout. Order types map to your Clover order types and appear on printed receipts, so your staff knows how to handle each order.
Yes. Individual line items, modifiers, discounts, and order notes are all sent to Clover. Kitchen staff see exactly what was ordered, including any customizations.
Yes. The modifier picker does NOT generate variations — it uses cart-item metadata, so combinations are stored as line meta, not as new product rows. Your wp_posts table stays clean no matter how many combinations customers configure.
Yes. The auto-print toggle pushes online orders to your existing Clover printer the moment payment completes, with itemized modifiers rendered as proper line items — not a flat block of text.
Yes. The Delivery Zones feature accepts a comma-separated allow-list with * and ? wildcards. Works for US, UK, and Canadian postcode formats automatically. Customers outside the zone see a friendly “not in delivery area” message instead of a failed checkout.
Yes. Set per-day open and close hours (overnight supported, e.g. close at 2am). Outside hours, checkout is blocked and a “Closed” banner appears on shop pages automatically — no surprise orders that staff aren’t there to fulfill.
Every restaurant feature is opt-in via a toggle and off by default. Non-restaurant stores see zero change — turn on only what you need (e.g. retail shops typically use Delivery Zones and Minimum Order, skip the modifier picker entirely).
North America (US & Canada), Europe, and Latin America. Each region uses different API endpoints, and the plugin handles routing automatically based on your settings.
Yes. The plugin declares full compatibility with WooCommerce High-Performance Order Storage (custom order tables). It works with both the legacy post-based storage and the new HPOS system.
WordPress 5.8 or later, WooCommerce 6.0 or later, PHP 7.4 or later, and a Clover merchant account with API access.
The Clover payment gateway is designed to work with WooCommerce Subscriptions for recurring billing with saved cards. Code paths and unit tests cover renewal flow; we recommend testing your first real subscription cycle in a staging environment before going live.
$60 per month, billed monthly. This includes all features: full bidirectional sync, payment gateway, POS operations, webhooks, and support. No tiers, no feature limits, no per-transaction fees.
Yes — 7-day refund, no questions asked. Install it, push real traffic through it, and if it doesn’t fit your workflow within the first 7 days, contact us for a full refund. No long-term contracts.
If your payment fails, there’s a 7-day grace period where the plugin continues to function. After that, sync and payment features are disabled. Your existing WooCommerce data is never affected — nothing is deleted.
Yes. Cancel your subscription at any time through Stripe’s customer portal. No cancellation fees, no long-term contracts.
Go to Clover → Logs in your WordPress admin. You can filter by sync type, status, and search for specific messages. Logs include timestamps, entity types, and detailed error messages.
First, verify your Clover connection by clicking “Test Connection” on the settings page. Check that your license is active (green checkmark). Review the logs for error messages. Make sure your WordPress cron is running (or set up a server-level cron).
Email us at support@cloverwoo.com. Include your WordPress version, WooCommerce version, and any error messages from the sync logs.
All transactional emails (license delivery, download links, renewal receipts, account notifications) are sent from support@cloverwoo.com. Stripe sends a separate payment receipt from its own domain. Replies to support@cloverwoo.com route directly to our support team — just hit Reply if you have a question.
We're here to help. Reach out and we'll get back to you within 24 hours.