Skip to content
BE
EnglishAlbanianالعربيةArmenianAzerbaijaniBelarusianBosnian中文FrançaisGeorgianDeutschBahasa IndonesiaItaliano日本語한국어PunjabiРусскийSerbianEspañolTiếng Việt
Зараза рэгістравацца
← Усе кіраўніцтвыTHEPANEL

Reseller service catalog checklist: IDs, changes and customer expectations

Рэдакцыя THEPANEL

A reseller catalog is easier to manage when each customer-facing offer has a clear link to its current source service. Names alone are unreliable: two services can sound similar while differing in limits, type and conditions.

Keep a useful service record

  • Source service ID and your own offer ID.
  • Platform, category and service type.
  • Accepted target format and required fields.
  • Price unit, currency and last review time.
  • Minimum and maximum quantity.
  • Stated speed, refill conditions and important restrictions.

Do not use one free-text title as the only place these rules exist. Preserve the source ID separately so catalog updates and support requests can be matched correctly.

Review changes before accepting new orders

Availability, price, limits and descriptions can change. Refresh the data on a schedule appropriate to your workflow and check critical fields again before submission. If a source service is unavailable, do not silently substitute another service with different conditions.

Make price comparisons using the same unit. A package and a per-1,000 service cannot be compared by their displayed number alone.

Describe what is known, not what sounds strongest

Keep start estimates, daily speed and observed averages distinct. Do not present a timing estimate as a fixed deadline or service completion as a promise of sales or platform approval. Explain refill coverage according to the actual service, including its limits.

Track the order lifecycle

Store the accepted panel order ID with your customer's internal order reference. Handle partial and canceled outcomes explicitly. If a submission result is uncertain, reconcile it before retrying so you do not duplicate an accepted order.

For support, distinguish source service IDs, panel order IDs and your own references. Do not expose API keys or another customer's details in a ticket. A well-kept record helps resolve the specific case without guessing which offer or delivery was involved.

Review API documentation · Compare pricing units · Prepare support information