Data formats in GC.Platform
It is possible to integrate price and product-availability data from CSV files. You can prepare such files yourself — for example, your ERP system can probably be configured to produce them — or prepare them manually in applications like Excel.
Files that can be imported:
GC.CART — erp_products.csv, prices.csv, availability.csv, profiles_prices.csv, profiles_customers.csv
GC.MDM — articles.csv, articles_cross.csv, files.zip, criteria.csv
GC.CART — CSV file formats for exchanging ERP data
Info
Files with _sync delete all past data, leaving only the data from the file available to users — e.g. prices_sync.csv (full-sync type). Files without _sync compare against past data and add or change it, but do not delete data that is not in the file — e.g. prices.csv (upsert type).
erp_products.csv / erp_products_sync.csv
Links TECDOC articles to customer products. It is very important to maintain the exact file structure: proper placement of semicolons, and keeping the first line (header) unchanged. Also make sure the file is named exactly erp_products.csv.
Format:
ARTICLE_ERP_ID;ERP_NUMBER;NUMBER;MANUFACTURER;NAME;CORE_ERP_ID
- ERP_NUMBER — the number of a customer product; it is the TECDOC equivalent of NUMBER.
- MANUFACTURER — the name of a manufacturer in TECDOC.
Data example:
ARTICLE_ERP_ID;ERP_NUMBER;NUMBER;MANUFACTURER;NAME;CORE_ERP_ID
BOS0123325012;0 123 325 012;0 123 325 012;BOSCH;Oil filter
BOS0204318582;0 204 318 582;0 204 318 582;BOSCH;Brake pads
TRWGDB1330;GDB1330;GDB1330;TRW;Brake pads
DTX1026R;DTX1026R;DTX1026R;DAXTONE;Common rail injector;COREDTX1026R
Download erp_products.csv example file
prices.csv / prices_sync.csv — prices and ERP key matching
Format:
ARTICLE_ERP_ID;PRICE_TYPE;PRICE;VAT;CURRENCY
An empty Price type is the base price for the article.
Warning
The separator in prices must be . (a dot), not , (a comma).
Data example:
ARTICLE_ERP_ID;PRICE_TYPE;PRICE;VAT;CURRENCY
242054;;178.23;20;EUR
242054;;44.50;20;EUR
A6845F;;200.00;20;EUR
A6845F;;50.00;20;EUR
Download prices.csv example file
availability.csv / availability_sync.csv — product availability
Format:
ARTICLE_ERP_ID;BRANCH;QUANTITY;BRANCH_TYPE
The BRANCH field contains the branch ID. The description that the GC.CATALOG user sees can be set additionally in GC.CART.
Data example:
ARTICLE_ERP_ID;BRANCH;QUANTITY;BRANCH_TYPE
242054;S01;5;
A6845F;S01;17;
242054;S02;1;
A6845F;S02;3;
For non-GC.CATALOG from Inter Cars S.A. clients, the BRANCH field can also contain three specific constants: GREEN, YELLOW, ORANGE. They are used to show colours in GC.CATALOG when displaying product availability on the main product list. From a business perspective, these colours can convey information to the user — e.g. GREEN = available today, YELLOW = available tomorrow — not only the number of goods in stock.
Data example:
ARTICLE_ERP_ID;BRANCH;QUANTITY;BRANCH_TYPE
242054;S01;5;
A6845F;S01;17;
242054;S02;1;
A6845F;S02;3;
242054;S03;4;
A6845F;S03;20;
242054;S04;99;
A6845F;S05;15;
Download availability.csv example file
profiles_prices.csv / profiles_prices_sync.csv
Lets you define all final prices of articles for all the different price profiles.
Format:
PROFILE_NAME;ARTICLE_ERP_ID;PRICE;CURRENCY;VAT
Data example:
PROFILE_NAME;ARTICLE_ERP_ID;PRICE;CURRENCY;VAT
PROFILE_01;242054;45.50;EUR;20
PROFILE_02;A6845F;180.50;EUR;20
PROFILE_03;242054;50;EUR;20
PROFILE_04;A6845F;200;EUR;20
PROFILE_05;242054;63.25;EUR;20
PROFILE_06;A6845F;250;EUR;20
Download profiles_prices.csv example file
profiles_customers.csv / profiles_customers_sync.csv
Matches particular users with particular price profiles.
Format:
PROFILE_NAME;CUSTOMER_ID
CUSTOMER_ID is the same field as "Number in ERP" in GC.CART.
Data example:
PROFILE_NAME;CUSTOMER_ID
PROFILE_01;208687
PROFILE_02;121213
PROFILE_03;PL-5481111
PROFILE_04;993234
Importing new price profiles does not require sending the profiles_customers.csv file. If you want to replace all relationships between users and price profiles, upload a new profiles_customers_sync.csv file — this removes all previous relationships, and only the relationships from the new file remain.
Download profiles_customers.csv example file
GC.MDM — file formats for importing data
ARTICLES.CSV — importing articles to GC.MDM
Format:
CODE;NUMBER;MANUFACTURER_ID;MANUFACTURER;NAME;DESCRIPTION;GROUP_ID;GROUP;USAGE_ID;USAGE;IMAGES;STATUS
Where:
- CODE — GC.MDM article ID (optional)
- NUMBER — GC.MDM article number
- MANUFACTURER_ID — GC.MDM manufacturer ID (optional if MANUFACTURER is present)
- MANUFACTURER — GC.MDM manufacturer name (optional if MANUFACTURER_ID is present)
- NAME — GC.MDM own product name (optional)
- DESCRIPTION — GC.MDM own short description (optional)
- GROUP_ID — GC.MDM group ID (optional)
- GROUP_NAME — GC.MDM group name (optional)
- USAGE_ID — GC.MDM usage ID (optional)
- USAGE — GC.MDM usage name (optional)
- IMAGES — GC.MDM list of image paths (optional)
- STATUS — GC.MDM product status
Data example:
;04.331ALU;;MARIX;;TŁUMIK MARIX 04.331ALU KOŃCOWY CITROEN C8, PEUGEOT 807 02-06;;;;;;A
;17.638ALU;;MARIX;;TŁUMIK MARIX 17.638ALU KOŃCOWY OPEL ZAFIRA B;;;;;;A
;17.386ALU;;MARIX;;TŁUMIK MARIX 17.386ALU ŚRODKOWY OPEL CORSA C;;;;;;A
Download ARTICLES.CSV example file
ARTICLES_CROSSED.CSV — importing cross-references and other linked articles to GC.MDM
Format:
TYPE;CODE;CODE_2;NUMBER;NUMBER_2;MANUFACTURER;MANUFACTURER_2;QUANTITY;STATUS
Where:
- TYPE — cross-reference type
- CODE — GC.MDM article ID (optional if the pair NUMBER + MANUFACTURER is present)
- CODE_2 — cross-reference article ID (optional if the pair NUMBER_2 + MANUFACTURER_2 is present)
- NUMBER — GC.MDM article number
- NUMBER_2 — cross-reference GC.MDM article number
- MANUFACTURER — GC.MDM manufacturer name
- MANUFACTURER_2 — cross-reference GC.MDM manufacturer name
- QUANTITY — leave empty
- STATUS — leave empty
files.zip — import of files linked to products
You can also import files linked with particular products, such as images. In this case, all files must be compressed and put into a single files.zip file.
The file structure should comply with the following format:
<MANUFACTURER_NAME>_<NUMBER>_<SORT_NUMBER>.<EXTENSION>
For example: TRW_GDB1330_1.jpg
Importing article criteria to GC.MDM with use of GC.DASHBOARD
When you need to assign technical criteria to a large number of articles at once, you can prepare a CRITERIA.CSV file and import it via GC.DASHBOARD.
CRITERIA.CSV file format
CODE;NUMBER;MANUFACTURER;MANUFACTURER_ID;GROUP_ID;CRITERION_KEY;CRITERION_VALUE;CRITERION_VALUE_LANG;STATUS
Where:
CODE— GC.MDM article ID (optional if NUMBER + MANUFACTURER is present)NUMBER— GC.MDM article number (optional if CODE is present)MANUFACTURER— GC.MDM manufacturer name (optional if MANUFACTURER_ID is present)MANUFACTURER_ID— GC.MDM manufacturer ID (optional if MANUFACTURER is present)GROUP_ID— article group ID in GC.MDM — the GRU code of the group the criterion belongs to (required)CRITERION_KEY— criterion key in GC.MDM — the KRY code of the criterion (required)CRITERION_VALUE— the value of the criterion for this article (required)CRITERION_VALUE_LANG— language code of the criterion value (only required if the criterion is translatable)STATUS— GC.MDM criterion status
Warning
Closed-list values must already exist. If a criterion uses a closed list of values (e.g. Tyre Type: All Season Tyres / Summer Tyres / Winter Tyres / Off-road tyres), the value must first be created manually in GC.MDM under Criteria for article groups. Only after the value exists in the list can it be used in a CRITERIA.CSV import.