WolfSellers — Adobe Experience Cloud Partner en México

Article

Adobe Commerce for Telecom Companies in Mexico

How Mexican telecom operators solve complex plan catalogs, subscription billing, and omnichannel commerce with Adobe Commerce and Adobe Experience Platform.

By WolfSellers··18 min read
Adobe Commerce for Telecom Companies in Mexico
On this page

Mexico's telecommunications sector works in one of the most commercially complex markets there is. It has more than 130 million active mobile lines (IFT, Q1 2026). Mobile phone penetration is above 90% of the population. And competition between operators is so fierce that every tenth of a percentage point in retention counts. So does every peso of ARPU (Average Revenue Per User), more than in almost any other industry.

In that setting, a telco's digital store is no longer an add-on channel. It is the main point of contact for activations, upgrades, number portability, contract renewals, and device sales. It has to work flawlessly for millions of users at the same time. And those users expect what the best apps in the world have taught them to expect.

WolfSellers works with telecom companies that face exactly that challenge. They must turn catalogs of thousands of SKUs into consistent buying experiences. Those SKUs include plans, devices, accessories, and value-added services. And the experiences must convert on the web, in the app, and in physical stores alike. In this article we explain how Adobe Commerce (formerly Magento) meets the specific needs of a telecom operator. It runs with Adobe Experience Platform (AEP) and the full Adobe Experience Cloud stack. We cover everything 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 manage all of this at once: 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 number of combinations is hard to present clearly. It is also 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 what competitors do.

Prices conditioned by buyer profile

In telecommunications, the price a customer sees is never the same for everyone. A new postpaid customer sees one price. A customer whose contract is about to expire sees another. So does someone porting their number from another carrier, or a corporate account with a 50-line master agreement. That makes four profiles and four price structures. Their discounts depend on outside 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 set concrete rules. Number portability must be processed within set deadlines. Plan information must show all costs clearly. Adhesion contracts need consent that is documented and can be downloaded. The ecommerce platform has to support these regulatory flows without hurting the buying experience.

Multiple buyer profiles with distinct journeys

A telco sells to buyers with very different needs, all at the same time:

  • Individual consumer (B2C): looks for the best price on unlimited data and compares coverage by city. They want to activate a new smartphone without going to a store.
  • Family (B2C family): needs a multi-line plan with parental controls and a single invoice. They also want to add or remove lines without calling an agent.
  • Small business (B2B simplified): needs 5–50 lines with central management and electronic invoices (CFDI 4.0). They also need to see usage for each line.
  • Corporate enterprise (B2B enterprise): asks for master contracts with SLAs and device fleet management (MDM). It also needs a multi-user admin portal and combined usage reports.

Each profile has its own funnel, its own sales pitch, and its own friction point. Some platforms can't serve all of them from the same architecture. Then the operator has to run several stores with duplicated business logic. That creates inconsistencies and massive technical debt.

BYOD and portability as traffic drivers

The Mexican market has one special trait. BYOD (Bring Your Own Device) is common among prepaid and mid-segment postpaid users. The portability flow has several steps: check eligibility, start the transfer, confirm the number, pick the new plan, and activate the SIM. All of it must be done 100% online, in under 10 minutes, without calling an agent or visiting a store. Telcos that get that digital flow right greatly lower the acquisition cost per incoming port. They also raise conversion rates compared to the in-store channel.

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

Adobe Commerce solves telecom catalog complexity with built-in features. For the most common cases, you need no custom development:

Configurable products and dynamic bundles

With Adobe Commerce's configurable product type, one device can show many options, such as color, storage capacity, and version. It all lives on a single product page with a single indexable URL. Each variant has its own price, availability, and images.

Bundle products let you link a device with plans on the fly, in the same checkout flow. The customer picks the base device. Then they choose a data plan from the options for that model. The final price is calculated in real time based on the chosen combination. This copies exactly the buying flow of a physical telecom store and brings it to the web without friction.

Customer group pricing

Adobe Commerce supports customer groups with different prices. A corporate user signed in 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 customer whose contract has expired and who qualifies for retention sees a renewal offer the general public can't get. All of this logic is native, with no custom development. It applies in real time on both the web storefront and the API that powers the mobile app.

Catalog and cart price rules

With Adobe Commerce's Catalog Price Rules and Cart Price Rules, you can set up complex discounts 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."

You manage these rules from the admin panel. You can turn them on and off by date without a deployment. In a telco, promotional campaigns have exact start and end dates. So this is 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 pick up at their preferred store (BOPIS) or ask for home delivery. When the order is confirmed, the system assigns the nearest source with stock available in real time.

Recurring billing and subscription commerce in Adobe Commerce

Recurring billing is the core of the telco business model. It has also long been one of the hardest areas for generic ecommerce platforms, which are built for one-time purchases.

Integration with specialized billing systems (BSS/OSS)

