Ecommerce Custom Field Mappings
Content
- Overview
- Where to Find Field Mapping Settings
- Setting Up Mappings
- Platform-Specific Field Types
- Practical Examples
- Validation and Error Prevention
Overview
Ecommerce Custom Fields Mappings allow you to pass additional product data — beyond the standard SKU and price — to your connected sales channel when a product or variant is created or added to cart. This lets you push configuration-specific metadata directly into Shopify products, Shopify variants, or WooCommerce product custom fields without any custom development.
When a customer configures and adds a product to cart, Mimeeq normally sends the SKU code and price to your ecommerce platform. With Custom Field Mappings, you can also send:
Platfrom | Field Type | What It Targets |
|---|---|---|
Shopify | Product Property | Standard Shopify product fields (vendor, barcode, tax code, etc.) |
Shopify | Product Metafield | Custom metadata stored on the Shopify product object |
Shopify | Variant Metafield | Custom metadata stored on a specific Shopify variant |
WordPress/WooCommerce | Product Metafield | Additional metadata attached to a WooCommerce product |
These mappings are evaluated at the time of product/variant creation and the values are written directly to the ecommerce platform record.
Where to Find Field Mapping Settings
- Open any product in the Product Admin
- Go to the Codes & Pricing tab
- Scroll down to the Add to Cart Configuration section
- Look for the Ecommerce Custom Fields Mappings collapsible panel
Setting Up Mappings
Step 1 — Select Your Method
At the top of Add to Cart Configuration, choose a Method. The method controls how configured products are sent to your sales channel, and it directly determines how field mappings are structured.
Method | How it works |
|---|---|
Single Product | The configured product is added to cart as a single item, with all components combined into one product. This is the simplest approach. |
Custom Defined Logic | Gives you three independent options that can be used separately or together: creating single variants, custom products, or bundles. This method supports more complex product structures. |
Step 2 — Select Your Integration Type
Once you've selected a method, set the Integration type:
Integration Type | Connects to |
|---|---|
Shopify | Mimeeq Shopify App |
WordPress | Mimeeq WordPress Plugin |
The available mapping types update automatically based on your selection.
Step 3 — Configure Your Field Mappings
How you configure field mappings depends on the method selected in Step 2.
If you selected Single Product
A single flat mappings table is available. Click Add row to add individual field mappings directly.
Each row has three fields:
Column | Description |
|---|---|
Type | The type of field on the ecommerce platform — see platform-specific options below |
Field / Key | The field name or identifier — format depends on the Type selected |
Value | The value to write to that field — can be a static value or a formula |
All mappings defined here are automatically applied to every product created via this configurator.
If you selected Custom Defined Logic
You can create one or more mapping groups, each containing its own set of field mappings. Groups can then be assigned to specific custom products and admin bundles.
Click Add mapping group to create a group. Each group:
- Has an optional Mapping Group Name for internal reference (not shown to customers)
- Contains one or more individual field mapping rows
- Can be added or removed as needed
Each row within a group has the same three fields as above: Type, Field / Key, and Value.
Platform-Specific Field Types
Shopify — Product Property
Maps to standard built-in Shopify product fields. Select from the predefined list:
Field Key | What It Sets in Shopify |
|---|---|
| Product vendor / manufacturer |
| Shopify product type |
| Product or variant barcode (EAN, UPC, ISBN) |
| Whether the product is taxable ( |
| Tax code for the product |
| Whether inventory is tracked ( |
| Whether shipping is required ( |
| ISO 3166-1 alpha-2 country code (e.g. |
| HS tariff code for international customs |
Shopify — Product Metafield & Variant Metafield
Maps to custom metadata stored on the Shopify product or variant object.
Key format: namespace.key
custom.lead_time
custom.sku_internal
myapp.product_category
Validation rules:
- Must contain exactly one dot (
.) separator - Namespace: 3–255 characters
- Key: 2–64 characters
WordPress (WooCommerce) — Product Metafield
Maps to WooCommerce product _meta fields.
Key format: snake_case
custom_sku
lead_time_days
product_origin
Validation rules:
- 1–255 characters
- Lowercase alphanumeric with underscores only
- Must match the pattern
lowercase_with_underscores
The Value Field
Static Values
Plain text or numbers written exactly as entered:
United Kingdom
true
GB
9401.61
Dynamic Formulas
Start the value with = to reference configuration data. Formulas can pull from:
- Option selections made by the customer during configuration
- Item Master data fields
- Mathematical calculations
Examples:
={fabric#code}
={frame_material#name}
={width_cm#value}
This means the value written to Shopify or WooCommerce can reflect exactly what the customer configured — for example, writing the selected material code as a searchable product metafield.
Practical Examples
Example 1 — Write a Material Code to a Shopify Variant Metafield
Store the selected fabric code in a Shopify variant metafield for use in order workflows.
Type | Field / Key | Value |
|---|---|---|
Variant Metafield | | |
Result: When a customer selects fabric LINEN_NATURAL and adds to cart, the Shopify variant record will include custom.fabric_code = LINEN_NATURAL.
Example 2 — Set Customs Data for Export Products
Apply HS code, country of origin, and tax code to every product created via this configurator.
Type | Field / Key | Value |
|---|---|---|
Product Property | | |
Product Property | | |
Product Property | | |
Example 3 — Pass Lead Time to WooCommerce
Write the lead time for the selected material to a WooCommerce custom field.
Type | Field / Key | Value |
|---|---|---|
Product Custom Field | | |
Each material option carries its own lead time value (e.g. 14 for standard, 28 for bespoke), which is passed through dynamically.
Example 4 — Tag Bespoke Variants with a Custom Metafield
Flag made-to-measure products using a combination of a static taxable value and a dynamic bespoke identifier.
Type | Field / Key | Value |
|---|---|---|
Product Property | | |
Variant Metafield | | |
Validation and Error Prevention
Rule | Detail |
|---|---|
Duplicate keys | Duplicate keys within the same mapping group are not allowed. An (already used) indicator appears and saving is blocked. |
Invalid Shopify metafield format | Keys must follow |
Invalid WordPress key format | Keys must be |
Shopify validation errors | If Shopify rejects a value (e.g. incorrect type or format), the product will not be created. These errors come from Shopify directly and must be corrected by the user. |
Related Articles
- Shopify Add to Cart Configuration Methods
- Shopify Latest Version Updates: Your Guide to New Features and Enhancements
- Custom Ecommerce Integration
Updated on: 16/03/2026
Thank you!
