“Just upload your supplier price lists” sounds like a quick route to launching an online auto parts store. In practice, files use different column names, part-number formats, brand spellings, currencies, units, minimum-order rules and definitions of availability. Import them without a data model and the store soon fills with duplicates, stale prices and items that cannot actually be ordered.
A reliable launch starts by separating two entities: the part in the catalogue and a commercial offer from a particular supplier. The product defines what the component is. The offer states who can supply it, at what cost, in what quantity and with which lead time.
First examine what the supplier files really contain
Do not design the process around one convenient spreadsheet. Collect feeds from the main suppliers and build a field map. Define the meaning, format, requirement and cleaning rule for every column.
| Field | What to verify | Common failure |
|---|---|---|
| Manufacturer | Canonical name and spelling variants | The same brand is created several times |
| Part number | Case, spaces, hyphens and service symbols | One component fails to match across sources |
| Name | Language, abbreviations and technical meaning | A supplier label becomes the product description |
| Price | Currency, tax, discount and update time | Wrong cost or a sale below cost |
| Quantity | Exact number, range, availability symbol or text | “Available” is treated as an exact quantity |
| Lead time | Warehouse, city, dispatch and working days | An unrealistic date is promised to the customer |
Do not create a new product from every row
The same part can appear under different descriptions in several price lists while sharing the same manufacturer and normalised part number. The system should find or create one product record, then connect each imported row as a separate supplier offer.
| Entity | Example data | Update frequency |
|---|---|---|
| Product record | Manufacturer, part number, name, OEM, crosses, alternatives and images | Occasionally, after catalogue validation |
| Supplier offer | Supplier code, cost, currency, quantity, warehouse and lead time | Every supplier feed refresh |
| Owned stock | Warehouse, bin, on-hand, reserved and available quantity | After every stock movement |
| Selling rule | Markup, minimum price, channel and delivery method | When business policy changes |
This separation displays one part without duplicates while allowing staff to compare several sources. If a supplier stops trading, the product record and its catalogue relationships remain intact.
A safe import must be repeatable
The first upload is not the main challenge. Feeds have to be updated frequently, so a repeat import must not create new brands, products and offers. Each supplier needs a mapping profile with column definitions and normalisation rules.
- Receive the file and validate its structure.
- Normalise manufacturer names and part numbers.
- Match each row to a product record.
- Create or update the supplier offer.
- Send errors and unmatched values to a separate report.
- Release data to sales channels only after successful checks.
Unsafe rows should not be silently skipped or published. Management needs to know how many offers changed, how many could not be recognised and the reason for every exception.
Availability is more than a number in a column
The customer needs an honest answer: can this item be ordered, when will it arrive and how reliable is the source? Exact stock in your warehouse and a supplier quantity last updated yesterday must not appear identical.
| Status | What it means operationally | What to communicate |
|---|---|---|
| In own warehouse | Free stock confirmed by internal inventory | Available now or an exact dispatch time |
| At supplier | Offer was valid at its last update | Expected lead time including confirmation |
| On request | Manual or automated confirmation is required | Clear terms and a response deadline |
| Stale data | The source missed its expected refresh | Do not promise availability without checking |
| Unavailable | No acceptable current offer exists | Suggest a cross-reference or alternative |
Calculate selling prices with rules, not one markup
The selling price may depend on supplier, brand, product group, cost, currency, channel commission, delivery cost and minimum margin. The rule should be transparent: staff can explain the amount, and management can change a parameter without editing thousands of products by hand.
Add protection against zero prices, sudden movements, unknown currencies and sales below an approved threshold. It is safer to hide and review a suspicious offer than publish it automatically.
Begin with a controlled assortment
You do not need to publish millions of items on the first day. Select product groups and suppliers with stable part numbers, prices and stock data. Test search, the product page, cross-references, checkout, supplier confirmation, returns and the next file refresh.
Expand the range after the pilot while retaining common rules. Otherwise every new feed adds exceptions rather than useful assortment, leaving sales staff to repair the data manually.
The operating setup required for launch
The industry registry should hold parts, OEM numbers, cross-references, alternatives and images. Supplier imports add current commercial offers. Warehouse records separately show owned stock and reservations, while each customer order preserves the selected source, price and lead time at the moment of sale.
The Business Reactor AutoParts module is designed for this flow: a parts registry, OEM numbers, crosses, alternatives, images, supplier offer imports and scheduled stock updates. See the complete connection in the ready-made solution for auto parts stores.
A supplier price list can accelerate launch when the system treats it as a controlled source of offers. It must not become the catalogue itself. A dependable store is built around one product record, verified relationships, and transparent rules for availability and price.
