Data & Auction State
Product types
Section titled “Product types”auction: an item offered for bidding, represented byWC_Product_Auction.auction_lot: a sale container, represented byWC_Product_Auction_Lot.
Auction configuration and current state use product metadata. Important keys include _auction_type, _auction_start_price, _auction_bid_increment, _auction_reserved_price, _auction_dates_from, _auction_dates_to, and _lot_id.
The implementation also contains legacy spellings in identifiers, such as _auction_current_bider. Preserve exact identifiers when integrating; do not silently correct stored key names.
Custom tables
Section titled “Custom tables”Names below use the current site’s $wpdb->prefix, not a hard-coded wp_ prefix.
| Table suffix | Main fields |
|---|---|
auctions_for_woocommerce_log |
id, userid, auction_id, bid, date, proxy, lot_id, session_number. |
auctions_for_woocommerce_seats |
id, user_id, auction_id, order_id, date. |
Bid logs record activity. Seat records identify participation eligibility. Neither table should be treated as a replacement for WooCommerce payment records.
Visibility
Section titled “Visibility”The auction_visibility taxonomy participates in archive filtering and auction state. Updating one metadata value alone can leave product, taxonomy, and linked order state inconsistent.
Orders and reporting
Section titled “Orders and reporting”Use WooCommerce order APIs for order integrations, including stores with HPOS enabled. Analytics also preserves completed-cycle history and records assignment context for newer bid/order data.
Use the plugin’s supported workflows for bidding, completion, relisting, and order creation. Direct database writes bypass their side effects, locking, and notifications.