CEPA Eligibility (HS Code Check): How to Confirm Preferential Tariffs

What you are actually checking when you ask “is this CEPA-eligible?”

Teams often ask: “Is my product eligible for CEPA?”

In practice you are checking three things:

1. HS code / tariff line: what tariff line your product falls under
2. Preferential rate: what the agreement provides for that line (now vs over time)
3. Origin rule + evidence: whether your product qualifies as “originating” and you can prove it

The UAE Ministry of Economy & Tourism describes CEPA as a framework for trade benefits (including reduced or eliminated tariffs and simpler customs procedures), and provides a UAE-India CEPA overview with references and a tariff dashboard.

Step 1: Confirm the HS code (do not skip this)

The HS is a standardized product nomenclature developed by the World Customs Organization. It uses six-digit codes as the international base.

Operationally:

• Your CEPA eligibility starts at the HS code.
• Your duties, restrictions, and documentation often follow.

If your HS code is unstable (different teams using different codes), you cannot run a reliable CEPA workflow.

Step 2: Check the agreement coverage for that tariff line

Once you have an HS code, check whether the CEPA provides a preferential rate for the tariff line and what the schedule is.

For UAE-India, the UAE Ministry of Economy & Tourism provides a CEPA market access dashboard entry point to look up preferential tariffs by tariff line.

Step 3: Validate rules of origin logic

Preferential tariffs typically apply only if the goods qualify as “originating” under the agreement.

The details vary by agreement and product.

Practically, your team must answer:

• Was the product wholly obtained?
• Or was it sufficiently processed/manufactured in an eligible country?
• If inputs are imported, do you meet the rule for that tariff line?

If you cannot explain your origin rationale in one paragraph, you probably do not have an “evidence pack” that will survive a query.

Step 4: Build an evidence pack before you ship

CEPA failures rarely happen because “the agreement doesn’t work”. They happen because evidence is not ready.

Build a simple evidence pack per product (reusable across deals):

• HS code rationale (internal note + any broker advice)
• Bill of materials (if needed)
• Supplier declarations / origin statements (if needed)
• Manufacturing / processing description (if needed)
• Certificates required by the buyer or customs

Then attach that pack to every deal.

Step 5: Operationalize the check (don’t make it an email)

Your CEPA check should look like a workflow:

1. Item created → HS code assigned
2. HS code locked (with owner)
3. Preferential rate confirmed
4. Origin rule satisfied (and documented)
5. Evidence pack attached to shipment
6. Certificate / declaration prepared

If any step is missing, the system should block “ship” or at least raise a visible risk.

How Tijara helps

Tijara helps you turn CEPA eligibility into a repeatable process:

• store HS codes per item with change history
• track CEPA checks as a timeline (not in inboxes)
• attach evidence packs to deals and documents
• keep landed cost and savings visibility tied to the deal

Related reading:

• /resources/how-to-calculate-landed-cost
• /resources/landed-cost-india-to-uae