Adobe Commerce for Telecom Companies in Mexico

The telecommunications sector in Mexico operates in one of the most commercially complex ecosystems that exists: more than 130 million active mobile lines (IFT, Q1 2026), mobile phone penetration exceeding 90% of the population, and competition between operators so fierce that every tenth of a percentage point in retention and every peso of ARPU (Average Revenue Per User) matters more than in almost any other industry.

In that environment, a telco's digital store is no longer a complementary channel. It is the primary point of contact for activations, upgrades, number portability, contract renewals, and device sales — and it has to work flawlessly for millions of simultaneous users whose expectations have been shaped by the best apps in the world.

WolfSellers works with companies in the telecommunications sector that face exactly that challenge: transforming catalogs of thousands of SKUs — plans, devices, accessories, value-added services — into coherent purchase experiences that convert on web, app, and in physical stores alike. In this article we explain how Adobe Commerce (formerly Magento) — powered by Adobe Experience Platform (AEP) and the full Adobe Experience Cloud stack — meets the specific requirements of a telecom operator, from catalog management to recurring billing and real-time personalization.

The unique challenges of telecom ecommerce in Mexico

A telco's ecommerce operation looks nothing like a fashion retailer's or a generic electronics store's. It has its own rules and its own sources of complexity:

Dynamic, highly relational catalogs

A mid-size operator might simultaneously manage 300 active plans (prepaid, individual postpaid, family postpaid, basic business, premium corporate) × 200 active devices × 80 compatible accessories × 15 value-added services (cloud storage, security bundles, streaming, device insurance). The resulting combination space is not just hard to present clearly — it is hard to keep accurate. Plan prices change weekly; devices go in and out of stock in hours; data plans are updated every quarter in response to competitive moves.

Prices conditioned by buyer profile

In telecommunications, the price a customer sees is never universal. A new postpaid customer sees a different price than a customer whose contract is about to expire, than someone porting their number from another carrier, or than a corporate account with a 50-line master agreement. Four profiles, four price structures, with discounts that depend on external variables such as payment history, contract type, and tenure. The platform has to resolve that logic in real time, for every session, without errors.

Mexico's specific regulatory framework

Mexico's Federal Telecommunications and Broadcasting Law (LFTR) and the IFT's guidelines impose concrete requirements: number portability must be processed within defined deadlines; plan information must be displayed with full cost transparency; adhesion contracts require documented and downloadable consent. The ecommerce platform has to support these regulatory flows without sacrificing the purchase experience.

Multiple buyer profiles with distinct journeys

A telco sells simultaneously to profiles with radically different needs:

• Individual consumer (B2C): looking for the best price on unlimited data, comparing coverage by city, wanting to activate a new smartphone without going to a store.
• Family (B2C family): needs a multi-line plan with parental controls, a single invoice, and the ability to add or remove lines without calling an agent.
• Small business (B2B simplified): requires 5–50 lines with centralized management, electronic invoice (CFDI 4.0), and per-line consumption visibility.
• Corporate enterprise (B2B enterprise): demands master contracts with SLAs, device fleet management (MDM), a multi-user administration portal, and consolidated usage reporting.

Each profile has a different funnel, a different sales argument, and a different friction point. A platform that cannot serve all of them from the same architecture forces the operator to maintain multiple stores with duplicated business logic — generating inconsistencies and massive technical debt.

BYOD and portability as traffic drivers

The Mexican market has a particular characteristic: BYOD (Bring Your Own Device) is widespread among prepaid and mid-segment postpaid users. The portability flow — checking eligibility, initiating the transfer, confirming the number, selecting the new plan, activating the SIM — must be completed 100% online, in under 10 minutes, without calling an agent or visiting a store. Telcos that achieve that digital flow significantly reduce the acquisition cost per incoming port and increase conversion rates compared to the in-store channel.

Plan, device, and accessory catalog: how Adobe Commerce handles it

Adobe Commerce resolves telecom catalog complexity with native capabilities that require no custom development for the most common scenarios:

Configurable products and dynamic bundles

