The creator seeding operations checklist: from shortlist to shipped

Seeding programs rarely fail at the interesting parts. Finding creators and getting a yes is the work everyone signs up for. What actually goes wrong is the stretch between “she said yes” and “the courier picked it up”. This is a checklist for that stretch, written for a Shopify store shipping to creators in India.

Why a checklist and not just a good intern

A seeding order looks simple: one product, one address, zero rupees. But every one of them passes through six or seven small decisions, and any of them can be wrong. Wrong variant. Address with no PIN. A duplicate creator who already got the parcel last month. A discount that was applied at 90% instead of 100%, so a creator gets a payment request for a gift.

At 20 orders a month you catch these by memory. At 200 you do not. The checklist exists so the same checks happen every time, whoever is placing the orders. For the cost side of the argument, read the hidden cost of barter ops; this post is the fix.

Step 1: design the intake sheet

Everything downstream depends on the sheet. Most teams reuse the outreach sheet, with its follower counts, niches and rate cards. None of that helps you place an order. Build a separate intake tab with only the columns that change how the order is placed.

Columns that matter

• Creator ID. A stable ID you assign, not the handle. Handles change; IDs do not.
• Handle and platform. Lowercase, no @ symbol. You will dedupe on this.
• SKU and variant. Two columns. “The green one” is not a variant.
• Quantity. Defaults to 1. Anything else should have been agreed in writing.
• Recipient name. The name on the door, which is often not the handle's display name.
• Phone. 10 digits, no +91, no spaces. This is the number the courier will call.
• Address line 1, line 2, city, state, PIN. Five columns, not one. This is the single biggest change you can make.
• Status. One of: confirmed, placed, shipped, delivered, posted, RTO, cancelled.
• Order number. Written back after placing. Empty means not placed.
• Added by and added on. So you know who to ask when a row is wrong.

One row per creator per order. If a creator gets two products, that is two rows with the same creator ID. This feels wasteful but it means every row maps to exactly one line item and the sheet can be imported directly; see importing orders from CSV for why the shape matters.

Step 2: dedupe creators

Duplicates come from an ordinary place: two people reached out to the same creator in different weeks, or the creator replied on two platforms. The parcel goes out twice.

Before every batch, run three checks:

1. Normalise the handle column (lowercase, strip @ and spaces) and flag exact matches within the batch.
2. Normalise the phone column (strip +91, 0, spaces, dashes) and flag matches within the batch.
3. Compare both against the placed tab, so a creator seeded in March is not seeded again in July by accident.

A flagged row is not automatically wrong; sometimes you do want to send a second product. But the person who added the row should confirm that, not the person placing the order.

Step 3: confirm SKU and variant

Social conversations produce product descriptions, not SKUs. “The 500g one” is what arrives in the sheet. Someone has to resolve that to a real variant, and it should happen in the sheet, before placing, where it can be reviewed.

• Keep a reference tab that lists every active variant with its SKU, title and option values, exported from your store.
• Resolve each row to a SKU from that tab. A bulk-order tool can do this matching automatically from free text; by hand, use a lookup formula.
• Check stock. A seeding order that oversells a variant will block a paying customer.
• Rows that cannot be resolved go back to whoever added them. They do not go into the batch with a best guess.

Step 4: validate address and phone before placing

Teams skip this step because the order will go through with a bad address. The courier finds out three days later, and the parcel comes back as RTO: forward shipping, return shipping, a re-dispatch, and a creator who has lost interest.

Minimum bar for a row to be placeable:

• A 6-digit PIN that exists, with city and state that agree with it.
• Address line 1 containing a house, flat or plot number, not just a landmark.
• A 10-digit mobile starting with 6, 7, 8 or 9. Ask specifically for the number the creator answers calls on, which is not always the messaging-app number.
• A recipient name the security guard or delivery agent can ask for.

Addresses from DMs usually arrive as a single line. Split them into the five columns before placing, whether with an auto-parser or by hand. There is a full routine for this in cleaning creator addresses before you ship.

Step 5: discount and tag conventions

Decide these once and write them down. The goal is that any seeding order can be identified, filtered and reported on months later without anyone remembering how it was placed.

Step 6: place in batches

Place orders in batches, not as each creator confirms. A batch has a start and an end, which means the checks above happen once for the whole set instead of being half-remembered per order. It also means the courier gets one pickup with 40 parcels rather than 40 pickups with one.

A sensible rhythm is two batches a week. Rows marked confirmed by Tuesday morning get placed Tuesday; rows confirmed by Thursday get placed Thursday. At 2 to 3 minutes per order by hand, a batch of 40 is roughly an hour and a half to two hours; a bulk-order tool that reads the sheet places the same batch in a few minutes and writes order numbers back. Either way, the checklist is the same. For the mechanics of the manual and bulk routes, see how to bulk-create orders on Shopify.

Step 7: fulfilment handoff to the courier

Once orders exist, they enter the same fulfilment flow as paid orders, which is the point of placing them as real orders rather than tracking them in a sheet. A few things are specific to seeding parcels:

• Pack against the order list, not the sheet. The order is now the source of truth.
• Prepaid, never COD. A ₹0 order flagged as COD will get a collection attempt and a confused creator.
• Print the ₹0 invoice and include it. Some couriers and building security want a document that matches the parcel.
• Add a note or card that says who it is from and what it is. Creators receive a lot of parcels.
• Book one pickup for the batch and record the AWB numbers against each order.

Step 8: share the tracking link

Send every creator a short message the day the parcel ships: what is inside, the tracking link, the expected delivery window, and who to contact if the courier cannot reach them. This prevents most of the “did you send it?” DMs and cuts RTOs, because a creator who knows a parcel is coming picks up the courier's call. If the store's shipping notifications are on, this happens automatically.

Step 9: follow up on content

Content follow-up belongs in the same sheet, not in a separate tracker. Add three columns: delivered on, follow-up on, and content link. When a parcel shows delivered, set the follow-up date about ten days out. On that date, check for a post; if there is one, paste the link and mark the row posted. If not, send one polite nudge and move the follow-up a week.

Two nudges is enough. After that, mark the row no content and move on. The value of this column is the rate, not the chasing: if 40% of delivered parcels produce content, you know what a batch of 50 is worth.

Step 10: the weekly review

Fifteen minutes, once a week, with the sheet open. Count four things: rows confirmed, orders placed, parcels delivered, and content received. Then walk the exceptions: orders that failed to place, parcels stuck in transit for more than five days, RTOs, and creators overdue on content. Each exception gets an owner and a next action written into the row.

Over a few weeks this tells you where the process leaks. Failed placements mean the SKU or address checks are being skipped. RTOs mean the phone column is unreliable. Delivered parcels with no content mean the shortlist, not the ops, needs work.

Ad-hoc vs checklist: what actually changes

A note for agencies

If you run seeding for several brands, keep one sheet per brand connected to that brand's store, and never place from a combined sheet. Keep the step 5 conventions identical across clients so nobody has to remember which brand uses which tag. The agency playbook goes deeper.

Where to start

Do not adopt all ten steps on Monday. Start with the sheet: split the address into five columns, add status and order number columns, and dedupe once. That removes the most expensive failures. Add the conventions the following week, then batching, then the weekly review. Within a month the process runs the same way whoever is at the desk.

If placing these orders by hand is eating your week, you can try it free and see your own list placed in minutes.