Telcos in Mexico use specialized billing platforms: Amdocs, CSG Systems, Oracle Communications Billing & Revenue Management, or their own in-house systems. Adobe Commerce connects to these platforms through its API layer (REST and GraphQL). It acts as the commerce front-end, while billing keeps running in the specialized system. This is the typical flow in this model:

  1. The customer sets up their purchase in Adobe Commerce (plan + device + accessories).
  2. Adobe Commerce checks availability in real time and builds the final cart.
  3. At checkout, Adobe Commerce sends the order payload to the BSS via API.
  4. The BSS confirms the activation, creates the first billing cycle, and sends back the account number.
  5. Adobe Commerce records the order, turns on the customer's access, and sends the post-purchase messages.

In this model, Adobe Commerce is the front-end orchestrator and experience layer. The BSS is the recurring billing engine. We recommend this pattern for telcos that already have mature billing infrastructure. It avoids replacing critical systems that already work. It also lowers the risk of the implementation a great deal.

Native subscriptions via certified Marketplace extensions

Some operators prefer to run subscription management inside Adobe Commerce. For them, certified extensions in Adobe Commerce Marketplace cover:

  • Recurring billing (monthly, annual, custom cycles) with PCI-compliant tokenization.
  • Plan upgrades and downgrades without canceling and restarting the subscription.
  • Automatic notices before billing (7 days before, 1 day before) to cut churn from expired cards.
  • A self-service portal where subscribers can change their payment method, see their billing history, pause service for a while, or cancel. They never have to call the contact center.

Electronic invoicing (CFDI 4.0)

In the Mexican market, issuing a CFDI 4.0 is mandatory for B2B sales and more and more expected in B2C. Adobe Commerce connects with SAT-authorized digital certification providers (PAC), such as Facturama, SW Sapien, and Comercio Digital, among others. It issues and stamps the tax receipt inside the checkout flow itself. The customer is never redirected, and no manual step is needed afterward.

Customer at home holds her older phone while reviewing a personalized upgrade offer on laptop

Personalization by segment: individual, family, and enterprise

Real-Time CDP: the unified telecom customer profile

A telco's customers create data in many systems that rarely talk to each other. 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.

In practice, the marketing team works without a full view of the customer. And the online store shows the same generic offer to everyone. Someone who hasn't upgraded in three years sees what a recent customer on a premium plan sees.

Adobe Real-Time CDP on Adobe Experience Platform (AEP) solves this. It unifies all those sources into a single customer profile you can act on. When that customer visits the online store, AEP can resolve their identity in milliseconds. It then passes profile attributes to Adobe Commerce to personalize the experience in real time:

  • Hero section: say the customer has a three-year-old device and a basic plan. The main section shows the upgrade they can get, with their own renewal pricing.
  • Catalog recommendations: maybe they have visited the family plan page four times without converting. Then the recommendation carousel puts family plans with the most aggressive multi-line offer first.
  • Personalized prices and promotions: if the customer's contract ends in 30 days, they see an early renewal offer the general public can't get.

Adobe Target: testing and conversion optimization

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

  • Run A/B tests on the portability flow, such as how many steps it has or what data each screen asks for. Then measure which variant gets higher completion rates.
  • Personalize the plan page based on the visitor's device. If the customer is browsing from an iPhone 13, the results put first the plans that fit their likely next upgrade.
  • Optimize the device insurance or add-on service offer at checkout. That is the highest-intent moment in the whole session.

Segmentation by active plan type

Here is a pattern we apply in telecom projects. We use Adobe Commerce's customer_group as a stand-in for the customer's active product segment. A customer tagged as "active prepaid" sees one experience, with the focus on top-up, portability, and entry-level plans. A "high-usage postpaid" customer sees another, with the focus on device upgrades, adding family lines, and value-added services. This segmentation uses native customer group logic. It needs no full AEP deployment, so it works 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 starts a portability request on the web but can't continue it in-store, because the agent can't see their progress. The call center can't access the abandoned cart. The app shows different prices than the web because of a sync problem. The customer sees these gaps. They create friction and damage brand trust in ways that are hard to reverse.

An Order Management System (OMS) linked to Adobe Commerce gives a single view of the order and the customer across all channels. These are the use cases we handle most often 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. There, an agent records the delivery with no second transaction.
  2. Return at any store: the customer buys online but can return the device at any store in the network. The store's system can see the purchase history.
  3. Cross-device continuity: the customer starts setting up the plan in the mobile app and finishes it on a laptop. They don't lose any data they 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. So the operator's mobile app can use the same commerce engine as the web store, whether it is built in React Native, Flutter, Swift, or Kotlin. Prices, inventory, and promotions stay consistent in real time. And no business logic is duplicated across platforms.

In the headless model, the frontend is decoupled and Adobe Commerce is the commerce backbone. It is the leading pattern in next-generation telecom projects. The app design and the web design can each change on their own, without tying those changes to the commerce backend.

Device inventory management: no overselling

A telco that sells physical devices runs the risk of "overselling," which means promising a model that is out of stock at the assigned warehouse. Adobe Commerce handles this with multi-source inventory (MSI). Each warehouse and store is its own source. Stock is reserved the moment a customer adds the item to their cart. If the cart expires without converting, the reservation is released on its own. Low-stock alerts, which you can configure, warn the operations team before a product hits 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 you can predict weeks or months ahead. With Adobe Journey Optimizer (AJO), you can set up automated journeys that respond to those moments. Each one sends 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)