Adobe Commerce's configurable product type allows a single device to be displayed with multiple options — color, storage capacity, version — from a single product page with a single indexable URL. Each variant has its own price, availability, and imagery.

Bundle products allow a device to be dynamically associated with plans in the same checkout flow: the customer selects the base device, then chooses a data plan from the available options for that model, and the final price is calculated in real time based on the chosen combination. This mechanism replicates exactly the purchase flow of a physical telecom store, translated to the web without friction.

Customer group pricing

Adobe Commerce supports customer groups with differentiated pricing. A corporate user authenticated as a "verified enterprise customer" sees volume pricing with per-line discounts; a new postpaid customer sees the list price with the current activation promotion; a retention-eligible customer whose contract has expired sees a renewal offer not available to the general public. All of this logic is native — no custom development required — and applies in real time on both the web storefront and the API that powers the mobile app.

Catalog and cart price rules

Adobe Commerce's Catalog Price Rules and Cart Price Rules allow complex discounts to be configured without touching code:

• "Device insurance included for 3 months with any new postpaid line activation."
• "20% off accessories when the cart includes an Unlimited Plus plan."
• "Zero activation fee on all incoming ports during the year-end campaign."

These rules are managed from the admin panel and can be enabled and disabled by date without requiring a deployment. In a telco context — where promotional campaigns have precise start and end dates — this represents a concrete operational advantage.

Device inventory management by channel

For physical devices, Adobe Commerce manages inventory by source: flagship store in Mexico City, northern distribution center, Monterrey store, Guadalajara store. A customer can choose to pick up at their preferred store (BOPIS) or request home delivery, and the system assigns the nearest source with real-time availability at the moment of order confirmation.

Recurring billing and subscription commerce in Adobe Commerce

Recurring billing is the core of the telco business model — and it has historically been one of the most challenging areas for generic ecommerce platforms designed for one-time transactions.

Integration with specialized billing systems (BSS/OSS)

Telcos in Mexico operate with specialized billing platforms: Amdocs, CSG Systems, Oracle Communications Billing & Revenue Management, or internally developed proprietary systems. Adobe Commerce integrates with these platforms through its API layer (REST and GraphQL), acting as the commerce front-end while billing continues to run in the specialized system. The typical flow in this model:

1. The customer configures their purchase in Adobe Commerce (plan + device + accessories).
2. Adobe Commerce validates availability in real time and consolidates the cart.
3. At checkout, Adobe Commerce sends the order payload to the BSS via API.
4. The BSS confirms the activation, generates the first billing cycle, and returns the account number.
5. Adobe Commerce records the order, activates the customer's access, and triggers post-purchase communications.

This model — Adobe Commerce as front-end orchestrator and experience layer, BSS as the recurring billing engine — is the pattern we recommend for telcos with existing, mature billing infrastructure. It avoids replacing critical systems that already work and reduces the risk profile of the implementation significantly.

Native subscriptions via certified Marketplace extensions

For operators who prefer to centralize subscription management within Adobe Commerce, certified extensions in Adobe Commerce Marketplace cover:

• Recurring billing (monthly, annual, custom cycles) with PCI-compliant tokenization.
• Plan upgrade and downgrade management without canceling and reactivating the subscription.
• Automatic pre-billing notifications (7 days before, 1 day before) to reduce churn from expired cards.
• A customer self-service portal where subscribers can change payment method, view billing history, temporarily pause service, or cancel — without calling the contact center.

Electronic invoicing (CFDI 4.0)

For the Mexican market, CFDI 4.0 issuance is mandatory for B2B transactions and increasingly expected in B2C. Adobe Commerce integrates with SAT-authorized digital certification providers (PAC) — Facturama, SW Sapien, Comercio Digital, among others — to issue and stamp the tax receipt within the checkout flow itself, without redirecting the customer or requiring any manual process afterward.

Personalization by segment: individual, family, and enterprise

Real-Time CDP: the unified telecom customer profile

