Service ID vs Order ID: An OgaViral Reference Guide

A service ID identifies the OgaViral service you select. An order ID identifies a particular order made for that service. Use the service reference when discussing which offer you mean, and the order reference when asking about a particular purchase. A refill request can also have its own reference, separate from the original order.

For Nigerian resellers and account managers, keeping those references separate makes records easier to follow. Start with our current service catalogue when choosing an offer. Once an order exists, retain its own details instead of relying on the catalogue number alone.

Think of the service as the option and the order as the purchase

A service describes what is being offered under particular conditions. An order records one request for that offer. Selecting the same service twice does not make the two purchases the same order. Each purchase needs its own record so you can distinguish its destination, quantity, date and outcome.

Imagine a hypothetical Lagos reseller managing two approved client requests. Both use the same service, but the quantities and destinations differ. The service reference helps identify the common offer. It cannot, by itself, tell the team which client's purchase they are discussing.

A useful question is: “Am I identifying an option in the catalogue, or one transaction already submitted?” Answer that before copying a number into a support note, spreadsheet or software field. A number without its label can be easy to misunderstand.

Read the labels in OgaViral's documentation carefully

Our public API documentation makes the distinction explicit. In its service-list response, service identifies a service. An add-order request uses that service ID, while the example response returns an order reference. A request for an order's status uses the order ID.

The documentation also separates creating a refill request from checking that request. Creating one uses the original order reference; the response can supply a refill reference. Checking refill status uses that refill ID. These are distinct jobs, even when the references concern the same original purchase.

The documentation's sample numbers, prices and currencies are examples. They are not a recommendation to submit those values or proof of a currently available offer. Read the current listing and your actual order record. This explanation does not require you to create an API connection.

Use a labelled record rather than a loose number

For each purchase, keep the service name and ID together with the order ID, destination, quantity and submission date. Give every column a clear heading. If you use your own client or job reference, label it as internal so nobody mistakes it for an OgaViral order ID.

For the fictional Lagos reseller, “Client A, first request” could be an internal label. It connects the approved brief to the actual purchase record but does not replace the reference returned for that order. A second purchase for Client A still needs a separate entry.

Record relevant service conditions as they appeared when you ordered. A service name is useful context, but a remembered label is a poor substitute for the actual purchase details. Keep any later clarification with that record instead of silently changing the original note.

Choose the reference that fits the question

If you want to clarify an offer before buying, identify the service and the wording you need explained. You will not yet have an order reference for a purchase that has not been made. Do not borrow an old order number to make the question look complete.

If a particular purchase has not progressed as expected, start with its order ID and relevant observations. Include the selected service as context. Our pending-order guide covers the delivery checks; this guide helps you identify which record those checks concern.

If your question concerns an existing refill request, retain both the original order reference and any refill reference available in the request record. The existence of a refill operation does not establish that your order qualifies. Eligibility follows the service conditions and applicable terms.

Prepare a precise support note

A useful note states the order reference, service, destination, date and issue in plain language. Describe what you can observe, such as a displayed status, and when you checked it. Say what you need clarified without describing an assumed cause as a confirmed fact.

An illustrative structure is: “I am asking about order [my actual order ID], for service [my selected service]. I submitted it on [date]. The recorded status is [status]. Please clarify [specific question].” Complete the note from your own record rather than copying example values.

Keep passwords, API keys and unrelated client information out of the note and screenshots. If a screenshot helps explain a problem, check the whole image before sharing it. The reference needed to discuss one order is different from a credential that grants account access.

Resolve missing or conflicting references before acting

If you cannot locate the order ID, review the existing account record and any saved confirmation before assuming no order exists. Keep the service, link, quantity and approximate submission time available for clarification. Do not invent a reference or treat a payment reference as an order number.

If two notes disagree, compare them with the original order record. Do not choose whichever number looks more familiar. Also avoid submitting a replacement purchase solely because a reference is unclear. OgaViral's terms restrict overlapping orders for the same destination while an existing order is unfinished.

An order ID does not prove completed delivery, permanent retention or a right to cancellation or refill. Purchased activity also remains separate from organic interest and does not establish buyers or platform approval. For your next order, create one labelled record and check that its service, order and any refill references each retain their own meaning.