[{"data":1,"prerenderedAt":71},["ShallowReactive",2],{"legacy:insights\u002Fsrm-sourcing-rfq-bid-tender:en":3},{"id":4,"title":5,"description":6,"keywords":7,"author":8,"robots":9,"bodyClass":10,"image":11,"jsonld":12,"html":70},"insights\u002Fsrm-sourcing-rfq-bid-tender","RFQ and tender done, yet ERP prices come from memory? Sourcing must leave a write-back conclusion - JEDP Digital Platform","The source tracing is interrupted during chatting and spreadsheets, and pricing cannot be traced back. The process of inquiry, bidding, and tendering must be recorded, price comparison must be auditable, finalization of the bid must be approved, and the results should be written back to the price master data before being transferred to procurement execution.","RFQ management, competitive bidding, tender management, SRM sourcing collaboration, price comparison, sealed quotation","Shenzhen Langbowan Information Technology Co., Ltd.","index, follow","page-insights","https:\u002F\u002Fwww.jedp.cn\u002Fres\u002Fimages\u002Fproduct\u002Fsrm-slide6.webp",[13,30,44],{"@context":14,"@type":15,"@id":16,"headline":17,"description":6,"inLanguage":18,"datePublished":19,"dateModified":20,"articleSection":21,"keywords":7,"image":11,"author":22,"publisher":24,"isPartOf":25,"mainEntityOfPage":27},"https:\u002F\u002Fschema.org","Article","https:\u002F\u002Fwww.jedp.cn\u002Finsights\u002Fsrm-sourcing-rfq-bid-tender#article","RFQ and tender done, yet ERP prices come from memory? Sourcing must leave a write-back conclusion","zh-CN","2026-03-26","2026-10-17","SRM · Supplier",{"@id":23},"https:\u002F\u002Fwww.jedp.cn\u002F#organization",{"@id":23},{"@id":26},"https:\u002F\u002Fwww.jedp.cn\u002Finsights#collection",{"@type":28,"@id":29},"WebPage","https:\u002F\u002Fwww.jedp.cn\u002Finsights\u002Fsrm-sourcing-rfq-bid-tender",{"@context":14,"@type":31,"itemListElement":32},"BreadcrumbList",[33,38,42],{"@type":34,"position":35,"name":36,"item":37},"ListItem",1,"Home","https:\u002F\u002Fwww.jedp.cn\u002F",{"@type":34,"position":39,"name":40,"item":41},2,"Insights","https:\u002F\u002Fwww.jedp.cn\u002Finsights",{"@type":34,"position":43,"name":17,"item":29},3,{"@context":14,"@type":45,"@id":46,"mainEntity":47},"FAQPage","https:\u002F\u002Fwww.jedp.cn\u002Finsights\u002Fsrm-sourcing-rfq-bid-tender#faq",[48,54,58,62,66],{"@type":49,"name":50,"acceptedAnswer":51},"Question","Must we implement RFQ, bidding and tender all at once?",{"@type":52,"text":53},"Answer","Not necessary. Layer according to category and amount: use inquiries for regular items, use bidding for price-sensitive items with clear rules, and use tenders for high-value items or those with high compliance requirements. The key is to go through the entire sourcing process within the same project once the method is chosen.",{"@type":49,"name":55,"acceptedAnswer":56},"What if suppliers will not quote online?",{"@type":52,"text":57},"Within the scope of the invitation, procurement may first be allowed to record sealed quotes on behalf of others, but opening, decryption, price comparison, and awarding still require a system timestamp. For long-term proxy recording, the proxy recorder and the supplier must be confirmed separately.",{"@type":49,"name":59,"acceptedAnswer":60},"Should award results sync to ERP?",{"@type":52,"text":61},"Price master data is authoritatively written into the source through sourcing, benchmarking, and approval, and then integrated back into ERP\u002Fpurchasing price lists; only the pricing results are stored, not the process, making it unclear during audits who won under what rules.",{"@type":49,"name":63,"acceptedAnswer":64},"Is collusion detection over-engineering?",{"@type":52,"text":65},"Not for high-value bids and key categories. Signals such as equity penetration, the same end customer, and abnormal convergent pricing are used to assist in review; they cannot automatically result in a fatal decision, but should be included as attachments for bid evaluation and pricing approval.",{"@type":49,"name":67,"acceptedAnswer":68},"Can we place a PO before sourcing finishes?",{"@type":52,"text":69},"Emergency short orders require explicit special approval and must have limits on quantity and validity period. Treat 'place the order first and then source later' as normal practice, and there will permanently be two sets of truths for price master data and order prices.","\u003Carticle class=\"insight-article\">\n    \u003Cdiv class=\"insight-container\">\n      \u003Cnav class=\"breadcrumb\" aria-label=\"Breadcrumb\">\n        \u003Ca href=\"\u002F\">Home\u003C\u002Fa>\n        \u003Cspan class=\"breadcrumb-sep\">\u002F\u003C\u002Fspan>\n        \u003Ca href=\"\u002Finsights\">Insights\u003C\u002Fa>\n        \u003Cspan class=\"breadcrumb-sep\">\u002F\u003C\u002Fspan>\n        \u003Cspan>SRM · Supplier\u003C\u002Fspan>\n      \u003C\u002Fnav>\n\n      \u003Cheader class=\"insight-hero\">\n        \u003Cdiv class=\"insight-tags\">\u003Cspan class=\"r-tag\">Sourcing collaboration\u003C\u002Fspan>\u003Cspan class=\"r-tag\">RFQ \u002F quotation\u003C\u002Fspan>\u003Cspan class=\"r-tag\">Competitive bidding\u003C\u002Fspan>\u003Cspan class=\"r-tag\">Tender\u003C\u002Fspan>\u003C\u002Fdiv>\n        \u003Ch1>RFQ and tender done, yet ERP prices come from memory? Sourcing must leave a write-back conclusion\u003C\u002Fh1>\n        \u003Cp class=\"insight-lede\">Compliance spot checks require a document explaining 'why this supplier was chosen.' The procurement team pulled out emails for inquiries, the local machine's comparison price sheets, and the winning bid prices from meeting minutes — the three don’t match the unit prices recorded in the ERP system. The problem is rarely 'no price comparison was done'; rather, sourcing has never been turned into an auditable, traceable project.\u003C\u002Fp>\n        \u003Cdiv class=\"insight-meta\">\n          \u003Cspan>Updated 2026-03-26\u003C\u002Fspan>\n          \u003Cspan class=\"dot\" aria-hidden=\"true\">\u003C\u002Fspan>\n          \u003Cspan>~8 min read\u003C\u002Fspan>\n          \u003Cspan class=\"dot\" aria-hidden=\"true\">\u003C\u002Fspan>\n          \u003Cspan>Manufacturing digitalization · SRM · Supplier\u003C\u002Fspan>\n        \u003C\u002Fdiv>\n      \u003C\u002Fheader>\n      \u003Csection class=\"insight-takeaways\">\n        \u003Ch2>What you'll take away\u003C\u002Fh2>\n        \u003Cul>\u003Cli>The goal of sourcing is a traceable pricing conclusion—not a few RFQ emails sent out\u003C\u002Fli>\u003Cli>Requesting quotes, bidding, and tendering apply to different scenarios, but all must have process traceability, auditable price comparison, approval for final selection, and the results written back to the price master data.\u003C\u002Fli>\u003Cli>The demand pool status should be dynamically assigned and closed-loop, and it is forbidden to remain in 'inquiring price' for a long time without an assigned person responsible for finalizing the bid.\u003C\u002Fli>\u003Cli>Sealing, multi-round rules, the evaluation committee, and abnormal convergence signals are the baseline for process credibility.\u003C\u002Fli>\u003Cli>First, get strategic materials and invitation for quotation running smoothly, then expand to competitive bidding and tendering; orders cannot be placed according to verbally agreed winning prices before pricing takes effect.\u003C\u002Fli>\u003C\u002Ful>\n      \u003C\u002Fsection>\n\n      \u003Cdiv class=\"insight-layout\">\n        \u003Cdiv class=\"insight-body\">\n\u003Ch2 id=\"审计要的不是中标通知-是完整项目包\">What the audit requires is not the bid-winning notice, but the complete project package.\u003C\u002Fh2>\n\u003Cp>Internal audit or group random inspection dropped a sentence: randomly select a strategic material, explain the scope of the invitation, each round of pricing, the comparison criteria, the approval person for the finalization, and the effective date of the price. The conference room went quiet—emails can be searched for inquiries, the Excel is on the purchaser's computer, the minutes say 'recommend choosing A,' but the ERP unit price is a different number.\u003C\u002Fp>\n\u003Cp>\"'Asked for prices, compared prices, opened bids'—if you cannot open the corresponding sourcing project review within one minute, it indicates the process is just a formality, and the authority to set prices still resides in conversations and memory. What sourcing collaboration needs to solve is to make the conclusions...\"\u003Cstrong>auditable, writable-back, and executable\u003C\u002Fstrong>, rather than opening multiple portal pages.\u003C\u002Fp>\n\u003Ch2 id=\"三种路径-一张需求池\">Three paths, one demand pool\u003C\u002Fh2>\n\u003Cp>Requesting quotes, bidding, and tendering are three different processes, but the endpoint should be the same: price comparison with records → approval of final bid → activation of price master data → conversion of demand to purchase order.\u003C\u002Fp>\n\u003Cdiv class=\"table-scroll\">\u003Ctable>\u003Cthead>\u003Ctr>\u003Cth>Mode\u003C\u002Fth>\u003Cth>Best fit\u003C\u002Fth>\u003Cth>Process essentials\u003C\u002Fth>\u003Cth>Common misuse\u003C\u002Fth>\u003C\u002Ftr>\u003C\u002Fthead>\u003Ctbody>\u003Ctr>\u003Ctd>RFQ \u002F quotation\u003C\u002Ftd>\u003Ctd>Specifications are clear, supplier pool is stable, multiple rounds of clarification needed\u003C\u002Ftd>\u003Ctd>Invitation scope, multiple rounds, optional sealing, price comparison can be audited\u003C\u002Ftd>\u003Ctd>Send an email requesting a quotation; without comparison, there is no fixed standard.\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Competitive bidding\u003C\u002Ftd>\u003Ctd>Price-sensitive, rules quantifiable, requires time-limited game\u003C\u002Ftd>\u003Ctd>Lobby, rounds\u002Ftime limits, and ranking rules are announced in advance\u003C\u002Ftd>\u003Ctd>Irregular bidding, screenshot to determine win or loss\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Tender\u003C\u002Ftd>\u003Ctd>High amount, high compliance requirements, requires pre-approval and bid evaluation\u003C\u002Ftd>\u003Ctd>Announcement\u002FInvitation, Bid Opening, Bid Evaluation Committee, Award Approval\u003C\u002Ftd>\u003Ctd>Only the bidding documents are available, there are no opening and evaluation records.\u003C\u002Ftd>\u003C\u002Ftr>\u003C\u002Ftbody>\u003C\u002Ftable>\u003C\u002Fdiv>\n\u003Cp>In one sentence about selection: the more complex the rules, the higher the amount, and the more likely an audit will occur, the more necessary it is to go through bidding; for daily categories, prioritize requesting quotes; use competitive bidding when market price discovery is needed. Do not use bidding to torment hardware accessories, and do not handle large equipment purchases with inquiry emails.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>The same requirement line should only follow one main path at the same time.\u003C\u002Fstrong> The demand pool should be able to distinguish between pending sourcing, under inquiry, under bidding, and under tendering, and support transfer to procurement; if it remains in 'under inquiry' for a long time, it is usually not because the supplier is slow, but because the person responsible for finalizing the contract is unclear, there is a dispute over the comparison criteria, or there is no one to handle approvals.\u003C\u002Fp>\n\u003Ch2 id=\"比价大厅-没有统一口径-就没有-比过价\">Price Comparison Hall: Without a unified standard, there is no 'price comparison'\u003C\u002Fh2>\n\u003Cp>The most common semi-digital way of requesting quotations is that the replies fall into individual emails, and procurement manually pastes them into Excel. 'Price comparison' only exists in local files, making auditing and review irreproducible; clarifications are done on WeChat, causing the quotes in the next round to drift.\u003C\u002Fp>\n\u003Cp>The minimum rules should include:\u003C\u002Fp>\n\u003Cul>\u003Cli>Transfer demand pool items to inquiry projects: materials, quantities, delivery dates, and technical attachments are all filed together;\u003C\u002Fli>\u003Cli>The supplier quotes on the portal, supporting multiple rounds and sealed (decrypted at a specified time);\u003C\u002Fli>\u003Cli>Price comparison is displayed according to a unified standard (including tax\u002Fexcluding tax, shipping, delivery time, minimum order quantity, etc.);\u003C\u002Fli>\u003Cli>After the calibration proposal is approved, it is entered into the price master data before allowing the purchase to be executed.\u003C\u002Fli>\u003C\u002Ful>\n\u003Cp>Without a price comparison standard and calibration feedback, email inquiries only complete half of the offline process. Only comparing base prices and performance costs that explode afterward is also a common trap.\u003C\u002Fp>\n\u003Ch2 id=\"竞价-规则不前置-系统只会更快制造争议\">Bidding: Without pre-set rules, the system will only create disputes more quickly\u003C\u002Fh2>\n\u003Cp>The limited-time bidding slogans have been shouted, but the ranking rules (lowest price \u002F overall score \u002F whether shipping is included) were not locked in advance; mid-course rule changes or extended rounds leave no trace; result screenshots are shared in the group, and the official pricing still relies on offline negotiations to be finalized — all of these turn the bidding into a 'faster price-pressuring stage'.\u003C\u002Fp>\n\u003Cdiv class=\"table-scroll\">\u003Ctable>\u003Cthead>\u003Ctr>\u003Cth>Rules\u003C\u002Fth>\u003Cth>Explanation\u003C\u002Fth>\u003C\u002Ftr>\u003C\u002Fthead>\u003Ctbody>\u003Ctr>\u003Ctd>Rules first\u003C\u002Ftd>\u003Ctd>Before bidding starts, lock rounds, duration, ranking definition, sealing, and whether withdraw is allowed\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Eligibility gate\u003C\u002Ftd>\u003Ctd>Only qualified suppliers or those who have passed the prequalification for this project are allowed to enter.\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Read-only process trail\u003C\u002Ftd>\u003Ctd>Each round’s quote timestamp and ranking snapshot can be replayed\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Award still goes through approval\u003C\u002Ftd>\u003Ctd>First place does not equal automatic winning of the bid; the quality\u002Fdelivery deadline red line can veto it with the reason recorded\u003C\u002Ftd>\u003C\u002Ftr>\u003C\u002Ftbody>\u003C\u002Ftable>\u003C\u002Fdiv>\n\u003Cp>The value of bidding is to discover prices under rules. Treating bidding as merely a tool for the lowest price while ignoring delivery times and quality thresholds can lead to contract collapse after selecting the lowest bid, and the 'cost reduction' on paper will be returned during a material shortage week.\u003C\u002Fp>\n\u003Ch2 id=\"招标-过程包导出不了-就不算走完流程\">Tender: If the process package cannot be exported, it does not count as completing the process.\u003C\u002Fh2>\n\u003Cp>There are tender documents, but no bid opening records; evaluation opinions are written on paper forms; conflicts of interest of the evaluation team members are not registered; after the winning bid notice is issued, the price master data is not updated — this string of issues is what compliance audits fear the most. When there are suspicions of bid rigging, if there are no convergence signals for review, one can only argue based on impressions.\u003C\u002Fp>\n\u003Cp>The tender project should cover: scope of public\u002Finvited bidding, pre-qualification, deposit, multiple rounds and sealed bidding, bid opening, configuration of the evaluation committee; the evaluation process and attachments should enter the sourcing archive; the award of the bid should undergo process approval.\u003Cstrong>write to price master data\u003C\u002Fstrong>. Signals such as abnormal convergence and identical terminals enter the compliance review attachment—this serves as an auxiliary decision-making tool and does not replace the judgment of the evaluation committee.\u003C\u002Fp>\n\u003Cp>Judgment criteria: After the project is closed, whether it is possible to export a complete process package (invitation list, bid opening records, evaluation opinions, finalization approval, price effective records) without having to piece together emails and meeting minutes.\u003C\u002Fp>\n\u003Ch2 id=\"定标回写与特批-两套价是永久伤口\">Calibration write-back and special approval: two pricing systems are a permanent wound\u003C\u002Fh2>\n\u003Cp>Placing orders based on the \"verbal winning bid\" before pricing takes effect, or manually entering prices into ERP even after pricing has been set, will create two sets of facts. Price master data should be authoritatively written into the source through sourcing, pricing, and approval, and then integrated back into the procurement price list; if the integration fails, it must be visible to the business, and \"portal shows pricing set, but ERP still has old price\" silent drift is prohibited.\u003C\u002Fp>\n\u003Cp>Emergency short orders can be specially approved, but it must be explicit: limit the quantity, validity period, and sourcing completion deadline. The proportion of special approvals continues to be high, and the sourcing module will only become a tool for retroactive recording. Suppliers who have not passed the admission should not be directly included in the invitation scope—sourcing is based on qualified suppliers or project pre-approval.\u003C\u002Fp>\n\u003Cp>Agree with upstream and downstream boundaries in advance: PLM provides drawings and sourcing attachments; materials and the general ledger are still based on ERP; SRM owns the sourcing process and pricing evidence on the collaboration side. Portal access is segregated: suppliers only see invitations for the project and their own quotations; internal viewing is inherited according to the organizational structure. Overseas collaboration prioritizes translating key buttons such as quote, clarification reply, and confirmation.\u003C\u002Fp>\n\u003Cp>In the supply plan, the demand and sourcing usually place the demand pool, inquiry\u002Fbidding\u002Ftender tracking, price comparison and final approval, and price master data feedback on the same chain. During JEDP-SRM acceptance, the priority is to spot-check whether 'strategic materials can open the complete sourcing files and whether the order price matches the effective price,' rather than first doing the bidding hall animation.\u003C\u002Fp>\n\u003Ch2 id=\"先跑通一种主路径-再铺另外两种\">First complete one main path, then lay out the other two.\u003C\u002Fh2>\n\u003Cdiv class=\"table-scroll\">\u003Ctable>\u003Cthead>\u003Ctr>\u003Cth>Stage\u003C\u002Fth>\u003Cth>Scope\u003C\u002Fth>\u003Cth>Action\u003C\u002Fth>\u003Cth>Sign of effectiveness\u003C\u002Fth>\u003C\u002Ftr>\u003C\u002Fthead>\u003Ctbody>\u003Ctr>\u003Ctd>First\u003C\u002Ftd>\u003Ctd>Strategic materials + invite-only RFQ\u003C\u002Ftd>\u003Ctd>Transfer demand into project, portal quotation, price comparison, finalizing, write back price\u003C\u002Ftd>\u003Ctd>Spot checks can open the complete inquiry file\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Then\u003C\u002Ftd>\u003Ctd>Price-sensitive categories\u003C\u002Ftd>\u003Ctd>Bidding hall rules are pre-configured and share the finalization\u002Ffeedback with the inquiry quotation\u003C\u002Ftd>\u003Ctd>'Screenshot to determine the winner' can be counted and decreased\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Later\u003C\u002Ftd>\u003Ctd>High-value \u002F compliance categories\u003C\u002Ftd>\u003Ctd>Tender prequalification, sealing, bid evaluation team, final approval; signal attached\u003C\u002Ftd>\u003Ctd>The process package can be exported; the order price is the same as the effective price\u003C\u002Ftd>\u003C\u002Ftr>\u003C\u002Ftbody>\u003C\u002Ftable>\u003C\u002Fdiv>\n\u003Cp>When the supplier's digital maturity is weak, lightweight quotation forms and proxy recording sealing are allowed, but decryption, price comparison, and bid determination must be completed in your system. If issues like multiple codes for a single item being unmanaged, the qualified supplier list being unreliable, technical attachments changing three times a week, and the special approval culture not being explicit are not resolved beforehand, no matter how many sourcing methods are added, a controllable price and personnel cannot be selected.\u003C\u002Fp>\n\u003Cp>Useful indicators: project sourcing closure rate, average calibration cycle, timeliness of price master data entry, completeness of price comparison standards, compliance rate of sealing and unsealing, archiving rate of bid evaluation opinions, proportion of special approval orders, consistency rate between order price and effective price. Projects not being closed just to create the appearance of activity, checking prices before sealing them, only comparing base prices — all are inflation.\u003C\u002Fp>\n\u003Cp>Calibration approval can start by focusing on: whether the invitation scope covers the qualified supplier strategy, whether the comparison criteria are consistent with the announcement, whether quality\u002Fdelivery\u002Fqualification red lines are reviewed, the effective date of the price and its applicable scope, and whether there are any abnormal convergences that need to be rechecked.\u003C\u002Fp>\n\u003Ch2 id=\"怎么继续\">What to do next\u003C\u002Fh2>\n\u003Cp>Select ten strategic material orders that are 'reported to have been price-compared': check whether there are corresponding sourcing projects, price comparison records, award approvals, and effective dates of the price master data in the system. If not, first complete this main path before discussing cost reduction narratives. At the same time, look at the long-pending lines in the demand pool that are 'under inquiry \u002F under bidding \u002F under tender'—if they are overdue with no follow-up, it indicates that the responsibility for awarding the contract has not been implemented.\u003C\u002Fp>\n\u003Cul>\u003Cli>SRM supply solution: sourcing collaboration and price master\u003C\u002Fli>\u003Cli>Supplier Admission and Observation Period\u003C\u002Fli>\u003Cli>Purchase Order Collaboration: Confirmation, Changes, and Feedback\u003C\u002Fli>\u003Cli>Outsourced processing reconciliation breakpoint\u003C\u002Fli>\u003C\u002Ful>\n        \u003C\u002Fdiv>\n        \u003Caside class=\"insight-toc\" aria-label=\"On this page\">\n          \u003Ch2>Contents\u003C\u002Fh2>\n          \u003Ca class=\"h2\" href=\"#审计要的不是中标通知-是完整项目包\">What the audit requires is not the bid-winning notice, but the complete project package.\u003C\u002Fa>\n          \u003Ca class=\"h2\" href=\"#三种路径-一张需求池\">Three paths, one demand pool\u003C\u002Fa>\n          \u003Ca class=\"h2\" href=\"#比价大厅-没有统一口径-就没有-比过价\">Price Comparison Hall: Without a unified standard, there is no 'price comparison'\u003C\u002Fa>\n          \u003Ca class=\"h2\" href=\"#竞价-规则不前置-系统只会更快制造争议\">Bidding: Without pre-set rules, the system will only create disputes more quickly\u003C\u002Fa>\n          \u003Ca class=\"h2\" href=\"#招标-过程包导出不了-就不算走完流程\">Tender: If the process package cannot be exported, it does not count as completing the process.\u003C\u002Fa>\n          \u003Ca class=\"h2\" href=\"#定标回写与特批-两套价是永久伤口\">Calibration write-back and special approval: two pricing systems are a permanent wound\u003C\u002Fa>\n          \u003Ca class=\"h2\" href=\"#先跑通一种主路径-再铺另外两种\">First complete one main path, then lay out the other two.\u003C\u002Fa>\n          \u003Ca class=\"h2\" href=\"#怎么继续\">What to do next\u003C\u002Fa>\n        \u003C\u002Faside>\n      \u003C\u002Fdiv>\n\n      \u003Cdiv class=\"insight-cta\">\n        \u003Cp>\u003Cstrong>Want to apply this in your plant?\u003C\u002Fstrong>Resources has matching self-assessments and templates—or book a live demo.\u003C\u002Fp>\n        \u003Cdiv class=\"insight-cta-actions\">\n          \u003Ca href=\"\u002Fresources?from=srm#selftest\" class=\"btn btn-outline\">Self-assessment in Resources\u003C\u002Fa>\n          \u003Ca href=\"\u002Fcases#case-srm\" class=\"btn btn-outline\">SRM acceptance case\u003C\u002Fa>\n          \u003Ca href=\"\u002Fcontact?from=srm\" class=\"btn\">Get a demo\u003C\u002Fa>\n        \u003C!-- next-step:BEGIN -->\u003Ca class=\"btn\" href=\"\u002Fproduct\u002Fsrm\">Product solution: \u003Cspan>JEDP-SRM Supplier Relationship Management\u003C\u002Fspan>\u003C\u002Fa>\u003Ca class=\"btn btn-outline\" href=\"\u002Fres\u002Fresources\u002Fkits\u002F22-srm-sourcing-portal.html\">Matching resource kit: \u003Cspan>Sourcing comparison + supplier portal checklist\u003C\u002Fspan>\u003C\u002Fa>\u003C!-- next-step:END -->\n        \u003C\u002Fdiv>\n      \u003C\u002Fdiv>\n      \u003Csection class=\"insight-faq\" id=\"faq\">\n        \u003Ch2>FAQ\u003C\u002Fh2>\n        \u003Cp class=\"insight-faq-sub\">Quick answers on this topic—still stuck?\u003Ca href=\"\u002Fcontact?from=srm\">Contact\u003C\u002Fa>\u003C\u002Fp>\n        \u003Cdiv class=\"faq-list\">\n        \u003Cdetails class=\"faq-item\" open>\n          \u003Csummary>Must we implement RFQ, bidding and tender all at once?\u003C\u002Fsummary>\n          \u003Cp>Not necessary. Layer according to category and amount: use inquiries for regular items, use bidding for price-sensitive items with clear rules, and use tenders for high-value items or those with high compliance requirements. The key is to go through the entire sourcing process within the same project once the method is chosen.\u003C\u002Fp>\n        \u003C\u002Fdetails>\n        \u003Cdetails class=\"faq-item\">\n          \u003Csummary>What if suppliers will not quote online?\u003C\u002Fsummary>\n          \u003Cp>Within the scope of the invitation, procurement may first be allowed to record sealed quotes on behalf of others, but opening, decryption, price comparison, and awarding still require a system timestamp. For long-term proxy recording, the proxy recorder and the supplier must be confirmed separately.\u003C\u002Fp>\n        \u003C\u002Fdetails>\n        \u003Cdetails class=\"faq-item\">\n          \u003Csummary>Should award results sync to ERP?\u003C\u002Fsummary>\n          \u003Cp>Price master data is authoritatively written into the source through sourcing, benchmarking, and approval, and then integrated back into ERP\u002Fpurchasing price lists; only the pricing results are stored, not the process, making it unclear during audits who won under what rules.\u003C\u002Fp>\n        \u003C\u002Fdetails>\n        \u003Cdetails class=\"faq-item\">\n          \u003Csummary>Is collusion detection over-engineering?\u003C\u002Fsummary>\n          \u003Cp>Not for high-value bids and key categories. Signals such as equity penetration, the same end customer, and abnormal convergent pricing are used to assist in review; they cannot automatically result in a fatal decision, but should be included as attachments for bid evaluation and pricing approval.\u003C\u002Fp>\n        \u003C\u002Fdetails>\n        \u003Cdetails class=\"faq-item\">\n          \u003Csummary>Can we place a PO before sourcing finishes?\u003C\u002Fsummary>\n          \u003Cp>Emergency short orders require explicit special approval and must have limits on quantity and validity period. Treat 'place the order first and then source later' as normal practice, and there will permanently be two sets of truths for price master data and order prices.\u003C\u002Fp>\n        \u003C\u002Fdetails>\n        \u003C\u002Fdiv>\n      \u003C\u002Fsection>\n      \u003Csection class=\"insight-related\">\n        \u003Ch2>Related reading\u003C\u002Fh2>\n        \u003Cdiv class=\"insight-related-grid\">\n          \u003Carticle class=\"r-card\">\n            \u003Cdiv class=\"r-tags\">SRM · Supplier\u003C\u002Fdiv>\n            \u003Ch3>Approved vendor lists keep growing? Onboarding must block unacceptable risk first\u003C\u002Fh3>\n            \u003Cp>Directory expansion has occurred, but those willing to increase volume have not, mainly because access only involved completing registration. Data, capability, business, and the observation period need to be unlocked in sequence for volume increase; crossing the red line is not allowed for entry into the directory, and the evidence chain is more important than the total score. …\u003C\u002Fp>\n            \u003Cdiv class=\"r-meta\">2026-03-12 · ~9 min\u003C\u002Fdiv>\n          \u003C\u002Farticle>\n          \u003Carticle class=\"r-card\">\n            \u003Cdiv class=\"r-tags\">SRM · Supplier\u003C\u002Fdiv>\n            \u003Ch3>Buyer says sent, supplier says unseen? Order collaboration starts on one effective PO\u003C\u002Fh3>\n            \u003Cp>Order collaboration chaos usually is not due to the supplier being uncooperative, but because confirmations, changes, and delivery feedback are not on the same document. Confirmation timestamps, change versions, and secondary confirmations, as well as feedback and commitments, are separated, yet the interface status on both sides is consistent. ...\u003C\u002Fp>\n            \u003Cdiv class=\"r-meta\">2026-04-09 · ~8 min\u003C\u002Fdiv>\n          \u003C\u002Farticle>\n          \u003Carticle class=\"r-card\">\n            \u003Cdiv class=\"r-tags\">SRM · Supplier\u003C\u002Fdiv>\n            \u003Ch3>Outsourcing reconciliation never ties? Split to documents and you find five breakpoints\u003C\u002Fh3>\n            \u003Cp>Outsourced reconciliation discrepancies almost never stem from accounting errors, but rather from the lack of mutually recognized documentation when the business occurs. Breaking it down to the document level across five points—material issuance receipt, loss criteria, direct process delivery, rework scrap, and accounting cutoff—shows …\u003C\u002Fp>\n            \u003Cdiv class=\"r-meta\">2026-05-14 · ~9 min\u003C\u002Fdiv>\n          \u003C\u002Farticle>\n        \u003C\u002Fdiv>\n      \u003C\u002Fsection>\n    \u003C\u002Fdiv>\n  \u003C\u002Farticle>",1793937990724]