Mexican DTC runs on Mercado Libre, VTEX, WhatsApp — and CFDI 4.0 on every line.

VTEX or Shopify Plus, plus Mercado Pago, plus OXXO Pay, plus CFDI. A typical Mexican DTC at MXN 20-200M GMV runs VTEX (Coppel, Liverpool-tier upper mid-market) or Shopify Plus (Guadalajara and CDMX founder-led DTC), plus a CFDI 4.0 partner — usually Facturama, SW Sapien, Diverza or EDICOM — handling SAT validation per invoice.

Payments stack: Mercado Pago Checkout + Stripe Mexico + Conekta + Clip + OXXO Pay + Apple Pay + Google Pay, with `meses sin intereses` (MSI) credit-card promotions through Banamex, BBVA, Santander and HSBC México driving 18-30% of cart conversion above MXN 1,500.

Fulfilment: Estafeta for Norte + Bajío, Mercado Envíos for central Mexico, DHL urban, FedEx air, MRW for southeast. The single largest operational mistake we see: bolting a US-built Shopify theme onto a Mexican brand without CFDI 4.0 routing in the checkout — and watching every AP team in the country bounce the invoice.

The three-way marketplace split is the macro story. Amazon Mexico holds ~40% share; Mercado Libre ~30%; a long tail of Walmart, Coppel, Liverpool, El Palacio de Hierro, Elektra and the DTC layer holds the rest (eMarketer 2025). Mercado Libre 2025 FX-neutral GMV in Mexico grew +35% YoY with items sold +45%; the company invested USD 3.4B in Mexico in 2025 — its largest-ever Mexico year.

The mid-market Mexican DTC sits between Inditex-style verticals (Liverpool, El Palacio de Hierro), the Asian marketplaces (Temu, Shein, AliExpress driving the cross-border pressure), and the price-led marketplace incumbents. The realistic wedge is not 'beat Amazon on price' — it is brand-comparison and alternatives queries plus WhatsApp-first commerce flows the marketplaces structurally cannot run.

CFDI 4.0 + Carta Porte 3.0 is the operational floor. Every B2B / B2C / B2G transaction since 1 July 2023 must issue a CFDI 4.0 XML invoice digitally signed by an authorised PAC. Every shipment of goods inside Mexico since 1 April 2024 must include a Complemento Carta Porte 3.0 with the correct RFC, transport mode, origin, destination and merchandise codes.

Penalties run MXN 19,700-112,650 per malformed invoice; Carta Porte fines run MXN 880-17,000 per missing complement. A Mexican DTC AP-failure cascade: invoice malformed → AP team blocks payment → cash flow stalls → next month's inventory order delayed. CFDI is procurement-critical for any Mexican DTC selling to other businesses or accepting cross-border returns above MXN 50,000.

LFPDPPP is the new floor, not the ceiling. Mexico's federal data protection law (LFPDPPP) took force 21 March 2025, replacing INAI with the Secretaría Anticorrupción y Buen Gobierno (SABG). For Mexican DTC the practical effects: explicit consent for non-essential cookies, opt-in for commercial electronic messages, cross-border data-transfer treatment in every privacy notice for US-region tools, and a documented DPIA for any AI-driven personalisation.

The pattern that compounds: server-side GTM in an EU or Mexico region, Consent Mode v2 with all-denied defaults, and signed Art. 28-equivalent DPAs with every US-domiciled sub-processor are baseline procurement diligence in 2026 — particularly for any DTC serving B2B accounts that must pass the buyer's procurement screen.

WhatsApp commerce is a first-class channel in Mexico. 84% of Mexican online shoppers use smartphone as primary device (Truora 2024); WhatsApp penetration in Mexico is ~92% of internet users — the highest in LATAM after Brazil. Mexican consumers expect WhatsApp Business contact on every product detail page, conversational checkout for high-AOV items, and order-status updates through WhatsApp rather than email.

Yalo's Nestlé Mexico deployment lifted AOV 5.3% in six months on product recommendations; Coca-Cola FEMSA's distributor-ordering flow on Yalo + WhatsApp drove 30% AOV lift plus 50%+ cost saving versus the call-centre baseline. A Mexican DTC that ships only an email + SMS marketing stack leaks the highest-converting channel in the country.