A telco's customers generate data across multiple systems that rarely communicate with one another: data and call usage history lives in the BSS; device and accessory purchases are in the online store; call center interactions are in the CRM; support tickets are in the helpdesk; mobile app behavior is in analytics logs. The practical consequence is that the marketing team operates without a complete view of the customer, and the online store shows the same generic offer to someone who hasn't upgraded in three years as to a recent customer on a premium plan.

Adobe Real-Time CDP on Adobe Experience Platform (AEP) resolves this by unifying all those sources into a single, actionable customer profile. When that customer visits the online store, AEP can resolve their identity in milliseconds and pass profile attributes to Adobe Commerce to personalize the experience in real time:

• Hero section: if the customer has a three-year-old device and is on a basic plan, the main section displays the available upgrade with their specific renewal pricing.
• Catalog recommendations: if they have visited the family plan page four times without converting, the recommendation carousel prioritizes family plans with the most aggressive multi-line offer.
• Personalized prices and promotions: if the customer is 30 days from contract expiration, they see an early renewal offer not available to the general public.

Adobe Target: testing and conversion optimization

With Adobe Target integrated, a telco's ecommerce teams can:

• Run A/B tests on the portability flow — how many steps it has, what information is requested on each screen — and measure which variant achieves higher completion rates.
• Personalize the plan page based on the device the visitor is using: if the customer is browsing from an iPhone 13, the results order prioritizes plans compatible with their likely next upgrade.
• Optimize the offer of device insurance or additional services at checkout — the highest-intent moment in the entire session.

Segmentation by active plan type

A pattern we apply in telecom projects: using Adobe Commerce's customer_group as a proxy for the customer's active product segment. A customer identified as "active prepaid" sees a different experience — emphasis on top-up, portability, entry-level plans — than a "high-usage postpaid" customer, who sees emphasis on device upgrades, adding family lines, and value-added services. This segmentation is implemented using native customer group logic, without requiring a full AEP deployment, as a first step toward advanced personalization.

Omnichannel in telecommunications: physical store, app, and web synchronized

Order Management: the bridge across all channels

The biggest omnichannel pain point in telecommunications is inconsistency between touchpoints: a customer who starts a portability request on the web can't continue it in-store because the agent can't see their progress; the call center doesn't have access to the abandoned cart; the app shows different prices than the web due to a synchronization problem. These inconsistencies are visible to the customer, create friction, and damage brand trust in ways that are hard to reverse.

An Order Management System (OMS) integrated with Adobe Commerce exposes a single view of the order and the customer across all channels. The use cases we most commonly address in telecom projects:

1. Click & collect (BOPIS): the customer pays for the device and activates the plan online; they pick up the device at their chosen store, where an agent records the delivery without requiring a second transaction.
2. Return at any store: the customer buys online but can return the device at any network location, with the purchase history accessible in the store's system.
3. Cross-device continuity: the customer starts configuring the plan in the mobile app and completes it on a laptop without losing any data already entered.
4. Agent visibility: the in-store agent can see the cart the customer built online and resume it to close the sale in person.

Headless architecture: the mobile app consumes the same backend as the web

Adobe Commerce exposes all of its catalog, pricing, cart, checkout, and account management logic through a full GraphQL API. This allows the operator's mobile app — built in React Native, Flutter, Swift, or Kotlin — to consume the same commerce engine as the web store, with consistent prices, inventory, and promotions in real time, without duplicating business logic across platforms.

The headless model — decoupled frontend, Adobe Commerce as the commerce backbone — is the dominant pattern in next-generation telecom implementations. It allows the app design and the web design to evolve independently, without coupling those changes to the commerce backend.

Device inventory management: no overselling

A telco selling physical devices faces the risk of "overselling": committing a model that is out of stock at the assigned warehouse. Adobe Commerce addresses this with multi-source inventory (MSI): each warehouse and store is an independent source, stock is reserved the moment a customer adds the item to their cart, and if the cart expires without converting, the reservation is automatically released. Configurable low-stock alerts notify the operations team before a product reaches zero.

Customer journey in telecom: from initial inquiry to plan upgrade

Adobe Journey Optimizer: orchestrating the subscriber lifecycle

A telecom customer's lifecycle has critical moments that are predictable weeks or months in advance. Adobe Journey Optimizer (AJO) allows automated journeys to be configured that respond to those moments with the right message on the right channel:

