On May 1, 2026, the RCEP Digital Certificate of Origin Platform was officially connected to the Indonesian Customs Digital Certification Gateway (INACOG). This signifies that Chinese exporters to Indonesia must have an Indonesian (IDN) version of the Certificate of Origin page on their official websites and achieve bidirectional API integration with the e-CO system. This adjustment directly impacts exporters in the machinery and electronics, light industry, textiles, agricultural products, and cross-border e-commerce sectors targeting the Indonesian market, as it directly relates to the efficiency of automatic issuance of electronic certificates of origin and customs clearance compliance. It is the first practical requirement explicitly targeting enterprise-level website technical capabilities in the implementation of RCEP rules.

Event Overview

Following the launch of the RCEP ASEAN e-CO system on April 29, 2026, the system will be officially connected to the Indonesian Customs Digital Certification Gateway (INACOG) starting from 00:00 on May 1, 2026. Chinese exporting companies to Indonesia must support Indonesian (IDN) versions of their declaration of origin pages on their official websites and complete bidirectional API integration with the e-CO system to ensure that overseas buyers can download pre-certified electronic certificates of origin (e-CO) from Indonesian customs with a single click. This capability requires multilingual structured data generation, cross-border electronic signature verification, and real-time customs status feedback.

Which sub-sectors will be affected?

Direct trading enterprises

For companies exporting to Indonesian end customers or distributors via B2B, their official website is the primary entry point for buyers to obtain the declaration of origin. Without IDN language-specific pages and API integration, buyers will be unable to download the pre-certified e-CO themselves, potentially delaying customs clearance, triggering manual review, or losing eligibility for RCEP tariff preferences.

Processing and manufacturing enterprises (including OEM/ODM)

Although they do not directly sign contracts with overseas buyers, they are often required to provide compliant documentation on their official websites that meets the requirements of the importing countries. Indonesian importers are increasingly including "whether or not a supplier has an INACOG-compatible website" in their supplier qualification assessment, affecting order allocation and long-term cooperation eligibility.

Cross-border e-commerce platforms and independent website operators

For Chinese independent websites operating locally in Indonesia, if the country of origin declaration module on the product page is not output in a structured manner according to IDN language and does not embed the e-CO status query interface, it will not be able to meet the Indonesian customs' digital verification requirements for "transaction as certificate", which may affect the listing of products or the weight of traffic distribution.

Supply chain service companies (including customs brokers and certificate of origin agencies)

The traditional paper-based Certificate of Oath (CO) agency model is facing pressure to be replaced. Its service value is shifting from "filling out and stamping on behalf of clients" to "system integration support," requiring assistance in completing website upgrades, API integration testing, and customs status feedback tests. Technical responsiveness has become a new service threshold.

What key areas should relevant enterprises or practitioners focus on, and how should they respond at present?

Pay attention to the updates to the INACCOG technical integration white paper released by the Indonesian Customs.

Currently, only the gateway connection has been confirmed, but details such as IDN page field specifications, signature algorithm standards, and status feedback frequency have not yet been disclosed. Enterprises should continuously monitor the official website of the Indonesian Ministry of Finance's General Directorate of Customs (DJBC) and the announcements on the China Council for the Promotion of International Trade's RCEP service platform to avoid blindly developing solutions based on generic multilingual approaches.

Prioritize adapting to key product categories, rather than generalizing the entire site.

Currently, Indonesia's RCEP origin claims for three categories of goods—mechanical and electrical components, household goods, and rubber products—account for over 68% of its total import claims to China (based on RCEP ASEAN e-CO trial operation data in Q1 2026). It is recommended that companies prioritize completing the development of IDN declaration pages and API integration for the corresponding SKUs to control implementation costs and timelines.

Verify whether the existing website building system supports structured multilingual data output.

Basic multilingual switching (such as i18n) is not sufficient to meet the requirements. The key lies in the ability to dynamically generate origin declaration data blocks containing digital signature hashes, issuance timestamps, and customs pre-certification marks according to the Indonesian Customs-specified schema (such as JSON-LD format). This capability verification requires collaboration between the IT team and the website development service provider.

Establish a collaborative verification mechanism with Indonesian importers.

The validity of the e-CO is ultimately determined by the status returned by the INACOG gateway. It is recommended that after completing the integration, enterprises invite key Indonesian customers to access the test link via their local IP addresses to verify whether downloaded files are recognized as "pre-authenticated and valid" by INACOG, rather than simply checking the page display.

Editor's Viewpoint / Industry Observation

Observably, this is not a policy announcement but an operational activation — the first cross-border digital certification gateway under RCEP to mandate enterprise-level website capability as a condition for tariff preference access. It signals a structural shift: preferential trade is no longer secured at the customs declaration stage alone, but embedded earlier in the commercial infrastructure (eg, exporter's website). From industry perspective, it reflects Indonesia's prioritization of import-side automation over exporter-side flexibility. Analysis shows that while the requirement is currently limited to Indonesia, Its technical architecture — particularly the bidirectional API and real-time status feedback — sets a precedent likely to be replicated with other RCEP members' national gateways in 2026–2027.

In conclusion, this connection to the Indonesian node is not an isolated technological upgrade, but a crucial step for RCEP digital rules from a "system framework" to "system coupling." It signifies that the focus of export compliance is shifting from documentation results to enterprises' digital infrastructure capabilities. Currently, it's more appropriate to understand it as a definite task with a clear timeframe, verifiable path, and requiring cross-functional collaboration (foreign trade + IT + legal), rather than a vague policy signal or long-term trend. Enterprises should adhere to the principle of "minimum viable integration," focusing on the core fields of the IDN page and basic API connectivity, avoiding excessive investment in generalized multilingual development.

Information sources include: the official announcement of the RCEP ASEAN e-CO system (April 29, 2026) and the statement from the Indonesian Ministry of Finance and Customs Directorate General (DJBC) regarding INACOG gateway access (effective at 00:00 on May 1, 2026). Areas to be continuously monitored include: the specific field list for IDN language-specific country of origin declarations, mandatory standards for electronic signature algorithms, and transitional arrangements for non-IDN pages.