Mexico NOM Certification: 5 Reasons Shipments Get Stuck at Customs

2026-11-06 · Mexico · NOM · 8 min read
The short version: when a Mexico NOM shipment stalls at customs, the product has rarely failed testing — the paperwork does not line up. The label is missing Spanish. The issuing body's scope does not cover your product category. The certificate holder and the importer of record are not the same RFC entity. A wireless product has NOM but no IFT. Or the model on the report differs from the model on the carton by a single letter.

Conformity gets you through the door. What decides whether the container actually ships is the document chain: certificate, label, invoice, bill of lading and HS code — five documents pointing at the same product, the same company, the same tax ID. Break one link and customs has grounds to leave the goods sitting in the yard.

This article is not "what NOM is". For the framework and the list of standards, start with the Mexico NOM knowledge base entry; what follows is only the detail you learn the hard way, set out in the order of the late-night calls I have taken from clients over the years.

Note: every standard number in this article (NOM-001-SCFI-2018, NOM-029-ENER-2017, NOM-050-SCFI and so on) is subject to the currently valid version. Mexico issues amendments and supplementary notices fairly often, so before you start, have the certification body or the importer confirm which text applies today — do not work from a draft that is two years old.

1. Labels in Chinese and English only, with not a word of Spanish

This one is extremely common, technically trivial, and it genuinely stops shipments. The product is fine and the tests passed, but by the time the goods reach Manzanillo or Lázaro Cárdenas, customs looks at the packaging and finds Chinese and English — not one word of Spanish.

Under the NOM framework, labeling and instruction information has to be in Spanish, and must carry the NOM mark and certificate number (commercial labeling generally follows NOM-050-SCFI-type requirements, subject to the currently valid version). Many people assume that sticking a NOM logo on the box is enough. What actually gets checked is whether the information is complete, legible and consistent with the certificate:

  • Do the product name and model match the certificate?
  • Are the importer's name, address and RFC printed — and printed correctly?
  • Do the electrical ratings (input voltage, current, power) match the report?
  • Is the country of origin marked?
  • Are the warnings and instructions in Spanish?

Three ways this goes wrong in practice: first, the outer carton and the inner box disagree — the color box was redone in Spanish, but the plain outer carton is still the old version; second, the printed certificate number belongs to the previous certificate and was never updated after the renewal or the change; third, the manual is a PDF translation printed as-is, with the terminology mistranslated — "adapter" turned into some other product category — and if customs cannot make sense of it, it may as well not be in the box.

Note: do not sign off the label on your own. Send the color box, the rating plate, the manual and the outer carton — all four artwork files — to the certification body and the Mexican importer for joint confirmation, then archive a single PDF version plus sample photos. Later, when someone asks which version you filed at the time, you can produce it.

2. The wrong certification body — and the certificate is worthless in your hand

Issuing a Mexico NOM certificate is not a matter of "find a lab, run the test, print a certificate". In framework terms, it is regulated by DGN under the Ministry of Economy (SE) and issued by certification bodies (organismo de certificación) such as NYCE and ANCE. Sounds straightforward. The trap is the word "scope".

Each certification body is accredited for a limited set of product categories and standards. If the NOM standard version that applies to your product falls outside the scope accredited to the body you picked, what you get back looks like a certificate but is not actually recognized. I have seen this more than once: the client is delighted with the certificate, the forwarder submits the documents, the Mexican side's system cannot find it — or finds it but the standard does not match — and the whole container comes back for a redo.

There is a subtler version of this too: treating a test report as a certificate. CB reports, CE reports and FCC reports from foreign labs are test evidence, not NOM certificates, and no substitute for one. They can cut some repeat testing, but they do not let you skip the issuance step.

How to avoid it:

  • Before you start, confirm three things — which version of the NOM standard your product falls under, which body holds that standard in its accredited scope, and whether the importer's details will appear on the certificate;
  • After issuance, look the certificate number up yourself on the body's website and keep a screenshot;
  • Any time you change body, standard or scope, confirm again — do not carry over what worked on the previous order.

One thing that is easy to mix up: Brazil runs on the ANATEL system (see the Brazil ANATEL entry), Mexico on NOM. Do not reuse a single document template across the two countries — the language, the certificate holder and the regulator are all different.

3. Importer and RFC do not match — so the certificate is not "yours"

This one, I think, is the quietest trap of the lot, because nothing errors out along the way — until the day of clearance.

In framework terms, the NOM certificate holder must be a Mexican company — a Mexican entity with an RFC (tax registration number). A Chinese factory has no Mexican entity of its own, so it appoints a local importer to hold the certificate. The problem is that the company you appoint and the company that files the entry are often not the same:

ScenarioHow it looksWhat actually happens
Company A holds the certificate, Company B files the entryBoth are Mexican companies, both have an RFCCertificate and importer of record do not match; a supplementary explanation is usually requested
Two entities in the same group, different RFCsSame group, near-identical namesDifferent legal entities, treated as different importers
Agent changed, certificate notThe new agent says it can clear the goodsThe certificate still carries the old company name; the chain is broken
RFC spelled differently from the invoice or bill of ladingMissing one "S.A. de C.V."Documents inconsistent; the entry is returned for verification

