Wholesale Pricing & Forecasting: Volume Tiers, Commitments, and Margins

Blog

Wholesale Pricing & Forecasting: Volum...

Wholesale Pricing & Forecasting: Volume Tiers, Commitments, and Margins

30 Oct 2025

Business
Wholesale Pricing & Forecasting: Volume Tiers, Commitments, and Margins

Wholesale pricing for eSIM is different to retail: you’re negotiating capacity, not just buying SKUs. That means tiers, commits, and forecasting accuracy decide your margin as much as your selling price. In this guide we unpack the mechanics of wholesale pricing eSIM: how tier schedules actually calculate, what “hard vs soft” commitments mean in practice, and how to build a forecast tied to travel seasonality and itineraries data. You’ll find worked breakeven maths, practical demand-shaping tactics that don’t hurt the traveller experience, and checklists you can run every month. We’ll also show where regional packs such as Esim Western Europe or Esim North America help you reach volume tiers faster—while still giving travellers the coverage they expect across popular routes like the US, France, Italy and Spain. If you’re a reseller, OTA, fintech, or device brand building travel connectivity, use this as your operating playbook.

What drives wholesale pricing for eSIM?

Wholesale price per GB (or per bundle) is set by a few levers:

  • Volume tiers: lower unit costs kick in above stated thresholds (e.g., 10k, 50k, 100k GB/quarter).
  • Commitments: price discounts in exchange for a minimum draw (soft commit) or pay-or-take (hard commit).
  • Geography and roaming policy: single-country vs regional vs global; in-country vs roaming partners.
  • Validity and pack size: shorter validity and micro-packs cost more per GB; larger bundles cost less.
  • Quality-of-service: 4G/5G access, throttling thresholds, and fair-use policies.
  • Commercial terms: price hold periods, FX currency, payment terms, and promotion allowances.

Pro tip: - Aggregate demand into broader regional products (e.g., Esim Western Europe) to climb tiers faster without sacrificing the traveller experience.

Tier schedules that actually work

A tier schedule defines your unit cost as volume increases within a time window (usually monthly or quarterly). There are two common models:

1) Stair-step (all units at the tier rate once you pass the threshold)
2) Marginal (each tier’s rate applies only to the units within that tier band)

Sample stair-step schedule (quarterly, illustrative USD):

  • Tier 1: 0–9,999 GB = $4.50/GB
  • Tier 2: 10,000–49,999 GB = $3.90/GB
  • Tier 3: 50,000–99,999 GB = $3.30/GB
  • Tier 4: 100,000+ GB = $2.80/GB

Blended cost calculation example (stair-step): - If you end the quarter at 12,000 GB, all 12,000 GB price at $3.90 → Blended = $3.90/GB. - At 9,800 GB you’re stuck at $4.50/GB. Missing the 10k tier by 200 GB costs: 9,800 × ($4.50 − $3.90) = $5880.

Marginal schedule example: - First 10,000 GB at $4.50, next 40,000 GB at $3.90, etc. - Blended = (10,000 × $4.50 + 2,000 × $3.90) / 12,000 = $4.40/GB.

Pro tips: - Ask which model applies; your demand-shaping tactics differ materially between stair-step and marginal. - Request a end-of-period “true-up” option if you’re near a threshold; it reduces expensive shortfalls.

Commitments: soft vs hard (and why it matters)

Commitments exchange predictability for price. The fine print decides your risk.

  • Soft commit (drawdown): You commit to a volume window (e.g., 30 TB/quarter). If you fall short, you may roll forward a portion or pay a gap fee.
  • Hard commit (take-or-pay): You pay for the committed volume whether you consume it or not, usually for deeper discounts.
  • Floors/ceilings: Some contracts allow ±10–20% variance without penalty.
  • Price protection: The wholesale rate is held for a fixed term; important in volatile FX or roaming markets.
  • Carryover and expiry: Clarify if unconsumed volume can roll to the next period.

Worked example (quarterly): - Commit: 30,000 GB at $3.60/GB (hard). Retail ASP blended = $5.40/GB. - If you consume 27,000 GB, you still pay for 30,000 GB. Effective cost per consumed GB = (30,000 × $3.60)/27,000 = $4.00/GB (margin shrinks). - If you hit 35,000 GB and a “best-tier-applies” clause exists, you may benefit from the 50k band if the schedule is marginal and pro-rata true-up is allowed.

Checklist before you sign: - Commitment type and tolerance band - Tier model (stair-step vs marginal), and true-up mechanics - Price hold duration and currencies accepted - Carryover rules and expiry dates - Penalties, promo allowances, and support SLAs

Forecasting that matches travel seasonality

Travellers don’t move in straight lines; your forecast shouldn’t either. Anchor your plan to itineraries and known peaks.

Key inputs: - Bookings and search data by corridor (origin–destination) - Seasonality curves (e.g., Europe peaks Jun–Sep; US peaks around spring break and summer) - Product mix by destination: Esim United States, Esim France, Esim Italy, Esim Spain, and regional packs like Esim Western Europe or Esim North America - Attach rate assumptions by channel (web, app, checkout upsell)

Step-by-step: from itineraries to SKU forecast

1) Map corridors and destinations
- Use your booking data and reference coverage in Destinations to build a top-20 route list.

2) Build monthly arrival curves
- Distribute expected travellers by month using last year’s arrivals and events calendars (festivals, trade shows, school holidays).

3) Set attach rate per corridor
- Example: OTA checkout upsell 8–12%, post-booking emails 3–5%, in-app for existing users 15–25%.

4) Choose pack mix by stay length and use
- City-breakers: 3–5GB; road-trippers: 10–20GB; remote workers: 20–50GB regional packs.

5) Convert travellers to data volume
- Travellers × attach rate × average GB per plan = monthly GB demand.

6) Layer variance buffers
- Apply ±15% range, then choose a commit that your p50–p60 scenario can reliably hit.

