OEM telecom gateway hardware is standard Telarvo equipment delivered under a partner’s brand: the hardware, firmware, and support are the same, and the branding, documentation, and packaging carry the partner’s identity. An OEM program lets a reseller, integrator, or telecom service provider sell proven gateway hardware as its own product line, without designing or manufacturing the devices.
This article covers what an OEM relationship involves, what the partner provides, and what to evaluate before starting one.
What the Partner Receives
An OEM program typically includes the hardware with partner branding, the firmware as supplied by Telarvo, and the documentation adapted for the partner’s customers. The partner handles the go-to-market: pricing, sales, distribution, and the customer relationship. Telarvo provides the product, the warranty, and the technical backing.
The division of labor is the point. The partner builds a product line from proven hardware without a factory or an engineering team; Telarvo gains distribution through partners who reach customers it would not reach directly.
The Hardware Base
The OEM hardware base draws from the Telarvo product families, and the mix depends on the partner’s market. An SMS-focused partner stocks SK-SMS Gateway models; a voice-focused partner stocks the GoIP and SK VoIP Gateway families; a full-service partner carries a mix with SIM pool and SIM bank products.
The standardization matters for an OEM program. Because the hardware is the same Telarvo equipment sold direct, the partner inherits the product’s tested behavior, the specification documentation, and the compatibility with the Telarvo ecosystem. The [SMS Gateway collection](https://www.telarvostore.com/sms-gateway) and the [VoIP Gateway collection](https://www.telarvostore.com/voip-gateway) provide the model references an OEM partner works from. The [Telarvo Store homepage](https://www.telarvostore.com/) lists the product families that form the base.
What to Evaluate Before Starting
Five questions decide whether an OEM program fits. First, demand: does the partner’s market buy gateway hardware, and at what volume? Second, support: can the partner triage first-line questions and escalate hardware issues to Telarvo? Third, logistics: can the partner hold inventory and handle delivery and RMA? Fourth, branding: does the partner have the packaging and documentation capability to present the hardware as its own? Fifth, terms: what MOQ, pricing, and warranty-sharing does the agreement set?
The evaluation is honest about the partner’s role. An OEM program is not a licensing deal where the partner does nothing; it is a distribution deal where the partner carries real operational responsibility.
The Support and Warranty Flow
The support flow has three tiers. The partner handles first-line questions: configuration, SIM provisioning, and deployment. Telarvo’s 7×12 support covers the hardware and deeper technical questions. The end customer follows the escalation path the partner documents at handoff.
The warranty responsibility is split the same way. Telarvo covers hardware defects on every unit; the partner handles the customer interface and returns; the customer returns the faulty unit through the partner. The flow should be written down before the first sale, not after the first failure.
Building the Partner Product Line
The partner’s product line is a selection of the Telarvo range presented under the partner’s brand. The typical structure is a small set of standardized models — an SMS gateway, a VoIP gateway, a proxy gateway — each with a clear role in the partner’s catalog. The standardization keeps inventory, documentation, and support consistent, and it matches how the partner’s customers actually buy.
The product line should map to the partner’s market. An SMS-focused reseller builds around the SK-SMS Gateway range; a voice-focused reseller around GoIP and SK VoIP; a full-service partner carries a mix with SIM pool and SIM bank products. The selection is a business decision, not a technical one.
The Commercial Model
The commercial model has three parts. Pricing: the partner buys at volume pricing and resells at its own margin, with the quotation defining the MOQ and price breaks. Inventory: the partner holds stock, tracks serial numbers and warranty start dates, and carries spares for coverage. Logistics: the partner handles delivery, returns, and the RMA flow with the end customer.
The model should be documented like the technical flow. A written agreement covering pricing, terms, support flow, and delivery commitments is what makes the OEM relationship sustainable rather than ad hoc.
A Worked Example
Consider a reseller that serves logistics companies. Its OEM line is the SK-SMS Gateway 16-128, branded for its market, with the SMS Caster software adapted for delivery notifications. The reseller holds a small stock, configures each unit for the client, and handles first-line support; Telarvo covers the hardware. The line lets the reseller sell proven gateway hardware as its own product, without a factory or an engineering team.
The example shows the OEM model: the partner owns the customer and the go-to-market, and Telarvo provides the product and the technical backing.
The Partner’s Responsibilities in Detail
The partner’s responsibilities go beyond selling. First-line support is the biggest one: the partner answers configuration, SIM provisioning, and deployment questions from its customers, and it escalates hardware issues to Telarvo only when the diagnosis points there. The partner also owns the RMA flow — the customer returns the faulty unit to the partner, and the partner coordinates the replacement with Telarvo.
The inventory role is equally real. The partner tracks serial numbers and warranty start dates, carries spares for coverage, and keeps the stock aligned with what its customers actually order. A partner that treats these responsibilities as part of the product builds a sustainable line; one that treats OEM as a label on the same box will struggle with support and returns.
The Product Documentation and Branding
The branding layer is where the partner’s identity appears. The hardware carries the partner’s brand, the documentation is adapted for the partner’s customers, and the packaging presents the product as the partner’s own. The [Telarvo Store homepage](https://www.telarvostore.com/) provides the product families that form the base, and the partner builds the presentation layer on top.
The documentation is part of the product. A partner that provides clear setup guides, a support page, and a warranty statement in its own voice reduces first-line support load and builds customer trust. The branding work is real work, and it is what turns OEM hardware into a partner product line.
The Partner’s Go-to-Market
The partner’s go-to-market is its own. Pricing, sales channels, and customer acquisition belong to the partner; Telarvo does not manage the partner’s end customers. The partner builds the product pages, the comparison tables, and the deployment guides from the Telarvo model documentation, and it presents the hardware in its own voice.
The [Telarvo Store homepage](https://www.telarvostore.com/) serves as the reference for the product families, and the partner adapts the material for its market. The go-to-market is where the OEM relationship becomes a business rather than a transaction, and the partner that invests in it builds a line that outlasts any single order.
The Product Documentation
The documentation is part of the product. A partner that provides clear setup guides, a support page, and a warranty statement in its own voice reduces first-line support load and builds customer trust. The partner adapts the Telarvo model documentation to its market, presents the hardware in its own voice, and keeps the guides current with each firmware or model update.
The [Telarvo Store homepage](https://www.telarvostore.com/) serves as the reference for the product families that form the OEM base, and the partner builds its presentation layer on top. The documentation work is real work, and it is what turns OEM hardware into a partner product line that customers trust.
The commercial terms deserve the same rigor as the technical flow. The agreement should state the MOQ per model, the price breaks at volume, the warranty sharing, and the support escalation path in writing, so both sides know the rules before the first order. The [Telarvo Store homepage](https://www.telarvostore.com/) links the product families that form the OEM base, and the partner’s product line is built from that foundation. A written agreement is what makes the OEM relationship sustainable rather than ad hoc.
A Checklist for the OEM Decision
Before signing an OEM agreement, work through a checklist. Confirm the demand in your market and the volume you can move. Confirm your support capability — can you triage first-line questions and escalate cleanly? Confirm your logistics — can you hold inventory and handle RMA? Confirm your branding — do you have the packaging and documentation capability? Confirm the terms — MOQ, pricing, and warranty sharing. The checklist turns the OEM decision from a conversation into a plan.
The Warranty and RMA Flow
The warranty responsibility is split across three parties. Telarvo covers hardware defects on every unit; the partner handles the customer interface and returns; the customer returns the faulty unit through the partner. The RMA flow — diagnosis, return authorization, replacement or repair, and turnaround time — should be in the partner’s documentation so a warranty event is handled consistently.
The flow should be written down before the first sale, not after the first failure. A one-page escalation guide — who to contact, what information to gather, and the expected response time — prevents the confusion that appears when a customer has a hardware problem and the partner has to discover the process on the spot. The [Telarvo Store homepage](https://www.telarvostore.com/) links the product families that form the OEM base.
Frequently Asked Questions
What is OEM telecom gateway hardware?
It is standard Telarvo gateway hardware delivered under a partner’s brand, with partner branding, documentation, and go-to-market.
What does the partner provide?
Pricing, sales, distribution, customer relationship, first-line support, and the branding and packaging.
What does Telarvo provide?
The hardware, firmware, warranty coverage, and technical backing.
What should I evaluate before starting an OEM program?
Demand, support capability, logistics, branding capability, and the commercial terms.
What support is included?
A 12-month warranty on each unit and 7×12 technical support, with first-line support flowing through the partner.