Metal-cost estimates inside WooCommerce
An admin-only calculator for your product editor. Save weight, purity and markups alongside your products. Review an indicative gold or silver estimate before deciding what to charge.
Selling prices stay unchanged. The plugin never updates regular prices, sale prices, carts or checkout prices.
Ask about early accessEarly access. Classic WooCommerce editor, simple products, gold and silver in GBP.
A price refresh, without repricing
Synthetic example: 10 g of gold, 900 fineness, no percentage markup and a £15 fixed addition. The selling price is set separately by the shop owner.
| Refresh | Estimate | Selling price |
|---|---|---|
| £80/g | £735.00 | £895.00 |
| £88/g | £807.00 | £895.00 |
| Fails | £807.00 | £895.00 |
A failed refresh keeps the last good observation and its timestamp. Refresh status shows the failure; the estimate continues to use the saved price. With no saved price, no real estimate is available.
From product inputs to an estimate
Install the ZIP
Upload and activate the plugin with WooCommerce active. Start in synthetic mode to try it without an API key.
Save product inputs
Open a simple product. Choose metal, weight and unit, fineness, percentage markup and a fixed addition. Update the product to save them.
Preview the estimate
Use the metal-cost calculator in the product editor. Previewing does not save inputs or change the product’s selling price.
Review refresh status
Connect Bullion API when ready. Check the last successful refresh, saved observation, next run and any failed attempts.
Configure your connection
Open WooCommerce → Bullion API connection as an administrator.
- Enter your API key in the connection settings and select real mode. The key stays on your WordPress server; it is never sent to the shopper’s browser.
- Enable hourly refresh and choose gold, silver or both. Background refresh is off on a new installation.
- Make sure your host runs WordPress cron. The plugin schedules the refresh; your host must execute it. The status page flags overdue runs.
Failed requests retain the last good price. Successful refreshes update the cached observation used for estimates. Neither changes your selling prices.