Listing thousands of products by hand is not possible. The supplier XML solves this problem; but when it is set up wrongly, it produces wrong prices, wrong stock and penalty points.
XML is a standard file format through which suppliers share their product catalog in a machine-readable form. It contains product name, stock code, price, stock quantity, images and attributes. The goal is simple: instead of entering thousands of products by hand, import the file into the system.
In practice, however, the two sides are incompatible: the format the supplier provides and the format the marketplace expects are almost never the same. The real work of the integration is that conversion.
The field called "urun_adi" at the supplier may be "title" on the marketplace, and "stok" may be "quantity." Every supplier uses its own naming. If correct mapping isn't done, products are transferred either wrongly or incompletely.
The supplier's category tree differs from the marketplace's. A product that falls into the wrong category never appears in the right searches. This is one of the hardest errors to notice after transfer, because the product appears to have been transferred "successfully."
The price in the XML is often the supplier's purchase price. You need to add your own margin, commission and shipping on top. If this calculation isn't done automatically, you either sell at a loss or list at a price so high you can never sell.
The right approach: Define a category-based margin rule (e.g. 45% for textiles, 18% for electronics). A single fixed multiplier doesn't work across all categories.
Supplier XMLs usually come with minimal information. Marketplaces, however, require attributes such as size, color and material. A product transferred with missing attributes is either rejected or invisible in filters.
XML is not a static file; the supplier updates price and stock during the day. If you read the file once a day, you are selling all day on old data.
A product that appears "in stock" in the XML may have sold out at the supplier. In that case you can't fulfill the order and have to cancel it — and seller-caused cancellation is one of the heaviest penalties in terms of ranking and seller rating.
| Check | Why |
|---|---|
| Pre-transfer validation | An erroneous record should never reach the marketplace |
| Category map test | Wrong category = invisible product |
| Margin rule check | Prevents selling at a loss |
| Price deviation alert | A supplier error can cut a price tenfold |
| Transfer report | How many products passed, and why the rest were rejected |
Especially price deviation alerts save lives: a typo in the supplier file that lists a 1,200 TL product at 12 TL causes serious losses until it is caught.
XML integration is not a "file upload" job but a continuously running data pipeline. When set up correctly, it lets one person manage thousands of products; left uncontrolled, it costs both money and reputation through wrong prices and cancellations. The difference is whether there is a validation layer.
XML Bridge converts different supplier formats into marketplace schemas, applies your profit margin rules and filters out erroneous records before transfer.