Sociovaults editorial team · Published 2026-10-23
Start with a service you can explain
Your first useful catalogue is a small one. Choose a platform and a result, then inspect the accepted target, minimum, maximum, price basis and refill conditions. Save the supplier service ID alongside your retail description. Two packages called Instagram followers can have different limits and coverage. A supplier catalogue is an input to your offer, not a complete customer-facing explanation.
Separate your business model from delivery
Reselling means that you sell a defined service to your customer and purchase the corresponding delivery from a supplier. Your work includes selecting products, setting expectations, collecting payment, keeping records and handling questions. A child panel can provide a storefront, but it does not create customers, eliminate support work or guarantee profit. Start by defining who you intend to serve and what problem your workflow solves.
Map a first order from customer to supplier
Record your customer reference, supplier service ID, public target and quantity. Check the URL type before submission. Use a profile target for a profile-based service and a content target for a post or video service. Keep the supplier order ID when the order is accepted. If a request times out, check whether an order already exists before repeating it; a network error is not proof that nothing was submitted.
Price using the complete cost
For a per-1,000 service, the supplier cost is rate multiplied by quantity divided by 1,000. Add funding fees, conversion costs and the support allowance you choose before setting your selling price. If you sell in KES, GHS or ZAR while your supplier wallet is USD, keep both amounts and the rate used in your records. Markup percentage and money earned on an order are different measures.
Check funding before making delivery promises
A gateway integration or a local-currency display does not establish that a particular payment method is active for your account. Open Add funds and inspect the actual choices. Check the minimum deposit, fee, charged currency and expected wallet credit. Avoid accepting an urgent customer payment until you know you can fund the supplier account through a method you can use.
Build a support record from the beginning
Keep the submission time, starting count if relevant, requested quantity, delivered result and later observations. Delivery and retention are separate. A completed order does not establish permanent retention or sales. For partial delivery, inspect the remaining quantity and any recorded wallet credit. For a drop complaint, check whether the original package includes a refill and whether the request is within its conditions.
Automate only after the manual workflow is clear
The API should reproduce a process you already understand. Keep the key on your backend, map retail products to supplier IDs and record returned order references. Synchronise service rates and availability before accepting more orders. Poll status at a reasonable interval, handle errors and distinguish a delayed response from a failed order. Use the live account documentation as the authority for fields and supported actions.
Measure the business rather than a headline counter
Review funded customers, first orders, repeat orders, gross margin, support workload and credits. A larger catalogue or more registrations does not necessarily improve the business. Begin with a limited test, write down what happened and revise the offer using that evidence. Do not claim organic growth, guaranteed monetisation or geographically local interactions from a general purchased-engagement listing.
Continue with your own figures
Use the live catalogue, country guides and published refund policy when planning an actual order. Contact support about an unclear requirement before submitting.