> For the complete documentation index, see [llms.txt](https://help.mimeeq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.mimeeq.com/commerce-and-integrations/woocommerce/custom-field-mappings.md).

# Custom Field Mappings

Map Mimeeq configuration data to WooCommerce product custom fields — fixed or dynamic values, with the automatic mimeeq prefix explained.

## Overview

Custom Field Mappings let you 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 fulfillment 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' job is simply to apply 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.

**Important:** 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 — it's not something you can turn 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

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

### A Fixed Value

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

* `United Kingdom`
* `true`
* `9401.61`

### A Value Based on the Configuration

Starting with `=`, referencing something from the customer's actual choices — for example, the code of whichever fabric they picked, or a calculated value like a width in centimeters. Refer to Mimeeq's documentation for the exact formula syntax available.

## Example

* The fabric's material code — you enter `material_code`, it's saved as `_mimeeq_material_code`
* Country of origin (fixed) — you enter `country_of_origin`, it's saved as `_mimeeq_country_of_origin`
* Whether this is a bespoke item — you enter `is_bespoke`, it's saved as `_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

* [Admin Settings](/commerce-and-integrations/woocommerce/admin-settings.md)
* [Add to Cart Methods](/commerce-and-integrations/woocommerce/add-to-cart.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.mimeeq.com/commerce-and-integrations/woocommerce/custom-field-mappings.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.