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
Dual SIM with eSIM: Two Numbers on One Phone (Calls, OTPs, Data)

Dual SIM with eSIM: Two Numbers on One Phone (Calls, OTPs, Data)

Staying reachable without burning money on roaming is the modern traveller’s headache. Dual SIM with eSIM solves it: keep your main number active for calls and OTPs, and add a low-cost local or regional data plan on the same phone. No SIM swapping. No missed texts from your bank. In this guide, we explain how dual SIM with eSIM works, how calls/SMS/data behave, and how to set it up on iPhone and Android. We also cover common use cases like work/personal separation and travel/local pairing, plus how WhatsApp and other apps handle two numbers. If you’re planning a trip, browse country and regional options via Destinations or pick ready-made bundles such as Esim Western Europe or Esim North America. For the US or single-country trips, see Esim United States, Esim France, Esim Italy and Esim Spain.What is dual SIM with eSIM?Dual SIM means your phone can maintain two mobile lines at once. One or both can be eSIMs (digital SIM profiles). Typical setups: - Physical SIM + eSIM active together. - Two eSIMs active (on many newer devices). - Multiple eSIM profiles stored, with up to two active at a time (device-dependent).On dual SIM dual standby (DSDS) phones, both lines are “on” for calls and texts when idle. You set a default line for data, calls and messages, and you can switch defaults at any time.Device support varies. Recent iPhones and most mid/high-end Android phones support dual SIM with eSIM, but some models allow only one eSIM active at a time or restrict 5G/VoLTE on the secondary line. Check your device’s specs before you travel.Why use dual SIM eSIM? Practical use casesWork and personal separationKeep your personal number private while making and receiving work calls on a second line.Set the default for outgoing calls to your work line during office hours and flip it back to personal later.Mute one line at set times to reduce interruptions without missing urgent personal calls.Travel: keep your home number for OTPs, add local dataKeep your home SIM active for banking OTPs, two-factor codes and critical calls.Add a local or regional eSIM for affordable 4G/5G data and local rates.Disable data roaming on your home line to avoid bill shock; use the travel eSIM for all data.Pick country plans like Esim United States, Esim France, Esim Italy or Esim Spain, or choose a multi-country pass such as Esim Western Europe or Esim North America. Explore more via Destinations.Coverage and cost optimisationUse the line with stronger coverage for data in fringe areas.Keep a cheap voice/SMS plan on one line and a high-data plan on the other.Switch defaults on the fly when you cross borders or move between networks.Teams, events and short-term projectsProvision temporary eSIM lines for contractors, events or field staff without shipping plastic SIMs.Centrally manage usage and budgets; see For Business.Partners and resellers can streamline deployments via the Partner Hub.How calls, SMS, data, OTPs and apps behaveUnderstanding how two lines interact avoids surprises.Calls in standby: Both lines can receive calls when idle. When you place or receive a call on one line, the other may go to voicemail or show as unreachable unless your device/network supports features like call waiting across lines or Wi‑Fi Calling. Behaviour varies by carrier and phone.Default for voice/SMS: You choose a default line for outgoing calls and texts, but you can select the other line per contact or per call.Mobile data: Only one line provides mobile data at a time. You set this in settings. Some phones support “allow mobile data switching”, automatically using the other line if the selected data line has weak signal.SMS-based OTPs: OTP texts arrive on the line tied to that number as long as that line is enabled and has signal. Data does not need to be enabled on that line. If you’re abroad, receiving OTPs may incur roaming SMS charges on your home line—turn off data roaming but keep SMS/calls enabled to control costs.iMessage/FaceTime (iPhone): You can enable iMessage/FaceTime for one or both numbers and choose which to use by default.WhatsApp and similar apps:The standard WhatsApp app supports one number per device. Data can come from either line.To run two WhatsApp accounts on one phone, use WhatsApp + WhatsApp Business (iOS/Android) or OEM dual-app features (on some Android devices).Your WhatsApp number does not change just because your data comes from your travel eSIM.Set-up: dual SIM with eSIMiPhone step-by-stepObtain your eSIM details: QR code or activation code from your provider.On iPhone, go to Settings &gt; Mobile Data &gt; Add eSIM (or “Add Data Plan”).Scan the QR code or enter details. Wait for activation.Label your lines (e.g., “Personal” and “Travel”). Clear labels prevent mistakes.Choose defaults: - Default Line for Calls and SMS. - iMessage &amp; FaceTime line. - Mobile Data line (set to your travel/local eSIM when abroad).Toggle “Data Roaming”: - Turn off for your home line while travelling. - Turn on for your travel eSIM, if required.Optional: Enable “Allow Mobile Data Switching” if you want automatic fallback.Test: Place a call from each line, send yourself an SMS from another phone, and load a webpage to confirm the data line.Pro tips for iPhone: - You can store multiple eSIMs and swap which are active. Many newer iPhones support two active eSIMs. - Backups don’t include eSIMs. Keep your activation details safe; some carriers limit re-downloads. - For Wi‑Fi Calling, enable it separately per line (Settings &gt; Phone &gt; Wi‑Fi Calling).Android step-by-step (Pixel/Samsung and similar)Get your eSIM QR/activation details from your provider.Open Settings &gt; Network &amp; Internet (or Connections) &gt; SIMs &gt; Add eSIM.Scan the QR code or enter details. Wait for activation.Name each SIM (e.g., “Work” and “Data”).Set preferences: - Preferred SIM for Calls. - Preferred SIM for SMS. - Preferred SIM for Mobile Data (set to the travel/local eSIM).Roaming: - Disable data roaming on your home line. - Enable on your travel eSIM if needed.Optional: Enable “Switch data automatically” or similar to allow fallback.Test calls, SMS, and data on both lines.Pro tips for Android: - Some phones let you duplicate apps (Dual Messenger/App Twin) to run two WhatsApp accounts. Alternatively, use WhatsApp + WhatsApp Business. - Not all Android models support two eSIMs active simultaneously. If yours doesn’t, use one physical SIM + one eSIM, or swap active eSIM profiles as needed. - VoLTE/5G availability can differ per SIM slot/line; check your device and carriers.Travel checklist: avoid bill shock and stay reachableBefore you fly: - Install and activate your travel eSIM over Wi‑Fi at home. - Label lines clearly and set the travel eSIM as the Mobile Data line. - Turn off Data Roaming on your home line; leave Calls and SMS on if you need OTPs. - Enable Wi‑Fi Calling for your home line if supported, to improve reachability without roaming data. - Check voicemail and call forwarding settings for both lines. - Tell your bank you’re travelling; ensure OTPs can arrive via SMS or app. - Save carrier support contacts and your eSIM activation details offline.On arrival: - Confirm the travel eSIM connects and data works. - Place a brief test call from each line and send a test SMS. - Keep an eye on status bar icons to ensure you’re not accidentally using data on the home line.Pro tips and common gotchasKeep eSIM credentials safe: Many providers allow limited re-installs. Don’t delete an active eSIM while abroad unless you’re certain you can re-download it.One data line at a time: Even with two active lines, only one provides mobile data. Choose carefully for maps, ride-hailing and tethering.Call collisions: During a call on one line, the other may be unreachable on some networks. If that’s critical, enable Wi‑Fi Calling and test how your phone behaves.Battery impact: Two active lines can use more battery. Mitigate by disabling 5G on the non-data line, reducing background activity, and using Wi‑Fi where possible.Apps tied to a number: Services like WhatsApp, Signal and Telegram can be re-registered to another number, but you may lose message history or access. Decide which number you want long-term before switching.Region-savvy plans: Multi-country eSIMs like Esim Western Europe simplify border crossings; US/Canada/Mexico travellers can look at Esim North America. Compare options by country on Destinations.Regional picks for travellersCity breaks or rail trips across multiple EU countries: Choose Esim Western Europe to avoid juggling separate plans.US road trip or conferences: Use Esim United States for nationwide coverage; combine with your home line for OTPs.Canada/US/Mexico multi-stop: Try Esim North America for cross-border continuity.Single-country travel: See Esim France, Esim Italy and Esim Spain for local choices, or browse the full list via Destinations.Business travel at scale: Central provisioning, spend control and support via For Business; partners can onboard faster with the Partner Hub.FAQsCan I use both numbers at the same time?Yes, both lines are on standby for calls and texts. Only one line provides mobile data at a time. If you’re on a call on one line, the other may be temporarily unreachable depending on device/network features.Will OTP texts arrive while my data is on the other eSIM?Yes. OTPs arrive on the line associated with that number as long as that line is enabled and has signal. Data does not need to be on for SMS. Roaming SMS fees may apply if you’re abroad on your home line.Can I use WhatsApp with two numbers on one phone?The standard app supports one number. To run two accounts, use WhatsApp + WhatsApp Business (works on iOS and Android) or an OEM dual-app feature on some Android phones. Your data can come from either line regardless of the WhatsApp number.How do I avoid roaming charges on my home SIM?Turn off Data Roaming for the home line. Keep Calls and SMS on if you need to receive OTPs or critical calls. Set your travel eSIM as the Mobile Data line. Consider Wi‑Fi Calling to improve reachability without data roaming.Does dual SIM affect battery life?Slightly, because the phone maintains two network registrations. Reduce impact by disabling 5G on the non-data line, using Wi‑Fi, and turning off the secondary line when not needed.What if my phone supports only one eSIM active at a time?Use one physical SIM plus one eSIM, or store multiple eSIM profiles and switch which is active as required. Check your device manual for limits on active lines and 5G support.Next step: Plan your trip and pick the right travel eSIM by browsing Destinations.

