Existing integration
Legacy XML / CSV
Keep your current identifiers and data structure.
Partner Tele.com · integration centre
The current Partner Tele.com product offer can be provided to registered customers as a regularly generated XML or CSV file.
See available formats02
Quick selection
The key questions are whether your integration is already active and how much data it needs.
Existing integration
Keep your current identifiers and data structure.
Frequent updates
Retrieve prices and stock at shorter intervals.
New full integration
Get full catalogue data, including compatibility.
Light and Fat formats use different IDs from Legacy files. Do not replace the format in an active integration without mapping the products accordingly.
03
Overview
Data scope and update frequency in one place.
| Format | Scope | Identifiers | Refresh | Best use |
|---|---|---|---|---|
| Legacy XML | Full catalogue data | Existing IDs | Once or twice daily | Active XML integrations implemented up to 2024, including Baselinker, RedCart and Sky-Shop |
| Legacy CSV | Full catalogue data | Existing IDs | Once or twice daily | Custom CSV integrations implemented up to 2024 |
| XML Light | Price, stock and EAN | New IDs | More often, by arrangement | Frequent price and stock updates in an XML integration |
| XML Fat | Full data + compatibility | New IDs | Once or twice daily | New, independently implemented integrations requiring the full catalogue |
| CSV Light | Price, stock and EAN | New IDs | More often, by arrangement | Frequent price and stock updates in a simple CSV file |
Legacy and Fat files are updated once or twice per day (every 1440 or 720 minutes). Shorter intervals are available for Light files and are agreed individually with your sales representative.
Data scope
The availability of individual fields depends on the selected format. The displayed stock level has an informational limit of 200 units.
04
Technical documentation
Expand a format to see its description and example structure.
Preserves the existing structure and product identifiers, maintaining compatibility with current implementations.
<produkty>
<produkt id="35402">
<nazwy>
<nazwa jezyk="it"><![CDATA[Futerał CHARMING 2]]></nazwa>
</nazwy>
<kategoria_tree>KALAID-CHARII</kategoria_tree>
<zdjecia>...</zdjecia>
<cena>
<cena_netto waluta="EUR" wartosc="2.96" />
</cena>
<dostepnosc>1</dostepnosc>
<producent><![CDATA[OEM]]></producent>
<producent_gpsr>...</producent_gpsr>
<podmiot_odpowiedzialny_gpsr>...</podmiot_odpowiedzialny_gpsr>
</produkt>
</produkty>A compatibility format for customers using previously implemented CSV solutions. Fields are separated with the ^ character.
product_id^product name^product description^multilevel category^category_code^image code^net_price^accessibility^ean^producer^nett srp price^producer gpsr^responsible entity gpsrA lightweight file intended for frequent downloads. It contains only the basic data needed to update an offer.
<produkty>
<produkt id="235810">
<ean><![CDATA[5903396077494]]></ean>
<cena>
<cena_netto waluta="PLN" wartosc="23.36" />
</cena>
<dostepnosc>30</dostepnosc>
</produkt>
</produkty>The most extensive format. It includes catalogue data and brand–model relations. It is not a drop-in replacement for Legacy in an active integration.
<produkty>
<produkt id="270434">
<nazwy>...</nazwy>
<opisy>...</opisy>
<zdjecia>...</zdjecia>
<cena>...</cena>
<ean><![CDATA[5901737919854]]></ean>
<dostepnosc>200</dostepnosc>
<marka_model>
<model marka="Apple" model="iPhone SE 2022" />
<model marka="Apple" model="iPhone 8" />
</marka_model>
<producent_gpsr>...</producent_gpsr>
</produkt>
</produkty>A minimal file for quick updates. Fields are separated with the ^ character.
product_id^ean^net_price^accessibilityGPSR
Download the current table with information required under the GPSR regulation.