Mexican-Spanish vocabulary is not Castilian Spanish. A Mexican DTC competing for AI-search citation faces the same 'Global Spanish' problem Spain faces but inverted — ChatGPT and Perplexity actually default toward Mexican-Spanish vocabulary because Mexico holds the largest Spanish-language internet population by absolute volume, but they still mix LatAm regional varieties (Argentine 'zapatillas' surfaces in Mexican answers, Chilean 'plata' in pricing answers).

A Mexican DTC publishing crisp es-MX-scoped hreflang, schema and llms.txt declarations captures the Mexico-coded citation surface that Castilian-Spanish content fails to claim.

Vocabulary that matters: `celular` (not móvil), `computadora` (not ordenador), `tienda en línea` (not tienda online), `carrito de compras` (not carrito de la compra), `meses sin intereses` (MSI — non-existent in Spain).

Buyer culture: founder + head of digital + finance director, with patriarch sign-off. Mexican DTC procurement runs founder-led in the Guadalajara Shopify Plus tier, committee-led with family-business patriarch sign-off in the Monterrey and Bajío industrial mid-market.

Cycles run 3-6 weeks for SaaS, 2-4 months for agency engagements, 4-6 months when family-business sign-off is in scope. References from CDMX DTC (Kavak, Cornershop, Justo, Ben & Frank), Guadalajara (Bonobos Mexico-equivalent founders), Monterrey industrial-family DTCs travel best. US-only references convert less reliably; Spanish references travel into Big-Four arms only.

Foundation. Shopify Plus or VTEX build with es-MX as default locale + EN for cross-border, CFDI 4.0 partner (Facturama, SW Sapien, Diverza or EDICOM) wired into checkout from commit one.

Mercado Pago Checkout + Conekta + Stripe Mexico + Clip + OXXO Pay + Apple Pay + Google Pay + Klarna México where present; `meses sin intereses` rendering at PDP and cart with the correct LSSI-equivalent transparency under Profeco rules. Product, Offer, Brand, AggregateRating, Review schema. Category pages with FAQ schema.

Programmatic landing pages per category × region × use-case ('mejores tenis veganos México', 'reloj artesanal CDMX envío 24h', 'crema solar mineral México OXXO Pay'). LFPDPPP-aligned consent gating, Profeco-compliant marketing electronic-message opt-in, IMMEX-ready RFC capture for B2B buyers, Estafeta + Mercado Envíos + DHL + 99minutos shipping integrations.

AI Search. Citation for 'mejor marca DTC México', 'alternativas a Mercado Libre', 'opiniones Ben & Frank', 'mejor tienda en línea ropa sostenible México', 'cómo elegir tenis de running México'. The Mexican-Spanish DTC surface is heavily weighted toward Mercado Libre product pages, Amazon Mexico, Reddit r/mexico, El Universal Lifestyle and Mexican beauty influencer content.

Brand-comparison and 'alternativas a X' queries are owned by everyone except the brands themselves. The 'Global Spanish' problem inverts in Mexico — ChatGPT defaults to Mexican-Spanish vocabulary because Mexico holds the largest LatAm-Spanish internet population, but mixes Argentine, Chilean and Colombian variants without es-MX scoping.

Foundation work targeting schema completeness, llms.txt with es-MX scope, FAQ schema in Mexican Spanish, and structured 'alternativas a X' + 'X vs Y' pages produces measurable lift in ChatGPT and Perplexity citation share within 60-90 days.

Voice Agent. Mexican-Spanish voice agent (es-MX) for VIP support, order status, returns, fit and size questions. Bilingual EN fallback for cross-border buyers. The VIP-segment economics mirror the LATAM pattern: top 5% of customers drive 25-40% of repeat GMV. EU-region or Mexico-region speech-to-text and LLM inference (AWS Mexico, Azure North-Mexico when GA, or Hetzner Frankfurt under LFPDPPP cross-border transfer treatment).

LFPDPPP-aligned consent capture; transcript storage with documented sub-processor list; human escalation path for any consequential decision. The leak being fixed: WhatsApp-arrived enquiries after the 6pm CDMX close that would otherwise sit in the inbox until next morning.

