---
title: "Input Header mapping"
url: "https://knowledge.bigmile.eu/en/article/input-header-mapping"
language: "en"
last_updated: "2025-08-14T08:38:29.000Z"
---

# Input Header mapping

Users can now align their source system headers (e.g. Shipment\_ID instead of Consgnment\_ID) with our internal system names without altering their original files. This eliminates the need for manual  transformations of column names.

![Update custom names.gif](https://codaio.imgix.net/docs/Tu4x9TyYjX/blobs/bl-25PtpN70Y-/0f1a8c582c544039452f43a3ee83e9426dba924ae88782a4f478fc32ee18b7123948899acdae7c7281ea43d7239d2118e93dc66c0f19d8989cd68f35ae5fc84a4a6a271ffd6ba95fea2dbc28f21a2dcb9e3bc743befbe5bd98f2eea66ad239a6c30594e1?auto=format%2Ccompress&fit=max)

### How To Use:

1.  Navigate to the **Definitions page**.
2.  Locate the editable Input Column columns.
3.  Edit the desired field name (e.g. change "Customer Name" to "Client").
4.  Upload a file that uses your own headers.

### Behavior Rules:

-   One-to-One Mapping Enforcement:  
    If both the original header (customer\_name) and a renamed version (Client\_Name) exist in a single upload, the system will reject the file.  
    → Only one mapped name should be present in the input file.
-   Recognition during Upload:
    -   Mapped headers will be recognized just like original headers during data ingestion.
    -   Original headers are also still recognized
-   You can only edit **Input Column** values that exist in input files. Rows with category *Output* or *Measure* are not alterable*.*
-   Process API: No changes applied. API responses and requests retain original naming conventions from before.   
    → ⚠️ This is intentional to avoid breaking changes but should be noted for API consumers.
-   Please note that it is still necessary for the Excel file tabs to contain the BigMile definitions ‘Shipments’ and ‘Emission assets’.