Template Overrides

The plugin integrates with WooCommerce template lookup. A theme template takes priority over the plugin fallback.

Override a template

Copy the required file from the plugin’s templates/ directory into the child theme’s woocommerce/ directory, preserving the relative path.

Plugin:      templates/single-product/auction-bid-form.php
Child theme: woocommerce/single-product/auction-bid-form.php

Common templates include:

• single-product/bid.php and single-product/auction-bid-form.php
• single-product/pay.php
• single-product/tabs/auction-history.php
• single-product/lot-products.php and single-product/lot-sessions.php
• single-product/lot-sequential-console.php
• myaccount/auctions-settings.php

Auction archive template

For the dedicated auction archive, the plugin checks the active theme for woocommerce/archive-product-auctions.php, then archive-product-auctions.php at the theme root. Put your override in the child theme:

Child theme: woocommerce/archive-product-auctions.php

Start from your theme’s current WooCommerce archive-product.php override, or WooCommerce’s templates/archive-product.php if the theme has none. Copy it to the path above and customize that copy. Preserve the WooCommerce loop and its hooks.

This lookup applies when the request is marked as an auction archive. It does not replace ordinary shop pages or every shortcode list. Without a dedicated override, the existing archive template remains in use; if no template is available, the plugin looks for the theme’s archive-product.php and then WooCommerce’s fallback.

Preserve the contract

Keep required form fields, hooks, and sealed-auction visibility conditions. Bid submissions must retain the security nonce for woocommerce_auction_nonce and use POST.

Use PHP hooks or template customization for placement changes. Enqueue custom styles and scripts through WordPress APIs rather than modifying the distributed plugin assets.

After updating

Compare overrides with the current plugin template, merge necessary changes, and test normal, reverse, proxy, sealed, and seated workflows used by the store. A successful theme render does not verify bidding or payment behavior.