Crowdfunding for WooCommerce plugin review and common issues

Campaigns must be published and approved to display in the listing. Check: (1) in IgnitionDeck → Projects, verify campaigns are in “Published” status (not Draft or Pending); (2) campaign listing page uses the IgnitionDeck shortcode or template — verify the page is correctly configured; (3) new campaign installations may require flushing WordPress rewrite rules (Settings → Permalinks → Save Changes); (4) check if the campaign start date is in the future — campaigns may not display before their configured start date; (5) clear all caches.

Pledge recording requires PayPal IPN to confirm payments. Go to IgnitionDeck → Settings → PayPal and verify: (1) the PayPal email is correctly entered; (2) IPN is enabled in your PayPal account (Profile → Selling Tools → Instant Payment Notifications) pointing to your site’s IPN URL; (3) the site is accessible from PayPal’s servers (not behind maintenance mode or protected by HTTP authentication); (4) verify HTTPS is active — PayPal requires SSL for IPN; (5) check IgnitionDeck’s payment logs for IPN receipt confirmation.

Front-end campaign submission requires: (1) the creator is registered as a user on the WordPress site with appropriate permissions; (2) the IgnitionDeck campaign submission form page is correctly configured with the submission shortcode; (3) the required campaign fields are all filled in (title, description, goal, deadline); (4) file upload permissions are correctly configured if the creator uploads a campaign image; (5) check browser DevTools Console for JavaScript errors during form submission. Verify IgnitionDeck Commerce is active if the campaign type requires it.

In IgnitionDeck → Projects → [campaign] → Reward Tiers (or Perks), add reward levels with a minimum pledge amount, reward description, and quantity limits. Example tiers: “$10 — Digital download of the final product,” “$50 — Signed copy + early access,” “$500 — Producer credit.” Each tier appears on the campaign page as a selectable backing level. When a backer pledges at or above a tier’s minimum amount, they are associated with that tier. Manage tier fulfillment through IgnitionDeck’s backer management after the campaign successfully funds.

In IgnitionDeck Commerce, configure the campaign’s funding model as “All or Nothing” in the campaign settings. With this model: backers’ payment methods are authorized (not charged) when they pledge; if the campaign reaches its goal by the deadline, all pledges are captured and charged; if the goal is not reached, all authorized pledges are released and backers are not charged. This model requires proper payment gateway setup (Stripe handles authorization/capture separately; PayPal requires pre-approval agreements). Configure the campaign deadline date clearly so backers know when the funding period ends.

IgnitionDeck is better when: the community or cause fits a niche that existing platforms do not serve well; keeping funds (avoiding Kickstarter’s 5% fee plus payment processing) is financially significant at the expected campaign scale; brand consistency and data ownership are organizational priorities; or the platform will host many ongoing campaigns rather than a single project. Kickstarter is better when: the existing Kickstarter audience is the primary source of backers (discovery on Kickstarter is a significant acquisition channel); campaign promotion infrastructure and trust signals of a known platform outweigh the fee cost; or the project organizers lack the technical capacity to maintain a WordPress platform.

Yes — IgnitionDeck Commerce integrates with WooCommerce for physical reward management. When a backer selects a tier with a physical reward, WooCommerce creates an order for that reward item. Campaign creators can use WooCommerce’s order management and shipping tools to fulfill physical rewards after the campaign funds successfully. This is particularly useful for campaigns where backers receive a tangible product — the campaign acts as a pre-order system backed by WooCommerce’s established e-commerce fulfillment workflow.

Yes, that can happen, especially on older sites with many plugins. This usually happens when the plugin, theme, and add-ons are updated out of sequence. In most cases, testing on staging catches the issue before it reaches the live site. From experience, backups and changelog reviews save a lot of cleanup time.

Start by checking whether another plugin already does the same job. In most cases, overlap is what creates avoidable conflicts and performance issues. A common issue is installing a plugin because it looks convenient without checking the stack first. From experience, a short compatibility review avoids most of the pain later.