Mapping Reviews

Review and confirm how columns from your uploaded files map to product fields in MerchantOps.

Understanding and configuring column mappings for accurate data extraction.

What is Column Mapping?

When you upload a document, MerchantOps needs to understand which columns in your file correspond to which product fields. Column mapping is the process of associating source columns (like "Item Name" or "MSRP") with target fields (like "Product Name" or "Price").

Our AI automatically detects likely mappings, but you can:

Review and confirm auto-detected mappings
Manually adjust incorrect mappings
Skip columns you don't need
Save mappings for reuse with similar files

When is Mapping Review Needed?

Not all uploads require manual mapping review. The system may request review when:

It's the first time processing files from this source
Column names don't match known patterns
Multiple columns could map to the same field
Critical fields (like product name) couldn't be auto-detected

Documents with status mapping_required need your review before processing can continue.

The Mapping Review Interface

When a document requires mapping review:

Navigate to the document in Lakehouse → Documents
Click the "Review Mappings" button
The mapping interface shows all detected columns

Interface Elements

Element	Description
Source Column	The column name from your uploaded file
Sample Values	Example data from the first few rows
Target Field	The MerchantOps product field to map to
Confidence	AI confidence level in the suggested mapping
Status	Confirmed, pending review, or skipped

Available Target Fields

Source columns can be mapped to these product fields:

Core Fields

Field	Description	Required
`vendor_id`	Vendor Style Id	Yes
`name`	Product name/title	Yes
`brand`	Brand or manufacturer name	No
`description`	Product description text	No
`features`	Features of a product (bulleted list)	No
`price`	Product price	No
`tagline`	Short Description of the product	No
`image_url`	Main product image URL	No

Custom Attributes

In addition to core fields, you can map columns to any attribute defined in your Attribute Dictionary. This allows you to import attribute values directly from your source files.

Reviewing Mappings

For each column, you can:

Confirm a Mapping

If the auto-detected mapping is correct, click the checkmark to confirm it. Confirmed mappings show a green indicator.

Change a Mapping

Click on the target field dropdown
Select the correct field from the list
The mapping updates immediately

Confirm All

Click "Confirm Mappings" to accept the current configuration. This triggers the document to continue processing with your approved mappings.

Reject/Confirm

If the auto-detection is significantly wrong, click "Reject Mappings" to clear all suggestions and start fresh with manual mapping.

Reprocessing After Changes

If you change mappings after a document has been processed:

Save your updated mappings
Click "Reprocess Document"
The system re-extracts products using the new mapping

Note:Reprocessing creates new lakehouse products. If you've already promoted products to the Catalog, those remain unchanged.

Saving Mapping Templates

For recurring file formats (like monthly vendor exports), you can save mapping configurations as templates:

Configure the mapping for your first file
Click "Save as Template"
Name your template (e.g., "Acme Vendor Export")
Future uploads can use this template automatically

To apply a saved template:

Open the mapping review for a new document
Click "Load Template"
Select the appropriate template
Review and confirm the applied mappings

Best Practices

Column Naming

Use clear names:Columns like "Product Name" map better than "Col_A"
Be consistent: Use the same column names across files from the same source
Include units:"Weight (oz)" is clearer than just "Weight"

Review Strategy

Check sample values: Verify the data matches the expected field type
Review low-confidence mappings: Pay extra attention to mappings with low AI confidence
Map attributes early: Configure attribute mappings in the first file to set the pattern

Next Steps

After confirming your mappings:

Review extracted products for accuracy
Upload more documents using saved templates
Set up attributes if you need more fields to map to