30 Oct 2025
Billing & Finance Ops: VAT Invoices, Multi‑Currency, and Refund Flows

Billing & Finance Ops: VAT Invoices, Multi‑Currency, and Refund Flows

Getting eSIM billing right isn’t just about taking payments—it’s about trust, compliance, and clarity for travellers and partners at scale. This guide covers the practical building blocks of esim vat invoicing multi currency operations: how to handle VAT/Sales Tax by region, present FX cleanly, calculate pro‑rations fairly, and run refund, chargeback, and dunning flows that reduce friction. Whether you’re a marketplace, reseller, MNO/MVNO, or travel brand, the goal is the same: ship fast, stay compliant, and keep customer effort low. We’ll walk through usable checklists and decision points, and point to where Simology supports your commerce stack—across destinations like Esim Western Europe, Esim North America, and single‑country packs such as Esim United States, Esim France, Esim Italy, and Esim Spain. For partnership options and operational tooling, see For Business and our Partner Hub.Why billing precision matters for eSIM at scaleTax compliance varies by region and buyer type. Poor handling risks fines or blocked payouts.Travellers expect local currency clarity and transparent FX—especially when buying on the move.Pro‑rations and top‑ups must feel fair; opaque maths is a refund magnet.A clear refund and chargeback playbook minimises losses and disputes.Strong dunning keeps B2B/wholesale cashflow healthy without harming relationships.VAT invoicing essentials for eSIM providers and partnersIdentify tax nexus by regionEU/UK: B2C digital services are typically VATable where the customer is located; B2B may use reverse charge if a valid VAT number is provided.US/Canada: Sales tax/GST/HST/PST rules vary by state/province and product classification; marketplace vs. seller of record impacts liability.APAC/ROW: Several countries operate VAT/GST on digital services to local consumers. Thresholds and registration rules differ.Note: Always validate assumptions with your finance team and align seller‑of‑record responsibilities in partner contracts.Data you must capture on a VAT‑compliant invoiceSeller legal name, address, and tax registration (e.g., VAT ID).Buyer details; collect VAT number for B2B where applicable.Unique invoice number, issue date, supply date (if different).Line items: product name (e.g., “eSIM 5 GB – France”), quantity, unit price, discounts.Tax rate and amount per line, and total tax.Currency of account and any FX conversion basis.Notes: reverse charge wording (when applicable), credit note references for refunds.Step‑by‑step: Configure VAT and invoice rulesDefine seller‑of‑record per market and channel (direct vs. reseller).Configure tax determination: by billing address, IP/geo, payment BIN, or combined evidence.Set B2B logic: VAT number capture, real‑time validation, and reverse charge handling.Attach tax codes to catalogue SKUs by region (e.g., EU digital service vs. US telecom).Generate VAT invoices on payment capture; issue credit notes on refunds.Store signed PDFs plus machine‑readable data (e.g., CSV/JSON) for audit.Provide travellers with self‑serve invoice downloads via order history.Pro tip: When selling cross‑border packs like Esim Western Europe, ensure your SKU structure supports per‑buyer tax determination even if the product spans multiple countries.Multi‑currency pricing and FX display that customers trustDisplay vs settlement currencyDisplay currency: what the shopper sees at checkout (e.g., EUR, GBP, USD, CAD).Settlement currency: what your gateway pays out in (often USD or EUR).Show the display currency by user location or browser currency, but disclose when settlement occurs in a different currency.Pro tip: Present a single total in the shopper’s local currency with tax included for B2C. For B2B, show net, tax, and gross with the buyer’s VAT status clearly flagged.Rounding, fees, and rate sourcesUse a consistent FX source (e.g., daily mid‑market rate plus a disclosed margin).Round prices to local conventions (e.g., .99, or 0.05 increments where applicable).Clearly disclose any FX mark‑up and that the card issuer may apply additional conversion fees.Step‑by‑step: Implement multi‑currency in your checkoutDetect preferred currency from locale and BIN, allow manual override.Convert base prices using your rate source and cache rates for the day.Compute taxes in the display currency; track base currency equivalents for accounting.Apply rounding rules per currency; store pre‑ and post‑round values.Show a plain‑English FX note (e.g., “Billed in USD; amounts shown in EUR for your reference” where relevant).Reconcile settlements: map PSP payouts in the settlement currency back to order‑level FX snapshots.Pro tip: Keep the FX snapshot (rate ID, timestamp, margin) on each order to simplify refunds and audits.Pro‑rations, expiries, and top‑upsCommon scenarios and calculationsMid‑cycle upgrade to a larger data pack: charge a pro‑rated difference based on remaining days or unused data value.Early cancellation (goodwill): offer a pro‑rated credit note based on unused data/validity.Auto‑renewal cancellations before renewal date: no proration; ensure clean cancellation messaging.Top‑ups: treat as separate SKUs with their own tax rules; avoid recalculating tax on the original order.Two pro‑ration models - Time‑based: Value remaining = price × (days remaining ÷ total days). - Usage‑based: Value remaining = price × (unused data ÷ total data).Pro tip: Pick one model per product family and document it in the checkout and invoice notes to avoid disputes.Refund and chargeback flows that reduce frictionRefund policy matrixTechnical failure (e.g., profile never delivered/activated): full refund.Partial usage but network issues verified: partial refund or goodwill credit.Buyer error (wrong device/region) with no usage: one‑time goodwill refund to reduce chargeback risk.Fraud or card testing: block and no refund; share device/usage fingerprints with your PSP.Always issue a credit note matching the original tax treatment and currency.Step‑by‑step: Process a refundVerify eligibility: review activation logs, usage, and support notes.Select type: full, partial (amount or percentage), or voucher credit.Calculate tax reversal: mirror original tax rate and FX snapshot.Create credit note linked to the original invoice; include reason code.Execute refund via PSP in the original payment method and settlement currency.Notify the customer with clear timelines (e.g., “3–10 business days depending on bank”).Pro tip: For travellers buying local packs like Esim France or Esim United States, add geo‑tips in the confirmation email (device compatibility, APN steps). Fewer setup issues mean fewer refund requests.Chargeback playbookPreventionStrong descriptor: include “Simology eSIM” and support URL.3‑D Secure where available; AVS/CVV checks and velocity rules.Pre‑delivery device checks (e.g., eSIM capability).Evidence for representmentOrder details, IP/device fingerprint, and BIN country match.Delivery proof: eSIM QR/profile delivered timestamp.Usage logs (data session started), and T&amp;Cs acceptance.Customer communications and refund policy shown at checkout.TriageLow‑value/high‑cost disputes: consider concession.High‑value/clear evidence: proceed to representment with focused docs.Post‑mortemUpdate fraud rules (e.g., block risky BIN ranges, disposable emails).Feed learnings into support macros and checkout copy.Pro tip: Create reason‑code playbooks (e.g., “product not received” vs. “fraudulent”). Standardise the evidence pack to submit within 48 hours.Dunning and collections for B2B and wholesalePractical timeline and commsDay 0: Invoice issued with net terms (e.g., Net 14/30). Include payment link, bank details, currency, and tax breakdown.Day 3 before due: Friendly reminder with statement of account.Day 0 due: Notice with next steps and escalation path.Day 7 overdue: Second reminder; offer card-on-file as a fallback.Day 14–21 overdue: Account manager call; agree a payment plan.Day 30+: Suspend non‑critical benefits (marketing funds, new activations) while preserving active travellers where possible.Pro tip: For resellers sourcing regional packs like Esim North America or Esim Western Europe, suspend new order creation before disabling existing lines to avoid traveller impact.Risk controls and suspension logicCredit limits per partner; auto‑adjust based on payment history.Collateral or prepayment for new partners until two clean cycles.Grace windows for active travellers; offer top‑up vouchers funded from security deposit if needed.Automated dunning across email + portal banners; keep comms factual and friendly.Regional nuances to watchEU/UK: Display VAT‑inclusive prices for consumers. If a B2B buyer enters a valid VAT number, apply reverse charge and show required wording on the invoice.US: Product taxability differs by state; telecom vs. digital service classification can change rates. Marketplace facilitator laws may shift liability.Canada: GST/HST/PST mix varies by province; register thresholds apply.Travellers often buy in one country for use in another (e.g., purchase from the UK for Esim Spain). Determine tax based on customer location rules, not the visited country, unless local laws require otherwise.Multi‑country bundles: Use consistent SKUs tied to the buyer’s location for tax, not each covered country.Pro tip: Keep your plan catalogue aligned with geo coverage on Destinations so tax and pricing logic stays in sync with what travellers actually buy.Reporting, reconciliation, and auditsDaily reconciliation checklistMatch orders to payments: amount, currency, fees, settlement date.Verify tax amounts by jurisdiction and product SKU.Confirm invoice and credit note sequences are gap‑free.Review refunds vs. payouts; reconcile FX differences to a gain/loss account.Surface anomalies: negative margin orders, duplicate refunds, or out‑of‑policy credits.Export formats and storageProvide CSV/JSON exports per day/week with:Order ID, SKU, region, buyer type (B2B/B2C), FX rate used.Net, tax, gross, currency, settlement currency, fees.Invoice/credit note numbers and links.Retain PDFs and raw data per statutory timelines; ensure timezone consistency across logs.Pro tip: Store an immutable “tax calc snapshot” per order so later tax engine changes don’t alter historical documents.Quick setup checklist (save this)Define seller‑of‑record per channel/region.Map tax codes per SKU and integrate VAT number validation.Implement display currency with clear FX notes; keep settlement currency stable.Choose a single pro‑ration model and document it.Automate credit notes for refunds; mirror original tax and FX.Build a reason‑coded chargeback pack and a 30‑day dunning cadence.Reconcile daily; export audit‑ready tax and payout data.FAQQ1: How should I handle VAT for B2B eSIM sales in the EU/UK? A: Collect and validate the buyer’s VAT number at checkout. If valid, apply reverse charge and include the correct wording on the invoice. If not, charge VAT as for B2C. Keep the validation result with the order.Q2: Can I show prices in multiple currencies but settle in USD or EUR? A: Yes. Use a stable settlement currency operationally, show shopper‑friendly display currencies, and disclose the settlement currency and any FX margin. Keep the FX snapshot per order for refunds and audits.Q3: What’s the fairest way to calculate partial refunds on data packs? A: Pick one method and be consistent. Time‑based works well for validity‑driven plans; usage‑based suits metered data. Mirror the original tax and FX when issuing the credit note.Q4: How do I reduce “product not received” chargebacks? A: Send a post‑purchase email with device compatibility checks, clear activation steps, and support links. Keep delivery logs of the eSIM profile and show your refund policy at checkout. For country packs like Esim Italy, add country‑specific APN tips.Q5: What should a VAT invoice include for eSIM? A: Seller and buyer details (including VAT IDs), unique invoice number, dates, line‑item prices, tax rates and amounts, totals, currency, and any reverse charge text. Issue credit notes for any refunds.Q6: How should dunning work for wholesale partners? A: Use a clear cadence (reminders before and after due), offer multiple payment methods, set credit limits, and suspend new activations before impacting existing travellers. Manage it via your partner portal—see our Partner Hub.Next step: Build a compliant, traveller‑friendly billing stack with Simology—start here: For Business.

30 Oct 2025