Moment	Trigger event	Journey action
Month 0	Plan activation	Onboarding: app tutorial, billing setup, activation of included services
Months 1–3	First months active	NPS survey, coverage issue detection, first upsell offer for value-added services
Month 10	Contract with 60 days to expiration	Early renewal offer with exclusive benefit (device, extra data)
Month 12	Contract expiration	Device upgrade offer + plan renewal + flexible payment options
Any month	Data consumption > 90% of plan	Data add-on offer before the customer calls support or switches carriers
Any month	Open support ticket	Automatic pause of all commercial campaigns until the issue is resolved
Any month	Outbound portability attempt	Retention journey with differentiated offer (not the same offer on the public site)

The last case — pausing campaigns when a support ticket is open — is an example of the kind of logic that separates an enterprise-grade journey from a generic email campaign. A customer with an active problem does not want to receive an upgrade offer; receiving one at that moment damages brand perception in ways that outlast the resolution of the original issue.

Adobe Analytics: measuring every step of the telecom funnel

The conversion funnel of a telecom store is longer and has more drop-off points than any retailer's. A typical flow includes:

1. Plan or device search.
2. Bundle configuration (plan + device + optional accessories).
3. Number selection (new number vs. portability from another carrier).
4. Existing contract validation (for current subscribers checking their tenure).
5. Identity data entry (CURP or national ID for postpaid contracts).
6. Payment method selection and recurring billing configuration.
7. Confirmation, SIM activation, and device delivery or pickup arrangement.

Each step has a different abandonment rate, and that rate varies by plan type, device, acquisition channel, and customer segment. Adobe Analytics makes it possible to measure exactly where most customers drop off, cross-referenced by those dimensions. That data feeds directly into UX decisions and Adobe Target test roadmaps.

What to evaluate before choosing an ecommerce platform for telecom

Not every ecommerce platform is equipped for the level of complexity a telco requires. This table summarizes the criteria we recommend evaluating:

Criterion	Minimum acceptable	The ideal	Adobe Commerce
Complex catalog	Simple products with basic variants	Dynamic bundles, configurable products, customer group pricing	✅ Native
Subscriptions and recurring billing	Single transaction per purchase	Recurring billing with tokenization, upgrades/downgrades without canceling, self-service portal	✅ Via BSS integration or certified extensions
Omnichannel	Web only	Unified OMS, BOPIS, persistent cart across devices and channels	✅ With integrated OMS
API-first / headless	Monolithic storefront	Full GraphQL for mobile apps, kiosks, voice assistants, distribution channels	✅ Native GraphQL
BSS/OSS integration	No native integration	API Gateway for specialized telecom billing systems	✅ Via REST API and GraphQL
Personalization	Basic recommendations from purchase history	Real-Time CDP + Adobe Target: real-time personalization on unified profile	✅ With AEP
Scalability	Thousands of concurrent users	Millions, with automatic scaling for traffic spikes (device launches, campaigns)	✅ Adobe Commerce Cloud
Electronic invoicing MX (CFDI 4.0)	Manual process or export	Integration with SAT-certified PAC in the checkout flow	✅ Via extension
Number portability (LFTR)	Manual or external flow	Digital flow integrated with regulatory platform, documented consent	✅ Configurable
PCI DSS security	Basic	Level 1 PCI DSS, card tokenization, strong authentication	✅ With certified gateway

The real cost of an under-dimensioned platform

Telcos that begin their digital transformation with generic ecommerce platforms — designed for simple retail, not for the complexity of the sector — inevitably accumulate custom development to cover the gaps in catalog management, subscriptions, and BSS integration. In our experience working on modernization projects, the total cost of that custom development frequently exceeds the cost of having chosen an enterprise platform from the outset.

More important than the cost: the accumulated technical debt slows the speed of response to market changes. Launching a new plan — something a competitor might do in 48 hours — can take weeks when pricing and catalog logic is scattered across undocumented custom code. In telecommunications, that slowness has a direct cost in market share.

