If you run a travel site, content channel, marketplace or mobility service, a well-run eSIM affiliate reseller program can become a predictable revenue stream. This playbook shows exactly how Simology partners earn, track and get paid—without guesswork. We cover practical commission tiers, link attribution, UTM best practice, pixel/postback options, fraud checks, and the monthly payout workflow. You’ll also get a launch checklist and high‑converting ideas tied to top routes and countries. Keep the traveller experience front and centre: promote plans that activate instantly, work across borders, and solve roaming pain—in destinations like the Esim United States, Esim France, Esim Italy, Esim Spain and multi‑country bundles such as Esim Western Europe or Esim North America. Bookmark this guide, then head to the Partner Hub to activate your links and track performance.

Who this is for—and what you can earn

• Travel publishers, bloggers, YouTubers, creators and communities
• OTAs, metasearch, airlines, rail, ferry and bus operators
• Co‑working, co‑living, expat and student platforms
• Telco dealers and retail resellers

You can promote single‑country eSIMs, regional bundles and long‑stay plans. Commission scales with volume and quality, paying on each qualified order (first purchase and, if applicable, top‑ups—see FAQ). Live rates and your status are visible in the Partner Hub.

Pro tip: Match content to destinations and travel seasons using the live catalogue on Destinations. It’s the fastest way to lift conversion.

Commission tiers explained

We use a volume-and-quality model: more approved orders and lower refund rates move you up. Check the Partner Hub for your current tier and live rates. Typical structure:

• Starter: up to 49 approved orders/month
• Commission: baseline rate on qualified orders
• Eligibility: new partners; light seasonal traffic
• Growth: 50–199 approved orders/month
• Commission: higher rate; performance review each quarter
• Extras: custom vouchers for campaigns
• Scale: 200–999 approved orders/month
• Commission: premium rate
• Extras: dedicated support, early access to promos
• Enterprise: 1,000+ approved orders/month
• Commission: negotiated
• Extras: co‑marketing, API and bulk ordering options via For Business

What counts as an “approved order” - A unique, paid order that passed fraud checks and remains outside the refund window - Suppressed: cancelled/chargeback orders; obvious self‑dealing; duplicate device activations

Quality guardrails - High refund/complaint rates may trigger a temporary tier freeze while we optimise your funnel - Vouchers discount the retail price but do not reduce your commission rate unless otherwise agreed

Pro tip: When you launch new placements, start with flexible, popular routes—e.g. Esim United States for long‑haul, Esim Western Europe for rail/Interrail content—to stabilise your conversion and refund mix.

Attribution and tracking that just works

We run a transparent, last‑click attribution model with a standard cookie window. Details:

• Attribution: last non‑direct click from a Simology‑approved tracking link
• Lookback window: 30 days cookie; same‑session for private browsing
• Cross‑device: supported when user logs in with the same email on checkout
• Vouchers: a partner code applies commission if the user arrives direct (fallback attribution)
• Override rules: self‑purchase suppression; voucher misuse; policy breaches (see Fraud)

UTM best practice (so your analytics match ours) - utm_source: your brand or network (e.g., travelblog) - utm_medium: affiliate, reseller, partner, newsletter, video - utm_campaign: campaign or season (e.g., summer_2025_eu) - utm_content: placement (e.g., sidebar_link, yt_description, dealbox) - sub1–sub5: your granular IDs (post slug, ad group, language, creative)

Example tracking link (simplified): - https://simology.io/esim-western-europe?utm_source=travelblog&utm_medium=affiliate&utm_campaign=summer_2025_eu&utm_content=dealbox&aff_id=123&sub1=interrail_guide

Pro tip: Always deep‑link to the exact plan page that matches the traveller’s intent, such as Esim Italy for Rome/Milan guides, or Esim North America for multi‑country trips.

Pixel and postback options

We support flexible conversion signalling so you can reconcile in your platform.

