WhatsApp Business API Integration: Brazilian E-commerce Guide 2026

Brazilian e-commerce runs on four dominant platforms: VTEX (mid-market and enterprise), Tray (SMB to mid-market), Nuvemshop (SMB), and Loja Integrada (SMB). Each platform requires a specific integration pattern to connect WhatsApp Business API for abandoned cart recovery, order confirmation, shipping updates, NF-e delivery, and Pix checkout inside the WhatsApp conversation. This guide walks through native connector setup for all four Brazilian platforms plus Shopify Brasil and WooCommerce, with code examples and event-by-event mapping.

Quick Answer: How Does WhatsApp Business API Integrate with Brazilian E-commerce Platforms?

For the four dominant Brazilian e-commerce platforms, native connectors through Message Central's WhatsAppNow handle the integration end-to-end: VTEX via VTEX IO app, Tray via REST webhook bridge, Nuvemshop via App Store integration, and Loja Integrada via direct API. The connector receives platform events (cart abandoned, order created, payment confirmed, shipped) and triggers WhatsApp templates plus Pix charge generation accordingly. Setup typically takes 2-5 business days. For platforms without native connector (Shopify Brasil, WooCommerce, custom Magento), REST API integration with webhook bridge is the standard path — typically 1-2 weeks of engineering work. See our WhatsApp Business API in Brazil platform.

The Four Brazilian E-commerce Platforms That Matter

VTEX

Brazilian-born e-commerce platform with the largest enterprise and mid-market footprint in Brazil. Used by Magazine Luiza, Coca-Cola, Walmart Brasil, Whirlpool, and many large brands. Built on VTEX IO (a TypeScript-based development platform) with full headless commerce capability. Native WhatsApp connector via VTEX IO app available through Message Central. Best fit for mid-market to enterprise Brazilian retailers.

Tray

Brazilian e-commerce platform owned by Locaweb, focused on SMB to mid-market. Strong omnichannel integration with marketplaces (Mercado Livre, Amazon Brasil). REST API for product, order, and cart event subscriptions. Native WhatsApp connector through Message Central via webhook bridge. Best fit for SMB to mid-market Brazilian online stores.

Nuvemshop

Latin America-focused SaaS e-commerce platform (formerly Tiendanube), strong Argentine and Brazilian presence. App Store ecosystem with hundreds of native integrations. WhatsApp connector available through Message Central as a Nuvemshop App. Best fit for SMB Latin American multi-country sellers.

Loja Integrada

Brazilian SMB e-commerce platform with strong free-tier strategy. Hundreds of thousands of active Brazilian stores. REST API for cart and order events. Direct integration with Message Central. Best fit for Brazilian SMB and microbusiness sellers.

VTEX Integration with WhatsApp Business API

VTEX IO apps are the recommended integration path for the WhatsApp Business API. Message Central provides a published VTEX IO app that handles the standard event flow:

• Cart abandoned event (from Order Form Configuration): triggers 3-touch WhatsApp recovery sequence (1h, 24h, 72h)
• Order created event: triggers order confirmation template via WhatsApp utility category
• Payment confirmed event: triggers payment receipt + NF-e delivery template
• Order shipped event: triggers tracking code template with delivery estimate
• Order delivered event: triggers NPS or review request after 72-hour delay

Setup: See VTEX developer documentation.

Tray Integration with WhatsApp Business API

Tray uses webhook subscriptions for event-driven integration. Message Central provides a webhook bridge that listens for Tray events and triggers the appropriate WhatsApp template:

• Subscribe to Tray webhooks for: order_created, order_paid, order_shipped, order_delivered, cart_abandoned (where supported by your Tray plan)
• Configure Message Central webhook endpoint and signature secret in Tray admin
• Map each event to a Meta-approved Brazilian Portuguese template
• Test with sandbox orders before going live

Setup time: 1-2 business days for standard event mapping. Custom flows (specific segmentation logic, upsell triggers) add another 2-3 days.

Nuvemshop Integration with WhatsApp Business API

Nuvemshop uses an App Store model.

• Install Message Central WhatsApp Now app from Nuvemshop App Store
• Grant required permissions (read orders, read customers, read products, send notifications)
• Configure WhatsApp Business API key from Message Central dashboard
• Choose which Brazilian Portuguese templates fire on which Nuvemshop events
• Activate — typical go-live in 1-2 days

For Argentine, Mexican, and Colombian Nuvemshop stores, the same connector supports multi-country WhatsApp routing with local sender IDs.

Loja Integrada Integration with WhatsApp Business API

Loja Integrada exposes a REST API for order and cart events. Integration with Message Central WhatsApp Business API:

• Generate Loja Integrada API key in admin panel
• Configure Message Central connector with Loja Integrada credentials
• Map order/cart events to WhatsApp templates
• For abandoned cart, configure recovery sequence timing (1h, 24h, 72h)
• For order confirmation, attach Pix charge generation for unpaid orders

Loja Integrada SMB stores typically go live in 1-2 days. Higher-volume stores may need custom template approval (4-hour Meta approval cycle via Message Central pre-screening).

Shopify Brasil and WooCommerce Integration

For Brazilian businesses on Shopify or WooCommerce, REST API integration is the path:

Shopify Brasil

