SYSTEM // LOADING
BIDQUEST // 2026
GRID // 1280px
BIDQUEST // 2026
Zero manual search • 100% Free
Review Make in India procurement treatment with checks for applicability, local-content classification, item evidence and the actual preference method.

DPIIT's official guidance describes Class-I and Class-II local suppliers using baseline local-content thresholds of 50% and 20%, with nodal authorities able to prescribe higher requirements. Applicability and preference procedure must be checked for the actual item and tender. Official DPIIT guidance.
This article provides an original bid-review method. It does not classify a specific product or determine a disputed preference entitlement.

Record the bidder's legal identity and the item or service actually offered. An Indian enterprise can supply an imported product, and a product's origin or local value addition needs its own evidence.
Do not use business registration as a substitute for the requested local-content declaration. Conversely, do not assume a product label explains every component of a formal calculation.
Have the appropriate technical and accounting reviewers identify what the applicable definition includes and how evidence supports it.
The claim should relate to the offer, not a general patriotic description of the company.

Identify the buyer, procurement framework, item-specific notifications and tender provisions. Check whether a nodal requirement changes the relevant minimum or treatment.
Do not apply a broad central-policy summary identically to every state or specialised procurement. Review the actual governing instruments and formal clarifications.
Record the exact provision and date used. If a current source cannot be retrieved, mark the verification limitation instead of asserting an unsupported current rule.
Material applicability questions should be resolved before the commercial team relies on preference in its bid decision.

| Question | Evidence-review task |
|---|---|
| What is offered? | Exact item, model or service scope |
| Which definition applies? | Current policy and tender reference |
| What minimum applies? | Relevant baseline or specific notification |
| What content is supported? | Reviewed calculation and source records |
| Who certifies? | Required declaration or competent certificate |
| What procedure follows? | Actual tender preference and evaluation method |
Keep unresolved rows visible. A classification should not be selected because it improves commercial prospects if the calculation is unsupported.