• JavaScript pixel: we fire a partner‑specific pixel on the order confirmation page
• Event: purchase
• Payload: order ID, currency, total, product/region, voucher code
• Server‑to‑server postback: preferred for networks
• Protocol: GET/POST with macros (order_id, amount, currency, status, sub1–sub5)
• Retries: automatic on transient errors
• Webhooks: real‑time events for approved, refunded, and topped‑up orders (opt‑in via Partner Hub)

Implementation steps 1) Request your pixel/postback template in the Partner Hub. 2) Provide your endpoint and required macros. 3) Validate in sandbox with two test orders (cancelled + completed). 4) Go live and compare click‑to‑order counts for the first week.

Pro tip: Use sub‑parameters to map every placement. It’s the fastest way to prune low‑quality traffic and scale the winners.

Fraud and quality controls (and how to stay compliant)

We protect travellers and partners by filtering bad traffic without blocking legitimate purchases.

What we check - Duplicate suppression: same device/email used across multiple partner links - Voucher abuse: leaked codes used outside permitted channels - Velocity: anomalous spikes from new sources; unrealistic geo/device patterns - Referrers: masked/referrer‑less clicks with high bounce or bot signatures - Refund anomalies: high refund rates clustered by source or sub‑ID

Your compliance checklist - Use approved tracking links/vouchers only - No forced clicks, cookie stuffing, toolbars or misleading claims - Label ads and sponsored content clearly - Don’t bid on Simology brand terms unless explicitly authorised - Keep your contact and payout details current in the Partner Hub

If we detect an issue, we’ll notify you, pause the affected traffic, and help you remediate. Approved, legitimate orders remain eligible for commission.

Monthly payout workflow (end‑to‑end)

• Month end (T+0): Month closes at 23:59 UTC on the last day
• Reconciliation (T+1 to T+5): Fraud screening, refunds/cancellations netted out
• Statement (T+6): Provisional report in the Partner Hub with order IDs and statuses
• Disputes window (T+6 to T+10): Query mismatches by order ID; we re‑check logs and referrers
• Approval (T+11): Final amount locked
• Payout (T+15): Funds sent via bank transfer or online payout
• Thresholds: Minimum payout applies; balances roll over if below threshold

Notes - Currency: Paid in your account currency; FX based on payout day mid‑market rate - Documentation: Ensure your account profile, tax information and payout method are complete to avoid delays - Returns: Orders refunded after approval are debited against the next cycle

Pro tip: Export your order‑level report monthly and match it against your analytics by sub‑ID to keep your funnel healthy.

Launch checklist (do this once, in order)

1) Apply in the Partner Hub and add your primary domains/social handles. 2) Create link presets with standardised UTM and sub‑parameters. 3) Request voucher codes if you need them for specific pages or newsletters. 4) Set up your pixel/postback and run two test orders (approved + cancelled). 5) Build at least three evergreen placements: - “How to get data in the US” linking to Esim United States - “Europe rail packing list” linking to Esim Western Europe - “City break guides” linking to Esim France, Esim Italy and Esim Spain 6) Add a global “eSIM for travel” link in your nav or resources pointing to Destinations. 7) Monitor CTR, conversion and refunds; scale the best placements.

Promotion ideas that convert

• Comparison blocks: “Local SIM vs roaming vs eSIM” with a clear CTA to regional bundles like Esim North America
• Itinerary‑specific CTAs: “Before you land in JFK, install your eSIM” linked to Esim United States
• Packing lists: Include an “eSIM ready” tip with links to Destinations
• Newsletter countdowns: “48 hours to departure? Activate Esim Western Europe in 2 minutes”
• Video descriptions: Persistent link with UTM + sub‑IDs, plus a voucher code

Pro tip: Surface regional bundles alongside single‑country plans; travellers often change routes late, and bundles lift conversions.

Reporting: the KPIs that matter

