Fulfilling Pledges in Batches

To begin batch fulfillment, change your project status to PM Closed (Soft).

In this state:

• Backers who are still in an “Open” status can access their pledge and complete it.
• New late-pledge backers can still join.
• No backer can make changes once their pledge moves to “Verified” or “Shipped.”

This status allows you to start fulfillment while still accepting late pledges.

Navigate to the Fulfillment tab.

When preparing your shipping files, always export only backers marked as “Verified”. These backers:

• Have completed their pledge
• Have locked their orders
• Are ready to be fulfilled

Hive provides specific filters to export exactly the data you need — use them carefully for batch processing.

Once you complete a batch of shipments:

1. Go to the Fulfillment tab.
2. Click Upload Tracking.
3. Upload your file matching backer IDs to tracking numbers.

When a tracking number is uploaded:

• The backer’s status automatically updates to “Shipped.”
• Backers in “Shipped” status can no longer reopen or modify their pledge.
• This ensures the order stays locked permanently.

Why Batch Fulfillment Requires Care

Batch fulfillment involves multiple cycles of exporting and shipping. To avoid errors:

1. Always export only Verified backers.
2. Never include Shipped backers in an export.
3. Upload tracking immediately after completing a batch.

This workflow ensures:

• No double shipments
• Clean, reliable tracking
• No last-minute backer changes

Fulfilling 1,200 Backers in Three Batches

Step-by-step workflow

Batch 1 – EU Shipments

• The creator exports Verified backers only, filtered by region = EU.
• 412 backers are ready.
• They generate labels, ship the 412 parcels, and then upload tracking.
• Hive automatically updates those 412 backers to “Shipped.”

Batch 2 – US Shipments

• Two days later, the creator returns to the Fulfillment tab.
• They select “Verified” backers again — now only Verified & not Shipped appear.
• 367 US backers are ready.
• After shipping, tracking is uploaded and all 367 become “Shipped.”

Batch 3 – Rest of World + Late Pledges

• One week later, 30 new late pledges arrive.
• They auto-lock and move to Verified.
• The creator exports the remaining Verified backers (421 total).
• After shipping and uploading tracking, the system updates them to Shipped.

Outcome

• No backer is shipped twice.
• No backer can alter their order once tracking is applied.
• Late pledges were included seamlessly in the final batch.
• Fulfillment progressed smoothly across three separate export cycles.

This case study demonstrates exactly how batch fulfillment can be executed cleanly and safely using Hive’s verification and tracking mechanisms.