Workflow Ops. Automation across the Shopify Plus or VTEX + Mercado Libre + Amazon Seller Central + WhatsApp + Mercado Pago + Estafeta + Mercado Envíos + 99minutos stack. SKU, price, image and review sync across the three-way marketplace split. CFDI 4.0 invoice generation per order through Facturama or SW Sapien with the correct uso (G03 for resale), forma de pago, método de pago codes.

Carta Porte 3.0 complement on every shipment. LFPDPPP ROPA documentation generation. Profeco-compliant unsubscribe audit trails. IMMEX-aware RFC capture for B2B accounts. Replaces the Zapier-and-spreadsheets layer that breaks every time Mercado Libre updates its API or SAT publishes a new CFDI complemento.

Knowledge Bot. Trained on catalogue, sizing tables, ingredient and allergen tables, returns policy, CFDI 4.0 invoice request flow, LFPDPPP-aligned consent language. Internal-facing for support agents on a Gorgias or Zendesk copilot pattern; external-facing for shoppers on the website and the WhatsApp Business channel; bilingual es-MX + EN for cross-border.

Engineered for deflection-not-replacement: high-volume low-variance queries handled autonomously (status, returns, sizing, CFDI request), high-variance cases escalated to the human agent with full conversation context.

Growth Stack. Klaviyo flows in Mexican Spanish — not translated from Castilian, not translated from English. WhatsApp Business flows via Yalo, Cliengo or Meta Cloud API direct: welcome, abandoned-cart, post-purchase, win-back, VIP, MSI promotion windows. Meta and Google paid with server-side GTM and Enhanced Conversions hosted in an EU or Mexico region under LFPDPPP rules.

Organic SEO programmatic per category × region (CDMX, Monterrey, Guadalajara, Bajío, Sureste). AI-search optimisation as a standalone channel. Bundled when the brand has post-PMF momentum and needs cross-LATAM expansion into Colombia, Chile, Argentina off a Mexican spine.

The 'Global Spanish' problem inverts in Mexico — but still hurts. ChatGPT, Perplexity and Claude default toward Mexican-Spanish vocabulary because Mexico holds the largest LatAm-Spanish internet population, but they still mix Argentine, Chilean, Colombian and Castilian variants without es-MX scoping. Mexican DTC pages that fail to declare es-MX market scope in hreflang, structured data and llms.txt get answered with cross-regional vocabulary that confuses buyer intent.

The fix is mechanical and the ROI is fast: explicit es-MX scoping, Mexican-Spanish vocabulary discipline (`celular` not móvil, `computadora` not ordenador, `tienda en línea` not tienda online, `carrito de compras` not carrito de la compra, `meses sin intereses` natively), and a Mexico-coded llms.txt declaration.

Brand-comparison and alternatives queries are owned by Mercado Libre product pages and Reddit, not brands. 'Mejores tiendas en línea ropa sostenible México', 'alternativas a Mercado Libre', 'opiniones Ben & Frank reales', 'Justo vs Cornershop' produce ChatGPT, Perplexity and Google AI Overview answers dominated by Mercado Libre product pages, Reddit r/mexico, Forbes México and Expansión lifestyle sections.

Mexican DTC brands rarely publish their own structured comparison content. A Foundation effort shipping brand-owned, evidence-backed comparison pages with Product, AggregateRating and FAQ schema captures that surface at materially lower content cost than competing on price against Temu.

Compliance-aware queries are under-served in Mexican Spanish. '¿envían factura con RFC [marca DTC]?', '¿aceptan OXXO Pay [marca]?', '¿hacen meses sin intereses [marca]?', '¿envían a Tijuana / Mérida / Cancún [marca]?', '¿cómo devolver pedido [marca] en México?' produce answers from forums and SAT-help pages rather than the brand's own page.

A DTC that ships a structured Mexico-FAQ page with CFDI 4.0 invoice flow, MSI eligibility per bank, OXXO Pay availability, regional carrier routing and returns process becomes the canonical answer surface. CFDI compliance and AI-citation depth are the same engineering problem.

The composite picture: Mexican DTC infrastructure is mature, peso-priced, marketplace-pressured on three sides, WhatsApp-anchored by default, and structurally invisible inside brand-comparison Mexican-Spanish AI search, compliance-aware Mexican-Spanish AI search, and CFDI / MSI / OXXO-Pay-aware procurement AI search. That is Areza's wedge.