Suppliers

G-Starlink is a Tier 1 reseller — all our products come from upstream suppliers. This page tracks who they are, how we work with them, and what’s important to remember.

Current suppliers

Fill in real supplier details. This section is internal-only and the most sensitive part of the handbook — treat access carefully.

What we track per supplier

• Supplier ID (internal code)
• Legal entity name and country
• Primary contact (name, email, phone, Slack/WhatsApp)
• Backup contact for urgent issues
• API endpoint and authentication method (keys in secrets manager, not here)
• Product coverage: which regions/carriers they supply
• Commercial terms: payment terms, SLA, minimum order
• Known issues and workarounds
• Historical performance notes

Relationship management

• Quarterly business review with top 3 suppliers — volume, quality, issues, forecast
• Monthly cost review — are their prices still competitive? Do we have alternatives?
• Incident review after any supplier-caused outage — was this one-off or systemic?

Diversification principle

For every major region we sell in, we should have at least two supplier options configured as variants. This protects us when:

• A supplier’s API goes down
• A supplier’s pricing gets uncompetitive
• A supplier has quality issues in one carrier but is fine on others
• A supplier threatens to stop supplying us (leverage)

If we’re 100% dependent on one supplier for, say, Japan — that’s a risk. Fix it by sourcing a second.

Onboarding a new supplier

Before signing:

• Test their API in a sandbox
• Order 10 test SIMs across their most-relevant products
• Activate each test SIM and verify the experience
• Compare their cost against current suppliers for same carriers
• Check references (other resellers using them)
• Get written commercial terms (not just WhatsApp messages)
• Add their supplier_id and products to Supabase

After signing:

• Add variants for each product we’ll sell from them
• Set appropriate routing priority (new supplier starts lower priority until proven)
• Flag any cost differences from existing suppliers for same carrier → investigate

Secrets management

Never store actual API keys in the handbook, in Slack, in chat, or in source code. Use:

• OMS secrets → Supabase Vault or environment variables in Vercel/Cloudflare
• Variant config references the supplier ID, which points to the secret

If you ever see a real API key in this handbook or in a git commit, that’s an incident — rotate immediately.