Brazil's DUIMP Customs Channels: Data Drives the Outcome

Since DUIMP (Brazil’s single import declaration) replaced the legacy DI for most containerized and air cargo, customs channel selection has stopped relying on statistical sampling. Brazil’s Federal Revenue (Receita Federal) now cross-references the attributes declared in the Portal Único Product Catalog, the importer’s history, and the consistency of customs value before assigning a channel. For an operations manager at a freight forwarder, this means the team that reviews the Product Catalog before filing the DUIMP directly influences which channel the cargo receives, and each channel changes the timeline, the workflow, and the cost of the shipment.

DUIMP channel selection evaluates declared data

Under the legacy DI, channel assignment followed mostly statistical criteria: a percentage of declarations was routed to inspection, and the importer had no practical way to anticipate the outcome based on what was declared. Under DUIMP, that logic changed. The Receita Federal cross-references the product attributes registered in the Portal Único Product Catalog with the declaration data, and the consistency between the two weighs in channel selection. An HS code with incomplete attributes, a customs value outside the expected range for that classification, or a mismatch between the Catalog entry and the commercial invoice all increase the likelihood of the cargo leaving the green channel.

The Receita Federal’s risk management framework still considers the importer’s profile, the origin of the goods, and the transaction value, as it always has. Product Catalog data quality entered the equation, and that is the component the operations team controls before filing.

What each channel demands from the operations team

The channel a DUIMP receives at selection defines what the operations team needs to do and how long the shipment sits at the bonded terminal.

Green channel releases cargo without inspection, and clearance can happen on the same day the declaration is filed, as long as there is no pending regulatory approval. The operator monitors the system, confirms clearance, and arranges removal. This is the scenario where the team works at the speed of the system.

Yellow channel means the Receita Federal reviews documents without physically examining the cargo. The customs officer checks the commercial invoice, the bill of lading, the packing list, and any regulatory approval documents. The timeline ranges from one to five business days, depending on the local customs unit and the volume of declarations under review. For the operator, yellow channel means having all documents assembled and accessible in the system before the officer requests them, because the delay usually comes from waiting for a missing document.

Red channel covers both documents and physical inspection. The customs officer examines the goods at the bonded terminal, and the inspection must be scheduled with the warehouse operator. The timeline runs from five to thirty days, depending on the facility, officer availability, and cargo complexity. The operational cost includes moving the container to the inspection area, having a representative present during examination, and, at many terminals, a positioning fee charged by the facility. The operations team coordinates the scheduling with the customs broker, tracks the inspection outcome, and, if the officer raises a requirement, prepares the response within the deadline.

The gray channel is the rarest and the slowest. The Receita Federal investigates suspected fraud, undervaluation, or fraudulent interposition, combining document review, physical inspection, and special customs control procedures. The timeline is open-ended, and the shipment can be held for months. A gray channel assignment means immediate escalation to the customs broker and the importer, because resolution depends on supplementary documentation that only the importer can provide.

The Product Catalog determines what happens before the channel

A DUIMP can only be filed when the Portal Único Product Catalog is validated for that HS code and that importer. Without a complete entry including all technical attributes and specifications required by each regulatory body, the system rejects the declaration. The shipment stalls before channel selection even begins.

Since May 2026, ANVISA (Brazil’s health regulatory agency) requires the “Import Purpose” attribute to be filled in the Product Catalog for every HS code subject to health clearance. A catalog entry that worked in April can block filing in September if that field was not updated. For teams handling dozens of HS codes under regulatory approval, maintaining the Catalog has become a recurring task, and the responsibility for it often sits unclaimed among the importer, the customs broker, and the freight forwarder.

The Product Catalog functions as a filter that sits before channel selection. A mismatched product description attribute or an incorrect classification code can create an inconsistency the system catches before the declaration even reaches the Receita Federal. When the entry is correct and consistent, the declaration enters channel selection with the data the risk model expects to find. When there is a mismatch, filing fails or the declaration enters selection flagged, which increases the chance of leaving the green channel.

LPCO and regulatory bodies: the timeline that runs parallel to the channel