Track these weekly: - Click‑through rate (placement quality) - Landing‑to‑install rate (clarity of instruction) - Install‑to‑activation rate (device fit, support) - Conversion rate and AOV (offer relevance) - Refund rate (content accuracy; set expectations) - Earnings per click (EPC) by sub‑ID (where to scale)

Pro tip: If install‑to‑activation drops, add a “Works on most modern iPhones and Androids—check device list” line near your CTA and deep‑link to the right region. Align content to the traveller’s device and route.

FAQ

• How is commission calculated? Commission is a percentage of the final paid amount on approved orders after discounts. Your tier determines the percentage. Track live rates and approvals in the Partner Hub.
• What’s the attribution window? Standard cookie window is 30 days with last non‑direct click. If a user applies your voucher code on a direct visit, attribution falls back to the code.
• Do I earn on top‑ups or extensions? Where top‑ups are processed under the same account/email within the attribution window and linked to your original referral, commission applies. The order‑level report shows this by event type.
• Can I buy through my own link? Self‑purchases and obvious self‑dealing are suppressed. If you need staff or creator plans for testing, request non‑commissionable codes via the Partner Hub.
• Which destinations convert best? High‑intent pages like Esim United States, Esim France, Esim Italy, Esim Spain and regional bundles like Esim Western Europe and Esim North America are consistently strong. Browse all options on Destinations.
• Can I get API or bulk ordering? Yes. Larger resellers and enterprise partners can use API access, white‑label flows and bulk provisioning via For Business. Contact us through the Partner Hub.

Next step: Ready to launch or optimise your esim affiliate reseller program? Activate your account and get your first links live in the Partner Hub.

Looking to add eSIM to your travel product without becoming a telco? This reusable case study template distils how a mid-sized travel brand launched a white-label eSIM shop in just six weeks, what they measured, and how they iterated. You’ll get a practical timeline, checklists, KPIs (activation rate, CAC, ARPU and more), pitfalls to avoid, and the wins worth replicating. Use it to scope your own white-label rollout with confidence and keep your team focused on what travellers actually need: fast purchase, easy install, and reliable coverage in the places they go. The example below references common launch destinations such as the United States, France, Spain and Italy, plus regional bundles for Western Europe and North America, so you can map to your own catalogue from day one. If you’re evaluating partners, you can compare what’s realistic against this blueprint and adapt the numbers to your brand’s audience size and channels.

Who this eSIM case study template is for

• Travel brands, OTAs and airlines exploring “esim case study white label” options
• Fintechs, super-apps and loyalty programmes adding a simple, high-margin travel utility
• Wholesale/partnership teams validating timelines, KPIs and GTM costs

If you need a quick view of coverage and plans by country, skim the live catalogue at Destinations, including Esim United States, Esim France, Esim Spain, Esim Italy, Esim Western Europe and Esim North America.

The 6‑week launch timeline (reusable)

This is a realistic, low-lift plan for a white-label eSIM powered by an established provider.

Week 1: Discovery and commercial basics

• Define goals: attach rate target, first-90-day GMV, acceptable CAC, initial ARPU target.
• Choose launch catalogue: 4–6 high-volume routes (e.g., US, France, Spain, Italy) plus 1–2 regional bundles (Western Europe, North America).
• Confirm commercial model: wholesale pricing, revenue share/margin, payment flows, refund rules.
• Legal/brand: co-branding, domain/subdomain, T&Cs alignment.

Pro tip: Start with 20–30 SKUs max. More choice rarely improves conversion at launch.

Week 2: Integration planning

• Select integration path: hosted white-label storefront vs. embedded SDK/API.
• Map flows: purchase, email delivery, in-app QR, on-device install, top-ups, refunds.
• Analytics plan: events for view → add to cart → purchase → install → activation → top-up.
• Support model: Tier 1 handled by you with provider escalation for network issues.

Checklist - Tracking IDs/UTMs set - Payment processor connected - Support macros drafted - Landing pages and FAQs drafted

