> 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).

# 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.

{% hint style="info" %}
**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.
{% endhint %}

```mermaid
flowchart LR
    A[Customer configuration in Mimeeq] --> B[Mapping rule in your Mimeeq account]
    B --> C[WooCommerce product custom field _mimeeq_name]
```

***

## 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.

{% hint style="warning" %}
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.
{% endhint %}

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:

{% tabs %}
{% tab title="Fixed value" %}
Plain text or a number, always the same regardless of what the customer picked:

* `United Kingdom`
* `true`
* `9401.61`
  {% endtab %}

{% tab title="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.
{% endtab %}
{% endtabs %}

***

## Example

<table><thead><tr><th width="61.0546875">#</th><th>Field</th><th>You enter</th><th>Saved as</th></tr></thead><tbody><tr><td>1</td><td>The fabric's material code</td><td><code>material_code</code></td><td><code>_mimeeq_material_code</code></td></tr><tr><td>2</td><td>Country of origin (fixed)</td><td><code>country_of_origin</code></td><td><code>_mimeeq_country_of_origin</code></td></tr><tr><td>3</td><td>Whether this is a bespoke item</td><td><code>is_bespoke</code></td><td><code>_mimeeq_is_bespoke</code></td></tr></tbody></table>

***

## 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

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>WooCommerce Admin Settings</strong></td><td>Configure API, cart, product naming and sync settings.</td><td><a href="/commerce-and-integrations/woocommerce/admin-settings.md">WooCommerce Admin Settings</a></td></tr><tr><td><strong>WooCommerce Add to Cart Methods</strong></td><td>Turn configurations into cart items, bundles or modular products.</td><td><a href="/commerce-and-integrations/woocommerce/add-to-cart.md">WooCommerce Add to Cart Methods</a></td></tr><tr><td><strong>WooCommerce Discount Codes</strong></td><td>Apply WooCommerce coupons to configured products and bundles.</td><td><a href="/commerce-and-integrations/woocommerce/discount-codes.md">WooCommerce Discount Codes</a></td></tr></tbody></table>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.