What pricing intelligence is — and how it differs from dynamic pricing
Price is the one variable in your business a competitor can see in 30 seconds with a scraper. And the one you see worse than they do — because they run pricing intelligence and you run Excel plus a Monday call with the product manager.
E-commerce in Latin America crossed USD 150 billion in GMV in 2024. Mercado Libre, Falabella, Liverpool, Cencosud, and Coppel have all spent at least four years building pricing intelligence as a core capability. Meanwhile, the typical SMB with USD 5–50M in revenue across Peru, Chile, Colombia, or Mexico still runs on phone calls and intern screenshots.
This piece is for the CFO, CMO, head of e-commerce, retail operator, or enterprise architect who already understands this approach has hit its ceiling. We break it down by layer: what pricing intelligence is, which stack actually works in LATAM, where naive setups fail, what fines COFECE, FNE, or SIC will hand out for "too-smart" algorithmic pricing, and the real cost of going from MVP to production.
Six bullets before we drop into the detail:
- Pricing intelligence ≠ web scraping. It is four layers: collection plus SKU matching plus elasticity modeling plus decision rules. Scraping without matching produces garbage.
- LATAM is specific. Mercado Libre, Amazon Mexico, and Falabella dominate the data stream, but they hide real prices behind promo codes and geo. Without residential proxies in Peru, Chile, and Colombia, you see 60% of the picture.
- Antitrust risk is real. COFECE (Mexico), FNE (Chile), SIC (Colombia), INDECOPI (Peru), and CNDC (Argentina) all examine algorithmic pricing. Quiet coordination through a shared SaaS equals fines up to 10% of revenue.
- Startup cost: USD 35–80k for an MVP in 3–4 months; USD 120–250k for production on 5,000+ SKUs.
- When not to run it: fewer than 200 SKUs, local brand without direct competitors, hyperinflation (Argentina in crisis windows), regulator-fixed prices.
- Realistic ROI: +1.5–4 percentage points of gross margin in 9–12 months for retail with a 25–45% margin profile.
Four concepts LATAM teams confuse all the time:
- Pricing intelligence is decision support. It pulls competitor prices, your sales history, category elasticity, and SKU margin, then hands the pricing team facts, hypotheses, and recommendations. Humans or approved rules make the call.
- Dynamic pricing is closed-loop. The algorithm changes the price with no human in the loop, the way Uber or airlines do it.
- Repricing is the narrow task of auto-pricing inside one channel (Amazon Buy Box, Mercado Libre). A subset of dynamic pricing at the marketplace layer.
- Market intelligence is broad market analytics: assortment, share-of-shelf, share-of-voice. Price is one slice among many.
In LATAM, roughly 90% of retail projects start with pricing intelligence (decision support), not dynamic pricing. The reason is simple: antitrust law and a commercial director's distrust of autonomous algorithms. That is the right order — first learn to decide with data, then automate.
The four layers we unpack below:
- Collection — extract prices and attributes from marketplaces, competitor sites, and physical stores via photos or crowdsourcing.
- Matching — connect "your SKU 1234" with "their SKU X-7-Z-blue". The hardest layer, especially in beauty, fashion, and electronics.
- Modeling — estimate demand elasticity, simulate scenarios, forecast response to price changes.
- Action — generate recommendations, run A/B tests, integrate with ERP (Odoo, SAP, NetSuite) to apply approved prices.
LATAM competitive landscape: 4–6 sources per country
Marketplace concentration in LATAM is higher than in the US or Europe. Public data from CEPAL and the Mexican e-commerce association AMVO put Mercado Libre at 35–55% of e-commerce GMV in Argentina, Uruguay, Chile, and Colombia. In Mexico the share splits more evenly across Amazon Mexico, Mercado Libre, and Walmart Mexico — see the Mercado Libre investor relations filings for the underlying numbers.
Peru. Falabella (plus Tottus), Ripley, Mercado Libre. Linio shut down in 2023 and the traffic shifted to Mercado Libre. Promart and Sodimac own the "home and renovation" category. Cross-border with Amazon US is a visible demand leak. Local implementation context lives in the Odoo Peru pillar.
Chile. Falabella (plus Sodimac, Tottus), Cencosud (Paris, Easy, Jumbo), Ripley, Mercado Libre. The most institutionalized e-commerce in LATAM. The antitrust regulator FNE is the most mature in the region. For per-country architecture see the Colombia playbook and compare to your Chilean setup.
Colombia. Mercado Libre leads, with Éxito (under GPA), Falabella, and Rappi (q-commerce). Éxito and Olímpica loyalty cards drive FMCG pricing. Regulatory detail in the Odoo Colombia pillar.
Argentina. Mercado Libre is the de facto monopoly with more than 70% of e-commerce GMV by local estimates. Frávega, Garbarino, Coto, Walmart. The dominant pricing challenge is peso volatility: any static price list becomes obsolete in 1–3 weeks. See the fiscal background in the Odoo Argentina pillar.
Mexico. The most complex market. Amazon Mexico (Prime), Mercado Libre, Walmex (plus Bodega Aurrera and Sam's Club), Liverpool, Coppel, Costco — plus explosive growth from Shein and Temu. US cross-border via Laredo is a segment with its own logic. Local architecture in the Odoo Mexico pillar.
What this means in engineering terms: each country forces 4–6 mandatory sources to monitor, each with its own antibot stack (Cloudflare, Akamai Bot Manager, PerimeterX), geo-IP blocks, and dynamic promo codes that rewrite the final price at checkout.
Regulatory milestones from 2023–2026 worth keeping in working memory:
- 2023: COFECE Mexico stated publicly that hub-and-spoke collusion through shared pricing software is an investigation priority.
- 2024: FNE Chile closed the public consultation on algorithmic coordination in retail pharma; SIC Colombia expanded its methodology for digital markets.
- 2025: OECD published an updated competition policy guideline for digital markets that LATAM regulators are already citing.
- 2026: expect deeper scrutiny of data sharing between direct competitors through shared SaaS vendors.
The four layers: collection, matching, modeling, action
One layer at a time. Each can be done fast-and-wrong and fail, or built properly and pay back in 9–12 months. The data engineering practice carries the first two layers; the ML practice carries the last two.
#1. Collection — where the data comes from
Mistake one: assuming pricing intelligence equals "I hire an intern who opens 50 competitor pages once a week and dumps it into Excel." That approach dies at 100 SKUs and three competitors.
Production-grade collection in LATAM needs:
- Headless browsers (Playwright, Puppeteer) for JS-rendered marketplaces. Pure HTTP scraping works on about 30% of target sites.
- A residential proxy pool with per-country geography. Datacenter IPs get banned by Mercado Libre and Amazon Mexico in 4–8 hours. Budget: USD 8,000–14,000 per year to cover 4 countries and 5 large sources.
- Cadence by priority: top-100 SKUs every 2–4 hours, top-1k 2–3 times/day, long-tail once a day or less. Blind-scraping everything hourly equals ban plus wasted budget.
- Promo detection. In Mexico, Liverpool and Walmex push "−15% at checkout with loyalty card" coupons. If your scraper doesn't simulate login or parse promo blocks, you see MSRP instead of the real price.
- Antibot resilience. Akamai Bot Manager on Mercado Libre Mexico is a serious adversary. Reserve 1–2 engineers who live in an ongoing arms race.
#2. Matching — where DIY projects die
Most home-grown projects die here. Connecting "iPhone 15 Pro Max 256GB Titanio Natural" (your catalog) to "Apple iPhone 15 PRO MAX (256 GB) - color Natural Titanium" (Falabella) and iPhone15ProMax-256-NT-Telcel-Plan (Liverpool) is not trivial.
Approaches available:
- Rules and regex. Works for electronics with clean SKU/MPN/EAN. Up to 60% catalog coverage.
- TF-IDF and Levenshtein. Apparel, footwear, and furniture get 40–60% precision without manual cleanup.
- Embeddings (CLIP, sentence-transformers). The current standard. Image plus text embeddings, cosine similarity, manual threshold review. Production accuracy is 80–92% precision at 70–85% recall — meaning 8–15% of matches still require human review.
- GPT-4o-mini or Claude Haiku for the borderline cases. Economically viable since 2024 — roughly USD 0.001–0.005 per SKU verification with batching.
Realistic benchmark: 50,000 SKUs across 4 categories; a matching pipeline takes 6–10 weeks with one ML engineer and one data analyst. Not a weekend project.
#3. Modeling — distinguish historical averages from causal estimation
This layer needs people who know the difference between "average drop in sales when price rises 5%" and causal elasticity estimation. Most LATAM retail analysts confuse the two.
Minimum production stack:
- Demand-forecasting models per SKU, category, and region. Prophet, NeuralProphet, or classical SARIMA are enough for any category with over 18 months of history.
- Elasticity estimation. For history-rich categories: geographic regression discontinuity or difference-in-differences. For thin data: Bayesian hierarchical models with priors borrowed from the parent category.
- Promotional uplift modeling. A separate story. Promotions often produce +200–400% demand, and a model without promo tags will return garbage elasticities.
- Price-pack architecture. Critical in FMCG: demand for "Coca-Cola 2L" at price X is not the same as for "Coca-Cola 600 ml × 4".
#4. Action — where data turns into decisions
The last layer. Three things are critical:
- Decision rules engine — the boundaries inside which the algorithm can recommend without human approval. Example: "auto-apply up to −8% off MSRP; escalate to the category manager below that."
- A/B-testing infrastructure. Without it, you cannot prove pricing intelligence paid for itself. Minimum: held-out categories, regions, or stores as a control group.
- ERP/POS integration. In LATAM mid-market that usually means Odoo with product.pricelist; less often SAP, Oracle, or NetSuite.
product.pricelistfits well but needs custom workflows for approval chains.
When it works and when it leaves money on the table
Before you sign the PO, drop your business onto one side of the line. The native retail pricing layer helps, but it cannot fix a market mismatch.
Works — good investment candidates
Scenario 1: multi-SKU portfolio with a 25–50% margin profile. Beauty (Estée Lauder, L'Oréal LATAM, Natura), home improvement (Sodimac, Promart, The Home Depot Mexico), consumer electronics (Coppel, Liverpool, Falabella), mid-tier fashion. Minimum 500 SKUs and at least two large competitors with catalog overlap above 40%.
Scenario 2: stable currency. Mexico, Chile, Colombia, Peru. Monthly inflation under 1.5%, stable currency. Models stay valid for 6–12 months before they need retraining.
Scenario 3: omnichannel with marketplace presence. If more than 30% of your GMV runs through Mercado Libre, Amazon Mexico, or Falabella, pricing intelligence pays for itself by optimizing the Buy Box in Mexico or Reputation Score in Mercado Libre.
Doesn't work — or works poorly
Scenario 1: fewer than 200 SKUs, local brand without direct competitors. A boutique artisan footwear shop in San Cristóbal de las Casas doesn't need pricing intelligence — it needs brand pricing and customer segmentation. Implementing this is overkill.
Scenario 2: hyperinflation. Argentina during crisis windows with annual inflation above 100%. Elasticity models collapse in 2–3 weeks because the reference price ages out instantly. Different tools apply here: Index-Compensated Repricing, anchoring to indexed replacement cost (FIFO/LIFO with indexed cost).
Scenario 3: opaque-promo categories. Postpaid telecom in Peru, insurance in Colombia, banking products — base price means nothing because the real cost hides inside the bundle. Pricing intelligence fails here; the right move is offer intelligence.
Scenario 4: B2B with long sales cycles. Industrial machinery, professional services. Price is contracted and competitors publish nothing. Pricing intelligence is irrelevant — what you need is win/loss analysis and deal-desk dashboards.
Scenario 5: regulator-fixed prices. Fuel in Mexico (tied to IEPS), some pharmaceuticals, utility tariffs. Price isn't a variable you control.
5 typical mistakes when launching pricing intelligence in LATAM
#1. They launch the scraper and forget the matching
"We have data!" says the CTO at week six. Three months later, 60% of SKUs aren't matched or are matched wrong, and the entire dashboard is garbage. Remedy: the matching pipeline must be ready before collection goes to full power. Not the other way around.
#2. They ignore antitrust risk
In Mexico, COFECE has stated since 2023 that hub-and-spoke collusion through shared pricing software will be prosecuted. FNE Chile opened public comments on algorithmic coordination in retail pharma in 2024. SIC Colombia and INDECOPI Peru are also active. Do not use the same pricing SaaS with a direct competitor where both of you feed your prices to the same vendor — regulators treat that as information exchange. COFECE sanctions can reach 10% of annual revenue.
#3. One scraper for eight countries
LATAM is not one market. Mercado Libre Mexico and Mercado Libre Argentina are different antibot systems, different categories, different SKU schemes. Teams that build one universal crawler spend three times more on debugging than teams that split by country.
#4. Outsourcing the whole stack to one vendor
Locking into Competera, IntelligenceNode, Wiser, or Sniffie without internal capability means your pricing decisions live inside a SaaS that can raise prices 40% tomorrow or exit the region. The healthy middle: external tool for collection and basic matching, internal team for modeling and action.
#5. No A/B testing means you don't know what worked
The team rolled out the system and margin lifted 1.8 percentage points. But in the same window the exchange rate moved, inflation dropped, the competitor stopped cutting prices, and seasonality pulled up. Without control groups you can't tell which lever did what. Minimum: one store, category, or region held out where you don't apply recommendations. Lean on supply chain analytics to isolate stock effects.
Anonymous case: 12 beauty brands, 4 countries, +2.1 percentage points of margin
Anonymized case from the portfolio of Sergei Filatov (Forbes 30 Under 30 LATAM). An international beauty group with 12 brands and operations in Peru, Chile, Colombia, and Mexico. Roughly 27,000 active SKUs and USD 180M in annual regional revenue. See also the multi-brand pricing case and the retail web-scraping plus dynamic pricing case.
Initial state (2022). A pricing team of four (one per country) ran a weekly manual review of 30–40 "strategic SKUs" through screenshots of Mercado Libre, Falabella, Linio, and Amazon Mexico. Decisions were debated in Excel and signed off in a weekly Zoom. Time-to-react to a competitive action: 7–10 days. About 15% of SKUs were not tracked at all. One promo miss in Q4 2022 cost the group roughly USD 1.2M in uncaptured margin.
Implementation (Q3 2023 — Q2 2024). Nine months of build:
- Collection layer: Playwright plus residential proxies (Bright Data, USD 11k/year), cadence ranging from 2 times/day on top-500 to once a week on long-tail. Coverage of 18 sources across 4 countries.
- Matching: CLIP image embeddings plus text similarity, manual threshold review every week. Production precision 87%.
- Modeling: Bayesian hierarchical elasticities, priors borrowed by category and brand. Promo-uplift model kept separate.
- Action: integration with internal PIM and the retail ERP (Odoo Enterprise in 2 countries, local ERPs in the other two). Recommendations through a decision rules engine; auto-apply up to ±6%, escalation above that.
Result after 9 months. Gross margin +2.1 percentage points (from 32.4% to 34.5%). Time-to-react to a competitive action: 36 hours → 4 hours. Out-of-stock loss dropped — the system now knows which SKUs to defend with price. The pricing team didn't shrink; it shifted from tactical monitoring to category management and strategic initiatives. Full payback at month 11.
"The most underrated change wasn't the algorithm. It was the weekly committee moving from arguing about 30 manual SKUs to approving exceptions on 5,000 recommendations."
Conclusion and next steps
Pricing intelligence in LATAM is no longer "tech for the top-5 retailers." A business above USD 20M in revenue with a 25%+ margin can pay back the investment in 9–12 months — but only if the four layers are properly built: collection, matching, modeling, action. Launching without matching or without A/B testing is a guaranteed failure. Launching without an antitrust review is a guaranteed risk of a COFECE / FNE / SIC / INDECOPI / CNDC fine up to 10% of revenue.
If you run retail in Mexico, Chile, Peru, Colombia, or Argentina and are evaluating pricing intelligence as a capability, walk through the country pillars and our services:
- Odoo by country: Mexico, Peru, Colombia, Argentina.
- Services: Data Engineering, Machine Learning, Odoo Retail Pricing, Computer Vision, Marketing Attribution, and Supply Chain Analytics.
- Anonymous cases: multi-brand beauty pricing and retail web-scraping plus dynamic pricing.
Ready to discuss pricing intelligence for your portfolio? A 30-minute audit session with Sergei reviews feasibility, sizes the MVP cost, and lands the antitrust risk for your country and category.
Frequently asked questions
How much does it cost to launch pricing intelligence in LATAM?
MVP (1 country, 1–2 sources, 1,000–3,000 SKUs, no advanced modeling): USD 35,000–60,000 over 3–4 months. Full solution (3–4 countries, 5–8 sources, 10,000+ SKUs, modeling and action): USD 120,000–250,000 over 8–12 months, plus USD 30–60k/year OPEX for proxies, infra, and LLM calls on edge-case matches.
Is Mercado Libre Insights or Amazon Brand Analytics enough?
They cover only your contracted channel and the category inside that channel. They don't see competitors outside the marketplace (Falabella, Coppel, direct brand sites). They work as a starter proxy for single-channel retail, but fall short of serious pricing intelligence.
Is pricing intelligence legal? What about antitrust?
Monitoring public prices is legal in every LATAM country. The risk is coordination: using the same SaaS with direct competitors, exchanging non-public forecasts, signaling through fast algorithmic price matches. COFECE Mexico, FNE Chile, SIC Colombia, INDECOPI Peru, and CNDC Argentina all have active investigation methodologies.
Recommendation: consult an antitrust lawyer before launching and document your data isolation architecture.
How many SKUs do I need for pricing intelligence to pay back?
Empirical threshold: 500+ active SKUs with a 25%+ margin profile. Below that, a manual process is cheaper than automation. Exceptions: high-velocity-low-margin (FMCG) starts paying off from 200 SKUs; ultra-high-margin (luxury) can work from 50 SKUs.
Which KPIs should I put on the project?
Primary: portfolio gross margin versus a held-out control group, and gross profit per active SKU. Secondary: time-to-react to a competitive change (hours), share-of-shelf in monitored marketplaces, and the share of SKUs with a fresh competitive price (data freshness ≤24h).
Does Odoo help with pricing intelligence?
Odoo isn't a pricing intelligence platform by itself. But product.pricelist plus custom modules plus integration with an external pricing engine is a valid architecture. For our clients in Peru and Chile, the action layer runs on Odoo 17/18 Enterprise, while collection and modeling live as standalone Python services on GCP or AWS, connected through REST or Kafka.
Can I launch this without a data engineer on the team?
MVP, yes — through SaaS (Competera, Prisync, Sniffie, Pricefy). Production, no: you need at least one internal data engineer and one ML engineer. Without them, you're a hostage to the vendor and can't adapt the stack as the market moves.
How do I isolate antitrust risk when picking a vendor?
Three rules. One: never share the data lake source with a direct competitor. Two: negotiate explicit contract language that bars the vendor from sharing your pricing signals with third parties, even aggregated. Three: keep modeling internal with your own data; outsource only collection and matching. Keep audit logs of every algorithm-suggested price change.
