Define each order's purpose
Assign a campaign reference and approved scope to every request. If orders use different actions, record them separately. If they use the same metric, decide whether they should run sequentially and check any service restriction on overlapping purchases.
Create observation boundaries
Save a baseline and time for each settled phase. When several active requests affect the same total, a single public count cannot reliably attribute progress to one of them. Note organic activity and other campaigns instead of assigning every change to the latest order.
Resolve one discrepancy at a time
Before adding a replacement or an extra installment, review unresolved orders on that target. Support may need the full list of related identifiers. A clear sequence makes it easier to explain whether a shortfall belongs to the original scope or a later addition.
Decision checklist
| Decision | What to check |
|---|---|
| Scope | Purpose per order |
| Sequence | Separate observation windows |
| Evidence | All related references |
Worked example
A hypothetical first order requests 600 units and a second requests 400 before the first settles. A total increase of 700 does not establish which order supplied which amount. Waiting for a settled phase would provide a clearer comparison.
Example figures explain the decision; they are not current prices or promised results.