Skip to main content

Project Fields

Overview​

Project Fields are the data standardization layer of 42feeds. They allow you to define a consistent internal schema that normalizes product data from different sources — regardless of how each supplier or system names their columns.

Imported feed columns are mapped to Project Fields, which then act as the single source of truth for transformation rules, item merging, and export templates.

The Mapping Flow​

Import Columns  →  Project Fields  →  Export Templates
(CSV / Feed Headers)   (Your Schema)   (Channel Fields)

Creating Project Fields​

Project Fields can be created in two ways.

Automatic Detection​

When you import a feed, all detected column names are automatically registered as Project Fields. You can then map or normalize them as needed.

Manual Creation​

You can manually create Project Fields at any time, for example:

  • sku
  • price
  • title
  • stock_quantity

Field Mappings​

Field mappings connect source columns from each feed to your standardized Project Fields.

Example​

Feed SourceOriginal ColumnProject Field
Supplier A CSVTitletitle
Supplier B XMLproduct_nametitle
Internal Feeditem_titletitle

All title values now flow into the same Project Field, regardless of source naming.

Auto-Mapping​

42feeds includes intelligent auto-mapping to speed up setup:

  • Exact matching of normalized names
  • Similarity matching for close variations
  • Predefined synonyms for common fields

Each suggestion includes a confidence indicator so you can quickly review and confirm mappings.

Using Project Fields in Exports​

When generating an export, 42feeds:

  1. Resolves channel fields via Project Fields
  2. Retrieves values from mapped source columns
  3. Applies transformation rules
  4. Outputs the final channel-specific file

Exports are fully decoupled from raw source column names.

Merge Key Field​

Overview​

The Merge Key Field is a Project Field used as the unique identifier for matching items across multiple feeds. It enables 42feeds to merge data into unified product records.

Why Use a Merge Key?​

Common use cases include:

  • Combining product and pricing feeds
  • Merging inventory updates
  • Enriching data from multiple suppliers
  • Consolidating variants

Setting a Merge Key​

To configure a merge key:

  1. Open Project Fields
  2. Locate the Merge Key Field section
  3. Select a Project Field
  4. Suggested identifiers are highlighted automatically

Common Merge Key Patterns​

The system recognizes and suggests:

  • id
  • product_id
  • sku
  • ean
  • gtin
  • upc
  • item_id
  • asin

Explicit configuration is recommended for reliable merging.

Auto-Detection Mode​

If no merge key is set, 42feeds attempts to auto-detect one using common identifier patterns. This works for simple setups but may be unreliable for complex projects.

How Merging Works​

When multiple feeds exist:

  1. Items are grouped by merge key value
  2. Fields are merged into a single record
  3. Missing values are filled from other feeds
  4. Existing values are never overwritten

Example​

FeedSKUTitlePriceStock
Products.csvABC123Widget29.99
Inventory.csvABC123150

Merged result:

{
  "sku": "ABC123",
  "title": "Widget",
  "price": "29.99",
  "stock": "150"
}

Field Source Tracking​

For each merged item, 42feeds tracks which feed each field value originated from. This allows you to:

  • Debug data quality issues
  • Understand data provenance
  • Identify responsible data sources

Source information is visible in the Items detail view.

Merge Priority Rules​

If multiple feeds provide values for the same field:

  • The first non-empty value wins
  • Only empty or missing fields are filled
  • Feed processing order matters

Item Diagnostics​

On the Items page you can:

  • Inspect merged items
  • Trace field values back to source feeds
  • Identify unmatched items
  • Search by merge key value

Items without a valid merge key appear as separate entries with generated identifiers.

Best Practices​

  1. Use stable identifiers (SKU over product name)
  2. Ensure all feeds populate the merge key
  3. Normalize formats before import
  4. Monitor unmatched items
  5. Set the merge key early in the project lifecycle
  • Field Mapping
  • Transformation Rules
  • Items View
  • Exports