How and who uploads goods to the online store?

Question

Online shopping

Hello!
I am doing a project (online store) for a portfolio on React. I want to know how the owners will generally upload product lists to their store? I understand that from the front-end side, you need to import arrays from JSON, map them, etc., but, let's say: a front-end developer handed over his work on an online store to a customer. How then will the owner fill the store with new goods? What specialists are involved in this and how does the process work?
And, most importantly: how can the front-end developer adapt his work as much as possible to the future use of the store by the owner?

Answer 1

In good stores, the product card is filled in manually, because. all of a sudden, people are watching her. In ugly stores, unloading from 1C is in progress, so there the hell is going on in all fields.
For example, compare Tiffany and Amazon stores. In the first beautiful pages of goods, pictures, human description. In the second ugly text without formatting.
Stock balances are synchronized by SKU or other unique product identifier.
How to do it right:
1. Initial bulk loading is done from any available file - csv, xls, xml, json, etc. These uploaded products receive the status of invisible on the site.
2. Absolutely all goods are passed and checked manually. Photos, videos, a human description are necessarily added to them. For technical goods, a specification, datasheets, drawings, diagrams, instructions, etc. are added. The more information, the better. This is what will lead users to you from search engines, social. networks and word of mouth. All self-created content must have persistent watermarks so that competitors do not steal it.
If you have a million positions and have sales experience, select the 1000 top sellers and fill it in first. This will increase your sales even more.
The React store must be made using SSR or you will have bad organic traffic.
> how can the front-end developer adapt his work as much as possible to the future use of the store by the owner?
Answer the question - how to bring the user to the site and make him buy the product. From and to.
In fact, everything depends on the product itself, the price, potential buyers and the design of the resource.
If you make a very good site, fast, beautiful, reliable and sell toilet paper on it for 1000 rubles per roll, then there will be few sales. But as soon as you put a price on it comparable to the price of competitors, then after a while there will be problems of scaling the business.
Do it right and everything will be fine.

Answer 2

Everything that is more than 1k positions needs to be done on csv
But there are options when they don’t think with their heads and then xml, json, excel 10GB each appear
The task in principle has little to do with the frontend

Answer 3

In large ones, export is done from internal accounting systems, 1s, my warehouse, etc.
In small ones, it is filled in by hand in the admin panel, sometimes a content manager is hired to fill it out.
The front-end developer does not interact with customers at all, because they need the whole site, sometimes also with marketing, promotion and a bunch of other things.
And how to connect the front and back is usually decided within the team.

Answer 4

Example as in the project I'm working on:
1) 1C creates a file in XML format. Then it compresses to zip
2) The file is uploaded to the S3 storage via API
3) The site regularly scans (by cron) this storage, when the file with the product appears - it is pulled to the site
4) The file is unpacked, XML is parsed
Frontend - this is just setting up paths / passwords where to get the file.

Answer 5

There are 2 most popular formats - xml formation schemes:
1) yml - format for Yandex.Market
2) CommerceML - format for 1C and MySklad.
Support for only these 2 formats is all that 99% of CIS customers need.

Answer 6

Usually - like this:
1. A cloud of folders or archives of folders in a predetermined format (photos, descriptions, publications, etc.).
2. And the index file itself: csv, xls(x), or the same, but in an archive, etc.
The best option: in addition to linking (correspondence of file-index fields and product bindings to products/categories on the site - linker/synonymizer) to create your own scheme for loading and unloading data.
Something like a constructor, where you can set the order of actions with content files, "reading" an index file, unpacking archives on the server side, etc.
Then, you can add a B2B API constructor, and so on.

Answer 7

A very unreasonable choice of technology for an online store... :) You will almost certainly get problems with indexing, I'm telling you as an SEO specialist...
Products must be uploaded to the store manually (if there are not enough of them) and imported from a .CSV file (if there are many), all other options create a bunch of problems out of the blue.