Build the batch from verified constraints
Set a product-seeding batch ceiling from the smallest verified constraint: units the brand has approved for seeding, destination-specific fulfilment capacity, the creator-compensation budget, the number of creator decisions the team can review properly and the number of parcels it can track. Record invited, accepted, shipped, delivered, asset-received and posted as separate stages. Do not convert an invitation, acceptance or shipment into a promised post. The worksheet below uses the brand's own costs and counts, not a universal conversion rate, so the next decision can be based on observed evidence rather than an invented benchmark.
Product seeding is a distribution method, not one standard creator contract. A brand can send an unconditional sample with no requested deliverable, offer product as compensation for agreed work, combine product and money, or commission paid work and ship the product only because it is needed for production. The batch plan must keep those arrangements separate because their commitments, disclosures and content permissions are different.
Write the offer before outreach begins. State the product, quantity, destination rules, compensation, requested work, timing, review steps and proposed usage. If there is no accepted deliverable, the brand should not count the parcel as an order for content. If work is requested, the creator should be able to understand the full exchange before accepting.
Start with the cost the brand actually gives up, not the retail price used in a pitch. Record the approved inventory quantity and the accounting basis the brand uses for each unit. Add packing materials, pick-and-pack labour, destination-specific postage, insurance when selected, creator compensation, platform or agency charges, internal review time, rights fees and a contingency that the budget owner can explain.
For cross-border parcels, check the destination and current carrier or customs treatment before approval. The Canada Border Services Agency explains that imported mail or courier items may be subject to duties and taxes. The plan should say who is expected to pay any charge and what happens if a parcel is refused; it should not surprise a creator after shipment.
Calculate a separate ceiling for every resource the campaign consumes, then choose the lowest one. Product inventory gives one ceiling. The approved fulfilment budget divided by a verified per-destination fulfilment estimate gives another. Creator-compensation commitments, staff review capacity and warehouse throughput create their own ceilings. A division that uses an unknown denominator is not evidence; resolve it or mark that ceiling unavailable.
Reserve the approved product before sending an offer that names it. Sized, seasonal, limited or perishable products need SKU-level checks because an available product family does not prove that the accepted variant can ship. Keep sellable customer inventory separate from the seeding allocation so later retail orders do not silently consume an accepted collaboration's unit.
A campaign needs named owners for creator approval, offer approval, address verification, fulfilment, delivery exceptions, submission review, disclosure checks and content-rights records. A large list does not create capacity for those decisions. If a role has no owner or response time, treat that stage as a blocking constraint before outreach expands.
Set the review standard before submissions arrive. It should describe what the brand will check, which revisions were agreed, who can approve a use and where the permission record is stored. Copyright protection generally applies automatically to original work in Canada, according to the Canadian Intellectual Property Office. Receiving a file therefore does not by itself prove that the brand owns it or can use it in every channel.
Use separate, timestamped states for invited, replied, accepted, approved, shipped, delivered, asset received, approved for use and publicly posted. Define each state before the campaign starts. A shipment should not be relabelled as content, and an asset received privately should not be relabelled as a public post. Keep declined, cancelled, returned and unresolved records visible rather than deleting them from the denominator.
Only calculate a rate from the brand's own completed, consistently defined window. Report the numerator, denominator, dates and collection method with it. If tracking changed during the window, retain the counts but mark the comparison not comparable. A first batch is allowed to end with unknowns; filling them with an industry average would only make the next decision less reliable.
Shipping requires personal information such as a recipient name and delivery address. The Office of the Privacy Commissioner of Canada summarizes fair-information principles under PIPEDA, including identifying purposes, limiting collection, limiting use, retention and disclosure, safeguards and individual access. The campaign should explain why an address is needed, who will use it, how long the operational record is retained and how a correction or privacy request can be made.
Do not collect an address before the creator has accepted an eligible offer and the brand has approved the collaboration. Restrict access to the people who need it for fulfilment or support, and do not copy delivery details into public briefs, content files or reporting exports. Record the operational status without exposing the underlying address.
Keep three totals. Planned cost is the approved forecast before outreach. Committed cost includes accepted compensation, reserved product and approved shipments. Actual cost uses recorded product, fulfilment, compensation, labour and rights costs after the batch closes. Reconcile the difference by reason rather than rewriting the original budget.
Unit costs become meaningful only when their denominator is named. Cost per shipment uses actual spend divided by shipped parcels. Cost per delivered parcel uses actual spend divided by confirmed deliveries. Cost per accepted asset or public post can be calculated only when those states were defined and observed. None of those measures proves reach, sales or profitability; each answers a narrower operational question.
Useful before you approve
Use the smallest verified ceiling created by available product, approved fulfilment and compensation budgets, staff review capacity and warehouse throughput. There is no universal batch size. A campaign should not invite or approve more collaborations than the brand can fulfil, track and review properly.
Include the brand's documented product cost, packing, fulfilment labour, destination-specific shipping, possible duties or taxes, creator compensation, operational labour, agreed content-rights fees and an approved contingency. Keep planned, committed and actual totals separate.
No. An unconditional product sample has no accepted deliverable. If a brand wants work in exchange for product, the requested work, compensation, timing and proposed usage should be stated and accepted before shipment. A shipment alone should never be counted as a promised public post.
Track invited, replied, accepted, approved, shipped, delivered, asset received, approved for use and publicly posted as separate states, along with declined, cancelled, returned and unresolved records. Define each state before collection so later comparisons use the same meaning.
Collect an address only after an eligible collaboration is accepted and approved, explain the fulfilment purpose, restrict access, protect the record, define retention and provide a correction or privacy-request route. Do not put delivery details in public briefs or reporting exports.
Primary source
Ready when you are
Sign in with your work email to create your dashboard, choose a plan, and prepare your first creator brief.