Use Shopify Webhooks for the following events: checkouts/create, checkouts/update, orders/create, orders/paid, orders/fulfilled. Configure HTTPS endpoint at Message Central API that receives and transforms the Shopify payload into WhatsApp template send. Shopify Brasil supports BRL pricing and integrates with Brazilian PSPs (Mercado Pago, PagSeguro) for Pix.

WooCommerce

Use WooCommerce REST API + webhook subscriptions. Custom webhook bridge required if no Message Central WooCommerce plugin available. Typical engineering work: 1-2 weeks.

Event-by-Event Integration Map

For all platforms, the standard event-to-WhatsApp mapping:

Cart abandoned (1h): Marketing template, soft reminder, no discount. Includes product image and one-tap return-to-cart button.

Cart abandoned (24h): Marketing template with 5-10% discount or free shipping. Pix charge generation option in same conversation.

Cart abandoned (72h): Marketing template with final 10-15% discount. Last touch, no further messages after this for this specific cart.

Order created (unpaid): Utility template with order summary and Pix charge for payment.

Payment confirmed: Utility template with payment receipt, order number, expected delivery date.

NF-e generated: Utility template with NF-e PDF attachment or download link.

Order shipped: Utility template with carrier name, tracking code, estimated delivery.

Order delivered: Service category, post-delivery NPS or review request (after 24-72 hour delay).

LGPD and Template Approval Considerations

Each event type maps to a Meta conversation category with different LGPD requirements:

• Abandoned cart messages: marketing category — require explicit WhatsApp opt-in under LGPD
• Order confirmation, payment receipt, shipping, NF-e: utility category — fall under contract execution legal basis, no separate opt-in needed
• NPS/review request: service category if inside 24-hour window, marketing if outside (requires opt-in)

See our LGPD WhatsApp Business compliance guide.

Common Integration Mistakes

Mistake 1: Sending abandoned cart messages without WhatsApp opt-in

‍Email opt-in does not cover WhatsApp under LGPD. Fix: collect WhatsApp opt-in at checkout (non-pre-checked checkbox).

Mistake 2: Confusing utility and marketing categories

‍Sending a promotional offer in a utility template gets rejected by Meta and damages Quality Rating. Fix: keep transactional content in utility, promotional in marketing.

Mistake 3: No idempotency on webhook handler

‍Webhook retries from VTEX, Tray, Nuvemshop can fire the same event multiple times. Fix: implement idempotency keys.

Mistake 4: Sending NF-e immediately on payment confirmation

‍Pix settles in seconds but fulfillment may not have written the order yet. Fix: 30-60 second buffer.

External Authority References

VTEX developer documentation. Tray Brazil API documentation. Nuvemshop developer documentation. Meta WhatsApp Cloud API documentation. BACEN Pix specifications.

Frequently Asked Questions

How long does WhatsApp Business API integration with Brazilian e-commerce platforms take?

For the four major Brazilian platforms with native connectors, integration typically takes 2-5 business days. VTEX via VTEX IO app: 2-3 days. Tray via webhook bridge: 1-2 days. Nuvemshop via App Store: 1-2 days. Loja Integrada via REST API: 1-2 days. Platforms without native connector (Shopify Brasil, WooCommerce, custom Magento) typically take 1-2 weeks of engineering work.

Which Brazilian e-commerce platforms support native WhatsApp Business API integration?

The four dominant Brazilian platforms all support native WhatsApp Business API integration: VTEX, Tray, Nuvemshop, and Loja Integrada. Shopify Brasil and WooCommerce are supported via REST API integration (custom webhook bridge required). Other platforms (Vnda, Linx, Magento custom builds) can integrate via webhook + REST API patterns.

Do I need separate LGPD opt-in for abandoned cart messages vs order confirmation?

Yes for abandoned cart, no for order confirmation. Abandoned cart messages are classified by Meta as marketing category and by LGPD as direct marketing, requiring explicit WhatsApp opt-in. Order confirmation, payment receipt, shipping notification, and NF-e delivery are utility category under contract execution legal basis, requiring no separate opt-in.

Can I integrate Pix payments inside the WhatsApp conversation via my e-commerce platform?

Yes. For all four major Brazilian platforms, Message Central integrations support Pix charge generation inside the WhatsApp conversation. When a customer responds to an abandoned cart message with purchase intent, the connector generates a Pix QR code and BR Code inside the conversation. Customer pays in their banking app and the e-commerce platform receives payment confirmation via PSP webhook. See our Pix payments guide.

What is the typical engineering effort for WhatsApp Business API integration with VTEX?

For VTEX, integration via the Message Central WhatsApp IO app takes 2-3 business days end-to-end: install the app from the VTEX App Store, configure API key, map event-to-template (cart abandoned, order created, payment confirmed, shipped, delivered), test with sandbox orders, and go live. Custom flows (specific segmentation logic, upsell triggers, multi-store routing) add another 2-5 days of engineering work.

Next Steps

To integrate the WhatsApp Business API with your Brazilian e-commerce platform, start with the WhatsApp Business API in Brazil platform page. For Pix integration to close sales inside the conversation, see the Pix payments guide. For abandoned cart recovery strategy, see the cart recovery guide. For Click-to-WhatsApp Ads to feed your funnel, see the CTWA guide. For LGPD compliance, see the LGPD guide.