Import only the part table the client may publish
Catalog work imports part numbers, parameters, and warehouses the client may publish. Missing fields stay blank and are listed in the import report.
Which fields are fixed first
The columns are agreed first: part number, parameters, document link, warehouse, and update time. If both spot and futures are sold, they are separate columns or rows and name the warehouse. They are not added into one total. Document links point to datasheets or images the client may publish.
The source is a file the client provides or a feed the client is allowed to call. A part list of unclear origin does not enter the table and is not uploaded.
When a parameter is missing
The cell stays blank. The import report lists the row and the field name, such as a missing package or voltage. A value from a similar part is not written in. On the storefront the blank tells the buyer that the figure is not in the file.
A row with no part number does not become a product. It is listed in the report. The other rows continue.
What the storefront can do after import
After import, the part page opens, category browsing can find it, and search hits the part number. Bill matching reads this imported set. The warehouse column maps to a warehouse in the admin. Spot stock is not written into futures because of the import.
A later update replaces parameters and stock for that part number and changes the update time. Orders already placed are not rewritten. They keep the quantity and price from when they were placed.
Common questions
Can parameters be taken from another mall?
That is not part of this work. Only data the client may use enters the table.
Will a blank parameter be filled?
No. It stays blank and the field name is listed in the import report.
Does a row without a part number become a product?
No. That row is reported. The other rows continue.
Does a later table update change old orders?
No. An order keeps the quantity and price from when it was placed.