Pro tips: - Bundle single-country with regional coverage to capture multi-country itineraries (e.g., France–Italy–Spain) under one plan and push volume into a single tier. - Use early-bird promotions to pull demand from month 1 to month 0 when you’re close to a tier.

Breakeven and margin maths made simple

Keep a small set of formulas in your pricing sheet:

  • Blended wholesale cost per GB = Weighted average of tiers and/or commits.
  • Revenue per GB (implied) = Average selling price (ASP) per plan ÷ Average consumed GB per plan.
  • Gross margin % = (Revenue − Cost) ÷ Revenue.

Worked example (USD, illustrative): - You sell a 10GB US plan at $18 ASP. Average actual consumption = 7.5GB (some users underuse). - Implied revenue per GB = $18 / 7.5 = $2.40/GB. - If your blended wholesale cost is $1.85/GB, gross margin = ($2.40 − $1.85) / $2.40 = 22.9%.

Breakeven ASP targeting: - Target ASP = Blended cost per GB × Expected consumption per plan ÷ (1 − Margin target) - With $1.85/GB cost, 7.5GB consumption, 25% margin: Target ASP = 1.85 × 7.5 ÷ 0.75 = $18.50.

Pro tips: - Monitor “consumption/entitlement ratio” (used GB ÷ plan GB). Improving utilisation by 0.5GB can lift margin more than a 20c price change. - FX hedging: if you buy in EUR and sell in USD/GBP, set an FX buffer in costs.

Demand shaping that respects travellers

The goal: reach better tiers without compromising experience.

Tactics that work: - Regional-first catalogues: Promote Esim Western Europe to travellers visiting France–Italy–Spain; promote Esim North America for US–Canada–Mexico trips. - Plan-size rationalisation: Offer 5GB/10GB/20GB core sizes; prune slow-moving variants that fragment volume. - Time-bound promos: Run 5–10% discounts late in the month/quarter if you’re within 5–8% of the next tier. - Value add-ons: Free hotspot allowance or extended validity instead of deep price cuts; protects ASP. - Tie-in at booking: Highlight coverage on destination pages like Esim France or Esim Italy within itineraries flows.

Guardrails: - Keep throttling and fair-use transparent; never silently degrade service to squeeze margin. - Cap promo frequency to avoid training customers to wait for discounts.

Risk management: variance and buffers

Even great forecasts miss. Design controls:

  • Safety commit: Contract at 60–70% of p50 demand; use spot or overage for spikes.
  • Spillover product: If a country SKU risks overage, route customers to a regional SKU with headroom.
  • Threshold alerts: Daily run-rate vs tier threshold; auto-trigger promotional levers when gap <8%.
  • SLA monitoring: Latency and attach success; quality issues can tank conversion and strand volume.

Scenario planning checklist

Run this monthly in the run-up to peak season:

  • Update arrivals and attach-rate assumptions by corridor
  • Refresh tier attainment model and true-up status
  • Recalculate blended cost and breakeven ASP
  • Identify SKUs to promote for tier climbing
  • Validate inventory/commit headroom by region
  • Confirm FX impact on costs and planned prices
  • Prepare switchbacks (alternative SKUs) if a network degrades

Case example: Western Europe summer peak

Context: - You expect 42,000 travellers across France–Italy–Spain June–August. - Attach rate target: 12% via checkout plus 4% in-app = 16% overall. - Average plan: 10GB regional.

Forecast: - Travellers × attach rate = 6720 plans. - Entitlement volume = 6720 × 10GB = 67,200 GB. Expected consumption ratio 0.75 → 50,400 GB used.

Commercial move: - Instead of three separate country SKUs, concentrate on Esim Western Europe to consolidate volume and achieve the 50k GB tier. - Offer a June pre-departure promo to pull 5% of July demand forward if you’re short of the threshold. - Feature destination coverage pages in your content stack: Esim France, Esim Italy, Esim Spain.

Outcome: - Blended wholesale rate improves by $0.40/GB at the higher tier, translating to ~$20k extra gross margin over the quarter without raising retail prices.

Operational mechanics and KPIs to track

Instrument these weekly:

  • Activation success rate and time-to-first-byte
  • Average consumed GB per plan and consumption/entitlement ratio
  • Top-ups per 100 activations
  • Overage and throttling incidence
  • Refund rate and support contact rate
  • Tier attainment tracker (run-rate vs thresholds)
  • Channel attach rate trends (checkout vs post-booking vs in-app)

Pro tip: - Tie a real-time “tier gap” widget into your merchandising engine to auto-boost regional SKUs when you’re near thresholds.

How Simology helps partners execute

  • Coverage and planning: Use Destinations to align catalogue with where travellers actually go, from the Esim United States to multi-country options like Esim North America.
  • Commercial tooling: Consolidate commits across country and regional SKUs, with clear stair-step vs marginal models and end-period true-up options where available.
  • Data and dashboards: Forecasting modules that ingest itineraries and seasonality; alerts for tier thresholds and SLA anomalies.
  • Partner enablement: Bulk provisioning, voucher flows, and flexible APIs via the Partner Hub.
  • B2B support: Contracting, FX-aware pricing guidance, and joint promotional planning—see For Business.

FAQ

1) What is “wholesale pricing eSIM” in plain terms?
It’s the rate you pay for eSIM data capacity at scale, influenced by volume tiers and commitments, not just per-plan retail price. Your margin depends on hitting thresholds and managing consumption.

2) Should I choose soft or hard commitments?
If your demand is seasonal or volatile, soft commits with limited carryover reduce risk. If your forecast is dependable and you can aggregate demand (e.g., regional SKUs), hard commits can unlock better rates.

3) How do I avoid missing a tier by a small margin?
Monitor run-rate daily. In the final week, promote regional packs (e.g., Esim Western Europe) or run a limited discount. Ask for end-of-period true-up rights when negotiating.