Look at the last case, which pauses campaigns while a support ticket is open. It shows the kind of logic that sets an enterprise-grade journey apart from a generic email campaign. A customer with an active problem does not want an upgrade offer. Getting one at that moment hurts how they see the brand, and the damage lasts longer than 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 setup (plan + device + optional accessories).
  3. Number choice (a new number or portability from another carrier).
  4. A check of the current contract (for subscribers who want to check their tenure).
  5. Identity data entry (CURP or national ID for postpaid contracts).
  6. Payment method choice and recurring billing setup.
  7. Confirmation, SIM activation, and setting up device delivery or pickup.

Each step has its own abandonment rate. That rate varies by plan type, device, acquisition channel, and customer segment. With Adobe Analytics, you can measure exactly where most customers drop off, cross-checked by those dimensions. That data feeds straight into UX decisions and Adobe Target test roadmaps.

IT director and ecommerce lead review printed criteria while evaluating a telecom commerce platform

What to evaluate before choosing an ecommerce platform for telecom

Not every ecommerce platform is built for the level of complexity a telco needs. This table sums up the criteria we recommend you evaluate:

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

Some telcos start their digital transformation on generic ecommerce platforms. Those platforms are made for simple retail, not for the complexity of the sector. So these telcos inevitably pile up custom development to cover gaps in catalog management, subscriptions, and BSS integration. In our experience on modernization projects, the total cost of that custom work often exceeds the cost of choosing an enterprise platform from the start.

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. We have experience with projects for telecommunications companies in Mexico. Our work in the sector has included:

  • Catalogs with tens of thousands of active SKUs and different pricing logic for each customer segment.
  • Linking Adobe Commerce to specialized billing platforms, while keeping the current BSS as the recurring billing engine.
  • Rolling out Real-Time CDP on AEP to personalize based on network usage data and storefront behavior.
  • 100% digital portability and activation flows that comply with IFT regulatory guidelines.
  • Headless architectures where the operator's mobile app uses Adobe Commerce's GraphQL API.
  • CFDI 4.0 integration in the checkout flow for B2B customers.

A documented case is AT&T Mexico's B2C store on Adobe Commerce, which combined hundreds of tangible and intangible products and an outlet with thousands of simultaneous users. We tell the story in the AT&T case study.

Does your company work in telecommunications and is it thinking about modernizing its ecommerce platform? Or are you facing any of the challenges in this article? We can help you map the specific needs of your operation. We can also help you define the right architecture before you commit budget to an implementation.

Frequently asked questions

Can Adobe Commerce handle number portability according to IFT guidelines?

Yes, with the right configuration and integration. Adobe Commerce can run the portability flow as a custom checkout flow. It captures the number to be ported, checks eligibility and contract tenure, and lets the customer pick the new plan. It also confirms identity and documents consent. Middleware services connected to Adobe Commerce via API talk to the portability regulatory platform (AMECE database). They also generate the portability NIP. The IFT requires portability to be done within 24 business hours at most. Well-built digital flows finish 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 segments with data from inside the store: purchase history, customer group, cart behavior. This is a solid starting point, and it is enough for many operations. With AEP and Real-Time CDP, you add data from outside the store: real network data usage, 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?

You can update plan prices in Adobe Commerce via API or in bulk from the admin panel. Some telcos update prices weekly or more often. For them, the recommended flow is an API integration with the product management system (PIM or the BSS itself). It pushes price changes to Adobe Commerce on its own. Promotional price rules can be scheduled by start and end date with no deployment. Catalog changes need no deployment either. They are database operations that show up 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 runs on infrastructure that Adobe manages on AWS. It is built to scale on its own when 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 and on its own when demand calls for it. That means more web nodes, more database capacity, and more cache instances.

An operator with millions of active customers should plan sizing directly with Adobe. The plan should take 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 many stores and websites from a single instance. Each brand gets its own catalog, pricing, design templates, and payment settings. This matters for telecom groups that run several brands in Mexico. Examples include a main brand plus a separate low-cost or prepaid brand, or a standalone device store apart from the plan portal. It also matters for operators with distinct B2C and B2B lines of business. Central management costs less to run than 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. A project with a complex catalog, BSS integration, AEP personalization, and full omnichannel features can take between 6 and 18 months. A first phase focused on the core (catalog, checkout, payments, CFDI) can be live in 4 to 6 months. Later phases then add advanced personalization and OMS. At WolfSellers, we define the scope of each phase during the discovery stage. That way, the first production release delivers concrete business value without waiting for the full solution.

If this topic is relevant to your business, these services from WolfSellers can help you implement it:

Want to dive deeper?

Let's talk.

We're an Adobe Gold Partner in Mexico with experience in Adobe implementations and integrations. If anything in this article applies to your operation, the first consultation is on us.

Or email us at contacto@wolfsellers.com

Keep reading

Chat with us on WhatsApp