When moving from a Kickstarter project to Shopify operations, separate existing backer promises from new storefront purchases. Keep rewards, paid amounts, options, addresses and delivery batches connected. An imported record should not automatically become a new payment request.
Map rewards to sellable goods
Organize rewards and add-ons, then map them to Shopify products, variants and quantity units. Record each item in a multi-item reward and distinguish project editions from ordinary retail versions. Preserve original project and backer identifiers for support and deduplication so customers do not need to reconstruct their earlier purchase.
| Original record | Mapping check | Problem prevented |
|---|---|---|
| Reward and options | Product, edition, quantity and add-ons | Wrong rewards or missing items |
| Payment | Paid, outstanding or refunded | Duplicate charges or failed payments treated as paid |
| Address | Latest confirmed destination and deliverability | Dispatch to an outdated address |
| Promise | Batch, timing, restrictions and updates | Retail terms replacing the project commitment |
Reconcile before creating fulfillment work
Freeze a reviewable data version and retain its source. Do not rewrite amounts or delivery promises during transformation. Place duplicate backers, unconfirmed choices, payment exceptions and missing addresses in a review queue. Release only records meeting the defined conditions to the warehouse.
Use “Shopify inventory locations and exception recovery” for receiving and synchronization. Project allocations should not be mixed unconditionally with retail availability. Track fulfillment and notices for each item when shipping in batches.
Design new post-project purchases separately
The store can sell available goods or offer preorders with their own prices, payment route, delivery information and support. Shopify preorder purchase options require an app and an eligible configuration; check the official preorder guidance. That capability does not establish that earlier Kickstarter payments become an authorization for new Shopify charges.
Keep contact information used for project delivery separate from new marketing subscriptions. Explain and confirm changes for additional goods, exchanges or extra shipping rather than silently altering what customers must pay during migration.
Accept one delivery batch before scaling
Reconcile the original promise, warehouse goods, payment record, address, tracking and notice for a controlled batch. Include address changes, missing reward items, partial refunds and repeated imports. Before automatic release, continue with “Shopify Plus automation: order states and intervention” to define records needing human review.
FAQ
Does importing backers as customers complete migration?
Also preserve the relationship between rewards, payment, options, addresses and promises. A customer record alone cannot determine the right fulfillment.
Should a backer who already paid check out again?
Design around the actual payment and commitment to avoid duplicate collection. Explain new purchases or confirmed outstanding payments separately.
Can every backer be put on a marketing list?
Keep delivery contact and later marketing choices separate. Contact information used for fulfillment does not itself establish a new marketing subscription.