WooCommerce Custom Field Mappings

Store extra configuration data on your WooCommerce products without code. Learn where mappings are set up, how values work and why fields get a prefix.

Custom field mappings carry extra information from a customer's configuration straight into a WooCommerce product's custom fields — without needing a developer to write any code for it.

For example: if a configuration includes a fabric choice, you could automatically store that fabric's material code on the resulting WooCommerce product, ready for your fulfilment team to see.

Where this is set up: the mapping rules themselves are configured in your Mimeeq account (in the product's configuration screen), not in WordPress. WordPress applies whatever mapping you've set up there onto the product it creates.

---

Where to find the setting in Mimeeq

1. Open the product in your Mimeeq account

2. Go to the Pricing and Codes tab

3. Find Add to Cart Configuration

4. Open Ecommerce Custom Field Mappings

For the exact screen and options, refer to Mimeeq's own help documentation, as it's part of the Mimeeq account rather than this plugin. Broadly, you'll be choosing:

• Integration type: select WordPress / WooCommerce

• Method: either one flat set of mappings for the whole configuration, or several independent mapping groups for more complex, multi-part configurations

---

What happens on the WordPress side

Whatever you map to WooCommerce Product Meta Field gets saved as a custom field on the product WooCommerce creates for that configuration.

Every field created this way is automatically made private (hidden from the WooCommerce order details view customers and staff normally see) and automatically gets a _mimeeq_ prefix added to its name. This happens no matter what you type as the field name — you can't turn it off.

So if you enter lead_time_days as the field name, it's actually stored as _mimeeq_lead_time_days.

This is intentional — it keeps these fields out of the way of your regular product data, while still being fully readable by any other tool, plugin or custom code that needs them.

---

Setting a value

There are two ways to fill in the value for a mapped field, both configured on the Mimeeq side:

Fixed value

Plain text or a number, always the same regardless of what the customer picked:

• United Kingdom

• true

• 9401.61

Value based on the configuration

Starts with = and references something from the customer's actual choices — for example, the code of whichever fabric they picked, or a calculated value like a width in centimetres.

Refer to Mimeeq's documentation for the exact formula syntax available.

---

Example

#	Field	You enter	Saved as
1	The fabric's material code	material_code	_mimeeq_material_code
2	Country of origin (fixed)	country_of_origin	_mimeeq_country_of_origin
3	Whether this is a bespoke item	is_bespoke	_mimeeq_is_bespoke

---

Reading these values later

If you (or a developer working on your site) need to retrieve one of these values — for a report, an export or a custom email — remember the _mimeeq_ prefix:

$product_id = $order_item->get_product_id();
$material_code = get_post_meta($product_id, '_mimeeq_material_code', true);

---

Related articles

WooCommerce Admin Settings

Configure API, cart, product naming and sync settings.

WooCommerce Add to Cart Methods

Turn configurations into cart items, bundles or modular products.

WooCommerce Discount Codes

Apply WooCommerce coupons to configured products and bundles.