OddPixel PC Configurator
OddPixel PC Configurator

OddPixel PC Configurator

0/5 (0 ratings) — active installs Updated Nov 7, 2026
Interactive PC configurator with eight core components, live pricing and a configuration summary.

Interactive PC configurator with eight core components, live pricing and a configuration summary.

Let your customers build a PC directly in your WooCommerce store.

OddPixel PC Configurator turns your existing WooCommerce simple products into an interactive PC builder. Customers choose components, view estimated pricing, and see compatibility warnings. You keep WooCommerce in charge of prices, taxes, stock and checkout.

What customers can do

  • Build a PC – Choose CPU, cooler, motherboard, RAM, GPU, storage, case and power supply, plus extras.
  • See the estimated price – Use the prices of real products already available in your store.
  • Understand compatibility – Get clear warnings about known conflicts and missing technical information.
  • Request a quote – Send a selected configuration to the merchant for follow-up.

What merchants can manage

  • Use existing products – WooCommerce still handles images, prices, tax, stock and checkout.
  • Keep PC components together – Group selected components into the cart and order.
  • Review configurations – Perform a manual technical review before preparing or shipping a PC.
  • Optional AI assistance – Request specification suggestions with your own provider credentials; review them before saving.

Compatibility checks

Checks include CPU sockets, DDR generations, form factors, clearances, storage interfaces and estimated power, when product specifications are available.

These checks are guidance, not a hardware certification. BIOS support, manufacturer QVL lists, cooling capacity, connectors and physical assembly still require professional verification.

Free edition and requirements

  • Insert the configurator on a WordPress page using [wp_pc_builder].
  • Use WooCommerce simple products; variable products and third-party bundles are not supported.
  • The core free features work without a subscription, license activation or external AI service.
  • HPOS and Cart/Checkout Blocks compatibility is not formally declared pending further validation.
  • Includes English text and French, Spanish and German catalogs; translations are not fully certified.
  • A separate optional Pro extension may be available; Free features are not license-gated.

Before accepting real orders: test on a staging store. See External services and Privacy below.

External services

No license service or plugin-vendor telemetry is required for the core configurator. Optional AI providers are configured by the store operator with their own credentials and are not contacted for enrichment automatically.

When a merchant explicitly requests AI analysis, the WordPress server sends the selected product name, SKU, manually supplied technical text and the extraction instructions to the chosen provider. A separate manual connection check sends an authenticated service/model request without product text. The provider receives the applicable API key or local gateway token in the request header. Review product data for personal information before enabling external AI; do not assume external processing stays inside the EU. Provider data handling, rate limits, billing and terms are governed by that provider.

  • GroqCloud / Groq API: api.groq.com (AI text analysis and model access check). Service/legal notices: https://console.groq.com/docs/legal ; privacy: https://groq.com/privacy-policy .
  • Google Gemini / AI Studio: generativelanguage.googleapis.com (AI text analysis and model access check). Gemini API terms: https://ai.google.dev/gemini-api/terms ; Google privacy: https://policies.google.com/privacy .
  • OpenRouter: openrouter.ai (AI text analysis and account access check). Terms: https://openrouter.ai/terms ; privacy: https://openrouter.ai/privacy . OpenRouter may route the request to another model provider, whose terms and data handling should also be checked.
  • Ollama / LM Studio: configured local OpenAI-compatible endpoint, by default loopback on the WordPress server, not on the merchant’s browser or own computer. An explicitly allowlisted remote HTTPS gateway may be used by a server administrator. A local installation does not require sending technical text to the above cloud providers, but a remote gateway may transfer it outside the WordPress server.

These third parties are optional. There is no AI provider key shipped with the plugin. Merchants should consult each provider’s terms and privacy policy before enabling a connection.

Privacy

Quote submission requires a consent checkbox. The saved quote contains customer-supplied name, email, selected products, estimate and workflow details; the plugin does not currently save a separate consent audit record or a timestamp of the checkbox. Quote records are stored privately in WordPress and may generate a notification email to the merchant; privacy export and erasure hooks are provided. The merchant is responsible for explaining the lawful basis, email routing, retention policy and third-party service use to customers.

To discourage quote spam, rate-limit markers derived from keyed hashes of visitor IP addresses and email combinations are stored in WordPress options; raw IP addresses are not intentionally stored by this rate limiter. These markers are cleaned up opportunistically when new quote requests are accepted and may remain longer on inactive sites. Quote retention is controlled by the merchant; when no retention period is explicitly chosen, no automatic expiration is assumed. Product and order records remain subject to WooCommerce’s own retention and privacy settings. API credentials are stored server-side; they are not intended to be exposed to storefront visitors. Avoid placing customer personal information in product technical descriptions sent to AI providers.

Hiding the missing-WooCommerce notice stores a dismissal preference in the current administrator’s WordPress user metadata, scoped to the current site. It is not sent to any external service.

No storefront user data is intentionally transmitted to the plugin author by default.