irisOne QuickConnect:
Migration from Connected Retail to Partner Program

Purpose of this documentation

This documentation describes how a retailer can migrate from Connected Retail to the Partner Program via irisOne QuickConnect.

irisOne QuickConnect enables retailers to keep most of their existing Connected Retail integration and only adjust the target endpoints, add a few additional columns, and provide a daily full export.

For retailers that are already integrated with Connected Retail, this means:

• The existing FCI CSV structure for stock and price updates can largely be reused.
• The existing OEA structure for order events can largely be reused.
• The main technical change is that the target endpoints change to irisOne QuickConnect.
• The FCI file must be extended with a few additional columns.
• A full export must be sent daily.
• For larger files, the transfer should be done via SFTP to avoid the 10 MB limit of the HTTP endpoint.

Reference: existing Connected Retail interfaces

The existing integration is usually based on the following Connected Retail interfaces:

• Fashion Connector Importer / FCI:
  https://docs.partner-solutions.zalan.do/en/fci/getting-started.html

• Order Events API / OEA:
  https://docs.partner-solutions.zalan.do/en/oea/index.html

This document is intended as a migration guide for retailers that already use these interfaces and are now being connected to the Partner Program via irisOne QuickConnect.

Migration overview

Area	Current: Connected Retail	New: Partner Program via irisOne QuickConnect
Stock and price updates	FCI CSV to Connected Retail endpoint	FCI-compatible CSV to irisOne QuickConnect endpoint or SFTP
Orders / order events	OEA	OEA-compatible events via irisOne QuickConnect
CSV structure	Existing FCI columns	Existing FCI columns plus additional required fields and optional product attributes
Full export	Depending on the current integration	Required daily
Delta export	Possible	Optional in addition to the daily full export
Large files	HTTP limit must be considered	Use SFTP for larger files
Target system	Connected Retail	irisOne QuickConnect

1. Stock and price updates via FCI-compatible export

The retailer can generally continue using the existing FCI export. The file does not need to be rebuilt from scratch. It only needs to be extended with additional fields.

Existing FCI columns

The known FCI columns remain unchanged, especially:

Field	Description
store	Store or location ID
ean	EAN / GTIN of the article
price	Current selling price
retail_price	RRP / original selling price
quantity	Available quantity
article_number	Article number / SKU
product_number	Product or style number
product_name	Product name
article_color	Article color
article_size	Article size
store_article_location	Location of the article inside the store

These existing fields can be provided as before.

2. Additional required fields for irisOne QuickConnect

For processing via irisOne QuickConnect, the existing export must be extended with the following additional required fields.

New field	Value	Description
erp_ean	Copy value from ean	EAN from the ERP system. Can be identical to the existing ean.
erp_article_number	Copy value from article_number	Article number from the ERP system.
erp_store_article_location	Copy value from store_article_location	Store article location from the ERP system. Can be empty if no location is available.
classification	default	Classification. Can initially always be set to default.

The required information is usually already available in the existing FCI file. It only needs to be copied into the additional columns.

Example mapping:

erp_ean                    = ean
erp_article_number         = article_number
erp_store_article_location = store_article_location
classification             = default

3. Optional recommended product attributes

In addition to the required fields, further product attributes can be appended to the CSV file. These fields are optional, but they improve data quality.

Recommended optional fields:

Field	Description
brand	Brand
productGroup	Product group / category
brandModelNumber	Manufacturer model number
gender	Target gender, for example men, women, unisex
ageGroup	Age group, for example adult, kids
baseColor	Base color
manufacturerColor	Manufacturer color
season	Season, for example SS, HW
seasonYear	Season year
description	Product description
imageURL1	Image URL

These columns can simply be added at the end of the existing CSV file.

4. Full export and delta export

Daily full export

For irisOne QuickConnect, a complete export must be transferred daily.

Required filename pattern:

*_full_*.csv

The filename must contain _full_. The remaining parts of the filename are flexible.

Example:

import_full_yyyymmddhis.csv

A full export contains the complete stock for all relevant stores and articles.

Optional delta export

A delta export can additionally be transferred if the retailer already works with delta files or wants to send intraday changes.

Required filename pattern:

*_delta_*.csv

The filename must contain _delta_. The remaining parts of the filename are flexible.

Example:

import_delta_yyyymmddhis.csv

A delta export only contains changes since the last export, for example changed prices or stock quantities.

Important: The daily full export is still required even if delta exports are sent.

5. Transfer to irisOne QuickConnect

The files are no longer transferred to the existing Connected Retail endpoint. They are transferred to the target systems provided by irisOne QuickConnect.

Option A: HTTP endpoint

For smaller files, the export can be sent to the irisOne QuickConnect HTTP endpoint.

Important points:

• The existing Connected Retail endpoint is replaced by the irisOne QuickConnect endpoint.
• The CSV structure remains largely the same.
• The additional QuickConnect columns must be included.
• The HTTP upload has a file size limit of 10 MB.

Option B: SFTP

For larger retailers or larger export files, the transfer should be done via SFTP.

SFTP should be used especially when:

• the CSV file is larger than 10 MB,
• many stores or articles are transferred,
• daily full exports create larger file volumes,
• the existing system landscape already prefers file-based exports.

Files larger than 10 MB can be transferred via SFTP.

6. Example: Delta export

Filename example:

import_delta_yyyymmddhis.csv

