<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Documentation on PaperPackLog</title><link>https://paperpacklog.com/en/tags/documentation/</link><description>Recent content in Documentation on PaperPackLog</description><image><title>PaperPackLog</title><url>https://paperpacklog.com/logo.png</url><link>https://paperpacklog.com/logo.png</link></image><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 03 Jun 2026 08:30:00 +0900</lastBuildDate><atom:link href="https://paperpacklog.com/en/tags/documentation/index.xml" rel="self" type="application/rss+xml"/><item><title>PPWR Asks for Proof, Not Promises: Six Documentation Packages for Export Packaging (2026-06)</title><link>https://paperpacklog.com/en/posts/ppwr-proof-not-promises-export-documentation-2026-06/</link><pubDate>Wed, 03 Jun 2026 08:30:00 +0900</pubDate><guid>https://paperpacklog.com/en/posts/ppwr-proof-not-promises-export-documentation-2026-06/</guid><description>With EU PPWR application set for 2026-08-12, the regulation is settling toward proof rather than promises. This post organizes the six documentation packages a Korean export-packaging supplier should have ready at the SKU level.</description></item><item><title>When PPWR and EPR Become Export Risks: A Support-Workflow Checklist for Korean SMEs</title><link>https://paperpacklog.com/en/posts/ppwr-epr-export-risk-sme-support-checklist-2026/</link><pubDate>Fri, 22 May 2026 07:15:00 +0900</pubDate><guid>https://paperpacklog.com/en/posts/ppwr-epr-export-risk-sme-support-checklist-2026/</guid><description>With EU PPWR general application starting August 2026, this guide covers the practical workflow for Korean SME exporters: how to use KOTRA, export support programs, and testing bodies by role, and how to build packaging document folders, verify EPR responsibility, and prepare consultation question sheets step by step.</description></item></channel></rss>