Skip to main content

​
WooCommerce Integration

The LauncherForge Commerce for WooCommerce plugin connects WooCommerce orders to LauncherForge game-key delivery.
WooCommerce handles checkout, taxes, payment methods, refunds, and customer emails. LauncherForge generates the game key. The plugin joins both systems.

​
What the plugin does

​
Requirements

  • WordPress with WooCommerce active.
  • LauncherForge Commerce for WooCommerce plugin.
  • Active Commerce API add-on.
  • Complete Commerce API key.
  • LauncherForge App ID for every game product.
  • CD-Key protection enabled for each mapped game.

​
1. Install the plugin

1

Open the plugin installer

In WordPress, open Plugins → Add New Plugin → Upload Plugin.
2

Upload the ZIP

Select launcherforge-commerce-for-woocommerce.zip.
3

Install and activate

Install the plugin, then activate it.
Upload the LauncherForge plugin

​
2. Configure the integration

Open:
Configure: Configure LauncherForge Commerce
Do not paste only the visible prefix. A value such as lf_commerce_live_d122d2cc091f is not the complete API key.

​
3. Create the WooCommerce product

Open:
Recommended configuration: Create a WooCommerce game product Map the product to a LauncherForge App ID
Use the numeric App ID expected by Commerce API. Do not enter the game slug.

​
4. Run a manual test

For the clearest manual test:
1

Create an order

Open WooCommerce → Orders → Add Order.
2

Add the buyer email

Enter a billing email.
3

Add the mapped product

Add the LauncherForge-enabled WooCommerce product.
4

Save the order

Save the order before changing its final status.
5

Mark it as Completed

Change the order status to Completed and save again.
Mark the test order as Completed
For manual testing, use Completed. In a real checkout, the plugin also listens for WooCommerce payment completion and paid order transitions, but the payment gateway controls the exact order-state flow.

​
5. Verify the result

Open the order and check:
  • An order note confirming that LauncherForge generated the key.
  • The key displayed under the order item.
  • A LauncherForge delivery ID.
  • The new key in LauncherForge.
Game key inside the WooCommerce order The customer can also see keys in:
Customer order details with the game key

​
Email delivery

The LauncherForge backend does not email the buyer for external deliveries. The WooCommerce plugin adds generated keys to customer order emails using WooCommerce’s email system. This means:
Your WordPress installation must be able to send email. For production, configure a reliable WordPress mail transport or SMTP plugin according to your hosting environment.

​
Quantities

If the customer buys quantity 3, the plugin requests three keys. Each unit uses a different idempotency key, so retries do not duplicate licenses.

​
Background processing

The plugin schedules delivery work through WooCommerce Action Scheduler. Open:
Search for:
LauncherForge scheduled action Possible states:
  • Pending.
  • Complete.
  • Failed.

​
Retry a failed delivery

Open the order and use:
The plugin reuses deterministic idempotency values. Existing successful units are not regenerated.

​
Logs

Enable Debug logging in the integration settings, then open:
Select the log source:
LauncherForge WooCommerce logs The plugin does not write the Commerce API key or generated game keys to the technical log.

​
Common problems

​
No LauncherForge fields appear in the product

Confirm that:
  • WooCommerce is active.
  • The LauncherForge plugin is active.
  • The product is being edited through WooCommerce.

​
The order completes but no key appears

Confirm that:
  • The integration is enabled.
  • The complete API key is saved.
  • LauncherForge delivery is enabled on the product.
  • The App ID is numeric and correct.
  • CD-Key protection is enabled for the game.
  • The Commerce API add-on is active.
Then inspect Scheduled Actions and WooCommerce logs.

​
INVALID_COMMERCE_API_KEY

The saved credential is invalid or contains only the prefix. Regenerate it in LauncherForge and copy the full value.

​
EXTERNAL_GAME_NOT_AVAILABLE

The App ID is wrong, the game belongs to another workspace, or CD-Key protection is disabled.

​
Production checklist

  • Use a staging store first.
  • Keep debug logging disabled after testing.
  • Configure reliable WordPress email delivery.
  • Test the real payment gateway in sandbox mode.
  • Verify customer email and My Account display.
  • Test quantity greater than one.
  • Test a repeated status update to confirm no duplicate keys.
  • Protect WordPress administrator access.