4) What pack sizes maximise margin without harming travellers?
Offer a tight set (5GB, 10GB, 20GB). Use data on average consumption; if 10GB users typically consume 7–8GB, pricing can be set to a healthy margin while keeping fair value.

5) Do regional eSIMs hurt user experience?
No—done right they improve it. Travellers moving between, say, France–Italy–Spain avoid swaps, and your volumes consolidate to better tiers. Highlight coverage pages like Esim Italy to build confidence.

6) How often can wholesale tiers or prices change?
Typically quarterly, with a price-hold clause. Mid-term adjustments can occur with FX swings or network changes; build 3–5% contingency into your margin model.

Next step: Explore tooling, APIs and commercial options in the Simology Partner Hub to structure your tiers, forecast with seasonality, and protect margins.

Read more blogs

Andes Highlights (3 Weeks): Peru–Bolivia–Chile–Argentina Connectivity

Andes Highlights (3 Weeks): Peru–Bolivia–Chile–Argentina Connectivity

Planning a south america itinerary 3 weeks through the high Andes? This route stitches together Peru’s Sacred Valley, Bolivia’s La Paz and Salar de Uyuni, Chile’s Atacama Desert, and northern Argentina’s quebradas or Mendoza wine country—often by long-distance bus and a couple of short flights. Connectivity is different at altitude: coverage is strong in cities but drops in high passes and salt flats; bus Wi‑Fi is patchy; border towns can be blackspots. The smart move is an eSIM with multi‑country coverage, backed by offline maps, offline translations, and a simple routine for crossing borders by bus without losing service. Below you’ll find a practical, connectivity-first itinerary; checklists to prep your phone, apps and documents; and on-the-ground tips for staying online where it matters: booking transport, hailing taxis, backing up photos, and navigating when the signal disappears.If you’re transiting via Europe or North America, you can also add a layover eSIM to stay connected door-to-door. Start with our country list on Destinations, then follow the steps, and you won’t waste time chasing SIM shops at 3,500 metres.The 3‑week Andes route at a glanceWeek 1: Peru (Cusco, Sacred Valley, Machu Picchu) - Fly into Cusco (or Lima then connect). - Base in Cusco; day trips to Pisac/Chinchero/Maras–Moray. - Train to Aguas Calientes; Machu Picchu visit; return to Cusco or continue to Puno/Lake Titicaca.Week 2: Bolivia and Chile (La Paz, Uyuni, San Pedro de Atacama) - Bus/collectivo via Copacabana to La Paz. - Fly or overnight bus to Uyuni. - 3‑day Uyuni–altiplano tour ending in San Pedro de Atacama (Chile).Week 3: Chile and Argentina (Atacama to Salta or Mendoza/Buenos Aires) - Choose: - North: San Pedro to Salta/Jujuy by bus; fly to Buenos Aires. - Or South: San Pedro–Calama flight to Santiago; bus or flight to Mendoza; onward to Buenos Aires.Connectivity notes (quick): - Cities: generally strong 4G/4G+; 5G in major hubs (Santiago, Buenos Aires). - Altitude/rural: expect long no‑signal stretches (Uyuni, altiplano passes, Paso Jama). - Bus Wi‑Fi: often advertised, rarely reliable. Plan to be offline onboard. - Border regions: networks switch; a multi‑country eSIM avoids sudden loss.eSIM vs local SIMs for a 4‑country tripFor a route with multiple borders and remote legs, eSIM wins on time and reliability.What a multi‑country eSIM gets you: - One plan across Peru, Bolivia, Chile, Argentina (check coverage per country on Destinations). - No passport/SIM registration queues at kiosks. - Keep your home number active on the physical SIM for calls/SMS codes. - Instant top‑ups if you burn data on photos or navigation.When a local SIM still helps: - Long stay in one country with heavy data use (e.g., a month in Buenos Aires). - Dead zones where a different local network performs better (rarely worth the hassle on a 3‑week pace).Practical approach: - Use an eSIM as your primary data line across all four countries. - If you find a specific local network far better in one region, add a cheap local SIM and keep the eSIM as backup.Device readiness checklist (before you fly)1) Check eSIM compatibility and SIM‑lock status on your phone.2) Buy and install your eSIM while on home Wi‑Fi. Keep a PDF/printed copy of the QR code.3) Label lines clearly (e.g., “eSIM Andes Data”, “Home SIM”).4) Turn on data roaming for the eSIM; leave roaming off for your home SIM to avoid charges.5) Set up dual‑SIM rules: data on eSIM; calls/SMS default to home SIM if needed.6) Download offline: Google Maps/Organic Maps for all target regions; language packs (Spanish at minimum); bus/air tickets; hotel confirmations.7) Cloud backups: set to upload on Wi‑Fi only; pre‑create shared albums for travel companions.8) Test tethering/hotspot with your laptop/tablet.If you’re transiting popular hubs, consider a short layover eSIM: - USA connections: add an Esim United States or a broader Esim North America.- Europe connections: Madrid/Barcelona? Use an Esim Spain. Paris or Rome? See Esim France and Esim Italy. Multi‑country layovers? Try Esim Western Europe.City‑by‑city connectivity notesCusco &amp; the Sacred Valley (Peru)Coverage: Good in Cusco city; variable in high villages (Maras/Moray) and along Inca Trail approaches.Tips: Download Sacred Valley maps offline; pin viewpoints and ruins. most taxis use WhatsApp—save your accommodation’s number.Machu Picchu/Aguas Calientes: Patchy to none at the citadel. Upload your photos later; don’t rely on live ticket retrieval.Lake Titicaca: Puno and CopacabanaPuno: Reasonable 4G; bus terminals crowded—screenshot QR tickets.Crossing to Copacabana: Expect a signal drop around the border; have directions saved offline.La Paz (Bolivia)Good urban 4G; the cable car network has decent signal but tunnels do not.Yungas/“Death Road” tours: Mountain valleys cause dead zones—share your emergency contacts with the operator, carry a charged power bank, and don’t plan remote calls.Uyuni and the Altiplano (Bolivia to Chile)Uyuni town: OK 4G; ATMs finicky—use Wi‑Fi for banking apps.Salt flats/lagunas: Assume offline for most of the 3‑day tour. Guides often carry satellite phones; agree a pickup time/place in San Pedro and preload your map route.San Pedro de Atacama (Chile)Town: Solid 4G; accommodations often have Wi‑Fi but speeds vary.Geysers, Valle de la Luna: Offline navigation essential; sunrise trips start before mobile networks wake up in some areas.Salta/Jujuy or Mendoza/Buenos Aires (Argentina)Salta/Jujuy: Good city coverage; quebradas have long no‑signal sections.Mendoza: City 4G/5G; vineyards outside town can be patchy.Buenos Aires: Strong 4G/5G; ideal for cloud backups and large downloads before you fly home.Border crossings by bus: step‑by‑stepThe big ones on this route: Peru–Bolivia (Puno/Copacabana), Bolivia–Chile (Uyuni–San Pedro via Hito Cajón), Chile–Argentina (Paso Jama to Salta or Los Libertadores to Mendoza).How to keep service and sanity:1) The day before:- Top up your eSIM data.- Confirm your plan includes both countries you’re entering/leaving.- Download offline maps for both sides of the border and your town of arrival.- Save bus company WhatsApp and terminal address offline.2) On departure morning:- Keep a paper copy or offline PDF of tickets, insurance, and accommodation proof.- Charge phone and power bank; pack a short cable in your daypack.3) On the bus:- Don’t count on bus Wi‑Fi. Keep your eSIM as primary, but expect drops near mountain passes.- If your phone supports it, enable “Wi‑Fi calling” for later when you reach accommodation Wi‑Fi.4) At the border posts:- Data may be unavailable. Keep QR codes and booking numbers offline.- After exiting one country and entering the next, toggle Airplane Mode off/on to re‑register on the new network.- If the eSIM doesn’t attach, manually select a network in Mobile Settings.5) Arrival:- Send your accommodation a quick WhatsApp when you’re back online.- Recheck your eSIM’s data roaming is on; confirm you’re on an in‑country network, not a weak roaming partner.Pro tips: - Dual profiles: If your eSIM allows, keep a secondary profile for a different network in the same country—helpful in border towns.- Cash buffer: Some border terminals don’t accept cards; download a currency converter for offline use.Offline survival kit (5‑minute setup)Maps: Download regions for Cusco, Sacred Valley, Puno, La Paz, Uyuni, San Pedro, Salta/Jujuy or Mendoza, and Buenos Aires.Translations: Download Spanish for offline use; add phrasebook favourites (bus tickets, directions, dietary needs).Documents: Save PDFs of passports, tickets, hotel addresses; star them for quick access.Rides: Screenshots of pickup points; pin bus terminals and hotel doors.Entertainment: Podcasts and playlists for long bus legs, set to download on Wi‑Fi only.Altitude and your tech: what changesCoverage gaps lengthen: Fewer towers at high altitude; valleys can block signal. Assume offline on remote excursions.Batteries drain faster in cold: Keep your phone warm and carry a power bank (10,000–20,000 mAh).Hotel Wi‑Fi may be congested: Schedule big uploads (photo backups, app updates) for big-city stays like Santiago or Buenos Aires.GPS still works offline: Your blue dot shows on offline maps without data—preload everything.Data budgeting for 3 weeksTypical traveller usage across this route: - Messaging/Maps/Bookings: 0.2–0.5 GB/day- Social and photo sharing: 0.3–0.7 GB/day- Occasional video calls/streaming: 0.5–1.0 GB/dayFor a mixed-use trip, plan 15–25 GB for 3 weeks. Heavy creators should double it and upload over hotel Wi‑Fi when possible. If you work remotely, consider a higher‑capacity plan and a backup eSIM; see our guidance on For Business.Practical route with transport and connectivity cuesDays 1–4 Cusco base: Strong city signal; day trips may be spotty—go offline-ready.Days 5–6 Machu Picchu: Expect no service at the ruins; sync tickets ahead.Days 7–8 Puno to La Paz via Copacabana: Border signal drop; re‑register networks after crossing.Days 9–11 Uyuni tour to San Pedro: Treat as offline; charge nightly; carry spare cables.Days 12–14 San Pedro: Stable in town; tours offline; top up data before Paso Jama.Days 15–17 Salta/Jujuy or Mendoza: Good urban 4G; rural patches are offline.Days 18–21 Buenos Aires: Strongest connectivity of the trip; clear your uploads and map downloads for the flight home.Partnering and stopover extrasHospitality and tour operators in the Andes: help your guests stay connected—explore co‑branded solutions via our Partner Hub.Transatlantic flyers: test your eSIM setup on a layover with an Esim United States or Esim Western Europe before hitting high-altitude blackspots.FAQs1) Do I need a local SIM in each country?No. A multi‑country eSIM covering Peru, Bolivia, Chile and Argentina is simpler and works well for a 3‑week pace. Consider a local SIM only if you’ll spend longer in one country and want the absolute best regional coverage.2) Will my WhatsApp number change with an eSIM?No. WhatsApp is tied to your registered number, not your data line. Keep your home SIM active for voice/SMS (roaming off if you wish), and use the eSIM for data—WhatsApp continues as normal.3) Can I hotspot to my laptop or camera?Yes. Enable tethering on your eSIM. Mind your data: cloud backups and OS updates can burn gigabytes—set them to Wi‑Fi only or schedule in big cities.4) What if there’s no signal on the Uyuni/Atacama legs?That’s expected. GPS still works offline. Pre-download maps and translations, carry a power bank, and sync plans with your tour operator before departure.5) Will I get roaming charges at borders?If you’re using a multi‑country eSIM with coverage in both countries, you won’t incur extra roaming fees from your home carrier. Keep roaming off on your home SIM to avoid accidental use.6) I’m connecting via Europe or the US—worth getting a layover eSIM?Yes. It’s an easy way to test your setup and stay reachable. Try Esim North America or country options like Esim Spain, Esim France, or Esim Italy for common hubs.Next step: Browse South America coverage options and build your plan on Destinations.

