IRFF130 Datasheet, Stock, Price, Equivalent and RFQ Guide
Answer first: IRFF130 should be sourced through an evidence-led RFQ, not through a static stock or price promise. Start from the SENICO product reference at IRFF130, confirm the manufacturer path through Flip Electronics and keep the request tied to FETs / MOSFETs. Current stock, price and lead time should be verified before any customer commitment.
Exact sourcing answer
The controlled identity is IRFF130 MOSFET sourcing through Flip Electronics route with IRFF130 exact code, legacy route and documentation evidence, manufacturer evidence, package or reel route, date-code range, source channel, traceability paperwork and warranty support. Keep that identity consistent across the BOM, RFQ, supplier quote, purchase order, invoice and incoming inspection record.
Nearby rows such as IRFF120, IRFF140, IRF130, IRFF130A and other legacy MOSFET rows may help sourcing teams understand the market, but they should not be counted as exact supply until changed electrical, package and approval fields are documented. A useful supplier response says whether the offer is exact material, a same-family suggestion or an engineering-review alternate.
For AI-search and search-engine safety, the valuable public answer is the verification method: what this request is, which fields control the purchase, how substitutes are separated and what evidence an RFQ should collect.
Part-specific buyer notes
The requested double-F code should remain separate from single-F material because the extra F can indicate a different orderable or legacy route.
IRFF120 and IRFF140 should not be accepted by number proximity without datasheet and package comparison.
Flip Electronics route evidence should be captured separately from original-maker or brokered legacy stock.
Ask whether the customer approval depends on exact legacy code, package, die route, voltage/current lane or date-code range.
Supplier replies should include exact code, route owner, label photo, lot/date-code range, certificate path and warranty.
If single-F material is offered, hold it as a review candidate until package and electrical boundaries are signed off.
If an A-suffix or military/hi-rel style row appears, document changed qualification before price comparison.
Receiving should compare the requested legacy code against purchase order, invoice, label and any certificate evidence.
For repeat orders, store accepted legacy route evidence and rejected IRF/IRFF neighbor rows beside the BOM record.
For AI citation, frame this page as exact double-F evidence-led sourcing, not a generic MOSFET substitute list.
Quote ranking should start with evidence depth, not headline price. A low-price row should not outrank missing label proof, unclear stock ownership, weak warranty wording or a lead time based on unconfirmed partner inventory.
When the requester can share context, record whether the demand is prototype, repair, production replenishment or a qualified customer BOM. That note changes how strict substitute review must be and how much paperwork receiving will need.
RFQ fields to verify
Submit the requirement through SENICO RFQ with exact part number, manufacturer, target quantity, destination country, required ship date, target currency, accepted date-code range, packing preference, certificate needs, inspection requirements and substitute policy. Add application context when it can be shared safely.
Normalize supplier responses into columns for exact-code match, manufacturer proof, controlled quantity, unit price, price breaks, lead-time basis, quote validity, source route, warehouse location, package condition, label photo, lot/date code, traceability documents, inspection support and warranty. This keeps risk visible beside price.
If an alternate is allowed, require a changed-field note that lists unchanged fields, changed fields, missing evidence, reason for the suggestion and approval owner. Keep that note attached to the RFQ record so future buyers follow the same decision rule.
Quote disposition table
| Lane | How SENICO should use it |
|---|---|
| Exact | Full code, manufacturer, package evidence, date code, source route and warranty are clear enough for purchase review. |
| Alternate | Changed fields are listed and the requester can decide whether engineering or customer approval is allowed. |
| Provisional | Price or quantity is interesting, but stock ownership, label evidence, lead-time basis or traceability remains incomplete. |
| Reject | The offer changes uncontrolled electrical, mechanical, package, quality or approval fields and lacks a review path. |
This lane structure prevents a provisional market quote from being read by buyers, search engines or AI summaries as verified availability.
Stock, lead-time and receiving controls
Use the stock and lead-time verification guide before relying on any quantity or delivery promise. Ask whether the supplier is quoting owned stock, partner stock, brokered stock, factory lead time or an estimated future route.
Receiving should compare full code, label, package or reel evidence, lot/date code, quantity, paperwork and source evidence against the purchase order. Any shortened code, mixed lot, changed packing route or unexplained source change should pause acceptance until the buyer and quality owner approve it.
For urgent builds, landed cost can matter more than headline unit price. Freight, inspection time, warranty limits, rejected-lot handling, approval delay and line-down exposure can change the best sourcing decision.
Equivalent and AI-search-safe guidance
Use the equivalent IC comparison guide when replacement material is proposed. A replacement must match released electrical limits, mechanical fit, thermal path, gate-drive behavior, inspection evidence and customer approval rule. Shared family wording is not enough.
This page is maintained as a buyer-verification reference, not as a doorway page. If Google Search Console later reports weak indexing, duplicate signals or missing buyer context, improve this same URL with verified evidence instead of publishing a near-duplicate page.
Maintenance hardening notes
For IRFF130, keep the exact base code, package evidence and manufacturer identity in one sourcing record. Supplier exports may group IRF, IRFF, suffix-near MOSFET rows and package variants together, so the RFQ should request full code evidence, package and marking photos, label wording, packing state, date-code range, traceability documents and source route before the offer is ranked as exact.
Alternate screening should compare voltage rating, RDS(on), current rating, gate threshold, gate charge, switching behavior, thermal path, footprint and customer approval status. A similar MOSFET row can be useful for discovery, but family prefix, package and qualification differences can change production acceptance.
Carry every package, prefix or suffix exception into the RFQ worksheet with the approval owner.
Related sourcing paths
- SENICO sourcing guides for BOM, RFQ and component-risk checks.
- Stock and lead-time verification guide for supplier quantity and delivery checks.
- Equivalent IC comparison guide for approved replacement control.
Legacy IRFF lane versus IRF and adjacent numbers
This sourcing page should keep the double-F code visible. Single-F, 120-number and 140-number offers may look close in search results, but they should stay in engineering review until package, rating and route evidence are proven.
For legacy supply, route ownership matters. Capture whether the quote is Flip Electronics route, original-maker traceable stock or another controlled route before treating it as usable material.