Week 3: Build and content

• Configure storefront: brand, colours, copy, pricing rules, currency.
• Localise essential pages and install guides (EN + top languages in your audience).
• Add plan cards for Esim United States, Esim France, Esim Spain, Esim Italy.
• Create regional bundles for Esim Western Europe and Esim North America.

Pro tip: Add “Install before you fly” guidance in the checkout and confirmation email to boost activation rate.

Week 4: QA and pilot

• Device testing: iPhone and Android across 8–10 common models.
• Pilot cohort: 50–200 real users from your newsletter or loyalty members.
• Validate KPIs: funnel steps, install success, activation within 24 hours, support ticket rate.

Week 5: Go-live and paid media

• Launch channels: email, app push, post-booking pages, and route-specific pages.
• Paid tests: small budgets on search and social (brand + destination keywords).
• Partnerships: cross-sell with travel insurance and airport transfer pages.

Pro tip: Put eSIM into your post-booking confirmation flow; travellers are primed to buy connectivity right after itinerary confirmation.

Week 6: Optimise and scale

• Iterate on pricing tiers and bundles.
• Add top-ups and auto-refill.
• Roll out additional countries from Destinations.
• Localise support macros based on real ticket themes.

The KPI framework that actually matters

Track these weekly, then lock a monthly view for management.

• Activation Rate: percentage of purchased eSIMs that successfully activate within 7 days. Target >90% with clear install guides and pre-travel prompts.
• CAC (Customer Acquisition Cost): paid media + creative + attributable fees divided by first purchases. Keep under 25–35% of first-order revenue at launch.
• ARPU (Average Revenue per User): total eSIM revenue / unique purchasers over 30–90 days. Track first-order ARPU and 60-day ARPU including top-ups.
• Refund Rate: proportion of orders refunded. Target <4%. High refund rates often signal install confusion, not network issues.
• Attach Rate: percentage of core bookings that include an eSIM add-on. Good early target: 3–7% on relevant routes.
• NPS / CSAT: collect post-activation; aim for 60+ with simple install and clear coverage notes.
• Support Ticket Rate: tickets per 100 orders. Target <10/100 after week 2.

Optional, but useful: - Top-up Ratio: customers who purchase additional data within 30 days (indicator of retention). - Gross Margin: after wholesale rate, payment fees and refunds. - CLV: early proxy is first order + 60-day top-ups; refine later.

Pro tip: Separate install failure from “no service” tickets in your dashboard. The fix for each is different.

Example baseline metrics from similar launches

Use these as a starting point; adjust to your brand and channel mix.

• Activation Rate: 92–96% within 7 days
• CAC: £3–£7 (email/owned), £8–£15 (paid search), £10–£18 (paid social)
• First-order ARPU: £10–£18 (country), £18–£28 (regional bundle)
• Refund Rate: 1.5–3.5%
• Ticket Rate: 6–12 per 100 orders (drops below 6 with better guides)
• Attach Rate (post-booking page): 4–8%

Reusable case study outline (fill-in template)

Use this structure to document your launch for stakeholders or for partner due diligence.

1. Context - Brand: industry, monthly travellers, top routes - Objectives: revenue, attach rate, NPS, time-to-market - Constraints: dev capacity, support hours, languages
2. Solution - White-label approach: hosted storefront vs. embedded - Catalogue at launch: list SKUs (e.g., US, France, Spain, Italy, Western Europe, North America) - Pricing strategy: country vs. regional bundle, 7/15/30-day tiers - Support model: Tier 1 scripts, escalation path
3. Implementation - Timeline: 6 weeks with key milestones - Integrations: payments, analytics, CRM, attribution - Content: install guides, FAQs, post-purchase emails - QA: device matrix, test results, pilot cohort
4. Results (first 60–90 days) - KPIs: Activation, CAC, ARPU, refunds, ticket rate - Revenue and margin: by SKU and channel - Learnings: what moved conversion, what reduced tickets
5. Next steps - Catalogue expansion from Destinations - Automation: top-up prompts, auto-refill - Localisation and partner bundles