31 Oct 2025
Best eSIM for Europe (2025): Plans, Coverage, Fair-Use

Best eSIM for Europe (2025): Plans, Coverage, Fair-Use

Choosing the best eSIM for Europe in 2025 comes down to what you actually do on the road: how many countries you’ll cross, how much data you burn, whether you need 5G, and if hotspot tethering matters. Pricing is competitive, but not all “Europe” eSIMs are equal—some throttle after small “unlimited” buckets, some exclude popular destinations, and others won’t let you tether at all. This guide compares Europe-ready eSIMs by price per GB, 5G access, hotspot policy, and fair-use rules, so you don’t discover limits at the worst time (like mid-ride-share across borders).For most travellers, Simology’s regional plan is a standout: consistent 4G/5G coverage across key countries, transparent allowances, hotspot enabled, and simple top-ups. If you’re mainly in one country, a local eSIM (e.g., France, Italy, Spain) can push price per GB down even further. Flying via the US or Canada? Pair a Europe eSIM with a North America plan to stay connected gate-to-gate. Below is how to choose, what to expect, and the fastest way to avoid fair-use surprises.Quick verdict: the best eSIM for Europe in 2025Best overall for multi-country trips: Simology Esim Western Europe — multi-country coverage, hotspot allowed, fair-use clearly stated, easy top-up.Best value if staying in one country: Simology country eSIMs such as Esim France, Esim Italy and Esim Spain — usually the lowest price per GB.Best for transatlantic travellers: Pair Esim United States or Esim North America with a Europe plan for seamless coverage on both sides.Best for teams and frequent flyers: Managed accounts via For Business — pooled visibility, cost control, consolidated billing.If you’re unsure which countries are covered, start with the full list on Destinations.How we compared Europe eSIMsPrice per GB: Divide plan price by included GB. Ignore “unlimited” claims unless a clear daily/total high-speed cap is disclosed.Coverage footprint: Number of countries, inclusion of the big four (France, Italy, Spain, Germany) plus the UK, Nordics, Benelux, Portugal, Switzerland and popular Balkans.Network quality: Access to top local operators and 5G in major cities; no permanent throttling.Hotspot/tethering: Explicitly allowed by default.Fair-use policy (FUP): Transparent thresholds, reasonable roaming terms, and no punitive restrictions for normal travel use.Ease of use: Instant delivery, QR installation, quick top-ups, responsive support.Simology’s regional and country eSIMs score well on the above, particularly on price-per-GB transparency and hotspot inclusion.The best Simology picks for EuropeEsim Western Europe — top pick for most travellersWho it’s for: - City-hoppers doing 3–12 countries in one trip - Families or remote workers who rely on hotspot - Travellers wanting simple top-ups and a single eSIM across bordersWhat you get: - Broad multi-country coverage across Western Europe with 4G/5G where available - Hotspot/tethering enabled - Clear, upfront data allowances with straightforward price-per-GB - Friendly fair-use terms intended for travel (not permanent roaming)Why it’s hard to beat: - You avoid the SIM shuffle at borders and keep one APN and one data monitor - 5G in major hubs for quick downloads and video calls - Competitive price-per-GB compared with typical regional packsConsider if: - You’re mostly staying in one country (a local eSIM may be cheaper per GB) - You need calling minutes (data-only eSIMs use VoIP apps; pair with your primary SIM for voice/SMS)Check availability and covered nations on Esim Western Europe and confirm your route against Destinations.Country eSIMs — the best price per GB when you stay putIf your itinerary centres on a single country, local plans often win on value and sometimes on peak speeds.France: See Esim France for dense 5G in Paris, Lyon, Marseille and strong rail-corridor coverage. Excellent for city weekends and Riviera road trips.Italy: Esim Italy offers solid 5G in major cities and coastal belts; good for hotspots on trains and ferries.Spain: With Esim Spain, coverage is wide across cities and islands; great for digital nomads needing steady tethering.Choose a country eSIM when: - You won’t cross borders or only do a quick day trip - You want the lowest cost per GB and plan to stream or hotspot frequentlyTransatlantic and multi-region itinerariesConnecting through North America? Avoid airport Wi‑Fi hunting by pairing your Europe eSIM with a North America plan:USA only: Esim United StatesUS/Canada/Mexico: Esim North AmericaInstall both profiles before you fly, then toggle data lines per region. If you’re organising trips for teams or events, centralise management with For Business. Travel brands and creators can explore partnerships via the Partner Hub.Fair-use policies in Europe explained (and how they affect you)Fair-use policies exist to prevent abuse of roaming and unlimited plans. Here’s what matters in practice:Roaming vs “local”: Most Europe eSIMs are regional roaming bundles. That’s fine for travel, but networks may apply FUP while roaming, such as deprioritisation or caps during congestion.“Unlimited” usually isn’t: High-speed data often has a daily or total cap (e.g., 1–5 GB/day at full speed, then throttled). If a plan says unlimited, look for the high-speed allowance first.Hotspot limits: Some providers block tethering or throttle hotspot specifically. Simology plans allow hotspot by default unless stated otherwise.Country exclusions: Not every “Europe” plan includes Switzerland, the Balkans or microstates. Confirm the exact list on Destinations.Usage window: Plans run for a set validity period from first activation; unused data may not roll over.Practical takeaways: - Pick a plan with a clear high-speed allowance if you work on the go. - Expect speed variation at busy times or on rural routes; try different network selections if your device allows. - For long trips, buy a sensible base allowance and top up rather than chasing “unlimited”.Step-by-step: how to choose the right Europe eSIM1) Map your route - List every country and the number of days in each. - If 3+ countries, lean towards Esim Western Europe; otherwise a country eSIM may be cheaper.2) Estimate your data need - Light (maps, messages, occasional rides): 3–5 GB/week - Moderate (social, short video, hotspot for email): 6–10 GB/week - Heavy (HD video, frequent hotspot/video calls): 12–20 GB+/week3) Decide on 5G vs 4G - If you upload media, join video calls, or plan to tether often, choose 5G access where available.4) Confirm hotspot - Ensure your plan explicitly allows tethering if you’ll share data to a laptop or tablet.5) Plan your dual-SIM setup - Keep your home SIM active for calls/SMS, but set the eSIM as your data line and switch data roaming off on your primary SIM to avoid bill shock.6) Check device compatibility - Most recent iPhone, Samsung Galaxy, Google Pixel and other flagships support eSIM. If unsure, consult your device specs.7) Buy and install early - Purchase from Simology, scan the QR code, and add the eSIM before departure while on good Wi‑Fi.8) Test and label - Toggle mobile data to the eSIM briefly at home to confirm activation. Name it “Europe Data” (or country) to avoid confusion.Activation and on‑trip checklistBefore you fly: - Install your eSIM profile over Wi‑Fi. - Set the eSIM as “Mobile Data” line; turn data roaming off on your primary SIM. - Download offline maps; update apps while on Wi‑Fi.On arrival: - Toggle the eSIM data line on. - Ensure Data Roaming is enabled for the eSIM line. - If speeds seem slow, briefly toggle Airplane Mode or select a different partner network in Settings.During your trip: - Monitor data usage in your phone settings. - Hotspot when needed; disable when idle to save battery and data. - Top up through your Simology account if you’re running low.Pro tips to save data and avoid surprisesUse Low Data Mode/ Data Saver on your phone.Disable auto-play for video in social apps.Cache music and podcasts on Wi‑Fi.Prefer Wi‑Fi for big backups; pause cloud photo sync while roaming.Use Wi‑Fi calling for voice; WhatsApp/FaceTime use your existing number even on a data-only eSIM.For road trips, keep offline maps for every country you’ll cross.If you’ll be in the US before/after Europe, install Esim United States or Esim North America in advance.FAQ: Europe eSIMs1) Will my phone work with a Europe eSIM? - Most recent iPhone (XR/XS and newer), Google Pixel (3 and newer), and flagship Samsung devices support eSIM. Region-specific models vary. If in doubt, check your device settings for “Add eSIM” or consult the manufacturer’s specs.2) Can I use hotspot/tethering with Simology eSIMs? - Yes, Simology plans allow hotspot unless stated otherwise on the specific product page. Tethering performance depends on local network conditions.3) How fast is 5G in Europe? - In major cities, typical real-world 5G ranges from 150–500 Mbps, with higher peaks possible. Speeds vary by network, location, and time of day, and can be managed during congestion.4) I’m visiting 8–10 countries in two weeks. What’s best? - A regional plan like Esim Western Europe keeps things simple across borders. If you’ll spend 5+ days in a single country with heavy usage, add a local eSIM (e.g., Esim France or Esim Italy) for cheaper per‑GB data during that block.5) Do I need to show ID to buy an eSIM in Europe? - Most data-only eSIMs in Europe do not require ID, but requirements vary by country. If verification is required, Simology will prompt you during checkout.6) Can I keep my WhatsApp number and receive texts from my bank? - Yes. Your WhatsApp stays linked to your number. Keep your physical SIM active for SMS; set the eSIM as data-only and turn off data roaming on the primary SIM to avoid charges.The bottom lineThe best eSIM for Europe is the one that matches your route, data habits, and need for 5G and hotspot. For most travellers crossing multiple borders, Simology’s Esim Western Europe combines solid coverage, transparent allowances, and tethering without hoops. If you’ll camp in one country, local eSIMs like Esim France, Esim Italy or Esim Spain usually deliver the lowest price per GB. Flying via the US or Canada? Add Esim United States or Esim North America for smooth connectivity end to end.Next step: Compare coverage and pick your plan on Esim Western Europe.

