Assign an internal reference
Create a stable key for the approved customer request before submission. It can link the brief, budget, and operator actions. This reference belongs to your workflow and should not be assumed to exist in the provider's system.
Attach the returned provider ID
When acceptance is confirmed, store the provider's exact identifier beside the internal key. Preserve it as returned rather than trimming or numerically reformatting it. Support and status operations must use the identifier expected by the documented API.
Handle one-to-many cases explicitly
A revised campaign or a legitimate split may produce several provider orders for one internal brief. Record each relationship with its quantity and charge. Do not overwrite the earlier identifier with the latest one and lose the purchase history.
Decision checklist
| Decision | What to check |
|---|---|
| Internal | Approved customer request |
| External | Accepted provider order |
| Relationship | Quantity and charge per link |
Worked example
A hypothetical campaign C-28 is fulfilled by two accepted provider orders for 600 and 400 units. Both identifiers must remain attached to C-28. Keeping only the second ID would hide the first 600-unit purchase and its charge.
Example figures explain the decision; they are not current prices or promised results.