> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gocrisp.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Space Planning Upload connector
> Configure how planogram and assignment files are interpreted when uploaded into Crisp.
The **Space Planning Upload** connector defines how planogram data and assignment files are interpreted when they are uploaded into Crisp. Together with the [Planogram Upload](/space-planning-ingestion/planogram-upload) tile, it forms the **Space Planning Ingestion** process — the connector controls how uploads are processed, and the Planogram Upload tile is where files are actually submitted.
This page configures **how uploads are processed**. Files are not uploaded from this screen. To upload files, see [Planogram Upload](/space-planning-ingestion/planogram-upload).
## What the connector does
The Space Planning Upload connector supports two types of inbound data:
* **Planogram data** from PSA files
* **Planogram and store assignments** from Excel or CSV files
The connector configuration determines how those files are processed when they are uploaded, including:
* Optional **categorizations** used to classify planograms
* The **retailer configuration**, which maps columns from assignment files
* Optional **validation rules** applied during file ingestion
## Categorizations
Categorizations define how planograms are grouped when they are uploaded through this connector. These values are selected during file upload and become attributes that can be used for filtering and analysis in dashboards.
When uploading data, users first select the **Retailer**, and then select values for each categorization defined in the connector. Categorizations should reflect how your organization groups planograms for analysis. A common example is a **category reset**, where multiple planograms are updated together for a specific retailer and time period.
Typical categorizations include:
* **Reset Date** or **Year**
* **Category**
* **Merchandising Program**
* **Test vs Production**
Up to **six categorizations** can be defined for a connector.
### Uniqueness behavior
Categorizations also determine whether an uploaded planogram is considered **new** or an **update to an existing planogram**.
If two planograms are uploaded with the same **planogram uniqueness settings** within the same categorization values, they are considered the **same planogram**, and the newly uploaded planogram overwrites the existing one. Choose categorizations carefully so they reflect the way your resets are organized and tracked.
For example:
| Categorization | Example value |
| -------------- | ------------- |
| Year | 2025 |
| Category | Frozen Pizza |
This allows planograms from different resets to coexist while still allowing updates to replace earlier versions within the same reset group.
## Retailer configuration
The **retailer configuration file** defines how assignment files are interpreted when they are uploaded through this connector. Each row in the file represents a retailer configuration. When uploading assignment files, users select the retailer, and the system uses the corresponding configuration to determine how the file should be processed.
The configuration controls:
* Which fields uniquely identify a **planogram**
* Which columns define **planogram assignments**
* Which columns define **store assignments**
* Any **validation rules** that should be applied during upload
The retailer configuration is managed using a **CSV file**.
Click **Download** to export the current retailer configuration file.
Open the CSV in Excel and update the rows for each retailer.
Click **Upload** to apply the updated configuration.
## Retailer configuration structure
The configuration file is organized into groups of columns that define different parts of the upload logic.
### Retailer information
These columns identify the retailer configuration.
| Column | Description |
| ------------------------------ | ---------------------------------------------------------------------------- |
| Retailer | The name of the retailer used when selecting the configuration during upload |
| Linked connector configuration | Optional reference to another configuration |
### Planogram key fields
These fields define how a planogram is uniquely identified in the uploaded data. Examples include:
* Planogram name
* ID
* Category
* Size
Multiple key fields can be defined to ensure that the correct planogram is identified when processing assignment files.
### Planogram assignment columns
These columns define which fields in the uploaded Excel file describe **planogram assignments**. They are used to match data between the planogram and store assignment files.
These fields may represent:
* Planogram identifiers
* Category assignments
* Other planogram-level attributes
### Store assignment columns
These columns define how planograms are assigned to **stores or store groups**. They are used to match data between the planogram and store assignment files.
Examples include:
* Store ID
* Store cluster
* Region
* Banner
These mappings allow the system to determine which stores should receive each planogram.
### Validation rules
Validation rules allow uploaded files to be checked for common data issues before they are processed. Each rule includes:
| Field | Description |
| ------------------ | ----------------------------------- |
| Validation name | Name of the rule |
| Validation field | Field being validated |
| Validation type | Type of validation applied |
| Validation pattern | Pattern or rule used for validation |
Validation rules can help ensure that required fields are present or that values follow expected formats.
## Example retailer configuration
| Setting | Value |
| --------------------------- | ----------------------- |
| Retailer | Target |
| Planogram key fields | `space_planogram_Desc2` |
| Planogram assignment column | `space_planogram_Desc2` |
| Store assignment column | `StoreNumber` |
In this example, the system identifies planograms using **Desc 2 (Planogram)**, assigns planograms using the same column, and determines store assignments using the **Store Number** column.
## Next step
Once the connector is configured, you're ready to upload planograms and manage store assignments.
Upload planograms and manage store assignments using the Planogram Upload tile.