Since April 27, 2026, regulatory approvals from ANVISA, MAPA (agriculture), Inmetro (standards), CNEN (nuclear), and ANP (petroleum) for ocean and air cargo must be requested through the LPCO within DUIMP, replacing the old import license model tied to the DI. The regulatory body’s timeline now runs parallel to the customs channel, and clearance only happens when both are resolved.

Automatic licensing has a legal deadline of up to ten business days from filing. Non-automatic licensing can take up to sixty calendar days, depending on the regulatory body and the complexity of the review. Cargo that received a green channel at selection but depends on a non-automatic LPCO from MAPA stays at the terminal until the regulatory body approves it. Storage costs and container detention run throughout the wait, and the importer hears that the cargo “got green channel but hasn’t been released” without understanding why clearance has not happened.

The control point is when the LPCO is requested. An LPCO submitted before shipment, while the cargo is still at origin, gives the regulatory body review time without the container occupying space at the bonded terminal. An LPCO requested only after the cargo arrives turns the regulatory timeline into storage charges.

The current DI shutdown schedule details which operations have migrated and which still accept the legacy DI.

What the operations manager checks before filing

The checklist that reduces non-green channel outcomes and regulatory holdups is short, and nearly all of it concerns data, because under DUIMP, data determines the outcome.

Before the customs broker files the DUIMP, the team verifies that the Product Catalog is current for every HS code in the shipment, with all mandatory attributes filled, including any that regulatory bodies added during 2026. The team checks whether the customs value on the commercial invoice is consistent with the import history for that product and that importer, because a large variance without documented justification is exactly the kind of mismatch the risk model catches. The team confirms whether the LPCO has been requested and, when possible, whether it has been approved before the cargo arrives at the terminal.

The team also checks whether the documents the Receita Federal would request in a yellow channel are ready and accessible in the system: commercial invoice, bill of lading, packing list, certificate of origin where applicable, and regulatory approval records. The import document review we covered previously on this blog explains the cost of each incorrect field in those documents.

Teams that build this review into their pre-filing workflow reduce two things at once: the number of declarations held in yellow or red channel due to data inconsistencies, and the time the shipment spends at the terminal when a hold happens because of a pending regulatory approval. In our experience with freight forwarders in Brazil, the manager who treats Product Catalog review as an operations task, with a named owner and a per-HS-code checklist, finds that most delays traced back to a field nobody was checking.

Frequently Asked Questions

How can I prevent an import from being assigned to the red channel under DUIMP?

The red channel results from inconsistencies in declared data, the importer’s risk profile, or a flag from the Receita Federal’s risk management model. What the freight forwarder controls is data quality: keeping the Product Catalog current with complete attributes, and ensuring the declared customs value is consistent with the importer’s history and the commercial invoice. These measures reduce the probability of a non-green channel, although the Receita Federal can select any declaration for review.

What is the Portal Único Product Catalog and why does it block DUIMP filing?

The Product Catalog is the centralized registry within Brazil’s Portal Único Siscomex where each importer registers the products it imports, including the HS code, technical attributes, and specifications required by each regulatory body. A DUIMP can only be filed when the product is registered and validated in the Catalog. A missing or mismatched mandatory attribute prevents filing, and the shipment stalls before customs channel selection even begins.

What is the difference between the channel timeline and the regulatory body timeline under DUIMP?

The customs channel (green, yellow, red, or gray) determines whether and how the Receita Federal reviews the declaration. The regulatory timeline is the time a body like ANVISA, MAPA, or Inmetro takes to approve the LPCO linked to the DUIMP. The two run in parallel, and clearance only happens when both are resolved. Cargo with a green channel and a pending LPCO remains at the bonded terminal until the regulatory body completes its review.

How Tier2 Cargo Organizes Clearance Data Across the Shipment

Keeping data consistent across what the importer declares, what the customs broker files, and what the operator tracks is what makes this workflow hold together. Tier2 Cargo keeps that data inside the import shipment: DUIMP and DU-E fields, CE Mercante and CCT records, clearance milestones, and the role of each partner from the customs broker to the carrier.

When documents that feed the declaration arrive by email or through the Tier2 Portal, Tier2 Cargo’s AI agent extracts the fields from the commercial invoice and the bill of lading and compares them against what the Product Catalog expects. A mismatch surfaces before the customs broker files, at the point where a correction costs minutes rather than days of terminal detention.

See how it works or get in touch.