What happens if the starting count drops organically during an active order?

If the client naturally loses followers while the order is processing, the system will still aim for the absolute mathematical target (Start Count + Quantity). You may need to trigger a refill once the order completes to cover the client's organic losses.

Why does my order status say 'Partial'?

A 'Partial' status means the server delivered a portion of the order but could not complete the rest (often due to platform updates or a deleted post). The system automatically refunds the undelivered remainder directly to your wholesale wallet.

Can I request a refill if the current count drops below the original Start Count?

No. Refill warranties only cover the quantity provided by the server. If the total metric falls below the original baseline Start Count, the system assumes the client purged their own organic audience, which falls outside the warranty parameters.

Tracking Campaign Delivery & Verifying Refill Warranties

1. The Foundational Metric: Start Count Verification

The most common dispute between digital agencies and their clients involves baseline metrics. If a client purchases 5,000 Instagram followers, you must know exactly how many followers they had before the campaign started.

This metric is known as the Start Count. When an order is dispatched via the API or dashboard, the server scrapes the target URL and logs the current metric (e.g., 1,250 followers). The campaign is only marked as "Completed" when the target URL successfully reaches the Start Count plus the ordered quantity (e.g., 6,250 followers). Recording this number protects your agency from clients claiming they did not receive full delivery.

2. Tracking Order IDs and Delivery Windows

When managing hundreds of links simultaneously, manual tracking is impossible. Every transaction generates a unique Order ID. This ID acts as your receipt and tracking number for backend fulfillment.

Understanding Delivery Variance: Not all services initiate instantly. High-retention, algorithmic-safe metrics often require a "warm-up" period where the server queues residential proxies. Before promising a client a 1-hour turnaround, agencies must review live delivery benchmarks to accurately quote Start Times (e.g., 0-6 hours) and Delivery Speeds (e.g., 500/day).

3. Managing Automated Drop Refills

Social media platforms regularly update their security algorithms, leading to inevitable metric purges across the industry. This is why premium fulfillment relies entirely on Refill Warranties (ranging from 30 days to 365 days).

How the Refill Protocol Works: If a client started with 1,000 likes, ordered 2,000 likes, and the post drops to 2,500 likes a week later, the warranty applies. The backend server compares the current URL count against the original mathematical target (3,000).

In most modern dashboards, clicking the "Refill" button next to the Order ID triggers an immediate API ping. The server independently verifies the drop and dispatches the missing 500 likes at zero additional cost to your agency.

4. The Agency Campaign Auditing Checklist

To prevent operational bottlenecks and client dissatisfaction, deploy this QA checklist for every campaign launch:

Pre-Flight & Post-Flight Audit:

Public Profile Check: Ensure the target account is strictly set to "Public." Private accounts will instantly return a "Canceled" status.
URL Formatting Validation: Verify that the link matches the required format for the specific service (e.g., providing a post link for likes, not a profile link).
Simultaneous Order Prevention: Never place two identical orders for the same URL at the same time. The servers will overlap the Start Counts, resulting in under-delivery. Always wait for Order A to read "Completed" before initiating Order B.
Warranty Logging: Flag the Order ID in your CRM with its expiration date (e.g., +30 Days) to proactively monitor the client's account for drops.

The Marketer's Guide to Tracking Campaign Delivery and Verifying Refill Warranties