D2C ·
Indiegogo rewards after the platform upgrade: prepare a current China release brief
Connect legacy perk promises and current reward records to approved components, selected pledge exports and Guangzhou release waves.
By SINO CEP Insight editorial team
Start with the current campaign records: an older Indiegogo perk spreadsheet may help explain a promise, but the Guangzhou release should use an approved current order selection, physical component mapping and recipient version.
Check the campaign stage and terminology
Indiegogo’s official upgrade guide records a move to Gamefound technology on 16 October 2025. Perks became Rewards; InDemand became Late Pledge. Its current Pledge Manager stage supports managing orders and collecting shipping details. Identify the stage used by your campaign before describing the handover.
For a migrated campaign, keep earlier perk references as supporting records and reconcile them with the current reward identities. For a newer campaign, use the actual current reward and order structure. Avoid assuming that an old worksheet’s column names still match today’s export.
Translate the promise into a physical specification
Create a mapping from each approved reward or legacy perk reference to the product SKUs, variants, quantities and included extras. Identify which items are physical and which are digital; a digital extra should not become a warehouse picking line.
Include any creator-approved bonus or exclusive item explicitly. Indiegogo’s upgrade guidance describes changes to former Secret Perks, so verify the applicable recipients and contents from the actual project records. Keep ambiguous or incomplete mappings on a decision list instead of inferring a kit from its marketing name.
This promise record guides supplier coordination: each expected delivery should identify the component it supplies and the rewards that depend on it. A changed component specification needs a creator approval and a new version.
Select the pledges for the intended wave
The current export guide uses the Orders tab and allows filtering by pledge ID, stage, payment status and product, among other fields. The creator should select the approved records for the wave and document the filters used. Export availability alone is not physical dispatch approval.
- Source: campaign, stage, export type and file version.
- Selection: the included pledges and the status criteria used.
- Contents: approved reward-to-component mapping and variants.
- Exclusions: unresolved choices, payment or recipient details.
Keep the original export with the operation record. Agree a sample field mapping before transferring live instructions, including the stable pledge or order identity used to detect a repeated record.
Connect selected demand to accepted supplier stock
Reconcile the selected wave’s component requirements with Guangzhou receiving records. Distinguish accepted quantities from supplier-promised deliveries and goods held for checks. Reserve the approved balance against this wave so it is not allocated again to later pledges or another store.
When arrivals differ from the plan, show the creator which rewards and quantities are affected. Obtain a decision on waiting or revising the wave, then update the release version and backer communication. A supplier substitution should not silently replace the promised reward.
Approve recipient changes before parcel preparation
Indiegogo’s address guidance limits backer changes once a pledge is ready for shipping, shipped or completed, and notes that creators can disable changes. Agree a separate operational cut-off with the Guangzhou team. Review each requested correction against whether its parcel is unpicked, packed or dispatched.
Close the wave with pledge, kit, parcel and tracking references, held reasons and remaining components. Use our Indiegogo operation brief, supplier handover, reward workflow and recipient handover to scope the work. Product, packing and destination acceptance require shipment-specific review.