One three-way comparison you must run before shipment: put the company name and RFC on the certificate, the buyer on the commercial invoice and the consignee on the bill of lading side by side and compare them word for word — including suffixes such as S.A. de C.V., "&" versus "Y", abbreviations versus full names. All three must be identical; if they are not, fix the documents. Do not count on explaining it away at the port.

Note: if your channel ships to a US warehouse first and then into Mexico, or imports under a distributor's name, the certificate holder and the actual importer are very likely not the same party. That structure has to be settled before certification starts; changing the certificate afterwards means paying the lead time and the cost all over again. If you want to talk the structure through, contact us and we can map the chain out together.

4. Wireless features covered by NOM alone, with no IFT

NOM covers electrical safety, energy efficiency and commercial labeling. Radio is not part of its remit.

If a product contains any radio transmitting function such as Bluetooth, WiFi or Zigbee, Mexico additionally requires type approval from IFT (the Federal Institute of Telecommunications). These are two separate tracks: a NOM certificate cannot stand in for IFT approval, and IFT approval cannot stand in for NOM. A wireless product needs both.

Conversely, if your product genuinely has no radio function — a power bank with USB output only, say, or an adapter with a pure DC input — then IFT does not apply and you can cross this line off. That is exactly why exporting power banks to Brazil and Mexico notes that "no RF saves a large block of lead time". The question is whether the product actually transmits radio, not whether the word "Bluetooth" appears on the box, and not whether it runs on a battery.

Three questions to ask yourself:

  • Is there a radio module in the BOM? Bluetooth, WiFi, 2.4G remote control and wireless charging all count;
  • What are the frequency bands and the transmit power? The IFT application asks for both;
  • If you use a "pre-certified module", does that module's approval cover your finished product? Ask the body — do not assume it does.

For Bluetooth products, you can plan alongside the Bluetooth product solutions and multi-country radio routes; for the US side of the radio logic you can cross-reference the FCC entry, but do not carry conclusions from one market over to the other.

5. Assuming a report can be reused when the test scope does not line up

"We already have a CB report — can we just use it?" Someone asks me this every day. The answer: it can save some testing, but it does not save you the issuance step, and it does not save you the Mexico-specific differences.

When reuse goes wrong, it is usually one of three situations:

  • Standard version mismatch: your report was issued to one edition of IEC while Mexico currently references another, so the national difference clauses are missing. This one is time-consuming, because it means retesting.
  • Model naming mismatch: the report carries the factory's internal code while the carton and rating plate carry the market model; or a series was filed with three models and the fourth is the one that actually ships. File the series list complete, in one go.
  • Critical components changed without notification: a different adapter supplier, a different cell manufacturer, a different fuse rating, a different housing material — in certification terms these are all "changes", and if they go unreported, the certificate no longer matches the actual product.
Note: at certification time, pin the critical component list (CKL) down as a contract annex — manufacturer and model for adapters, cells, fuses, optocouplers, transformers and housing material, in writing. If purchasing later wants to switch something, check with certification before placing the order — do not find out at mass production that a re-filing is needed. This comes up especially often with power adapter solutions.

6. Energy efficiency gets left off the list

A lot of people read NOM as "one safety certificate" and miss the energy-efficiency branch entirely.

In framework terms, AC adapters and external power supplies shipped with the product usually have to meet energy-efficiency NOM requirements as well (the one usually cited is NOM-029-ENER-2017, subject to the currently valid version). Note the keyword here: "bundled". The main unit can be finished while the 5V/2A adapter in the box is not — and that still counts as a missing item.

The reverse is worth saying too: the product itself does not necessarily fall under an energy-efficiency standard. A power bank body, for example, generally does not follow the adapter efficiency regime, but the bundled AC adapter is assessed separately. Do not draw that boundary yourself — let the body determine it from the packing list of what you actually ship.

Practical advice: open the shipping packing list, circle every component with a plug or an AC input, and ask of each one, "does this need energy efficiency?" Adapters, charging cradles and power cords with adapter heads all count.

7. The test sample and the model do not match

This one hurts, because the standard is not at fault and the body is not at fault — it is purely an internal misalignment.

Test samples have to be units that represent mass production. What actually happens: engineering sends a hand-built sample while mass production runs a different PCBA revision; or model A is submitted while the customer orders model B, which differs only in color — except the color comes with a different housing material and a different flame rating.

A few concrete steps:

  • Before sending samples, take six-side photos plus a close-up of the rating plate, including the PCB silkscreen, and archive them;
  • Keep one sealed retention sample, labeled with the date, model, firmware version and critical component batch;
  • Compare the first mass-production unit against the retention sample once, especially the silkscreened electrical ratings — 100-240V input versus 120V; customs and bodies both look at that kind of difference;
  • Standardize model naming: internal code, report model, rating plate model and invoice model — the four names must map to one another, so build a cross-reference table.

