Before buying data in bulk for resale, confirm that the supplier permits the proposed model and that the products fit the customers' SIMs. A bulk-order facility is an operational feature, not evidence of a wholesale discount or permission to resell any retail bundle.
Define the product before comparing the price
Record network/provider, allowance, validity, time restrictions, application restrictions and whether the purchase is a once-off or recurring product. A “10 GB” description can combine different wallets. Do not divide the price by the headline allowance and ignore how the customer can use it.
The live catalogue comparison deliberately separates unambiguous price-per-GB products from allowances that need more interpretation. Use the actual current catalogue and written supplier terms for a resale quote.
Confirm the commercial arrangement
- Is resale allowed through your shop, website or downstream platform?
- What price, fee and settlement rules apply to that arrangement?
- Who supports delivery, expiry, wrong-recipient and disputed orders?
- Which customer information is needed and how should it be protected?
- What confirms a completed transaction and how are adjustments reconciled?
Do not market a personalised operator promotion as a universally available reseller product. Some retail transfers, promotions and device-specific products have their own conditions. A working network lookup does not establish commercial resale rights.
Check recipients before a batch
Obtain the customer-authorised number list and the intended product per recipient. Normalise local and +27 formats, resolve duplicate rows intentionally and confirm the current provider where supported. Portability means a broad prefix is insufficient.
Use the network guide for the supported lookup task. A host-network association can still need retail-provider compatibility checks. Avoid assuming that a virtual-operator account accepts every bundle labelled with its host.
Submit once and reconcile by reference
A controlled batch begins with a small authorised test of the intended product and workflow, not a blind large upload. Review the queued rows and total, then retain an internal reference and supplier reference for every order. Read the CSV workflow guide for the existing platform process.
Distinguish queued, pending, completed and failed outcomes. A slow response is not proof of failure. Query the existing order before retrying, and record adjustments separately from the original sale. Keep unresolved customer commitments visible until the outcome is confirmed.
Model contribution and cash tied up
Use the actual price, payment costs, support effort and error experience. Buying a larger amount can increase working-value requirements without improving unit contribution. The economics guide provides hypothetical calculations and explains why turnover is not profit.
Give customers an accurate product description and receipt. Avoid claiming rollover, roaming or expiry benefits that the supplied product does not promise. Keep the supplier's current terms with the price record used for the sale.
When an API is useful
Consider integration when order volume and reconciliation requirements justify it. The distribution-platform guide covers catalogue, ordering and status workflows. Commercial terms, customer-funds handling and support responsibilities still need agreement.
If your role is to refer businesses rather than resell value yourself, use the affiliate programme and its terms. Do not describe referral commission as a bundle discount.
Bulk data questions
Does “bulk” mean cheaper per GB?
No automatic discount is assumed. Compare actual supply prices and the complete product conditions.
Can I reuse a failed-looking row?
First establish the original supplier outcome. An uncertain delivery can be duplicated by an unconditional retry.
SIMcloud catalogue/workflow and commercial-page references reviewed 1 November 2026. No wholesale rate or guaranteed resale margin is quoted.