A housekeeping notification just re-cut the tariff lines under your chemical imports

On 22 July 2026 the Directorate General of Foreign Trade issued Notification No. 24/2026-27, syncing ITC (HS), 2022 Schedule-1 (Import Policy) with the Finance Act, 2026. The title reads like administration. The argument here is that in Chapter 29 - organic chemicals - it is not: the notification changes how finely the schedule cuts, recording eight-digit codes as deleted and listing narrower lines named for specific substances in their place. It came into force with immediate effect. So two things are already true. Several eight-digit codes that were in the schedule on 21 July were not in it on 22 July. And among the lines the annexure lists, the policy condition recorded against them is not uniform - it varies from one line to the next inside the same chapter.

What a "syncing" notification actually does

The notification is issued under Section 3 read with Section 5 of the Foreign Trade (Development and Regulation) Act, 1992, read with paragraphs 1.02 and 2.01 of the Foreign Trade Policy 2023. Its stated effect is that ITC (HS) 2022, Schedule-I (Import Policy) is amended in sync with the Finance Act, 2026 - an Act dated 30 March 2026 - and that this comes into force with immediate effect.

The substance is in the annexures rather than the operative paragraphs. Paragraph 2 states that the list of ITC (HS) codes and related policy conditions inserted, deleted, amended, split or merged in sync with the Finance Act is annexed as Annexure-I. Paragraph 4 states that the updated Schedule-1 will be available on the DGFT website.

That structure is worth noticing. The operative text announces an alignment exercise. The list of codes that stopped existing on 22 July is a table further down.

Chapter 29 is where the granularity changed

Three examples, all from Annexure-I, all in organic chemicals.

Acetyl chloride. ITC (HS) 29159010, "Acetyl chloride", is recorded as Deleted. In its place the annexure lists 29159011 for acetyl chloride and 29159012 for propionyl chloride. Two substances that shared a code now have one each.

Malonic acid. ITC (HS) 29171920, "Malonic acid", is recorded as Deleted, replaced by 29171921 for malonic acid, 29171922 for diethyl malonate and 29171929 for other.

Phenylacetic acid. ITC (HS) 29163400, "Phenylacetic acid and its salts", is recorded as Deleted, replaced by 29163410 for phenylacetic acid and 29163490 for other.

The pattern is the same in each case, and it is the pattern that matters more than any individual line. A code that carried a group now carries one member of it, and the remainder of the group has been given its own destination. An importer whose systems declare against the deleted parent code is not declaring against a code with a changed description. They are declaring against a code the schedule no longer contains.

Lines that did not exist before

The same annexure also creates eight-digit entries for substances that previously had no line of their own. Among them, all with Import Policy shown as "Free":

• 29333700 - N-Phenethyl-4-piperidone (NPP)
• 29333970 - 4-Piperidone, and 29333980 - 1-Boc-4-piperidone
• 29333991 - Norfentanyl
• 29183070 - Methyl alpha-phenylacetoacetate
• 29189940 - P-2-P methyl glycidic acid and its esters
• 29242991 - Alpha-phenylacetoacetamide
• 29329940 - 3,4-MDP-2-P methyl glycidic acid, and 29329950 - 3,4-MDP-2-P methyl glycidate

The following is inference rather than anything the notification states: each of these substances is now separately classifiable where, on the face of the annexure, it previously had no line of its own - and a substance with its own line is one the schedule can address individually. Conditions, restrictions and reporting can attach to it without touching anything else that used to share its code. Whether or not anything is attached to these lines today, the schedule is now built so that something could be, line by line, without a further re-cut.

The Policy Condition column is not uniform

One feature of Annexure-I is easy to miss, because it is a column rather than a sentence, and it carries more operational weight than anything in the operative paragraphs.

Against ITC (HS) 29394210, pseudoephedrine (INN), and 29394290, the Policy Condition column reads "Subject to Policy Condition No. 3 of the Chapter". Against 29396310, lysergic acid, and 29396390, it reads "NOC from Narcotics Commissioner of India, Gwalior". Policy Condition No. 3 of Chapter 29 requires a No Objection Certificate from the Narcotics Commissioner before import of the item.

Against 29333700, 29333970, 29333980 and 29333991 - the piperidone and norfentanyl lines listed above - the Policy Condition column is blank.

This article draws no conclusion from that contrast, and a reader should not either without going to the consolidated schedule. This is the article's reading, not a statement in the notification: Annexure-I is a record of what this exercise changed, which is not the same document as a statement of every condition in force against a line - and paragraph 4 points to the updated Schedule-1 on the DGFT website as the place to look. The practical point is therefore not what the blanks mean. It is that within one chapter, in one annexure, the condition recorded against a line varies from line to line - so the classification decision an operator makes is also, in effect, the decision about which condition set they are declaring under.

Deleted codes do not fail loudly

This paragraph is inference, and no instrument requires it. The reason a re-cut like this is worth attention out of proportion to its apparent significance is the way it fails. A deleted code does not announce itself. It sits in an ERP item master, a supplier's commercial invoice template and a broker's standing instruction, and it keeps looking correct until a bill of entry is filed against it. The failure surfaces at the port, on a consignment, with the clock running - and it surfaces as a classification question, which is slower to resolve than a documentation gap because it needs a technical view on what the material actually is.

That is a different risk profile from a policy change. A policy change is loud and dated, and it tends to reach the people who need it. A schedule re-cut is quiet, and the parties likeliest to be working from stale codes are the ones furthest from the notification - overseas suppliers preparing invoices, and brokers working from a code list someone gave them.

What a well-run operation does differently

Three things, none of which are on the commercial side of the house.

Reconcile the item master against Annexure-I, not against the description. The test is whether the eight-digit code still exists in the schedule, not whether the product description still reads correctly. A description that still matches against a deleted code is precisely the case that will not flag itself.

Treat split lines as a classification decision, not a mapping exercise. Where one code became three, someone has to decide which of the three each material falls under. That is a technical judgement about the substance, and Annexure-I shows it can determine which policy condition is recorded against the line.

Check the consolidated schedule, not the annexure. Paragraph 4 puts the updated Schedule-1 on the DGFT website. The annexure is a change log; the schedule is the instrument. For any line that matters, the condition in force is the one in the consolidated document.

The notification came into force with immediate effect. On its own terms it changes nothing of substance - the schedule was brought into alignment with an Act dated 30 March 2026. For an operator, the alignment is the change.