# Turn vendor price files into updated prices > Cost updates land, map to your items and recompute landed cost the same day, then a margin-preserving reprice stages, honors every contract and publishes on its effective date. Source: https://revomo.ai/solutions/cost-pass-through-repricing/ --- Solutions · Cost pass-through & repricing ## Vendor price files in. Updated prices out. Cost updates land, map to your items and recompute landed cost the same day, then a margin-preserving reprice stages, honors every contract, and publishes on its effective date. [See Revomo in action](https://revomo.ai/contact/)[Assess your margin opportunity](https://revomo.ai/margin-assessment/) <24 hrs From vendor file to staged reprice 1 spine Costs, lists and contracts on one record 100–300 bps Margin improvement target · industry-benchmarked The problem ### Every week between the vendor’s effective date and yours is donated margin. Vendor files die in inboxes “The price file sat in an inbox for three weeks.” Cost updates arrive as attachments in a dozen formats; mapping them to your SKUs by hand takes weeks you pay for in margin. Repricing by hand skips what matters “We repriced everything except the contract exceptions, by hand.” The spreadsheet pass misses protected items or, worse, repriced them, and either way nobody can list the exceptions afterward. The pass-through lag never gets measured “Cost went up 6%; price went up 0%, for a quarter.” Nobody tracks days-to-pass-through, so the same lag repeats every cycle and compounds across every vendor. Cost updates, vendor price files Files this quarter 23 SKUs with cost movement 3,214 Awaiting reprice 1,661 **Alcoa extrusions · price file** +6.2% avg · 412 SKUs · effective Aug 1 Mapped *landed cost updated* **Fastener supply program** +3.5% avg · 1,204 SKUs · effective Aug 15 Mapped *landed cost updated* **LTL freight index · Q3** +4.8% · lane-based · 45 SKUs unmatched Review *mapping suggested* Vendor files land, map to your items, and recompute landed cost per SKU, the same day, not the same quarter. Illustrative preview · not connected to live data RV·2026·S9 · Cost intake ### Vendor files land and map themselves Price files in any format map to your items, recompute landed cost per SKU, and queue what needs repricing, with the unmatched handful routed for review instead of silently dropped. - Any vendor format, mapped, not re-keyed - Landed cost recomputed per SKU, same day - Unmatched items routed with suggested mappings RV·2026·S9 · Reprice by rule ### Margin-preserving, contract-honoring, previewed Choose the rule (hold GM%, hold markup, absorb for strategic accounts) and preview the full impact. Contract-protected items hold to term automatically; floors clamp; every exception is named. - Margin-preserving rules instead of blanket percentages - Contract-protected items held out, with their records - The full preview before anything stages Margin-preserving reprice, scope & rule RULE·GM·HOLD **Preserve gross margin %** Selected Reprice each SKU to hold GM% at its current corridor position → 1,616 SKUs · avg +4.1% · effective Sep 1 RULE·ABS·SEG **Absorb for strategic accounts** Hold price where the account plan says defend share → alternative · margin impact quantified before choosing EXCEPTIONS **Held out of this run** 37 contract-protected to term · 8 clamped at corridor floor · each with its record Stage reprice for approval Illustrative preview · not connected to live data Pass-through timeline, this cycle vs last The gap between the vendor’s effective date and yours is pure margin donation. The work is shrinking it, cycle after cycle, measurably. Illustrative preview · not connected to live data RV·2026·S9 · Shrink the lag ### Days-to-pass-through, measured every cycle The timeline from vendor effective date to yours is the metric that matters, and once it’s visible, it shrinks. Every cycle’s absorbed-cost window is measured against the last. - Vendor date → approval → your effective date, on one strip - Absorbed-cost days quantified per cycle - The lag becomes a KPI someone owns How it runs ### Vendor file to published price, one governed path Step 01 **Land & map** Vendor files map to items and recompute landed cost on the spine, no re-keying. [Data & Context Studio →](https://revomo.ai/platform/#data-context-studio) Step 02 **Reprice by rule** Margin-preserving rules stage the update; contracts and floors are enforced, not remembered. [Price Management →](https://revomo.ai/platform/#price-management) Step 03 **Publish & measure** Approved prices publish on their effective date, and the pass-through lag lands on a dashboard. [Analytics & Insights →](https://revomo.ai/platform/#analytics-insights) FAQ ### The questions purchasing and pricing ask first Our vendor files are a mess, different formats, part numbers, units. Really? That mess is exactly what the mapping layer is for: files map to your item master with suggested matches for the stragglers, and each mapping is remembered for the next cycle. The second file from a vendor is nearly touchless. How is this different from the Cost, Tariff & Freight Recovery solution? Same spine, different altitude. This is the operating motion, routine vendor updates flowing through to prices continuously. Cost recovery is the strategic response when a tariff or freight shock hits the whole book at once. Most customers run both. Can we pass through selectively, protect some accounts, reprice others? Yes, that is what repricing by rule means. Strategic accounts can absorb by policy while the rest of the book preserves margin, and the cost of each choice is quantified before you make it. ### Stop donating the lag. Bring last quarter’s ugliest vendor file. We’ll show you the mapping, the reprice and the days you would have saved. [See Revomo in action](https://revomo.ai/contact/)[Assess your margin opportunity](https://revomo.ai/margin-assessment/) Plate S9 · Series 2026 · Solutions · RV·2026·S9