KC, RF, Electrical Safety, Batteries & BESS –One Wrong Label Can Stop Your Shipment at Korean Customs ③
- HOSOON CHOI

- Nov 16
- 6 min read
Updated: Nov 17
When you ship IT and power equipment into Korea, three questions will come up sooner or later:
Published on: November 16, 2025
Author: Hosoon Choi (Strategic Logistics Expert | Certified Logistics Manager, Licensed Bonded-Area Customs Specialist, PMP, MBA)
"Logistics that speaks through data" – Insight from Korea’s strategic logistics frontline

When you ship IT and power equipment into Korea, three questions will come up sooner or later:
“Do you have KC?” “What about RF approval?” “How is the battery certified?”
Most exporters answer: “Yes, we have it.” The problem is: that’s where the trouble often starts.
This article explains, from a Korean IOR/EOR and logistics perspective,
how KC / EMC / RF / electrical safety / battery & BESS regulations actually affect imports,
where shipments get held at customs or by inspection bodies, and
when it is much safer to bring in a Korean IOR specialist early.
1. Why KC / RF / Electrical Safety / Battery Are a “3+1 Package” for Korea
For AI data centers and high-density IT projects, you typically ship:
IT / telecom equipment: servers, switches, routers, firewalls, gateways, Wi-Fi APs
Power equipment: PSU, PDU, rack-mount UPS, standalone UPS
Energy storage: rack-level ESS, container-type BESS
Accessories: monitoring units, sensors, wireless modules, cables, etc.
From a Korean regulatory point of view, these map roughly to:
KC Safety / KC EMC (Electromagnetic Compatibility)
RF (Radio) approval
Electrical safety (AC power, UPS, PDU, etc.)
Battery / ESS / BESS standards + installation regulations
The challenge is that modern equipment is increasingly integrated:
servers with built-in wireless modules,
UPS with large lithium-ion packs inside,
rack-level ESS turning into container-size BESS.
So what looks like “one box” to you can look like “several regulated products in one box” to Korean customs and authorities.
If you are designing an IOR/EOR structure for Korea, you cannot treat “server + UPS + battery + RF module” as one simple item. You need to unpack:
What exactly is inside this chassis, and how is each component certified?
2. Servers & Network Equipment – KC/EMC and RF Together
Typical IT equipment into Korean data centers:
GPU servers, general servers, storage appliances
switches, routers, security gateways, firewalls
Wi-Fi APs, LTE/5G gateways, IoT edge devices
2.1 KC Safety vs KC EMC vs RF
In practice:
KC Safety (Electrical Safety)
Products directly connected to AC mains: PSU, adapters, some UPS, etc.
KC EMC (EMI/EMC compliance)
IT/telecom devices’ electromagnetic emissions & immunity
Servers, switches, routers, etc. generally fall here.
RF Approval (Radio)
Devices with Wi-Fi, BLE, LTE modules, etc.
Wi-Fi APs, wireless gateways, some management modules.
Most exporters know these three in theory.Real trouble starts at module level.
2.2 The “Module” Trap
Examples we see often:
The chassis has KC/EMC certification,
but the internal RF module is certified under a slightly different model name,
and shipping documents (invoice, packing list, spec sheet) use yet another variant.
Korean customs or test labs will ask:
“Is this RF module exactly the same as in this RF certificate?”
If the answer is not crystal clear, you lose time.
That’s why, when planning an IOR structure, we recommend working at BOM level:
For each server chassis, list which PSU and which RF module is inside.
For each component, map which certificate (KC/EMC/RF) covers it.
If you don’t do this before shipping,you may have to “prove equivalence” after arrival—with your shipment waiting at the port.
3. Power Line Issues – PSU, PDU, UPS Quietly Create Problems
In many projects we see:
server certifications: perfect,
network gear: solid,
and then the power line breaks the schedule.
3.1 PSU (Power Supply Units)
If the PSU is permanently integrated into the server and certified together, it’s usually fine.
But if you ship separate or optional PSUs:
they may be viewed as separate electrical products,
and therefore require their own safety assessment or documentation.
3.2 PDU (Rack-mount Power Distribution Units)
PDUs often look like “just a fancy power strip”, but in Korea, authorities care about:
rated voltage and current,
overload protection,
plug/socket type,
grounding and safety markings.
If PDU labels and documents are not aligned, a single PDU model can delay an entire container.
3.3 UPS – Where Power and Battery Regulations Meet
UPS units have a “combo” nature:
AC electrical product,
containing large lithium-ion or lead-acid batteries,
sometimes with network / monitoring modules.
This means electrical safety + battery standards + EMC (+ sometimes RF) may all apply.
If you do not define up front:
How is the UPS certified?
Are internal battery packs treated as separate products?
then Korean customs and inspection bodies will force you to answer those questions after arrival,with the clock ticking.
4. Lithium-ion Batteries – Cell / Module / Pack / System
In AI and data-center projects, batteries are no longer accessories:
rack-mount UPS,
rack ESS,
building- or campus-scale BESS.
Think in four levels:
Cell
Module (group of cells)
Pack (with BMS, protection, housing)
System (rack, cabinet, container)
At each level you need to think about:
safety / performance standards (e.g. IEC/KS 62619 etc.),
transport regulations (UN38.3, dangerous goods),
post-installation regulations (ESS/BESS fire safety guidelines, building & fire codes).
The problem: many projects describe all that in one vague line:
“Battery modules 16EA”,“Rack-mount ESS set”, “UPS 10kVA x 20EA”
For exports to Korea, your IOR/EOR configuration must clarify:
where “equipment import” ends, and
where facility / installation / fire-safety regulations begin.
5. When BESS Is Involved, You Are Shipping a Facility, Not Just a Product
BESS (Battery Energy Storage Systems) in Korea:
are not seen only as “big UPS boxes”,
but as hazardous energy facilities with strict fire and building constraints.
Once you go to container-type or large-scale BESS, you face:
foundation and civil works,
fire compartments,
ventilation and gas handling,
detection & suppression systems,
remote monitoring and emergency shutdown.
From a Korean perspective, your container is close to a “small building plus energy system”.
For IOR/EOR planning, the key questions are:
What will this BESS be classified as in Korea?
Do you only need import-level documentation,or do you need to check local fire/building/ESS guidelines in advance?
How will you split responsibility betweenexporter, Korean IOR, local installer, and final ownerfor safety, permits, and post-installation issues?
At this point, the IOR is no longer just a “paper importer”.You need someone who understandshow equipment regulations and facility regulations connect in Korea.
6. Top 5 Label & Documentation Mistakes (That Kill Time)
Here are the patterns we see most often in Korean imports:
Model name mismatches
Certificate: ABC123-4
Label: ABC-123-4 or ABC1234 or ABC123-04
Invoice/spec: ABC123 Rev.B→ Each small difference invites questions.
Missing or incorrect KC / RF markings
Only on the carton, not on the device
Mixed SKUs using the same label
Non-standard logos or fonts
Incomplete voltage/frequency info
No clear “100–240V 50/60Hz” marking
Documents list only 110/220 V while label says something else
Battery specs unclear or wrong
V, Ah, Wh not correctly shown
UN38.3 / DG markings missing or inconsistent
Label vs documents not aligned
Label: Model X-100
Invoice: X100 Rev.B
Manual: X100-APAC
Certificate: X100
Explaining that “all of these are actually the same model” can easily consume emails, meetings, and weeks.
7. You Don’t Have to Learn All of This – You Just Need the Right Partner in Korea
If you have read this far, you might be thinking:
“Do we really have to understand KC, EMC, RF, electrical safety,battery, BESS, fire codes, and customs all at once… just to ship to Korea?”
The honest answer is: No. You don’t need to master everything—but you do need to know when to hand it over to a specialist.
That is where I come in.
8. You really don’t have to figure out IOR/EOR alone
For imports of GPU servers, network gear, UPS, BESS and other data-center / AI infrastructure equipment into Korea –
including:
HS / ECCN classification
KC, RF and electrical safety
logistics and permit flows for lithium-ion batteries, ESS / BESS
IOR/EOR structure design (direct import + IOR hybrid models)
I can help you unpack all of this in practical, real-world terms.
Examples of what I can support you with:
First question: “For this project, should we use an IOR model or just go with direct import?”
Mapping out the whole picture when GPU / servers / UPS / BESS are all mixed together:certifications, regulations, customs, bonded movement, on-site installation flow
Organizing how HS / ECCN / KC / RF / battery certifications should be reflected in your contracts, invoices and import documents
Acting as the person who explains to HQ / global vendors “This is how Korea will actually treat this equipment.” – in a way they can accept
Consulting – very simple.
Consultation is free.
Even if your only question is:
“Is this something that really needs an IOR model, or can we just go with normal direct import?”
— that’s perfectly fine.
Time zones don’t matter. You can leave me an e-mail or message any time, 24/7, 365 days a year, and I’ll review it and get back to you as quickly as I can.
If one blog post could solve every case, you honestly wouldn’t need me at all.
But in the real world, the moment equipment / project / country / regulations start to mix, “exception case” becomes the default.
The moment it starts to feel complicated, you can simply hand it over to a specialist.
My job is to take your messy situation and translate it into language that the buyer, vendor, customs and permitting authorities can all understand and agree on.
If, while reading this, you thought
“This sounds exactly like our project…”
then right now is a perfect moment to send me that first e-mail. 😉

![[HCI Opinion] "Roadmap for Industrial Safety and Logistics Innovation Based on the Ulsan AI Data Center"](https://static.wixstatic.com/media/4ddd7d_db550b7e63bb4a7fa0c240d7987c7ec8~mv2.png/v1/fill/w_980,h_653,al_c,q_90,usm_0.66_1.00_0.01,enc_avif,quality_auto/4ddd7d_db550b7e63bb4a7fa0c240d7987c7ec8~mv2.png)
Comments