Pro tip: Keep the outline in a shared doc and update weekly for the first month; it becomes your internal “runbook”.

Pricing, packaging and catalogue strategy

• Keep it simple: three durations (7, 15, 30 days) and two data tiers per country.
• Bundle where it helps: Esim Western Europe and Esim North America convert well for multi-city trips.
• Anchor value with examples: “2GB is enough for maps + messaging on a weekend in Paris; consider 5GB for longer stays.”
• Promote hero SKUs early: Esim United States, Esim France, Esim Spain, Esim Italy.

Pro tip: Nudge buyers to top up in-app before roaming data runs out; it reduces support and increases ARPU.

UX and content that drives activation

• Pre-travel prompt: “Install before you fly” banner + email reminder 24 hours pre-departure.
• One-screen install: clear QR code, device-specific steps, and a 60-second video link.
• Plain-English coverage notes: where 5G/4G is available; hotspot policy.
• Troubleshooting microcopy: “Toggle Airplane Mode, ensure eSIM is set to ‘Data’ line, turn on Data Roaming.”
• Post-purchase checklist:
• Add eSIM
• Set as data line
• Keep primary SIM for calls
• Enable data roaming
• Restart on arrival

Pro tip: Show estimated daily usage examples (Maps, WhatsApp, ride-hailing). It reduces “ran out too fast” tickets.

Support playbook (Tier 1)

• Install issues (most common)
• Ask device model and OS
• Confirm eSIM is set as the data line
• Toggle data roaming and restart
• If still failing, escalate with order ID and ICCID
• No data on arrival
• Check APN settings (auto vs. manual)
• Confirm local network availability
• Toggle airplane mode, select network manually
• Unexpected consumption
• Check OS updates and background sync
• Suggest low data mode and turning off iCloud Photos/Drive on mobile data

Target response under 5 minutes on live chat during business hours; under 2 hours via email.

Common pitfalls and how to avoid them

• Too many SKUs on day one
• Start with 6–8. Expand when you see real demand.
• Vague install instructions
• Use device-specific steps and screenshots. Link them in the checkout and email.
• No pre-travel reminders
• Activation rate can drop 10+ points without them.
• Misaligned pricing to local competition
• Check live pricing frequently; adjust small deltas rather than big swings.
• Under-investing in analytics
• Track install and activation, not just purchases. It’s where experience breaks.

Pro tip: Treat refunds as a learning loop; tag each with a concise reason and fix the top two drivers weekly.

What made this launch work (wins to replicate)

• Traveller-first copy and support reduced tickets by 41% after week 2.
• Regional bundles lifted ARPU by 22% without hurting conversion.
• Post-booking placement drove a 6.2% attach rate versus 2.1% on generic pages.
• Pre-departure reminders improved activation from 88% to 95%.
• A small, curated catalogue made the decision easy and boosted checkout completion by 9%.

What to ask a white-label eSIM partner

• Catalogue breadth and depth: Are priority markets covered with 4G/5G? See live Destinations.
• Commercials: Clear wholesale rates, currency, settlement, and refund policies.
• Integration options: Hosted storefront, SDK or API? Time to live?
• Analytics: Event-level data for install and activation.
• Support: SLAs, escalation, and proactive network incident notices.
• Compliance and security: Data handling, PCI scope for payments, uptime.

For enterprise requirements and wholesale pricing, explore For Business and the partner resources in the Partner Hub.

Quick launch checklist

• Objectives set (attach, ARPU, activation)
• 6–8 SKUs selected (US, FR, ES, IT + 1–2 regional bundles)
• White-label storefront themed and priced
• Install guides and FAQs published
• Analytics and attribution wired
• Pilot cohort completed and fixes applied
• Go-live across post-booking, email, and app
• Weekly KPI review and content optimisation

