Map each authorized account
List the account reference, exact post URL and approved action on one row. Keep internal client names separate from public handles where necessary. Approval for one account should not be treated as permission to place an order against another account that reused its content.
Review the line-level specification
Check the service ID, target type and quantity for every row before submitting. Follower requests target an account, while post actions require the relevant publication. A bulk sheet should preserve that difference instead of using one generic link field without validation.
Reconcile after purchase
Attach the resulting order ID and charge to the original row. This lets you follow a delayed request without searching through similar post titles. Keep separate completion records even when all orders were placed together and funded from one account balance.
Decision checklist
| Decision | What to check |
|---|---|
| Account | Authorized identity |
| Post | Exact publication URL |
| Purchase | Order reference per row |
Worked example
A hypothetical agency publishes the same announcement for two regional brand accounts. The text is identical, but the post URLs differ. Mapping each approved quantity to its exact account and URL prevents one account receiving both purchases while the other remains outside the order.
Example figures explain the decision; they are not current prices or promised results.