Mass orders: sending a hundred at once without losing money
A mass order is the difference between an evening of clicking and ninety seconds of work. It is also the fastest way to spend money on the wrong thing, because a batch charges line by line and does not stop to ask.
The format, and what it really accepts
One order per line, three fields: the service ID, the link, and the quantity.
6605 | https://facebook.com/yourpage | 1000 6109 | https://facebook.com/otherpage | 5000
The separator can be a pipe, a comma, or a tab. That matters more than it sounds, because almost nobody types a mass list — it comes out of Excel, Google Sheets or a CSV export, and those produce tabs and commas. Paste straight from a spreadsheet and it will be read correctly.
Where a link contains a comma — a Google Maps URL with coordinates in it, say — use pipes. The pipe wins wherever it appears on a line, so the comma inside the link stays part of the link.
Price the batch before you send it
Type or paste your lines and the panel checks every one of them against the same pricing the real submit uses, without placing anything. You get the total, the number of lines that will go through, the number that will be skipped, and the reason for each.
Use it. A batch charges line by line, so without that check the first sign of a typo is a receipt saying six of your nine lines went through and your balance is gone. The check costs you nothing and takes under a second.
The mistakes that cost money
- Copying the ID from the wrong column. The service ID is the number in the first column of the price list — the supplier's number, the same one printed on every panel reselling the same catalogue. It is not the row position, and it is not the category.
- Quantities below the minimum. Every service has a floor. A line asking for 100 on a service with a 500 minimum is skipped, not rounded up — and if you assumed it went through, your delivery is short and you will not know why.
- The same link on twenty lines. Twenty orders of 1,000 to one profile is not the same as one order of 20,000, and it is not safer. Twenty simultaneous deliveries to one account is the single most obvious growth pattern there is. If you want volume on one target, use drip-feed instead.
- Stale links from an old sheet. Usernames change. A sheet built three months ago is full of profiles that have moved, and every one of those becomes an order delivered to a stranger or refunded after the fact.
What happens to a line that fails
Nothing is charged for it. Each line is attempted on its own, and a bad service ID, an invalid quantity or a missing link stops that line and nothing else. The report afterwards names every line by number, tells you what happened, and shows the input you gave, so you can fix three lines and resend those three rather than the whole batch.
That per-line independence is the whole point of the format. A batch that failed as a unit would be safer in one narrow sense and useless in every other.
Size, and why the batch stops itself
Two hundred lines is the ceiling per submission. The batch also gives itself a time budget, and if it runs out it stops in an orderly way and reports every line it did not reach as not submitted and not charged.
That is deliberate. The alternative — a request that runs until the server kills it — leaves the earlier lines paid for and placed while the customer gets a blank error page naming none of them. Better to be told plainly that forty lines went through and sixty did not.
Splitting a large job sensibly
If you have four hundred orders, send two batches rather than trying to squeeze one. If you have four hundred orders for one client across forty profiles, think about the shape of the delivery rather than the size of the paste: forty profiles each gaining a thousand followers in the same ten minutes is a pattern, and patterns are what platform review systems are built to find.
Spreading a client's work across a few days costs nothing extra and looks like growth instead of a purchase.
Keep the sheet, not the paste
The most useful habit for anyone running volume is keeping the source spreadsheet rather than typing into the box. Three columns, one row per order, and a formula that builds the line. Then a batch is reproducible: you can see what you sent last week, adjust the quantities, and resend without reconstructing anything from memory.
It also gives you somewhere to record what happened. The panel keeps every order, but your sheet is where the client name, the invoice number and the agreed price live — and those are the numbers you will be asked about, not the order IDs.
Before you press submit
- Run the check and read the total. If it is not roughly what you expected, something is wrong with a quantity.
- Look at the skipped count. Zero is the number you want; anything else means fix it now, not after.
- Confirm your balance covers the total. The batch stops charging when the wallet runs out, and the remaining lines are reported as unsubmitted — recoverable, but a wasted trip.
- Spot-check two links by opening them in a signed-out browser window. If you cannot see the profile, neither can the supplier.
Reading the report afterwards
The result page lists every line by its number, in the order you submitted them, with what happened to it. Green lines carry the order number and the charge; red lines carry the reason and the exact text you gave.
Keep it open while you fix things. Because the line numbers match your paste, correcting a batch is a matter of pulling out lines 7, 19 and 31, fixing those three, and sending them as a small second batch — rather than re-reading a hundred rows looking for what went wrong.
The orders themselves appear in your orders list immediately, exactly as if you had placed each one by hand. There is no separate "batch" object to track and nothing behaves differently afterwards; the mass form is a faster way to submit, not a different kind of order.
When not to use a mass order
Two cases. First, anything needing custom comments — those services take a list of the comments themselves, and there is nowhere in a three-field line to put them. Order those from the single form.
Second, anything where you are unsure of the service. The mass form is for work you have already decided on. Testing a new service belongs in the single order form, at a small quantity, where you can read the whole specification beside the box you are typing in.
Comments
No comments yet — be the first.
