01
🔧OEM cross-reference block
Adds equivalent numbers from ATE, Bosch, Brembo, TRW, Febi so professionals find your card via OEM search.
Turn TecDoc XML rows into proper product cards with cross-references, year/engine fitment, and DIY difficulty — at 400+ SKUs per 2 hours.
Sound familiar?
Cards have only OEM number and part name — no explanation of what car it fits or how to install it
Revenza writes a fitment block, install notes, and a DIY rating per SKU — pulled from TecDoc data and part type
Compatibility says 'for Toyota Camry' but skips year and engine (2.5 vs 3.5, 2015 vs 2020 facelift) — returns rate jumps
Year ranges, engine codes and facelift markers are generated explicitly: '2015-2017 pre-facelift, 2.5L 2AR-FE only'
Brake pad material (organic / semi-metallic / ceramic) is missing, even though it changes braking behavior completely
Friction material, disc type, sensor presence are extracted into a spec table — buyers compare without leaving the card
OEM cross-references to ATE, Bosch, Brembo are absent — professional mechanics buy from Exist.ua or AutoDoc.ua instead
OEM cross-references to ATE, Bosch, Brembo, TRW are listed in a structured block, matching how PARTS.ua presents them
'In stock' has no warehouse status — customer doesn't know if it ships tomorrow or in 3 weeks
Stock status text adapts to your warehouse field: 'ships in 24h from Kyiv' vs 'order from supplier, 14-21 days'
Lamps, mirrors, brake pads sold without EMARK note (Directive 2007/46/EC) — risk on EU orders
EMARK / E-mark and Euro 5/6 compliance flags are auto-inserted for lamps, mirrors, catalysts and filters
What Revenza does every day
1000
products in 1 hour
5¢
per description (Pro)
9
platforms supported
6
languages, one click
Face cream, moisturizes skin. Volume 50 ml. Brand: XYZ. Ingredients: water, glycerin…
Nourishes and restores your skin overnight. Formula built on 3% hyaluronic acid + argan oil. Visible results in 7 days.
Plug in the API key or upload a TecDoc/Hotline.ua feed. Revenza pulls categories, OEMs and existing specs.
Choose which sections appear: fitment, OEM cross-ref, material, DIY rating, EMARK note, install warning.
Revenza drafts 50 SKUs first so you check fitment accuracy before scaling to 5000-100000 cards.
Approved descriptions sync back via API in batches that respect the 100 req/hour limit. CTA goes above reviews.
Adds equivalent numbers from ATE, Bosch, Brembo, TRW, Febi so professionals find your card via OEM search.
Generates explicit fitment: model, year range, engine code, facelift. No more 'fits Camry' guesswork.
Reads TecDoc-style fields and Horoshop import structure, mapping spec attributes into readable HTML with h2/ul.
Marks each part 1-10: 'home garage, basic tools' vs 'lift required, torque spec critical' — buyers self-qualify.
Auto-adds EMARK for lamps/mirrors and Euro 5/6 notes for catalysts and DPFs per Directive 2007/46/EC.
Respects the 100 req/hour API cap, batches imports overnight, and writes only allowed HTML tags.
Revenza only writes fitment that exists in your TecDoc data or supplier feed. If a SKU has no engine code, the card says 'check VIN before purchase' instead of inventing one. We never fabricate OEM numbers.
Yes. Stores in the 5000-100000 SKU range are the typical case. Generation runs in batches; publishing to Horoshop is throttled to the 100 req/hour API limit, so a 60k catalog usually rolls out over 3-5 nights.
Yes, when your feed includes cross-reference data (TecDoc, supplier price lists). Revenza formats them in a structured block — brand, number, note — instead of a wall of text.
For categories where it matters — headlights, mirrors, brake pads, catalysts, DPFs — Revenza inserts the relevant compliance line referencing EMARK (Directive 2007/46/EC) or Euro 5/6 (Regulation 715/2007), but only if your product attributes confirm certification.
No. Horoshop pulls H1 from the product name, so Revenza skips repeating 'Brake pads Bosch 0986494321' and starts with fitment, material and install context — better for SEO and for the buyer.
Revenza flags the SKU instead of guessing. You get a list of cards that need an OEM or cross-reference added before publishing — protecting you from trademark issues with unlicensed OEM claims.
Get fitment, OEM cross-refs and EMARK notes on every card before the spring brake-and-suspension rush hits.