FAQ

1) What does “white-label eSIM” mean?
A ready-made eSIM storefront or component you brand as your own. The provider handles the telecom backend; you focus on UX, marketing and support.

2) How fast can we realistically launch?
With a hosted white label, six weeks is achievable, including QA and a pilot. Embedded SDK/API integrations may add 1–3 weeks depending on your app release cycle.

3) Which destinations should we start with?
Prioritise top routes and high-volume tourist markets: Esim United States, Esim France, Esim Spain, Esim Italy, plus bundles like Esim Western Europe and Esim North America.

4) How do we keep activation rates high?
Send pre-departure reminders, offer clear device-specific install steps, and make sure data roaming is on for the eSIM line. Keep troubleshooting one tap away in the order email.

5) What margins are typical?
It depends on wholesale rates and pricing, but many brands target 25–45% gross margin after payment fees and refunds, with regional bundles often carrying higher ARPU.

6) Do we need 24/7 support from day one?
Not necessarily. Start with expanded hours around peak departure times and clear self-serve guidance. Add 24/7 coverage once volumes justify it.

Next step: Ready to scope your own white‑label rollout and see commercial options? Visit the Simology Partner Hub.

Launching an eSIM brand should be fast, predictable, and traveller‑friendly. Simology’s white label eSIM platform gives you a complete stack: a branded website, native iOS and Android apps, and the operational portals your team needs to run day‑to‑day. You get the product catalogue, provisioning, payments, fraud tools, analytics, and support workflows out of the box—so you can focus on growth, not plumbing. Typical partners go live in weeks, not months.

This overview breaks down every module you receive, who does what during implementation, and the exact steps to launch. We also show how the traveller experience stays front‑and‑centre—from finding the right plan (e.g. [Esim United States] or [Esim Western Europe]) to one‑tap installation and instant connectivity. Where visuals help, you’ll find annotated screenshots in the Simology [Partner Hub]. If you’re comparing build vs buy, use the checklists and timelines below as a benchmark for scope, effort, and ownership.

What’s included in the white label eSIM platform

1) Branded web storefront

A conversion‑ready site that sells global and regional eSIMs with best‑practice UX for travellers:

• Mobile‑first product pages, plan comparison, and checkout
• Region and country collections (e.g. [Esim United States], [Esim France], [Esim Italy], [Esim Spain], [Esim Western Europe], [Esim North America])
• Device compatibility checks and guidance
• Currency, tax display, and multi‑language localisation
• Payment orchestration (cards, Apple Pay, Google Pay, local methods)
• Account area for order history, re‑downloads, invoices
• SEO structure and landing pages aligned to [Destinations]

Content, branding, and domain are tailored to you. You manage pages and promotions from the Partner Admin Portal (details below).

2) Native iOS and Android apps

App‑store ready, with all traveller essentials:

• In‑app eSIM install using system frameworks (no QR code required on supported devices)
• Auto‑detect compatible devices; QR fallback for older models
• Real‑time status: installed/activated, data balance, expiry
• Data counters and top‑up flows
• Push notifications for install reminders, low data, and expiry
• Support entry points: chat, guided troubleshooting, help articles
• Secure account, biometric sign‑in, and purchase history

We ship you branded builds; you publish under your own Apple/Google developer accounts to retain your customer relationship and store analytics.

3) Operational portals (with screenshots in the [Partner Hub])

