Use the documented identifier
Treat the service ID as the catalog key supplied by the provider, not as a number you can infer from a name or category. Preserve its original representation. Similar service titles can refer to different actions, targets, or coverage conditions.
Keep a mapping record
Store your customer-facing product reference alongside the provider identifier and the relevant description version. Review the mapping when the catalog changes. A renamed product should not silently inherit another service's requirements just because the text looks familiar.
Validate before submission
Confirm that the mapped service remains available and accepts the planned quantity and target. If the mapping is missing or ambiguous, stop the affected request for review. Do not fall back to the first search result or a nearby numeric identifier.
Decision checklist
| Decision | What to check |
|---|---|
| Internal key | Your product reference |
| Provider key | Documented service ID |
| Validation | Current scope and eligibility |
Worked example
In a hypothetical integration, product VIEW-A maps to provider service 417. Another service named Video Views uses ID 912 with different requirements. A name-based search should not automatically switch VIEW-A from 417 to 912.
Example figures explain the decision; they are not current prices or promised results.