WooCommerce Checkout Blocks: setup guide

1. Requirements and editions #

• Booster 9.0, WooCommerce and a supported WordPress/PHP combination.
• A staging checkout page using the WooCommerce Checkout block. In Pages > All Pages, edit the assigned checkout page to confirm its block type. A classic checkout shortcode is a different integration.
• Enable each required module in Booster > Plugins. Existing Free, Plus and Elite module limits still apply. The Blocks and applicable HPOS foundations are shared, not Elite-only.
• For conditional custom-field visibility, use WooCommerce 9.9 or later. Do not assume an unsupported field type will be converted.

2. Collect one file with an order #

1. Open Booster > Plugins > Cart & Checkout > Checkout Files Upload. Enable the module.
2. Under File #1, set a descriptive Label, such as Artwork for this order. Set Accepted file types, for example .jpg,.jpeg,.png, and keep the server upload-size limits in mind. Use Required only when an order cannot proceed without that file.
3. Save the settings. Add a product to the staging cart and open the Checkout block.
4. Choose a small permitted test file. Remove it and choose a replacement. If the field is required, confirm the checkout explains that a missing file must be supplied.
5. Place one test order using a test/manual payment method. Open that order from WooCommerce > Orders and check its upload entry.

Expected result: only the retained file belongs to that order. A removed file is not silently reattached. File access respects the permitted session/order context. Do not use confidential customer files for setup testing.

File positions and options designed for Classic checkout are not a promise of identical placement in Blocks. See the Checkout Files Upload guide for the module’s remaining settings.

Important Note: Due to security policies, the Checkout Files Upload module requires private directory configuration to work with the WooCommerce Checkout Block (Gutenberg). Please follow the steps below to configure storage:

1. Create a Private Storage Directory:
   Create a dedicated folder outside your public document root (e.g., outside public_html or htdocs).
   Example: /home/username/booster_uploads/ on live hosting.
2. Define the Constant in wp-config.php:
   Open your site’s wp-config.php file and add the absolute path using the WCJ_CHECKOUT_FILES_PRIVATE_DIR constant:

   define( 'WCJ_CHECKOUT_FILES_PRIVATE_DIR', '/home/username/booster_uploads' );

3. Verify Permissions:
   Ensure the web server process has read and write permissions to this directory so customer file uploads can be stored securely.

3. Add a supported custom field #

1. Open Booster > Plugins > Cart & Checkout > Checkout Custom Fields and enable the module.
2. Within your edition’s field limit, enable Custom Field #1. Set Type to Text and Label to Delivery reference. Save.
3. At staging block checkout, enter Front desk and place a test order.
4. Open the order in WooCommerce > Orders and find the saved field.

Expected result: the supported field appears and its value is saved with the order. Supported types are text, select and checkbox. Radio options appear as a select. Textarea and unsupported types remain Classic-only. Product/category/cart visibility depends on the configured rules, supported WooCommerce version and edition limits.

Full Checkout Custom Fields setup

4. Change the order button wording #

1. Open Booster > Plugins > Button & Price Labels > More Button Labels.
2. Enable the module and find Place order (Order now) Button. Set the text, for example Place my order, and save.
3. Open staging block checkout and check the final order button.

Expected result: the supported button label is shown. This changes wording, not payment authorization, totals or the customer’s order commitment. A gateway or third-party checkout may manage its own button; check it separately.

5. Check the store’s order storage #

HPOS is WooCommerce’s dedicated order-storage system, separate from the choice of Classic or Blocks checkout. Booster 9.0 uses WooCommerce order APIs in affected exports and reports and carries forward the shared applicable HPOS foundations in all editions.

1. On staging, open WooCommerce > Settings > Advanced > Features and inspect the current order-storage setting and any compatibility warnings.
2. Before changing storage, back up the store and follow WooCommerce’s synchronization and extension-compatibility requirements. Do not switch while migration or synchronization is incomplete.
3. Using your intended storage mode, inspect a test order and its retained fields/files. Run the Booster export or report that your store uses and compare the order identity, status and amounts with WooCommerce.

Expected result: affected Booster workflows read the correct order data. This does not certify every installed extension or promise faster exports. Preserve your normal refund and order-edit permissions.

Troubleshooting #

The upload or field is missing

Confirm the module and field are enabled, the page uses the Checkout block, the type/position is supported and your edition permits the configuration. Check visibility conditions and clear staging page caches.

A file is rejected

Check the actual file type, extension and server upload-size limit. Do not disable file-safety checks to accept an unsafe file.

An order already exists after a connection error

Inspect the existing order before placing another. Do not assume a timeout means that no order was created.

A gateway or theme changes the checkout

Check that extension’s supported Blocks integration on staging. Do not claim success from a Classic-only test.

Order data differs after a storage change

Check WooCommerce’s synchronization status and extension warnings before editing orders or rerunning writes. Preserve the discrepancy for support.

Related guides #

• Checkout Blocks overview
• Customer Return Requests
• Rule Explanations and Returns Summary
• Order Health and Morning Store Briefing