It sounds minor. When something does go wrong, that one model cross-reference table can save you two weeks of back-and-forth explanations.

8. No timeline calculation, and the goods land before the certificate

For conventional products, the NOM lead time is roughly 4–8 weeks, at a cost broadly in the USD 3,000–8,000 range. A certificate usually runs for 5 years, with periodic surveillance audits in between. Treat both figures as a range reference — the actual specifics are subject to the certification body's assessment, and depend on the product category, the number of standards, whether retesting is needed and how complete the documents are.

In real projects, though, the time rarely goes into testing alone. Delays usually come from:

  • Documents going back and forth: the label is not finalized, the critical component list has gaps, the manual is not in Spanish — one round trip is three to five days;
  • Body scheduling: capacity tightens around year-end and long holidays (Mexican statutory holidays, Chinese New Year);
  • Retesting: the reused report is missing clauses, so one extra test item means rescheduling;
  • Certificate holder not settled: the importer has not signed, the certificate cannot be issued in anyone's name, and everything stalls;
  • Certificate effective date out of step with the sailing schedule: the certificate is not out, the container is already at port, and storage and demurrage charges burn by the day.
Note: do not plan backwards from 8 weeks — plan from 12 weeks. Use the first 2 weeks to finalize models, labels and the critical component list (no body involvement needed, but this is what decides whether the rest runs smoothly), the middle 4–8 weeks for testing and issuance, and keep the last 2 weeks for three-way document alignment and shipment. Building in buffer is not conservatism; it is the industry norm.

9. A 5-step action checklist

Here are the eight points above, compressed into actions, in order:

StepActionOutputPass criteria
1 Fix the designLock model naming, the critical component list and the four label artwork filesModel cross-reference table + CKL + label PDFsInternal code / report model / rating plate / invoice all map one to one
2 Fix standard and bodyConfirm the applicable NOM standard version, and that the body's accredited scope covers that standardWritten confirmation of standard and bodyThe body states explicitly that it can issue for this standard
3 Fix the entitySign the Mexican importer and obtain the RFC and full company nameRFC + company name + addressCertificate holder, invoice buyer and bill-of-lading consignee are identical in all three places
4 Work the parallel branchesRadio goes through IFT, bundled adapters go through energy efficiency, lithium batteries need UN 38.3IFT approval / efficiency report / UN 38.3 reportEvery branch has a clear owner and a named responsible person
5 Align and archiveAlign the HS code with the customs declaration, archive the documents, set an expiry reminderArchive package + certificate validity reminderCertificate code = declaration code; renewal triggered 3 months before expiry

The HS code point in step 5 deserves separate emphasis: the HS code declared on the NOM certificate must match the customs declaration. Mexican enforcement has watched this closely in recent years; if the codes do not match, the certificate and the goods are two different things. If you are unsure of the tariff number, get written confirmation from the customs broker — a verbal check is not enough.

And for lithium battery products, do not forget UN 38.3 — it is a hard precondition at the transport stage (IATA/IMDG Class 9), required for both air and sea; without that report the forwarder will not take the cargo. It is a separate matter from NOM, and neither can substitute for the other. Subject to the currently valid version.

Final thoughts

In the Mexican market, the barrier is not "can the product pass testing". After all these years, the products that genuinely fail are few; what stalls is nearly always a misalignment in the document chain — a label missing one foreign language, a body missing one line of scope, a certificate holder and an importer of record that are not the same company, a wireless product missing one branch, a report model missing one suffix.

These misalignments share one trait: none of them is expensive, but all of them are slow. Fixing a label costs a few dozen dollars; rescheduling a test costs four weeks. That is why sequence matters more than effort — fix the design and the entity first, then talk about testing. Do it the other way round, and the two weeks you saved up front come back as two months later.

If you have a product heading into Mexico right now, tell me four things — product type, whether it is wireless, whether an adapter is bundled, and in whose name you plan to import — and I will walk through the five traps one by one and show you where your route is likely to break first.

▍Questions about this article? Leave a comment or message me, with "Mexico NOM" in the note.

▍One-line value proposition: Get the certification path right the first time, and save the return trips.

Related reading: Mexico NOM knowledge base | Exporting power banks to Brazil and Mexico | Brazil ANATEL | US FCC | Certification quick lookup

CertFastLine | Export Certification & Testing & Management Systems Consulting Statement: this article is compliance education and shared experience, not legal advice, and does not constitute any commitment regarding certification or customs clearance outcomes. NOM standard numbers, energy-efficiency requirements, certificate validity and cost/lead-time ranges are all subject to the currently valid version and the certification body's assessment; execution is subject to the current requirements of Mexico's Ministry of Economy (SE), DGN, IFT and the issuing certification bodies, and you are advised to confirm the actual practice at your port of entry with your Mexican importer.

Not sure which certifications your product needs?

Tell us your product type, whether it has wireless features and your target markets for a free certification route plan

📞 Free Consultation