Example content:

store;ean;price;retail_price;quantity;article_number;product_number;product_name;article_color;article_size;store_article_location;erp_ean;erp_article_number;erp_store_article_location;classification;brand;productGroup;brandModelNumber;gender;ageGroup;baseColor;manufacturerColor;season;seasonYear;description;imageURL1
1;0737427865676;99.90;115.90;2;132001006-40;132001006;HELSINKII;schwarz;40;;0737427865676;132001006-40;;default;Ecco;men > sneaker > low;050104/00101x;men;adult;schwarz;shaddow black;HW;HW2027;;
1;0737427865683;99.90;115.90;0;132001006-41;132001006;HELSINKII;schwarz;41;;0737427865683;132001006-41;;default;Ecco;men > sneaker > low;050104/00101x;men;adult;schwarz;shaddow black;HW;HW2028;;
2;0737427865676;99.90;115.90;1;132001006-40;132001006;HELSINKII;schwarz;40;;0737427865676;132001006-40;;default;Ecco;men > sneaker > low;050104/00101x;men;adult;schwarz;shaddow black;HW;HW2030;;

7. Example: Full export

Filename example:

import_full_yyyymmddhis.csv

Example content:

store;ean;price;retail_price;quantity;article_number;product_number;product_name;article_color;article_size;store_article_location;erp_ean;erp_article_number;erp_store_article_location;classification;brand;productGroup;brandModelNumber;gender;ageGroup;baseColor;manufacturerColor;season;seasonYear;description;imageURL1
1;0737427865669;99.90;115.90;1;132001006-39;132001006;HELSINKII;schwarz;39;;0737427865669;132001006-39;;default;Ecco;men > sneaker > low;050104/00101x;men;adult;schwarz;shaddow black;HW;HW2026;;
1;0737427865676;99.90;115.90;3;132001006-40;132001006;HELSINKII;schwarz;40;;0737427865676;132001006-40;;default;Ecco;men > sneaker > low;050104/00101x;men;adult;schwarz;shaddow black;HW;HW2027;;
1;0737427865683;99.90;115.90;1;132001006-41;132001006;HELSINKII;schwarz;41;;0737427865683;132001006-41;;default;Ecco;men > sneaker > low;050104/00101x;men;adult;schwarz;shaddow black;HW;HW2028;;
2;0737427865669;99.90;115.90;1;132001006-39;132001006;HELSINKII;schwarz;39;;0737427865669;132001006-39;;default;Ecco;men > sneaker > low;050104/00101x;men;adult;schwarz;shaddow black;HW;HW2029;;
2;0737427865676;99.90;115.90;0;132001006-40;132001006;HELSINKII;schwarz;40;;0737427865676;132001006-40;;default;Ecco;men > sneaker > low;050104/00101x;men;adult;schwarz;shaddow black;HW;HW2030;;
2;0737427865683;99.90;115.90;6;132001006-41;132001006;HELSINKII;schwarz;41;;0737427865683;132001006-41;;default;Ecco;men > sneaker > low;050104/00101x;men;adult;schwarz;shaddow black;HW;HW2031;;

8. Orders / OEA via irisOne QuickConnect

The existing OEA logic can continue to be used. The integration no longer runs directly through Connected Retail, but through irisOne QuickConnect.

The known order events remain largely the same for the retailer:

Event	Meaning
assigned	The order was assigned to a store.
fulfilled	The order or order item was fulfilled.
cancelled	The order or order item was cancelled.
returned	The order or order item was returned.

For retailers that want to keep their existing OEA integration, usually only the target endpoints and credentials need to be changed.

9. Alternative: full irisOne Order API

As an alternative to the OEA-compatible integration, the full irisOne API can be used.

It provides additional options, for example:

• processing orders directly in the retailer’s own system,
• actively reporting order statuses,
• retrieving additional order information,
• implementing more individual process logic.

OpenAPI documentation:
https://app.swaggerhub.com/apis-docs/irisOne/irisOne

IAM / API Keys:
https://app.swaggerhub.com/apis-docs/irisOne/IAM-Keys/1.0.0

10. Migration checklist

Step	Description	Done
1	Identify the existing FCI export
2	Add the required fields erp_ean, erp_article_number, erp_store_article_location, classification
3	Copy values from existing columns
4	Add optional recommended product attributes if available
5	Set up the daily full export
6	Keep or add optional delta exports if needed
7	Agree on HTTP upload or SFTP transfer
8	Use SFTP for files larger than 10 MB
9	Change the target endpoints to irisOne QuickConnect
10	Change OEA endpoints and credentials to irisOne QuickConnect
11	Transfer a test file and validate processing
12	Go live

Summary

The migration to the Partner Program is handled via irisOne QuickConnect. The retailer does not need to rebuild the existing Connected Retail integration from scratch.

The most important changes are:

• The retailer sends data to irisOne QuickConnect instead of the existing Connected Retail endpoints.
• The existing FCI CSV can be reused.
• Only a few additional required fields are needed.
• The additional required fields can be filled from existing FCI information.
• A full export must be provided daily.
• The full export filename must contain _full_; a delta export filename must contain _delta_.
• SFTP should be used for larger files to avoid the 10 MB limit of the HTTP endpoint.
• The OEA logic remains compatible and can continue to be used via irisOne QuickConnect.
• Alternatively, the full irisOne Order API can be integrated if more functionality is required.