B2B Aggregator Distributes FoxReload to 200+ Merchants via White-Label API
This case is a composite archetype based on anonymized data from FoxReload partners. Names and specific figures are illustrative and combine patterns from three regional B2B aggregators distributing FoxReload codes between 2024 and 2025.
Context
The archetype: a regional B2B aggregator headquartered in either Tashkent, Dubai or Kuala Lumpur, focused on distributing digital-goods inventory to downstream merchants in their region. At the time of FoxReload integration: ~80 downstream merchants, mixed quality, average $14k annual GMV per merchant. The aggregator had grown organically through founder relationships but was now hitting an inventory and SLA ceiling — their upstream-supplier mix (5 specialised vendors per category) was operationally heavy and didn't scale to 200+ merchants.
The thesis: by replacing 5 upstream suppliers with FoxReload's white-label API, the aggregator could (a) expand catalogue depth without new contracts, (b) free up operational capacity to onboard more merchants, and (c) standardise SLAs across the entire downstream network.
Integration
10-week build:
- Weeks 1–2: FoxReload partner-tier API onboarding, white-label catalogue setup, currency mapping.
- Weeks 3–5: Aggregator-side merchant dashboard rebuild on top of the FoxReload partner API. Merchant KYC, per-merchant pricing tiers, settlement reports.
- Weeks 6–8: Migration of existing 80 merchants from legacy suppliers (staged: 20%, 50%, 100%).
- Weeks 9–10: Onboarding sprint — 35 new merchants signed in the first 2 weeks after migration.
FoxReload features used: white-label partner API, per-merchant rate limiting, settlement reports, multi-currency invoicing, and the aggregator-tier revenue-share/markup configuration.
Economics
The 3-tier margin stack:
| Tier | Role | Margin | Annual revenue at scale |
|---|---|---|---|
| FoxReload (upstream) | Catalogue, fulfilment, licences | ~10% | wholesale base |
| Aggregator (mid-tier) | Regional KYC, FX rails, merchant support | ~18% | ~$2.1m |
| Merchant (downstream) | Last-mile UX, customer support | 25–35% | varies per merchant |
Aggregator performance:
| Metric | Before | After 14 months | Change |
|---|---|---|---|
| Active downstream merchants | 80 | 217 | +171% |
| Avg merchant annual GMV | $14k | $39k | +179% |
| Aggregator GMV/year | $1.1m | $8.5m | 7.7× |
| Aggregator net revenue/year | $130k | $2.1m | 16× |
| Operational staff | 4 | 5 | +1 |
The unit economics that made this work: replacing 5 upstream contracts with one (FoxReload) freed 1.5 FTE of contract/ops time, which redirected to merchant onboarding and support. Merchant onboarding velocity went from ~3 per month (legacy) to ~10 per month (post-FoxReload).
Lessons
- The middle tier earns its margin by hiding upstream complexity. Downstream merchants don't want to talk to 5 suppliers — they want one branded dashboard. That's the aggregator's job and the 18% is the price of doing it well.
- White-label means full UX control. The aggregator kept its own brand, dashboards and merchant-facing pricing. FoxReload was invisible to the downstream layer, which protected the aggregator's commercial relationships.
- Per-merchant pricing tiers matter. Some merchants needed 22% markup, others 14%. A flat retail price would have cost the aggregator the high-volume merchants.
- Settlement automation removes the biggest scaling tax. Manual monthly reconciliation across 200+ merchants would have been a full FTE. FoxReload partner-tier settlement reports cut that to a half day per month.
If you're building a regional B2B aggregator and want a similar white-label setup, request access at foxreload.com.