A SABER certificate works the same way wherever the goods are made. What changes when the exporter is Indian is everything around it — which of your test reports will be accepted, what your BIS licence is worth in Riyadh, whose factory the certificate names when you are a merchant exporter, and how much of your week overlaps with your importer's.
Four things Indian exporters get wrong:
There is no Indian version of a SABER certificate. It is issued in Saudi Arabia, to your Saudi importer, by a conformity body holding SASO approval for your product regulation. Nothing about that changes because the goods left Nhava Sheva rather than Shanghai.
What changes is the work that happens in India before it. Indian exporters arrive with a specific set of assets and a specific set of assumptions — NABL reports, a BIS licence, a contract manufacturer, a domestic carton design, an invoice written for DGFT — and each of those meets the Saudi file differently. This page is about those meetings, because that is where Indian files stall.
Everything here is specific to exporting from India. None of it appears on a generic SABER page, and all of it has cost an Indian exporter money.
An Indian laboratory report is accepted on the same terms as any other: ISO/IEC 17025 accreditation covering the specific standard, under an ILAC mutual recognition arrangement. NABL accreditation qualifies. What fails is a report from a lab accredited for adjacent tests, or an in-house report on lab letterhead.
ISI marking and BIS registration evidence conformity to Indian standards under Indian law. Saudi Arabia assesses against Saudi technical regulations. The underlying test data sometimes transfers; the certificate and the mark never do, and assuming otherwise is the most expensive assumption Indian exporters make.
Contract manufacturing and job work are ordinary in India and awkward on a certificate. The site that made the goods is named in the scope, so moving a production run to a second unit mid-season makes that run uncertified even though the product is identical.
If you buy from a manufacturer and ship under your own name, the technical file, the test reports and the factory access all sit with someone else. The certificate still requires them, so the commercial relationship has to be arranged to release them before the file starts.
Certificates of origin are issued by an Indian chamber and then authenticated. It happens in India, before the goods sail, and it cannot be retrofitted from Riyadh once a consignment is sitting at the port.
Indian production lines print cartons and labels well ahead of dispatch. Arabic content, the energy label and origin marking have to be settled before that print run, or the correction is a reprint of the whole order.
The Saudi week runs Sunday to Thursday. Friday is their weekend and your working day; Sunday is the reverse. Anything needing a same-day exchange between your factory, us and a Saudi importer has four usable days, and a file planned on five will slip.
Indian export invoices are often written for DGFT and drawback purposes, with descriptions that do not match the Saudi heading the certificate was issued against. Saudi clearance compares the two, and a description written for one audience fails in front of the other.
Worth reading in full if a Saudi tender has been answered on the strength of Indian certification. The two columns share almost nothing but the word certificate.
The answer decides who has to cooperate for the file to proceed — and whether that cooperation needs negotiating before you quote.
You own the plant, the drawings and the test reports.
The straightforward case. The technical file already exists in-house, the factory can be audited where the scheme requires it, and additions to the model list are yours to make.
You buy finished goods and export under your own invoice.
Agree evidence access with the manufacturer in writing before you quote. The certificate scope names their factory, so a supplier who will not release the technical file or admit an auditor cannot be certified through you.
Your brand, somebody else’s production line.
Brand and model list are certified together. Where several brands come off one line, they can often share evidence, but each brand still has to appear in the scope that reaches the border.
The same product made at more than one Indian site.
List every site that might produce the order at the outset. Adding a unit later is an amendment, and a consignment made at an unlisted unit is uncertified regardless of how it was made.
Eight inputs, gathered in India. Two of them belong to your manufacturer rather than to you, which is why merchant exporters should read this list before accepting an order.
Every one of these is recoverable early and expensive late. Five of the six are settled before a single sample is despatched.
A tender answered on the strength of BIS approval, with SASO discovered afterwards. The gap between them is measured in weeks of testing, not in paperwork.
A merchant exporter finds out at certification that the manufacturer treats drawings and reports as confidential. Nothing proceeds until that is renegotiated, usually at a worse price.
Capacity shifts to another plant to meet a delivery date. The goods are identical, the unit is not on the certificate, and the consignment arrives uncertified.
A full season of packaging printed without Arabic content or the energy label, because artwork was signed off on the Indian domestic version.
A four-day approval chain scheduled as though both sides work the same week. Each handover that lands on a non-shared day costs a calendar day nobody budgeted.
The certificate of origin is complete but not authenticated. It is an India-side task, and there is no way to complete it once the goods are at a Saudi port.
The wider India to Saudi lane, the consultant question, and the two steps Indian files most often stall on.
Test reports, BIS, merchant exporting, cost and timelines from India.
The certificate itself is issued in Saudi Arabia, to your Saudi importer, by a conformity body holding SASO approval for your product regulation. What happens in India is the preparation: confirming the HS code, testing at an accredited laboratory, assembling the technical file, settling Arabic artwork and getting the certificate of origin issued and authenticated. An Indian exporter cannot hold the certificate in its own name.
Yes, where the laboratory holds ISO/IEC 17025 accreditation covering the specific standard being tested, under an ILAC mutual recognition arrangement. NABL accreditation meets that description. Acceptance turns on the scope of accreditation rather than on the country — a report from a lab accredited for a neighbouring test is refused wherever it was issued.
Not as a certificate. BIS attests conformity to Indian standards under Indian law and carries no weight in a Saudi assessment. Where it helps is indirectly: the product has already been through accredited testing, so the data and the sample history exist, and some of that testing may be reusable if it was run against a standard the Saudi regulation also cites.
Yes, but only with the manufacturer’s cooperation. The certificate scope names the production site, and the assessment needs the technical file, the test reports and — where the scheme requires it — access for an audit. Agree that access in writing with your supplier before you quote a Saudi buyer, because it is the step that most often stops a merchant export file.
The certificate fee is a small part of it. The cost is driven by whether accredited testing already exists, how many models and variants the scope has to carry, whether the regulation requires a factory audit, and whether artwork has to be reworked. Two exporters shipping the same product can differ by a multiple on those four alone.
Where valid accredited test reports already exist, the certification step is usually a matter of weeks. Where testing has to be commissioned, the laboratory queue governs the timeline and it is materially longer. Plan around the shared working days too — India and Saudi Arabia overlap on four days a week, not five.
It is issued by an Indian chamber of commerce and then authenticated for use in Saudi Arabia. Requirements vary with the document type and the counterparty, and Saudi Arabia’s accession to the Apostille Convention has changed the route for some documents while commercial documents still begin with chamber attestation. Confirm the exact route per consignment before the goods sail — it cannot be completed afterwards.
No. A SABER certificate is a Saudi certificate. Other GCC states run their own conformity regimes, and while the G-Mark is a Gulf-wide marking for some product families, it is not a substitute for each country’s own requirements. Budget separately for each market you quote.
Electrical goods and fittings, cables, lighting, building and construction materials, chemicals and paints, auto components, toys, textiles and home appliances all commonly fall under Saudi technical regulations. Food, cosmetics and medical goods route to SFDA instead, which is a different process entirely rather than a harder version of this one.
Yes. The file work is document-led, so location within India makes little difference to how it runs. What does need arranging locally is laboratory sample despatch and, where the regulation calls for it, the factory audit at the site that will actually produce the goods.
The product, the HS code, whether you own the factory and what testing already exists. That is enough for us to tell you what your Indian file actually needs — and what it does not.