Title: MegaSend for WooCommerce Author: weblixtech Published: 22 fevereiro, 2026 Last modified: 16 outubro, 2026 --- Pesquisar plugins ![](https://ps.w.org/megasend-for-woocommerce/assets/banner-772x250.png?rev=3481948) ![](https://ps.w.org/megasend-for-woocommerce/assets/icon-256x256.png?rev=3481929) # MegaSend for WooCommerce Por [weblixtech](https://profiles.wordpress.org/weblixtech/) [Baixar](https://downloads.wordpress.org/plugin/megasend-for-woocommerce.1.0.28.zip) * [Detalhes](https://br.wordpress.org/plugins/megasend-for-woocommerce/#description) * [Avaliações](https://br.wordpress.org/plugins/megasend-for-woocommerce/#reviews) * [Instalação](https://br.wordpress.org/plugins/megasend-for-woocommerce/#installation) * [Desenvolvimento](https://br.wordpress.org/plugins/megasend-for-woocommerce/#developers) [Suporte](https://wordpress.org/support/plugin/megasend-for-woocommerce/) ## Descrição MegaSend for WooCommerce lets you recover abandoned carts and send automated order notifications through WhatsApp. Connect your MegaSend account, configure your WhatsApp message templates, and start engaging your customers on their preferred messaging platform. **Key Features:** * **Cart Abandonment Recovery** — Automatically detect abandoned carts and send WhatsApp recovery messages with a direct link to restore the cart. * **Follow-up Sequences** — Configure multi-step follow-up messages if the initial recovery message does not result in a completed order. * **Order Notifications** — Send WhatsApp messages for order created, payment complete, order fulfilled, order cancelled, and order refunded events. * **Template Mapping** — Map your approved WhatsApp Business message templates to WooCommerce events with a visual variable mapping interface. * **WhatsApp Preview** — See a real-time preview of your WhatsApp message as you configure the template mapping. * **Easy Onboarding** — A guided 3-step setup wizard gets you up and running quickly. * **GDPR Consent** — Optional consent checkbox on the checkout page before tracking cart data. * **Dashboard Analytics** — Track abandoned carts, recovery rates, revenue recovered, and message delivery status. * **Message Log** — Full log of all sent messages with status, recipient, template, and error details. **Requirements:** * A MegaSend account with an active WhatsApp Business API instance. * Approved WhatsApp message templates configured in your MegaSend dashboard. * WooCommerce 8.0 or later. ### External Services This plugin connects to the [MegaSend](https://megasend.io) WhatsApp Business API to send automated WhatsApp messages on behalf of your store. **Service:** [MegaSend](https://megasend.io) — WhatsApp Business API platform ** Service Provider:** Weblix Ltd **Data transmitted to MegaSend:** * Your MegaSend API token (for authentication). * Customer phone numbers (to deliver WhatsApp messages). * Template name and language (to identify which approved template to send). * Template variable values (customer name, order number, cart total, etc.) to populate the template. **When data is transmitted:** * When validating your API token during setup. * When fetching your approved WhatsApp message templates. * When sending a WhatsApp message for an abandoned cart or order event. **Terms of Service:** [https://megasend.io/terms](https://megasend.io/terms) ** Privacy Policy:** [https://megasend.io/privacy](https://megasend.io/privacy) ## Instalação 1. Upload the `megasend-for-woocommerce` folder to the `/wp-content/plugins/` directory. 2. Activate the plugin through the ‘Plugins’ menu in WordPress. 3. Click MegaSend in the WordPress admin menu and follow the setup wizard. 4. Enter your MegaSend API token and select your WhatsApp number. 5. Configure your abandoned cart template and optional order event templates. ## Perguntas frequentes ### Do I need a MegaSend account? Yes. This plugin requires a MegaSend account with an active WhatsApp Business API instance. You can sign up at [megasend.io](https://megasend.io). ### What WhatsApp templates can I use? You can use any approved WhatsApp Business message template from your MegaSend account. Templates must be approved by Meta before they can be sent. ### How does cart tracking work? The plugin tracks checkout form data (email, phone, name) via JavaScript as customers fill in the checkout form. This works with both the classic WooCommerce checkout and the block-based checkout. ### Is the plugin GDPR compliant? The plugin includes an optional GDPR consent checkbox that can be enabled in the Abandonment Settings. When enabled, cart data is only tracked after the customer explicitly consents. ### Can I customize when the abandoned cart message is sent? Yes. You can configure the abandonment threshold (in minutes) and set up multi-step follow-up sequences with custom delays. ### How much does it cost? The plugin itself is free. You need a MegaSend account with WhatsApp Business API access to send messages. Visit [megasend.io](https://megasend.io) for pricing details. ## Avaliações Não há avaliações para este plugin. ## Colaboradores e desenvolvedores “MegaSend for WooCommerce” é um programa de código aberto. As seguintes pessoas contribuíram para este plugin. Colaboradores * [ weblixtech ](https://profiles.wordpress.org/weblixtech/) [Traduzir o “MegaSend for WooCommerce” para seu idioma.](https://translate.wordpress.org/projects/wp-plugins/megasend-for-woocommerce) ### Interessado no desenvolvimento? [Navegue pelo código](https://plugins.trac.wordpress.org/browser/megasend-for-woocommerce/), consulte o [repositório SVN](https://plugins.svn.wordpress.org/megasend-for-woocommerce/) ou assine o [registro de desenvolvimento](https://plugins.trac.wordpress.org/log/megasend-for-woocommerce/) por [RSS](https://plugins.trac.wordpress.org/log/megasend-for-woocommerce/?limit=100&mode=stop_on_copy&format=rss). ## Registro de alterações #### 1.0.28 * Fix: When MegaSend cannot confirm a message in time, the Message Log now shows“ Sent, not confirmed” instead of “Failed”: the message may or may not have been sent. It is never sent again automatically, so a customer cannot get the same cart reminder or order update twice. * Fix: When your MegaSend subscription is not active, the Message Log, the order notes and the dashboard now say so, with a link to update billing, instead of“ Invalid or expired API token”. * Fix: A test message MegaSend could not confirm now says “Sent, but MegaSend could not confirm it; check WhatsApp before sending again” instead of showing an error. * Fix: Messages MegaSend holds back on purpose now show as “Not sent” with the reason, instead of “Failed”: the customer is muted (unsubscribed or blocked) in MegaSend, the customer opted out of marketing, a marketing template to a US number, or another app such as Meta’s business AI is handling the WhatsApp chat. * Fix: A muted customer or a WhatsApp account problem no longer shows “Invalid or expired API token”, which sent store owners looking for a problem with their MegaSend connection that did not exist. * Fix: Error details from MegaSend are shown as readable text instead of “Array”, and keep the WhatsApp error code, so the Message Log can explain more errors and what to do about them. #### 1.0.27 * New: Cart reminders and other marketing templates are no longer sent to US phone numbers, because WhatsApp does not deliver marketing messages to US numbers. These now show in the Message Log as “Not sent” with the reason, instead of failing. Utility templates such as order updates, and Canadian and other +1 numbers, are not affected. #### 1.0.26 * New: Each shipping method can now have its own complete message. Choose any of your templates — not just ones shaped like your standard message — and set its own fields, link button and header image, with the live preview and Send Test, in the same editor as your standard message. A new shipping-method message starts as a copy of your standard one, so you only change what differs. * Improved: The shipping-method screen now says in plain words what orders shipped each way receive, with Edit and “Use standard message” on every method. Changes take effect immediately; there is nothing left unsaved. * Fix: Shipping-method messages that WhatsApp would reject are now flagged on the message card and the dashboard, like standard messages. * Fix: When the same template exists in several languages, choosing one (for example the Hebrew copy) no longer selects another language with the same name. * Fix: Switching a message to a template with fewer variables no longer sends the old extra values, which made WhatsApp reject the message. #### 1.0.25 * Fix: The setup wizard could save a message that WhatsApp would reject on every send. It saved the template without its language (so a Hebrew template was stored as English), without its button link or header image, and without checking the variables. The wizard now takes you straight to the full message editor, which checks all of these. * Fix: The setup wizard set up “Order Placed”, which fires before the customer pays. It now sets up “Payment Received”, the confirmation most stores want. * Fix: The WhatsApp number picker listed SMS lines, web widgets, Messenger and Instagram as if they were WhatsApp numbers, and showed an internal Meta ID where the phone number should be. Picking one of those made every message fail. It now lists only WhatsApp numbers and never shows the internal ID. * Fix: Typing in the abandonment timing fields gave the wrong numbers — typing “ 30” produced 150 minutes. The fields now accept what you type and only check it when you leave the field. * Fix: Editing a paused message and saving it switched it back on, sending to customers without asking. A paused message now stays paused until you switch it on. * New: Send a test message before you save. Previously you could only test a message after it was already live for customers. The test uses your unsaved draft and messages no customers. * New: MegaSend now tells you when it can’t connect. A revoked API token or a MegaSend outage used to be invisible; the dashboard now shows a clear notice and what to do, and Settings shows your live connection status. * New: A setup checklist on the dashboard for new stores, instead of empty statistics. * Improved: The Message Log now shows times in your own timezone (they were shifted by your UTC offset), readable event names, a link to each order, and a plain- language reason and fix for common WhatsApp errors. Customers who could not be messaged (for example, no valid phone number) now appear in the log instead of silently disappearing. * Improved: Message editor: a “Payment link” field for “complete your payment” reminders, a Media Library picker for header images, fixed “Custom text” values, order totals with the currency symbol, and test numbers can be typed the local way (for example 050-123-4567). Link buttons now only offer values that work as the end of a link. * Improved: Shipping-specific messages: shipping methods are grouped by shipping zone, the ones with their own message are highlighted, and each shows the first line of its message. * Fix: Messages WhatsApp rejects are now flagged. If you set up cart reminders with an earlier version’s setup wizard, the message may have been saved without its values and in the wrong language (for example a Hebrew template saved as English), so WhatsApp rejected every send even though it showed as switched on. The message card and the dashboard now tell you — even if your store has been sending for a while — and “Fix it” corrects it in one save. * Fix: Send Test now sends exactly what real messages send. Previously a test could pass on custom text that WhatsApp then rejected for real customers (for example text containing a tab or several spaces in a row). Values WhatsApp would reject are now cleaned the same way for tests and real sends. * Fix: Shipping-specific messages only offer templates that can actually be sent with your standard message’s text, link and image. Previously a template needing a header image or a button link could be chosen and was then sent without it. * Fix: After updating, a store that was already connected no longer sees a “MegaSend is not set up yet” notice, and is no longer sent back into the setup wizard. * Security: Channel details shown in the admin are now limited to an approved list of fields, so any new sensitive field added to your MegaSend account can never reach the browser. * Improved: Accessibility — each message’s on/off switch now names its event for screen readers. * Fix: The plugin’s website link returned an error page, and the installation instructions named the wrong menu. #### 1.0.24 * New: Shipping-specific templates. Any order event can now send a different message depending on the delivery method the customer chose — a pickup confirmation for Local Pickup, a courier message for your flat-rate zones, and so on. Open an order event and choose “By shipping method”. Entirely optional: leave it alone and every message behaves exactly as before. * Methods are read straight from your WooCommerce shipping zones, so you pick from your own delivery options by name and never type an ID. Anything you leave on“ Use the standard message” keeps getting the event’s normal template. * Templates are matched on WooCommerce’s internal method and zone identity, not on the method’s name, so renaming a delivery option in WooCommerce does not change which message goes out. Rules for a delivery method you later delete are flagged in the admin and kept until you remove them — those orders fall back to the standard message rather than losing it. #### 1.0.23 * New: Shipment tracking variables for order messages — Shipping Carrier, Tracking Number, Tracking Link and Tracking Text. Read from HFD, UPS, Datalogics (K-Express) and WooCommerce Shipment Tracking / AST order data, so an “Order Completed” template can include the customer’s tracking link. Tolerant of every storage shape those plugins use; a tracking lookup can never break the message or the order screen. * Security: The Instances list returned to the admin screen no longer includes the WhatsApp access token or app secret. #### 1.0.22 * Fix: On stores running a page cache (LiteSpeed, WP Rocket, Cloudflare, or a host- level cache), the admin screens could keep showing the old data after a change. Adding a follow-up step, saving a template mapping or deleting a step worked correctly, but the screen refreshed itself from a cached copy taken before the change — so the new step never appeared and the action looked like it had done nothing. The plugin’s admin screens now bypass every caching layer when reloading data. This was the root cause of the “Add Follow-up Step does nothing” reports. #### 1.0.21 * Fix: The “+ Add Follow-up Step” button appeared to do nothing. Adding, removing or editing a step reloaded the sequence, and the reload replaced the entire list— including the button itself — with a loading spinner. On a long settings screen the page collapsed by a couple of thousand pixels mid-click, moving the button away and leaving the newly added step off-screen. The list now stays in place while it refreshes, and a newly added step is scrolled into view. * Fix: Confirmation for follow-up actions appeared at the very top of the Abandonment Settings screen, several screens above the controls that triggered them. Confirmations and errors now appear inside the Follow-up Sequence panel, next to the action. * Improvement: Database errors are no longer shown verbatim in the admin screens. Store owners get a plain explanation of what failed; the technical detail goes to the site’s error log for support, and is still shown on screen when WP_DEBUG is enabled. #### 1.0.20 * Fix: Saving a follow-up step or a template mapping could report success while the change was silently discarded. A failed database write is now reported as an error instead of returning the previously stored configuration as if it had just been saved. * Fix: Errors from the “Add Follow-up Step”, “Remove” and per-step controls appeared at the very top of the Abandonment Settings screen, far below the fold from the buttons themselves — so a failed action looked like an unresponsive button. Follow- up errors now appear directly inside the Follow-up Sequence panel. * Fix: Every server error was replaced in the admin screens with the generic text“ The server encountered an error. Please try again later.”, hiding the actual reason (expired API token, template not found, MegaSend API outage). The real message is now shown. * Fix: Mapping a template that is already mapped to the same event now returns a clear explanation instead of an unexplained server error. * Fix: Database schema is re-verified on upgrade. Follow-up step columns added in earlier releases (audience conditions, minimum cart value) are now explicitly checked and added if a host’s schema update had silently skipped them — this could make adding or configuring follow-up steps fail with an unexplained error. * Fix: Removed default values from TEXT columns, which some MySQL configurations reject outright, causing table creation to fail silently on those hosts. * Improvement: Database errors on admin screens now include the underlying reason and are written to the site’s error log, so a store owner or support can identify the cause without enabling debug mode. #### 1.0.19 * Fix: Closed a remaining timing case where a customer who already completed and paid for an order could still receive an abandoned-cart WhatsApp about one abandonment- threshold later. The post-purchase safety check now suppresses the message whenever the customer placed a paid order in the last 24 hours (matched by phone) — even when a late, post-checkout tracking ping created a fresh cart record moments after the order, which previously fell outside the lookback window. Follow-up to the 1.0.18 fix. #### 1.0.18 * Fix: Customers who already completed and paid for their order could still receive an abandoned-cart WhatsApp roughly half an hour later. As a shopper leaves the checkout page after ordering — or simply switches apps / locks the phone on mobile— the browser sends one last tracking ping, which could revive the just-completed cart so the abandonment detector treated it as newly abandoned. A converted cart is no longer revived by that trailing ping. * Fix: The safety check that suppresses abandonment messages for customers who already ordered now matches by phone number (both international and national form), not email alone — so it also protects phone-only carts, which are the norm for WhatsApp-first checkouts. The check is anchored to when the cart was first seen, so a post-order tracking ping can no longer push the order outside its window. #### 1.0.17 * Fix: Returning-customer detection for audience-targeted follow-ups now works when a customer’s order phone was saved in national format (e.g. 0546162881) while their tracked cart stored the international form (+972546162881). The 1.0.16 matching change compared only the international form, which could mis-classify a genuinely returning customer as new (and skew lifetime-value targeting) in markets where checkout phones are entered nationally. Order phones are now matched against both the international and national forms by exact equality — still with no risk of matching a different customer who merely shares trailing digits. #### 1.0.16 * Security/Privacy fix: Resolved a cross-customer data exposure where a recovery link could open the checkout pre-filled with a different shopper’s phone number. On stores behind a full-page/edge cache (e.g. Cloudflare “Cache Everything”), the tracking session ID was previously baked into the cached checkout HTML and shared between visitors, causing two shoppers to write to the same tracked-cart row. * Fix: The tracking session ID is now established per browser on the client side( at the same cookie path/domain the server uses), so a cached page can never make two customers share an identity. Incoming session IDs are format-validated server- side. * Fix: The checkout page and the cart-recovery flow now emit explicit no-cache directives (`DONOTCACHEPAGE` + `Cache-Control: no-store, private`) so per-customer billing data is never stored by a page or edge cache. * Security: Recovery links now carry a signed 7-day expiry and can no longer be replayed indefinitely. Links already delivered before this update continue to work. Expired links restore your saved items but no longer pre-fill personal details. * Fix: Tightened recovery matching — order-to-cart and sibling-cart matching now compare the full phone number for equality instead of a trailing-digit “contains” match, so a different customer who merely shares the last digits of a phone number can no longer be matched. Audience targeting stats use the same exact match. * Improved: The cart-recovery experience no longer dead-ends on a blank checkout. Customers now see a friendly message when a link has expired, when saved items have sold out, when only some items could be restored, and a reassuring confirmation on success — never exposing any personal data. * Hardening: The recovery handler guards against uninitialised WooCommerce session/ cart/customer objects; the unload-time tracking beacon reports the real GDPR consent state; and all admin-screen strings now use the correct text domain so translations load. #### 1.0.15 * New: Per-step audience targeting for follow-up sequences. Each follow-up can now be sent only to carts matching specific conditions: * New: **Cart total range** — set a minimum and/or maximum cart value per step. * New: **Customer type** — target only new customers (no prior paid orders) or returning customers (1+ prior paid orders), matched by phone number. * New: **Customer lifetime value range** — target VIP customers above a threshold or first-timers below it. * New: **Minimum item count** — only send to carts with N or more items. * Improved: All audience matching is by phone number (E.164) — works equally for guest checkouts and registered customers, fully aligned with the WhatsApp-first model. * Improved: HPOS-native — phone matching uses the WooCommerce custom orders table directly when HPOS is enabled, classic postmeta when not. * DB: Schema upgrade adds a `conditions` column to the follow-up steps table. Existing steps continue to work unchanged (legacy `min_cart_value` is read transparently). #### 1.0.14 * Fix: Customers no longer receive abandoned cart messages after successfully placing an order. When a customer retried checkout across multiple sessions, sibling cart rows for the same email/phone were left in `active` state and could trigger a stale abandonment message minutes after the order completed. * Fix: Recovery_Tracker now sweeps both `active` and `abandoned` sibling carts when an order is paid — active siblings transition to `completed`, abandoned siblings to `recovered`. * Fix: Detector now performs a defense-in-depth check before sending the initial abandonment message: if the customer has placed a paid order since the cart’s last activity, the cart is marked `recovered` and the message is suppressed. #### 1.0.13 * Fix: “Order Cancelled” message is now suppressed if the customer already has a successful (paid) order — prevents confusing notifications when a failed order is auto-cancelled after the customer already retried and paid * UX: Redesigned the Template Mappings event cards for maximum clarity — each card now shows a lifecycle timeline (Checkout Placed Paid Shipped Done), a color- coded payment status pill, a plain-language example scenario, and a “Best for” recommendation line * UX: Payment status pills (“Not paid yet” / “Payment confirmed” / “Paid & shipped”) make it visually impossible to confuse Order Placed with Payment Received * UX: Left accent stripe on each card is colored by payment stage (amber for unpaid, green for paid, blue for shipped) for at-a-glance scanning #### 1.0.12 * UX: Renamed Template Mapping event labels for clarity: “Order Created” “Order Placed (Awaiting Payment)” and “Payment Complete” “Payment Received” * UX: Added status badges (UNPAID / PAID / SHIPPED) on event cards so admins can see at a glance which payment stage each event fires at * UX: Inline warning on “Order Placed” when active — explains that message fires BEFORE payment is confirmed, so abandoned payments still receive it * UX: Page-level intro explains the WooCommerce event lifecycle and recommends “ Payment Received” for most stores * UX: Conflict warning when both “Order Placed” and “Payment Received” are active— prevents accidental double-messaging * UX: Expanded descriptions on each event card with clearer wording and use-case guidance #### 1.0.11 * Fix: Duplicate order event messages — dedup now re-fetches the order to bypass stale in-memory meta caches when multiple WooCommerce hooks fire in the same request * Fix: Atomic dedup using direct DB insert (HPOS + classic compatible) prevents the read-then-write race between woocommerce_payment_complete and woocommerce_order_status_processing * Added: Second-layer dedup in the Action Scheduler callback queries message_log by order_id + event_type * Added: order_id column on megasend_message_log with composite index (order_id, event_type) for fast dedup lookups * DB: Schema upgrade runs automatically on plugin update (dbDelta adds new column and index) #### 1.0.10 * Fix: Revenue Recovered dashboard card now uses locale-aware currency formatting with thousand separators * Fix: Cart total values are clamped to a sensible maximum (9,999,999.99) to prevent corrupt WooCommerce session data from poisoning analytics * Fix: Dashboard SUM queries ignore absurd cart_total values so existing bad rows don’t break the display * Improved: Stats card value now wraps gracefully on long numbers instead of overflowing #### 1.0.9 * Fix: Cart recovery links now correctly restore cart items — session is explicitly persisted before redirect * Fix: Validate product availability during recovery — skip out-of-stock or deleted items gracefully * Improved: Recovery handler moved from template_redirect to wp_loaded for proper WooCommerce session timing #### 1.0.8 * Fix: Cart tracking now returns actual DB error when insert fails instead of silent success * Improved: Better error diagnostics for cart tracking issues #### 1.0.7 * New: UTM tracking parameters for cart recovery URLs — configure utm_source, utm_medium, utm_campaign, utm_term, and utm_content in the Abandonment Settings. * New: Dynamic placeholders ({cart_id}, {session_id}) supported in UTM values. * New: Smart defaults for new installs (megasend/whatsapp/cart_recovery). #### 1.0.6 * New: Payment abandonment detection — customers who place an order but never complete payment (PayPal redirect, bank transfer, etc.) now receive abandonment messages after the threshold period. * Fix: Orders with “pending” status no longer prematurely mark tracked carts as completed. Cart status is only finalized when payment is confirmed. * Fix: Cancelled and failed orders now re-enable the linked cart for abandonment detection. * New: Order status transition hooks (processing, completed, on-hold, cancelled, failed) for smarter cart lifecycle management. #### 1.0.5 * Fix: Corrected wc-ajax URL generation for cart tracking on all hosting environments. #### 1.0.4 * Fix: Cart tracking now uses WooCommerce wc-ajax endpoint instead of admin-ajax. php, resolving silent tracking failures caused by caching plugins (WP Rocket, LiteSpeed Cache, Cloudflare, etc.) serving stale nonces. * Fix: GDPR consent is now properly enforced on page unload beacon tracking. * Fix: AJAX retries only fire on actual network failures, not on HTTP error responses. * New: Debug logging for abandonment detection pipeline when WP_DEBUG_LOG is enabled. #### 1.0.3 * Fix: Checkout tracking script now loads reliably on all themes, including WoodMart, Flatsome, and Elementor-based checkouts that override WooCommerce templates. #### 1.0.2 * New: Marketing Consent Settings — optionally restrict abandonment messages to customers who opted into SMS/WhatsApp marketing via the checkout consent checkbox. * New: GDPR consent status now stored in database for compliance auditing. * New: Admin warning when Marketing Consent is enabled without GDPR checkbox. #### 1.0.1 * Fix: Cart recovery now displays phone number in local format instead of E.164( e.g., “054-616-2881” instead of “+972546162881”). * Fix: Cart recovery now restores all checkout fields (country, city, address, postcode). * Fix: Order event dispatcher now correctly skips draft orders created by Block Checkout. * Fix: Added fallback payment hook for gateways that bypass payment_complete(). * Fix: Optimized event deduplication to avoid redundant database lookups. #### 1.0.0 * Initial release. * Cart abandonment detection with configurable threshold. * Follow-up message sequences. * Order event notifications (created, paid, fulfilled, cancelled, refunded). * Template mapping with visual variable mapping and WhatsApp preview. * 3-step onboarding wizard. * Dashboard analytics and message log. * GDPR consent checkbox support. * WooCommerce HPOS and Block Checkout compatibility. ## Meta * Versão **1.0.28** * Última atualização **12 horas atrás** * Instalações ativas **Menos de 10** * Versão do WordPress ** 6.2 ou superior ** * Testado até **7.1.3** * Versão do PHP ** 8.1 ou superior ** * Idioma * [English (US)](https://wordpress.org/plugins/megasend-for-woocommerce/) * Tags * [abandoned cart](https://br.wordpress.org/plugins/tags/abandoned-cart/)[cart recovery](https://br.wordpress.org/plugins/tags/cart-recovery/) [order notifications](https://br.wordpress.org/plugins/tags/order-notifications/) [whatsapp](https://br.wordpress.org/plugins/tags/whatsapp/)[woocommerce](https://br.wordpress.org/plugins/tags/woocommerce/) * [Visualização avançada](https://br.wordpress.org/plugins/megasend-for-woocommerce/advanced/) ## Classificações Ainda não foi enviada nenhuma avaliação. [Sua avaliação](https://wordpress.org/support/plugin/megasend-for-woocommerce/reviews/#new-post) [Ver todas avaliações](https://wordpress.org/support/plugin/megasend-for-woocommerce/reviews/) ## Colaboradores * [ weblixtech ](https://profiles.wordpress.org/weblixtech/) ## Suporte Tem algo a dizer? Precisa de ajuda? [Ver fórum de suporte](https://wordpress.org/support/plugin/megasend-for-woocommerce/)