WolfSellers and the telecommunications sector in Mexico

WolfSellers is a certified Adobe Commerce and Adobe Experience Cloud partner with experience in implementations for telecommunications companies in Mexico. Our projects in the sector have involved:

• Catalogs with tens of thousands of active SKUs and differentiated pricing logic by customer segment.
• Integration of Adobe Commerce with specialized billing platforms, maintaining the existing BSS as the recurring billing engine.
• Implementation of Real-Time CDP on AEP for personalization based on network usage data and storefront behavior.
• 100% digital portability and activation flows with compliance with IFT regulatory guidelines.
• Headless architectures where the operator's mobile app consumes Adobe Commerce's GraphQL API.
• CFDI 4.0 integration in the checkout flow for B2B customers.

If your company operates in telecommunications and is evaluating modernizing its ecommerce platform — or if you are facing any of the challenges described in this article — we can help you map the specific requirements of your operation and define the right architecture before committing budget to an implementation.

Frequently asked questions

Can Adobe Commerce handle number portability according to IFT guidelines?

Yes, with the correct configuration and integration. Adobe Commerce can orchestrate the portability flow — capturing the number to be ported, validating eligibility and contract tenure, selecting the new plan, confirming identity, and documenting consent — as a customized checkout flow. Communication with the portability regulatory platform (AMECE database) and generation of the portability NIP is handled through middleware services connected to Adobe Commerce via API. The IFT requires portability to be completed within a maximum of 24 business hours; well-implemented digital flows complete it in under an hour.

What is the difference between using Adobe Commerce with AEP versus without AEP for a telco?

Without AEP, Adobe Commerce works with segmentation based on data from within the store: purchase history, customer group, cart behavior. This is a solid starting point and is sufficient for many operations. With AEP and Real-Time CDP, you incorporate data from outside the store: actual network data consumption, support history, mobile app interactions, offline channel behavior. That allows you to personalize the offer not just based on what the customer purchased, but based on how they use the service today. The difference in offer relevance — and in conversion rates on upgrade and retention campaigns — is significant.

How does Adobe Commerce handle plan prices that change frequently?

Plan prices can be updated in Adobe Commerce via API or from the admin panel in bulk. For telcos that update prices weekly or more frequently, the recommended flow is an API integration with the product management system (PIM or the BSS itself) that automatically propagates price changes to Adobe Commerce. Promotional price rules can be scheduled by start and end date without requiring a deployment. Catalog changes also require no deployment — they are database operations that are reflected in real time on the storefront and in the API.

Does Adobe Commerce scale for the traffic volume of a large operator in Mexico?

Adobe Commerce in Cloud mode — infrastructure managed by Adobe on AWS — is designed to scale automatically under traffic spikes. Large telcos have very concentrated, predictable spikes: the launch of a new iPhone model, a Hot Sale campaign, or the start of the monthly billing cycle. Adobe Commerce Cloud scales horizontally — more web nodes, more database capacity, more cache instances — automatically when demand requires it. For an operator with millions of active customers, sizing should be planned directly with Adobe, taking into account SKU volume, expected concurrent users at peak, and catalog access patterns.

Does Adobe Commerce support multiple brands or sub-brands under a single instance?

Yes. Adobe Commerce supports multiple stores and websites from a single instance, with independent catalogs, pricing, design templates, and payment configurations per brand. This is relevant for telecom groups that operate multiple brands in Mexico — a main brand and a separate low-cost or prepaid brand, or a standalone device store separate from the plan portal — or for operators with distinct B2C and B2B lines of business. Centralized management reduces operational costs compared to maintaining two independent platforms with separate teams and development streams.

How long does an Adobe Commerce implementation take for a telecom company?

It depends on scope. An implementation with a complex catalog, BSS integration, AEP personalization, and full omnichannel capabilities can take between 6 and 18 months. A first phase focused on core functionality — catalog, checkout, payments, CFDI — can be in production in 4 to 6 months, with subsequent phases for advanced personalization and OMS. At WolfSellers, we define the scope of each phase during the discovery stage, so the first production release delivers concrete business value without waiting for the complete solution to be ready.