Projektbeschreibung
It is necessary to synchronize 1C with the site, according to the following scenario:
The exchange of information should take place “realtime”, on the event, with the shortest possible time intervals.
Approximate call of goods 3600.
There is an old file for unloading goods from the site.
You need to think about the xml structure for upload files (you need to know the structure of upload files from 1C, and you need to form a structure for upload files from Opencard).
Fields that are needed for synchronization in the exchange of goods:
1. Name of goods (bilateral communication)
2. Article (bi-sided)
3. Supplier (bilateral)
4. Price (C 1 s in Opencart) (The first time the price will fraternize from opencart to 1 c)
5. Purchase price (from 1c to Opencart (the first time will be taken from opencart to 1c)
Fields required for order exchange (two-way communication):
1. Buyer Infa (bilateral)
2. Date (bilateral)
3. Names of goods (link by article) (bilateral)
4. Price (bilateral)
Project
The exchange of information should take place “realtime”, on the event, with the shortest possible time intervals.
Approximate call of goods 3600.
There is an old file for unloading goods from the site.
You need to think about the xml structure for upload files (you need to know the structure of upload files from 1C, and you need to form a structure for upload files from Opencard).
Fields that are needed for synchronization in the exchange of goods:
1. Name of goods (bilateral communication)
2. Article (bi-sided)
3. Supplier (bilateral)
4. Price (C 1 s in Opencart) (The first time the price will fraternize from opencart to 1 c)
5. Purchase price (from 1c to Opencart (the first time will be taken from opencart to 1c)
Fields required for order exchange (two-way communication):
1. Buyer Infa (bilateral)
2. Date (bilateral)
3. Names of goods (link by article) (bilateral)
4. Price (bilateral)
Project
Softwareentwicklung E-Geld