30 Oct 2025
Simology API & SDK: Quick Start for Catalog, Checkout & Activation Webhooks

Simology API & SDK: Quick Start for Catalog, Checkout & Activation Webhooks

Integrating Simology’s eSIM into your app or site should be quick, safe and predictable. This guide shows you how to stand up a working flow end‑to‑end: pull a live catalogue, create a checkout, and handle activation webhooks to deliver eSIM credentials. You’ll get example endpoints, headers, sample payloads, sandbox tips, and robust error and retry strategies so you can go live with confidence.We assume you’re building for travellers and want a clean, reliable purchase and activation journey. The same patterns apply whether you’re selling a single-country plan like Esim United States or regional bundles such as Esim Western Europe and Esim North America. If you’re still shaping your plan range, explore available markets on Destinations and see what resonates with your audience. When you’re ready to partner, head to the Partner Hub or our For Business page to get access.What you’ll buildA minimal, production‑ready integration includes:Catalog: Fetch plans (SKU, coverage, allowance, validity, price) and display them.Checkout: Create an order/checkout session and direct the user to pay.Webhooks: Receive order status and eSIM activation credentials securely.Activation: Present LPA QR or SM‑DP+ + activation code in your UI.Post‑purchase: Poll or subscribe to status updates; offer top‑ups if supported.PrerequisitesA Simology partner account with API credentials: request access via the Partner Hub.Sandbox environment enabled (for test cards and simulated activations).Public HTTPS webhook endpoint (TLS 1.2+, supports POST, returns 2xx on success).Server ability to store secrets and verify signatures.Optional: SDK installed (Node.js or Python) or curl for initial testing.Tip: While you prototype, use live product copy from Destinations. For regional content and FAQs, see Esim France, Esim Italy and Esim Spain.Environments and authenticationTypical environment split:Sandbox base URL (example): https://sandbox-api.simology.ioProduction base URL (example): https://api.simology.ioAuthentication:Use the HTTP header: Authorization: Bearer YOUR_API_KEYSend JSON: Content-Type: application/jsonUse idempotency for POSTs: Idempotency-Key: a-unique-uuid-per-intentPro tips: - Rotate keys regularly; keep them server-side only. - Scope keys to least privilege; separate sandbox and production keys. - Log the response header request_id (if provided) for faster support.Step 1: Fetch the eSIM catalogueEndpoint (example): - GET /v1/catalog?country=US - GET /v1/catalog?region=western-europeExample request:GET /v1/catalog?country=US HTTP/1.1 Host: sandbox-api.simology.io Authorization: Bearer sk_sandbox_123 Accept: application/json Example response:{ &nbsp;"items": [ &nbsp; &nbsp;{ &nbsp; &nbsp; &nbsp;"sku": "US-5GB-30D", &nbsp; &nbsp; &nbsp;"name": "United States 5 GB / 30 days", &nbsp; &nbsp; &nbsp;"region": "US", &nbsp; &nbsp; &nbsp;"coverage": ["US"], &nbsp; &nbsp; &nbsp;"data_allowance_mb": 5120, &nbsp; &nbsp; &nbsp;"validity_days": 30, &nbsp; &nbsp; &nbsp;"price": { "amount": 14.99, "currency": "USD" }, &nbsp; &nbsp; &nbsp;"activation_method": "lpa", &nbsp; &nbsp; &nbsp;"esim_type": "data", &nbsp; &nbsp; &nbsp;"terms_url": "https://simology.io/esim-united-states", &nbsp; &nbsp; &nbsp;"available": true &nbsp; &nbsp;} &nbsp;], &nbsp;"updated_at": "2025-01-10T09:12:44Z" } Implementation notes: - Cache catalogue responses for several minutes; invalidate on webhook or daily refresh. - Use query params to filter by country/region to reduce payloads. - Map regional SKUs to your UX—e.g., “Western Europe” → Esim Western Europe.Pro tips: - Localise currencies client-side only if your payment provider requires it; keep SKU and currency from the API authoritative. - Surface coverage and validity clearly; travellers value transparency.Step 2: Create a checkout session (order)Endpoint (example): - POST /v1/checkout/sessionsExample request:{ &nbsp;"customer": { &nbsp; &nbsp;"email": "alex@example.com", &nbsp; &nbsp;"country": "GB" &nbsp;}, &nbsp;"items": [ &nbsp; &nbsp;{ "sku": "US-5GB-30D", "quantity": 1 } &nbsp;], &nbsp;"success_url": "https://yourapp.example/checkout/success?session_id={SESSION_ID}", &nbsp;"cancel_url": "https://yourapp.example/checkout/cancel", &nbsp;"metadata": { &nbsp; &nbsp;"user_id": "u_789", &nbsp; &nbsp;"source": "ios-app" &nbsp;} } Example response:{ &nbsp;"id": "cs_abc123", &nbsp;"payment_url": "https://pay.sandbox.simology.io/cs_abc123", &nbsp;"status": "pending", &nbsp;"expires_at": "2025-01-10T09:27:44Z" } Redirect the user to payment_url.On success, Simology will send a webhook (see next step) such as checkout.completed or order.paid.Error example:{ &nbsp;"error": { &nbsp; &nbsp;"code": "sku_unavailable", &nbsp; &nbsp;"message": "Requested SKU is not available in the selected region.", &nbsp; &nbsp;"request_id": "req_9x8y7z" &nbsp;} } Pro tips: - Always include a unique Idempotency-Key on POSTs to prevent duplicate orders. - Do not fulfil on the browser redirect alone; wait for the signed webhook.Step 3: Webhooks for checkout and activationExpose a POST endpoint, e.g., https://yourapp.example/webhooks/simologyExpected events (names may vary by integration): - checkout.completed — customer returned from payment - order.paid — funds confirmed; fulfilment can begin - activation.ready — eSIM credentials ready for delivery - order.failed or payment.failed — handle gracefullySecurity: - Simology signs webhook payloads. Expect a header like: - Simology-Signature: t=1736500000,v1=hex-hmac-sha256 - Verify HMAC using your webhook secret and the raw request body + timestamp t. - Reject if signature invalid or timestamp skew &gt; 5 minutes.Example webhook: order.paid{ &nbsp;"type": "order.paid", &nbsp;"id": "evt_123", &nbsp;"created": "2025-01-10T09:20:02Z", &nbsp;"data": { &nbsp; &nbsp;"order_id": "ord_456", &nbsp; &nbsp;"session_id": "cs_abc123", &nbsp; &nbsp;"items": [ &nbsp; &nbsp; &nbsp;{ "sku": "US-5GB-30D", "quantity": 1, "unit_price": 14.99, "currency": "USD" } &nbsp; &nbsp;], &nbsp; &nbsp;"customer": { "email": "alex@example.com" } &nbsp;} } Example webhook: activation.ready{ &nbsp;"type": "activation.ready", &nbsp;"id": "evt_789", &nbsp;"created": "2025-01-10T09:21:10Z", &nbsp;"data": { &nbsp; &nbsp;"order_id": "ord_456", &nbsp; &nbsp;"line": { &nbsp; &nbsp; &nbsp;"iccid": "8988307000001234567", &nbsp; &nbsp; &nbsp;"smdp_plus": "LPA:1$sm-dp-plus.simology.net$ACT-CODE-1234", &nbsp; &nbsp; &nbsp;"qr_url": "https://sandbox-api.simology.io/v1/qr/ord_456.png", &nbsp; &nbsp; &nbsp;"valid_from": "2025-01-10T09:21:10Z", &nbsp; &nbsp; &nbsp;"expires_at": "2025-02-09T23:59:59Z" &nbsp; &nbsp;} &nbsp;} } Retries: - Respond 2xx on success within 5 seconds. - Non-2xx triggers automatic retries with exponential backoff (e.g., 1m, 5m, 30m, hourly up to 48h). - Webhooks are idempotent; use the event id to deduplicate.Pro tips: - Store the full webhook event before processing; reprocess safely if needed. - Use a separate signing secret per environment; rotate on a schedule.Step 4: Deliver and activate the eSIMOnce you receive activation.ready: - If you display QR in-app: render qr_url or generate your own QR from the LPA string (smdp_plus). Confirm the screen brightness/instructions for scanning. - If you deliver manually: present the SM‑DP+ address and activation code clearly.UI checklist: - Show coverage and validity (mirror your catalogue details, e.g., Esim North America). - Provide concise device instructions (Settings &gt; Mobile Data &gt; Add eSIM). - Remind users to keep primary SIM for calls/SMS if needed, using data on eSIM. - Offer a link back to plan details (e.g., Esim United States) for FAQs.Step 5: Post‑activation status and top‑upsCommon endpoints (examples): - GET /v1/orders/{order_id} — check latest status. - GET /v1/lines/{iccid} — inspect data used/remaining. - POST /v1/topups — add data to an existing line.Example line status:{ &nbsp;"iccid": "8988307000001234567", &nbsp;"status": "active", &nbsp;"data": { &nbsp; &nbsp;"used_mb": 1200, &nbsp; &nbsp;"remaining_mb": 3920 &nbsp;}, &nbsp;"valid_until": "2025-02-09T23:59:59Z" } Pro tips: - Cache status for 30–60 seconds to avoid rate limits. - If you surface data usage, include a timestamp and note that roaming networks can report with slight delay.Errors, rate limits and observabilityHTTP status patterns: - 400 validation_error — your request is malformed (missing field, invalid SKU). - 401/403 auth_error — bad or expired credentials, wrong environment key. - 404 not_found — order/line ID not recognised. - 409 conflict — duplicate idempotency key with different payload. - 429 rate_limited — back off using Retry-After header. - 5xx server_error — transient; retry with backoff and jitter.Canonical error body:{ &nbsp;"error": { &nbsp; &nbsp;"code": "rate_limited", &nbsp; &nbsp;"message": "Too many requests. Try again later.", &nbsp; &nbsp;"request_id": "req_123", &nbsp; &nbsp;"retry_after": 30 &nbsp;} } Best practices: - Always log request_id and error.code. - Implement circuit breakers for persistent 5xx. - Respect Retry-After on 429; apply exponential backoff with jitter. - Use unique Idempotency-Key per action (e.g., “create checkout for cart 123”). - Monitor webhook delivery success rate and age of last processed event.SDK quick startWhile you can integrate with raw HTTP, SDKs speed up auth, idempotency and webhook verification. The shapes below reflect the examples above; adapt to your language and tooling.Node.js (example):import { Simology } from "@simology/sdk"; const sim = new Simology({ apiKey: process.env.SIMOLOGY_API_KEY, baseUrl: "https://sandbox-api.simology.io" }); const catalog = await sim.catalog.list({ country: "US" }); const session = await sim.checkout.create({ &nbsp;customer: { email: "alex@example.com", country: "GB" }, &nbsp;items: [{ sku: "US-5GB-30D", quantity: 1 }], &nbsp;success_url: "https://yourapp.example/success?session_id={SESSION_ID}", &nbsp;cancel_url: "https://yourapp.example/cancel" }); Webhook verification (pseudo):app.post("/webhooks/simology", express.raw({ type: "application/json" }), (req, res) =&gt; { &nbsp;const signature = req.header("Simology-Signature"); &nbsp;const event = sim.webhooks.verify(req.body, signature, process.env.SIMOLOGY_WEBHOOK_SECRET); &nbsp;// process event.type ... &nbsp;res.sendStatus(200); }); Python (example):from simology import Simology sim = Simology(api_key=os.getenv("SIMOLOGY_API_KEY"), base_url="https://sandbox-api.simology.io") catalog = sim.catalog.list(country="US") Tip: Keep the webhook route using raw body to preserve signature integrity.Security and privacy essentialsStore only what you need (e.g., order_id, sku, iccid). Avoid storing full QR images if the LPA string is sufficient.Encrypt secrets at rest; restrict access via IAM.Validate webhook payload against expected schema before acting.Do not render raw error messages to end users; translate to helpful guidance.Go‑live checklistSandbox to production switch with environment flags.API key rotation plan and secret storage verified.Idempotency implemented on all POST operations.Webhook endpoint verified with signature checks and 2xx acks.Observability: logs capture request_id, event.id, order_id, iccid.Rate limit handling and backoff tested.Happy path and failure path user messaging in place.Regional catalogue mapped to your content (e.g., Esim France, Esim Italy).FAQHow do sandbox and production differ? Sandbox uses test payment and simulated activation events. Payload shapes mirror production, but no real provisioning occurs. Use separate API keys and webhook secrets per environment.Can I test activation without scanning a QR? Yes. Use the LPA string (SM‑DP+ and activation code) from activation.ready to test your UI. In sandbox, you can display it without provisioning a real profile.What happens if my webhook endpoint is down? Simology retries with exponential backoff for a defined window (for example, up to 48 hours). Keep processing idempotent and return 2xx only after you have safely stored/handled the event.How should I handle plan regions in my UX? Keep your SKUs aligned with clear coverage descriptions (country vs region). Link to destination pages like Esim United States or Esim Western Europe for clarity, and aggregate them under Destinations.Can I issue refunds or cancellations via API? Many setups support POST /v1/refunds or cancelling unpaid checkouts. Always wait for webhook confirmation (refund.processed) before altering customer entitlements.Do you support top‑ups and usage queries? Yes in most cases—use the lines and topups endpoints as shown. Cache usage responses briefly and inform travellers about reporting delays when roaming.Next step: Ready to get credentials and sandbox access? Visit the Partner Hub to kick off your integration.

30 Oct 2025