• Partner Admin Portal
• Catalogue: enable/disable countries and regions, set retail and promo pricing
• Merchandising: bundles, upsells, vouchers/coupons
• Content and localisation: copy blocks, FAQs, help articles
• Theming: logos, colours, typography
• Integrations: payment, analytics, SSO, webhook endpoints
• Support Portal
• Search by email/order/ICCID; view eSIM state and history
• One‑click reissue, reshare activation details, or refund
• Network tools: APN, roaming status, attach/detach logs
• Customer notes, macros, and SLA timers
• Finance & Reporting
• Revenue, margin, and cohort dashboards
• Tax breakdowns, invoicing exports, settlement files
• Chargeback tracking and fraud signals
• Reseller/Agent Portal (optional)
• Sub‑accounts with role‑based access
• Commission structures and wallet balance
• Bulk codes and activation batches

4) Provisioning, APIs, and webhooks

• Order to eSIM fulfilment: allocate eUICCs, assign plans, deliver LPA links/activation codes
• Multi‑IMSI routing and network redundancy
• REST APIs for order creation, status, and refunds
• Webhooks for order paid, eSIM issued, installed, activated, data thresholds, and expiry
• SDKs for in‑app purchase and install flows

Traveller experience: designed to minimise friction

Your customers should be online in minutes, not hours. The default flow:

1. Discover a plan via search or region page (e.g. [Esim North America] or a single country like [Esim France]); device check runs automatically.
2. Pay with a familiar method; receive activation in‑app or via email.
3. Install directly within the app (or scan a QR code); mobile data toggles are guided step‑by‑step.
4. Land and connect. If needed, the app confirms roaming/APN settings with one tap.
5. Manage usage, top up, and extend validity inside the app or website.

For travellers hopping multiple countries—say [Esim Western Europe] across France, Spain, and Italy—the app keeps the plan active and shows local tips and APN guidance. For US trips, [Esim United States] is surfaced with the most relevant data packs.

Integration at a glance

You can launch with Simology defaults on day one, then extend. Typical touchpoints:

• Payments: Stripe/Adyen out of the box; add local methods as needed.
• Identity: Email + OTP by default; optional SSO (OAuth/SAML).
• Analytics: GA4 and server‑side events; optional Segment, BigQuery exports.
• Support: Native portal included; optional Zendesk/Freshdesk connectors.
• Messaging: Email templates included; optional SendGrid/postmark; optional SMS for OTPs.
• Tax: Display and calculations by region; export summaries for your accountant.
• Webhooks: Plug into your ERP, BI, or marketing automation.

Pro tip: Start with the vanilla stack to ship faster; integrate your preferred tools in sprint two.

Timelines and responsibilities

Most partners launch in 4–6 weeks. Here’s a proven plan.

Week 0: Readiness checklist

• Brand assets (logo, colours, app icons)
• Company and support details (legal name, address, emails)
• Domain and DNS access
• Apple and Google developer accounts
• Payment PSP account (or use Simology’s PSP to start)
• Initial catalogue selection (countries/regions and pricing)
• Privacy, terms, refund policy copy (templates provided)

Week 1–2: Brand, content, and catalogue

• Simology: Stand up staging storefront; load initial plans; enable [Destinations] taxonomy.
• Partner: Provide copy and translations; confirm pricing and promotions.
• Joint: Review product pages for key markets (e.g. [Esim Italy], [Esim Spain]).

Week 2–3: Payments, analytics, and domain

• Simology: Configure PSP, GA4, and webhooks; set up tax display; connect support portal.
• Partner: Verify PSP; connect domain and SSL; configure consent and cookie banners.

Week 3–4: Apps build and QA

• Simology: Produce branded iOS/Android builds; run device install tests; pass test artefacts.
• Partner: Publish to stores; validate purchase and install across target devices; localise store listings.

Week 4–5: Launch and optimise

• Go live; monitor conversion and install success
• Introduce vouchers or welcome discounts
• Enable additional regions (e.g. [Esim North America]) based on demand

Who does what

• Simology
• Platform hosting, provisioning, updates, and monitoring
• Default integrations (payments, analytics, messaging)
• Portals, APIs, and dashboards
• Compliance templates and security controls
• Partner
• Brand, domain, app store ownership
• Pricing strategy and promotions
• Customer service staffing and tone of voice
• Local tax registration and accounting
• Joint
• QA, go‑live readiness, and post‑launch optimisation
• Roadmap: loyalty, resellers, and enterprise features

