English
Romana
A store carrying OE parts from YQ Service and aftermarket parts from TecDoc is really running two parallel data feeds, each with its own update rhythm and format. The hard part isn't connecting both sources — it's keeping them in sync over time, so the stock and price shown to the customer stay accurate regardless of which source the part came from.
The imbalance rarely shows up at launch. It surfaces months in, once one data source starts updating on a different cadence than the other, and the catalog begins showing stale stock or price on a subset of parts.
This guide covers how to structure the sync job for a dual OE + aftermarket catalog, what differs operationally between YQ Service and TecDoc, and how this was solved in stoauto.ro, an original auto parts store built by HappyWeb.
Why stock and price drift out of sync between YQ Service and TecDoc
YQ Service and TecDoc are updated by different providers, each on its own publishing schedule. If a store runs both sources through a single sync job at the same frequency, one of them ends up trailing reality almost all the time.
Import file formats differ too: the stock/price field structure for OE parts rarely matches the structure used for aftermarket parts. A single job written for one format mishandles the other, often without throwing a visible error.
How to structure the sync job for a dual catalog
- A separate job per source (YQ Service and TecDoc), each with its own import format and its own run schedule.
- A frequency calibrated per source, not one frequency forced onto both.
- A separate error log per source, so it's immediately clear which one failed.
- A final reconciliation step that explicitly flags parts without a recent update, instead of silently leaving the old price/stock displayed with no warning.
Operational differences between syncing YQ Service and TecDoc
| Aspect | YQ Service (OE) | TecDoc (aftermarket) |
|---|---|---|
| Data source | Vehicle manufacturers, direct licensing | Aggregated aftermarket suppliers |
| Typical reference volume | Tied to the covered vehicle range | Usually larger, with multiple equivalents per position |
| Stock/price import format | Own structure, often CSV per supplier | TecDoc's own structure, different from OE |
| Main sync risk | Stale price on rarely ordered parts | Stock shown for parts discontinued by the supplier |
Practical plan: implementing sync for an OE + aftermarket catalog
- Map stock/price fields from both sources onto a shared internal data model, even if the import formats themselves stay separate.
- Set up two distinct jobs, each running at the frequency that fits its source (e.g. OE price daily, aftermarket stock every few hours, if the supplier allows it).
- Add a "last updated" field, visible internally, on every part for fast debugging when a discrepancy appears.
- Define a fallback rule: what gets shown to the customer if a job fails (e.g. last known stock, flagged as "availability to confirm," not a false in-stock state).
- Test the failure scenario separately for each source, not just the success path.
Common risks and how to avoid them
- One job for both sources — avoided by fully separating the jobs, even if they run on the same server or close to each other in time.
- No alert on sync failure — avoided with an active per-source log that explicitly flags a failed or partial import.
- Stale stock/price shown without warning — avoided with an explicit fallback rule, not by silently keeping the last known value.
- Same frequency for very different data volumes — avoided by calibrating frequency to each source's real volume, not an arbitrary shared value.
Case study: syncing in stoauto.ro
stoauto.ro is an original auto parts online store built by HappyWeb, with yqservice.eu API integration: a vehicle database, searchable OE parts diagrams, VIN search, and price import/update via CSV, integrated into the store's ecommerce modules.
The OE price import flow runs as an independent job, with its own CSV format and its own schedule — a structure built precisely so a second sync flow for an aftermarket source could be added later without touching the existing YQ Service job.
Frequently asked questions about syncing OE + aftermarket stock and prices
Can a single job handle both YQ Service and TecDoc?
Technically yes, but it's not recommended: import formats differ, and the optimal frequencies usually don't line up, which leads to stale data on one of the two sources.
How often should aftermarket stock be synced?
It depends on how often the TecDoc supplier makes updates available; the store's internal sync frequency can't outpace the source's actual update rhythm.
What happens if a sync job fails for a day?
With a proper fallback rule, the store shows the last known stock/price, flagged internally as not current, instead of blocking the part or showing clearly wrong data.
Does a central ERP managing both sources make sense?
Yes, if the parts volume and catalog complexity justify the investment; for smaller catalogs, two well-separated jobs can be enough without a dedicated ERP.
Conclusion
A dual OE + aftermarket catalog only works correctly if stock and price from YQ Service and TecDoc are synced separately, each with its own frequency and fallback rules. HappyWeb has already built this kind of flow for stoauto.ro and can assess how to extend it correctly for a store adding a second parts source.
Want original and aftermarket parts synced correctly in the same store? Let's discuss combining YQ Service and TecDoc for a complete catalog, without stock or price drift.
Write a comment