| 开发者 |
wpanchorbay
forhadkhan sankarsan arifac shuvendushekhar |
|---|---|
| 更新时间 | 2026年7月24日 03:26 |
| PHP版本: | 8.0 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPL-2.0-or-later |
| 版权网址: | 版权信息 |
Yes. CartBay requires WooCommerce 9.8 or higher and WordPress 6.6 or higher.
Yes. CartBay natively supports both the classic checkout and the WooCommerce Block Checkout. On Block Checkout the consent field appears in the contact section as a WooCommerce additional checkout field.
Open WooCommerce > CartBay > Templates and click Edit in WooCommerce for the email you want to change. Each recovery email is a native WooCommerce email, so you can edit its subject, heading, preheader, body, button text, and additional content, and it automatically uses your store's WooCommerce email logo, colors, and footer - with the same preview and test-send tools as your other WooCommerce emails. Supported placeholders include {restore_url}, {coupon_code}, {coupon_expiry}, and {unsubscribe_url}.
No. CartBay strictly uses WooCommerce-native order storage and is fully compatible with WooCommerce HPOS (High-Performance Order Storage). There are no custom database tables.
CartBay Free lets you reference a coupon you created in WooCommerce > Marketing > Coupons and include it in your recovery emails as plain text for the shopper to enter at checkout. Automatically generated, unique, single-use expiring coupons that auto-apply at checkout are part of CartBay Pro.
Yes. Capture and recovery work normally. CartBay Free does not auto-apply coupons; any coupon code you configure is included in the recovery email as plain text for the shopper to enter at checkout.
Enable Test Mode in WooCommerce > CartBay > Settings, then use Trigger Test Flow in the Templates section to schedule a sample recovery email about 30 seconds out and preview the email and its restore link. Use Test Mode on staging or during controlled QA, and disable it for normal production monitoring.
No. The free plugin does not contact WPAnchorBay licensing services or any third-party API. CartBay sends recovery emails through your WordPress/WooCommerce mail setup and sends capture requests only to your own site's local REST API endpoint at /wp-json/cartbay/v1/capture.
CartBay hands recovery emails to WordPress and WooCommerce for delivery - it does not send email itself. If a send fails, the cause is almost always your site's mail configuration (no SMTP plugin, misconfigured SMTP credentials, or your host blocking PHP mail()), not CartBay. Use the built-in Send Test Email tool in the setup wizard or under WooCommerce > CartBay > Notifications to check your configuration, and see https://docs.wpanchorbay.com/cartbay/getting-started/email-delivery-setup/ for help setting up reliable delivery (SMTP/transactional email and SPF, DKIM, and DMARC records).
Sent means WordPress/WooCommerce accepted the email for delivery. It does not by itself guarantee inbox delivery - that still depends on your SMTP configuration, domain authentication, and the receiving mailbox.
When a shopper gives consent at checkout, CartBay stores the email address, a cart snapshot, the checkout source, timestamps, notification history, and recovery metadata in WooCommerce-native order records. Restore and unsubscribe tokens are stored only as SHA-256 hashes, never in raw form. This data stays on your WordPress site unless your mail provider processes outgoing recovery emails. You can enable Delete Data on Uninstall in Settings to remove CartBay data when the plugin is deleted.
Documentation is at https://docs.wpanchorbay.com/cartbay/. For questions, please use the plugin's support forum on WordPress.org.
cartbay_offers_coupon_notice_relevant, so extensions can control the new Offers notices.