Operational controls and reliability

• Inventory and routing
• eUICC pools with automatic allocation
• Multi‑IMSI and network failover where supported
• Fraud and abuse
• Velocity checks, BIN and geolocation risk scores
• Device fingerprinting and disposable email filters
• Compliance and privacy
• GDPR‑aligned data handling; role‑based access controls
• Data retention and export tools
• Finance
• Settlements, tax summaries, and reconciliation exports
• Dispute workflows with evidence packs

Pro tip: Use webhooks for “installed” and “activated” events to trigger welcome emails with APN tips—this cuts support tickets by ~20%.

Merchandising the catalogue

Start focused; expand with data.

• Lead with your top 10 routes by audience (e.g. [Esim United States] for Northbound travel, [Esim France] and [Esim Spain] for summer peaks)
• Offer regional passes like [Esim Western Europe] for multi‑country trips
• Create bundles (e.g. 15‑day pass with top‑up credit) to increase average order value
• Use the [Destinations] structure for SEO and easy browsing
• Test price points and promotions; the portal shows conversion and refund impact

Pro tip: Add a pre‑trip email series (T‑7, T‑2, landing) with install reminders and local network tips; it boosts first‑try success and reduces roaming confusion.

Launch checklist (copy/paste)

• Domain connected and SSL green
• PSP payments live; test Apple Pay and Google Pay
• Top 20 destination pages reviewed (copy, images, FAQs)
• iOS/Android app published; install flow verified on two devices per OS
• Support macros written for install, APN, and top‑up
• Refund policy and help centre pages live
• Webhooks connected to your CRM/marketing tool
• Dashboard alerts set for conversion drop, failed installs, and chargebacks

Frequently asked questions

• How long does it take to launch?
• Most partners launch in 4–6 weeks. If you use Simology’s default PSP and templates, a soft launch can happen in 2–3 weeks while apps are in review.
• Can we customise everything to our brand?
• Yes. You control logo, colours, typography, voice/tone, domain, and app store presence. Product names, pricing, and promotions are also fully configurable.
• What devices are supported?
• Any eSIM‑capable iPhone, iPad, and recent Android flagships. The storefront and apps auto‑detect compatibility and guide QR vs in‑app install accordingly.
• Do we need our own payment processor?
• You can go live on Simology’s PSP setup initially, or connect your own Stripe/Adyen account for direct settlement. Apple Pay and Google Pay are supported.
• How do we handle support?
• Use the built‑in Support Portal with search, reissue, and refund tools. You can also connect to your helpdesk. Macros and guides are preloaded for common issues.
• What about taxes and invoices?
• The Finance portal provides tax breakdowns and exports. You remain the merchant of record and handle filings in your jurisdictions; templates are provided to streamline.

Pro tips from successful partners

• Keep the homepage simple: three featured regions, one traveller proof point, one CTA.
• Default to in‑app install messaging; QR codes are your fallback, not the hero.
• Add low‑data alerts at 80% usage; enable one‑tap top‑ups to protect NPS.
• Localise help articles per top destination (APN names, roaming toggles, common devices).
• Use vouchers for first‑time buyers rather than site‑wide discounts to protect margin.
• Review “install failed” logs weekly; small tweaks to copy or timing can lift completion rates.

Integration summary

• Mandatory to launch: Brand assets, domain, PSP (or Simology PSP), app store accounts
• Strongly recommended: GA4, webhooks to your CRM, email sender
• Optional: SSO, BI exports, Zendesk/Freshdesk connectors, reseller portal

Next step: Explore features, see portal screenshots, and request access in the [Partner Hub]. If you’re assessing suitability for your organisation, start with [For Business] and map the catalogue via [Destinations].