Preserve the original request
Save the submitted post URL, order ID and current status before removing the item where practical. If it has already been deleted, use the retained order history. The replacement's similar wording does not establish that it inherits the original service request.
Resolve active processing
Ask support how the selected service treats an unavailable target and whether any change is supported. Do not assume that remaining quantity or coverage moves automatically. A new target may have different eligibility and requires its own check under the current listing.
Keep the metrics distinct
Start a separate observation row for the replacement post. Comparing the original post's starting counter with the replacement's counter would mix two items. If campaign totals combine both publications, label that aggregation clearly and retain the underlying individual records.
Decision checklist
| Decision | What to check |
|---|---|
| Original | Submitted URL and status |
| Replacement | New published target |
| Report | Separate item history |
Worked example
For illustration, a company republishes an announcement after correcting a document attachment. Even if the text is unchanged, record the replacement separately. Ask about the unfinished original order before purchasing again or describing the new post's starting count as a delivery loss.
Example figures explain the decision; they are not current prices or promised results.