Identify eligibility, margin, quantity treatment and the procedure stated by the procurement. Determine whether the requirement is divisible or handled through another specified method.
Do not assume preference means the buyer pays your original higher price or guarantees the entire contract. Use the actual conditions and any required matching or confirmation process.
Have finance assess whether the business can deliver at the price required under that process. Policy relevance does not remove cost and cash-flow review.
Ask a focused clarification where the mechanism is unclear.
For a reseller, identify the manufacturer information and certification required by the actual tender. Obtain authentic records for the exact offered product and period.
Do not reuse a local-content statement for another model or assume a manufacturer-wide percentage applies to every item.
If a product configuration changes, check whether its evidence and calculation remain valid. A cheaper imported component can alter a previously supported claim.
Keep supplier commitments and evidence linked to the technical offer so the submitted configuration and declared content remain consistent.
Establish the applicable numerator, denominator, inclusions, exclusions and treatment of multiple components. Use the actual current definition and required certification.
Do not build a formal declaration from a rough percentage guessed by sales. Do not count an invoice value as domestic value addition without examining the rule.
Have the accountant or other required competent person review the supporting records, and technical staff confirm component identity.
The calculation should be reproducible from evidence and traceable to the offer.
Suppose an illustrative product's reviewed content position is near the applicable minimum. A proposed configuration change introduces a different component.
The team should re-examine the relevant calculation and classification rather than keeping the earlier favourable declaration unchanged.
If the revised position changes the applicable category, finance and the bid owner review eligibility and preference effects. They do not treat the issue as a minor catalogue edit.
The example does not define a lawful calculation or product category; it shows why configuration and policy evidence must be connected.
Assume a made-up procurement's applicable preference procedure requires a supplier to accept a specified evaluated price. The business's internal cost is ₹9 lakh and the reviewed offer price would be ₹9.3 lakh.
The simplified difference is ₹30,000 before other accounting or financing effects. Management should assess whether that result funds the actual contract.
These values are illustrative and do not reproduce a universal preference rule. The point is to test the commercial consequence of the actual process.
Do not rely on policy positioning to justify a commitment below a reviewed sustainable level.
An enterprise may have both relevant MSE status and a local-content position. They are separate policy concepts with potentially different evidence and procedures.
Create separate claim rows and examine how the actual tender handles their interaction. Do not combine them into a broad “government preferred” label.
Where the combined application is unclear, obtain the applicable official guidance and qualified review. Do not choose whichever sequence produces a favourable internal result.
Preserve the formal basis for each claim in the bid record.
Identify who must sign, what wording or format is required and whether a particular professional certificate is needed for the procurement.
Do not assume an old threshold or certificate method remains current for every event. Verify the current requirement and the actual offer value or scope.
Give the reviewer the product evidence and calculation, not merely a ready-made sentence to sign.
Retain the approved version and source data so a later verification request can be answered consistently.
Organise item identity, supplier records, component evidence, calculation and declarations in a controlled file. Protect commercially sensitive information appropriately.
If a question is raised, identify what is requested and use the official response route. Preserve the original submitted statement and explain the actual basis truthfully.
Do not create new facts or alter records to maintain a category that the evidence does not support. Obtain specialist advice for consequential disputes or corrections.
The response should distinguish verified evidence, interpretation and requested clarification.
Review the actual contractual local-content commitments and evidence requirements during supply or service delivery. Do not assume the declaration matters only at bidding.
If components, suppliers or scope change, refer the impact to the contract owner and competent reviewers before committing to the change.
Use the required formal approval and record process. Keep technical configuration, purchasing and contractual evidence aligned.
This protects truthful performance rather than relying on a certificate that no longer describes the delivered item.
Summarise applicability, offered-item identity, supported classification, required evidence, preference mechanism and commercial consequences. List unresolved questions and owners.
Have technical, finance and procurement reviewers confirm their parts. The final uploader should not decide classification from a dropdown without a reviewed basis.
Keep the note with the approved bid and transfer relevant commitments to operations after award.
A short accurate record is more useful than a long policy summary that never connects to the product being supplied.
Do not equate an Indian bidder with an automatically qualifying product. Do not reuse a certificate for a different configuration. Do not assume preference guarantees award or removes pricing discipline.
Another error is using an old policy summary without checking item-specific requirements. A final one is failing to reassess content after a supplier change.
Prevent them with product-specific evidence, competent calculation review and a clear preference-method record.
Where several items are supplied, identify the treatment required by the governing method. Keep the item-level evidence and any reviewed aggregate result traceable.
Do not assume a high-content component makes every other item qualify separately. Do not average percentages casually when the actual basis requires a different calculation.
Have technical staff reconcile the package configuration and the competent reviewer confirm the applicable method.
The declaration should describe its actual scope, including any unresolved item question before submission.
Sales can record that a reviewed policy position is relevant to the opportunity. It should not forecast an assured contract merely because the business expects preference treatment.
Identify the applicable procedure, other qualification conditions and required commercial decision. A price-matching step may need a separate finance and management review.
Keep hypothetical scenarios labelled. Do not invent competitor classifications or evaluated prices to produce a confident win prediction.
The policy review supports an informed bid decision, not an award promise.
Tell purchasing which configuration and supplier evidence support the submitted claim. Require review before a substitution that could affect technical compliance or local-content position.
Record the proposed difference, cost effect and required formal action. A cheaper component can create a larger contractual problem if it undermines the offered classification.
Have the appropriate reviewers assess the change and retain the actual decision. Do not assume a catalogue edit changes the accepted contract.
The supply delivered should remain consistent with the reviewed claim or its formally authorised amendment.
Keep country-of-origin information, local-content evidence and MSE or startup status as different fields. They can coexist, but each answers a different procurement question.
Do not substitute one certificate for another merely because all are issued in India or describe business eligibility.
Use the actual tender's requirement map to connect each field to evidence and treatment. Resolve material ambiguity through official guidance and qualified review.
This makes combined policy preparation easier because the team can see exactly what is claimed and what supports it.
Give purchasing the approved configuration and relevant content-evidence constraints before it commits a supplier change.
No. Review the offered item and applicable definition separately.
Check relevant nodal and tender-specific requirements.
Use the actual procedure and evaluation conditions; do not assume a guarantee.
They address different claims.
Yes, where it can affect the supported calculation or commitment.
Prepare a product-specific classification and preference review before bidding. Explore BidQuest for discovery and verify the actual current policy and tender provisions.
Department for Promotion of Industry and Internal Trade. Accessed 12 Oct 2026.

Understand when MSE bid-security or EMD relief may apply, what documents tenders request, and why registration alone is not a universal exemption.
Read the guide
Compare Udyam, GeM seller onboarding and NSIC SPRS for Indian MSE bidders, with a decision matrix, evidence checklist and tender-specific caveats.
Read the guide
Some procurement provisions reserve specified items for relevant MSE sourcing, but the actual current list, product description and applicable buyer framework must support the claim.
Read the guide