1C unloading - a fundamental question?

Question

PHP

Good afternoon.
All the same, as it grows, tasks come for picking up new, unknown modules, into the principle of which, due to lack of experience, you stick not immediately.
For example, let's take any more or less tolerable CMS, in which the ability to synchronize goods from 1C to the site is sewn out of the box.
Of course, I read the class responsible for this connection, but there is too much of everything, I get confused along the way, again - experience.
So how does this process take place?
In my understanding, these are:
1) 1C connects via http (in my case, via FTP) and uploads template content, categories, products, price fields, etc. to the XML directory.
2) CMSs use these default fields, a predefined class where XML is parsed and the fields are matched - "take the <price> field and put it in the database at price"
3) On the side of the controller model, again in default , there is a standard selection of already loaded content in the database, and in the resulting array, we already get everything that was unloaded, and use it for joy.
Like, as I understand it.
But, apparently, there are also non-standard fields in 1C - product characteristics, several types of prices, and so on.
That is, in order for me to correctly accept this, I need to climb into the class, define a "box" for a new field, also create an additional field in the database in the store module, write everything down there, and, accordingly, everything else is already clear.
In a simplified form, in everyday pygmy language, is it possible to reduce this synchronous process to an ordinary simple parsing of the incoming XML?

Answer 1

it is more promising in terms of "offline" interaction to embed v8.1c.ru/edi/edi_app/enterprisedata support into your CMS , then integration with all modern 1c configurations will be the simplest.