ICEGATE
Short Shipment on a Shipping Bill: Filing the Shortship Amendment on ICEGATE
The dedicated Shortship webform, why message type R and the remark are locked, the four segments you fill, and the 101 to 147 error codes that reject the whole request.
By Aaryan Kakani · · 14 min read
What counts as a short shipment on a shipping bill?
ICEGATE uses a narrow, mechanical definition. A short shipment refers to a situation where the actual quantity of goods exported is less than the quantity declared on the shipping bill (User Manual SB Shortship Webform v1.01, 09.07.2025, icegate.gov.in/guidelines/sb-short-shipment). Nothing else is required for the definition to bite. Not a reason, not a fault, not a value threshold. Less went than you said would go.
In practice the same handful of causes turn up again and again:
Everyday causes of a short shipment
- Cargo shut out at the terminal. The vessel closes, the stack date passes, or the terminal runs out of slots and part of the booking never gets loaded.
- Part of a consignment fails carting or examination. Packages are held back at the examination shed while the rest of the lot is cleared and loaded.
- A container is rolled to the next vessel. The line reassigns space, so one container of a multi-container shipping bill sails a week later.
- Packages damaged before loading. Cartons are crushed in handling and pulled from the shipment at the dock.
The stakes are downstream, not at the port. The declared quantity drives the FOB value on the shipping bill, and FOB is the base for export incentives and for export duty where duty applies. If the shipping bill still says a thousand units went out when eight hundred and eighty did, three things are simultaneously wrong: the incentive claim is computed on an overstated base, any export duty is computed on an overstated base, and the realisation expectation sitting in EDPMS against that bill can never be matched, because the buyer will only ever pay for what actually arrived. That last one is the quiet killer. An EDPMS entry that cannot close is an entry that ages into a bank query and then into a caution list problem.
It is worth remembering why the correction is your obligation and not the department's courtesy. Under Section 50 of the Customs Act 1962 the exporter presents the shipping bill electronically and declares the truth of its contents, and is responsible for the accuracy and completeness of the information furnished (CBIC consolidated Customs Act 1962 text, 30-March-2022, taxinformation.cbic.gov.in). A bill you know to be overstated in quantity is a declaration you know to be inaccurate.
Why is a short shipment a separate webform and not a normal amendment?
Because ICEGATE built it that way. The guidelines section publishes SB Amendment and SB Amendment-Shortship as two distinct webforms with two distinct user manuals: the Shortship form has its own 33-page User Manual v1.01 dated 09.07.2025, and the amendment form has a separate User Manual SB Amend Webform v1.01 dated 26.08.2025.
The hard-coding is the whole point of the split. In the Shortship webform, Message type is R and non-editable , Amendment Type is R and non-editable , and Remarks is pre-filled with 'Short Ship' and non-editable (SB Shortship Webform manual v1.01). You cannot type over any of them. The consequence runs in both directions: a short shipment cannot be quietly mislabelled as an ordinary amendment, and an ordinary quantity correction that is not a short shipment should not be pushed through the Shortship route just because the field you want to change happens to be a quantity.
| Attribute | SB Amendment | SB Amendment-Shortship |
|---|---|---|
| Menu path | Services widget → Electronic Filing → Webforms → SB Amendment | Services widget → Electronic Filing → Webforms → SB Amendment-Shortship |
| Message type | Set by the amendment being filed | Hard-coded to R |
| Editability of type and remarks | Filer supplies the amendment type and the remarks | Amendment Type R and Remarks 'Short Ship' both non-editable |
| Stakeholders permitted | IEC, CHA and SEZ | Importer/Exporter and CHA only |
| DSC requirement | No DSC step described in the flow | User must authenticate DSC before submission |
| Rejection behaviour | Standard webform validation | All-or-nothing: any invalid, inconsistent or mismatched code rejects the entire request with a negative acknowledgement |
Where is the Shortship webform and what does segment one ask for?
The path is Services widget → Electronic Filing → Webforms → SB Amendment-Shortship , and the manual states that the user must authenticate the digital signature certificate before submission. The form is split into segments; segment 1 is the header block that identifies which shipping bill you are amending and under whose authority.
| Segment 1 field | Status | What to put in it |
|---|---|---|
| Message type | R , non-editable | Nothing. It is set for you and cannot be changed. |
| Custom House Code | Required | The custom house of the original shipping bill, not the one nearest your office |
| User Job No / User Job Date | Required | Your own filing reference and its date. This is how you find the request again later |
| SB Number / SB Date | Required | Exactly as on ICEGATE for the declared Custom House Code |
| Remarks | Pre-filled 'Short Ship', non-editable | Nothing. Your narrative goes in Reasons for Amendment. |
| Reasons for Amendment | The field that matters | A specific factual reason: what was shut out, how much, on which vessel or flight, and why |
| Request Letter Number / Request Date | Optional | Fill only if you have actually issued a covering letter with that number |
| Amendment Status | Optional | Leave blank unless you have a value to report |
| Amendment Number / Amendment Date | Required | Your sequence for this amendment against this bill, and its date |
| Amendment Type | R , non-editable | Nothing. Same lock as Message type. |
Treat the optional fields as genuinely optional. Request Letter Number, Request Date and Amendment Status exist for filers who work off a physical covering letter or who are tracking a multi-stage amendment. If you do not have those references, an invented value is worse than a blank one, because the shared validation engine will happily reject a payload over a reference you did not need to supply.
Reasons for Amendment is the one a human reads. Everything else on this form is machine-checked. This field is where an officer forms a view of whether the short shipment is a logistics fact or a story. "Short shipped" is not a reason. "180 of 1,000 cartons shut out at CFS on 04.08.2026, vessel closed before carting completed, balance to move on next sailing" is a reason.
Which invoice and item fields are actually mandatory?
Segment 2 looks intimidating and is not. It carries Invoice Details, Freight and Insurance Details, Third Party Details, Item Details and Supporting Document Details. But the mandatory surface inside all of that is tiny, and it is tiny in exactly the right places.
| Segment 2 block | Mandatory content | Practical advice |
|---|---|---|
| Invoice Details | Invoice Serial Number only | Identify the invoice whose line is short. Do not restate the whole invoice. |
| Freight and Insurance Details | None. Optional | Leave alone unless freight or insurance genuinely changed because of the shortfall |
| Third Party Details | None. Optional | Skip entirely on an ordinary shut-out |
| Item Details | Item serial number and quantity only | Quantity is the thing that changed, so quantity is the thing you file |
| Supporting Document Details | Uploads are PDF only | Attach the shut-out advice or the terminal / carrier confirmation |
That minimum is not an accident. A short shipment is a quantity event; the design of the form says so. Only the Invoice Serial Number is mandatory under Invoice Details, and only quantity and item serial number are mandatory under Item Details, with freight, insurance and third party blocks all optional (SB Shortship Webform manual v1.01).
Item Details branches by Product Type , and each branch opens a different set of tabs:
Product Type branches and their tabs
- Plants and Related Items. Info, Control, Declaration
- Drugs and Related Items. Constituent, Production, Control, Declaration
- Other Items. Info, Control, Declaration
What are the licence, job work and cargo-back segments for?
Segment 3 carries Invoice and Item Details, License Details and Job Work Details. The job work block is gated behind a branch question. "Is the items exported under job work scheme?" with a Yes or No answer. Answering Yes opens the job-work block; answering No keeps it closed and keeps that whole part of the payload out of validation. Licence details matter when the goods moved under an authorisation whose quantity utilisation now has to be read down, because the licence was debited on the declared quantity and only the shipped quantity actually left the country.
Segment 4 is the part that makes Shortship a genuinely different animal from a paper correction: Cargo Back, Package Back and Container Back Details. This is the physical reconciliation of what did not go. A paper amendment adjusts a number on a document. Shortship asks you to account for the actual cargo, the actual packages and the actual containers that came back off the loading plan, and the customs system can compare that account against the manifest.
Keeping the physical and documentary positions in agreement
- Describe returned cargo in the same units as the item line. If the item line moves in kilograms, the cargo back block should not be expressed in cartons.
- Make the arithmetic close. Declared quantity minus cargo back quantity must equal the revised item quantity. If it does not, one of the two is wrong and the engine will find it.
- Package back must reconcile to package count. The number of packages you report coming back plus the packages that sailed should equal the packages the original bill declared.
- Container back is per container, not pro-rata. A rolled container comes back whole. Do not split a container notionally to make a value work out.
On uploads, the rule to hold on to is that supporting documents on the Shortship form are PDF only . On file size, honesty is more useful than false precision: the manual states two different caps in adjacent sections, so there is no single number this page can responsibly publish. Work to the lower of the two. A compressed PDF that comfortably clears the smaller cap is accepted under either reading; a file sized to the larger cap is a coin flip.
What happens when the Shortship request is rejected?
The rule is blunt and it is worth internalising before you file. Where the information supplied is invalid or inconsistent, or where there is any code mismatch, the request is fully rejected and a negative acknowledgement is sent back to the user (SB Shortship Webform manual v1.01). There is no partial acceptance. Nine correct item lines and one bad currency code produce zero accepted lines.
The negative acknowledgement carries a code. The manual publishes the full range from 101 to 147, which is unusual. Most filing portals leave you guessing. Read the code, identify which family it belongs to, and note who actually has the power to fix it, because for a large slice of this table the answer is not you.
| Code | Message | Likely cause | Who fixes it |
|---|---|---|---|
Grouped, the table reads as six families. Identity and licence covers 103 and 145 (Invalid CHA Number), 104 (CHA License Expired) and 105 (Invalid IEC). Documentary covers 106 (LC/Embassy Letter Not Available), 107 and 146 (Invalid LC Number) and 108 (LC Expired). Routing and reference data covers 101, 102, 109 to 113 and 147. Manifest is the long stretch from 114 to 127. Item runs 128 to 135, bond 136 to 139, and transport and container 140 to 144.
Two codes deserve a specific mention because they waste the most time. 127 (No IGM Record Exists) almost never means you typed the SB wrong; it usually means the carrier has not filed or corrected the manifest yet, so there is nothing to match against. Chase the line, not the form. 147 (Latest Currency Rate Not Available) means there is no notified rate on file for the currency and date you declared. Waiting, or refiling on a date the rate covers, fixes it, and re-entering the same payload immediately will not.
What has to be corrected downstream after a short shipment?
This is the chain nobody assembles in one place. The Shortship amendment fixes the shipping bill. It does not fix the four systems that already consumed the old figure.
| Downstream system | What breaks | What to do |
|---|---|---|
| Incentive base | Reduced quantity means reduced FOB, so the incentive base falls | Recompute the claim on the revised FOB before it is submitted, not after it is questioned |
| EGM (carrier) | The export general manifest must reflect what actually shipped, not what was booked | Get the line or its agent to file or amend the EGM to the shipped quantity |
| DGFT transmission | DGFT may still hold the pre-amendment SB, so the corrected bill needs re-transmission | Raise the re-transmission request. But it will be refused while the SB is provisionally assessed or the EGM has not been filed |
| EDPMS realisation expectation | RBI still expects realisation against the overstated value | Check the RBI-SB-EDPMS enquiry and read the FE Realization details, which show RBI's figure rather than ICEGATE's |
| Balance shipment | The shipped-out balance may go on a fresh shipping bill | Make sure the two bills do not double-count against the same invoice |
The re-transmission gate is worth stating plainly because it catches people in the wrong order. A DGFT re-transmission request will be refused while the shipping bill is provisionally assessed or the EGM has not been filed (DGFT Re-Transmission User Manual V0.2, icegate.gov.in/guidelines/dgft-re-transmission-for-sb). So the sequence is: Shortship amendment accepted → EGM corrected by the carrier → provisional assessment finalised if applicable → only then re-transmission.
Worked example: what the numbers actually do
A shipping bill declares 1,000 units at USD 12.50 per unit. At the terminal, 120 units are shut out and roll to the next sailing. Illustrative figures only. Substitute your own unit price, exchange rate and applicable incentive rate.
- 1 Declared FOB on the original bill 1,000 × USD 12.50 = USD 12,500.00
- 2 Quantity actually exported 1,000 − 120 = 880 units
- 3 Revised FOB after the Shortship amendment 880 × USD 12.50 = USD 11,000.00
- 4 Overstatement if the bill is left uncorrected USD 12,500.00 − USD 11,000.00 = USD 1,500.00 (12.0% of declared FOB)
- 5 Effect on an incentive claim at an illustrative 1.0% rate On declared FOB: 12,500.00 × 1.0% = USD 125.00 On revised FOB: 11,000.00 × 1.0% = USD 110.00 Over-claim: 125.00 − 110.00 = USD 15.00 The 1.0% here is a placeholder for arithmetic, not a RoDTEP or drawback rate. Use your own line rate.
- 6 Effect on the EDPMS realisation expectation Expected before: USD 12,500.00 Buyer will pay for 880 units: USD 11,000.00 Permanent unmatchable gap if uncorrected: USD 1,500.00 At an illustrative INR 84.00 to the dollar that is 1,500.00 × 84.00 = INR 1,26,000.00 of realisation that can never arrive against this bill.
- 7 Where the 120 units go Onto a fresh shipping bill for USD 1,500.00 when they sail. The two bills together must come to USD 12,500.00 against the invoice. Not USD 14,000.00, which is what happens if the first bill is never short-shipped.
Short shipment filing checklist
Before you open the form
- Confirm the shortfall against the actually loaded quantity and the carrier's record. Not against your own packing list alone
- Confirm this is a short shipment and not an ordinary correction: use SB Amendment-Shortship , not SB Amendment
- Have Custom House Code, User Job No and Date, SB Number and SB Date to hand, matching ICEGATE exactly
- Have the DSC token plugged in and tested. Authentication is required before submission
- Have the shut-out advice or carrier confirmation ready as a PDF, compressed under the lower of the two stated caps
While filling it in
- Write a specific Reason for Amendment: what was shut out, how much, from which vessel or flight, and why
- Fill only Invoice Serial Number, item serial number and quantity unless something else genuinely changed
- Leave freight, insurance and third party blocks blank. Every extra field is another rejection surface
- Complete Cargo Back, Package Back and Container Back so the physical and documentary positions agree to the unit
- Answer the job work branch question honestly. A No keeps the whole job-work block out of validation
After submission
- Expect all-or-nothing: a negative acknowledgement means nothing was accepted
- Read the 101. 147 code and identify the family and the fixer before touching the form again
- Record the Tracking ID against your own User Job No
- Chase the carrier for the EGM correction, then raise DGFT re-transmission. In that order
- Reconcile the EDPMS realisation expectation to the reduced value through the RBI-SB-EDPMS enquiry
- Recompute the incentive claim on the revised FOB, and make sure the balance shipment's new SB does not double-count the same invoice
What else do exporters ask about short shipments?
What is a short shipment on a shipping bill?
ICEGATE defines a short shipment as a situation where the actual quantity of goods exported is less than the quantity declared on the shipping bill. It typically arises when cargo is shut out at the terminal, when part of a consignment fails carting or examination, when a container is rolled to the next vessel, or when packages are damaged before loading. Because the declared quantity drives FOB value, and FOB is the base for export incentives and export duty, an uncorrected short shipment overstates the incentive claim and leaves the EDPMS realisation expectation permanently unmatchable.
Can I use the normal SB Amendment form instead of the Shortship form?
No. ICEGATE publishes SB Amendment and SB Amendment-Shortship as two distinct webforms with two distinct user manuals. The Shortship form is reached at Services widget → Electronic Filing → Webforms → SB Amendment-Shortship, and it hard-codes the message type, amendment type and remarks so a short shipment cannot be filed as an ordinary amendment. The reverse is also true: an ordinary quantity or description correction that is not a short shipment should be routed through the SB Amendment webform, not through Shortship.
Why is the Remarks field locked to 'Short Ship'?
In the ICEGATE Shortship webform the Message type and Amendment Type are hard-coded to R and Remarks is pre-filled with 'Short Ship', all three non-editable. Locking these fields means every request submitted through this form is unambiguously classified as a short shipment in the customs system, so the request cannot be mislabelled by the filer and cannot be routed to the wrong queue. The field you actually write in is Reasons for Amendment, which is the free-text field the officer reads.
Is a digital signature required for a Shortship amendment?
Yes. The ICEGATE SB Shortship webform manual states that the user must authenticate the digital signature certificate before submission. This is one of the differences from the SB Amendment webform flow, which does not describe a DSC step. Have the DSC token plugged in and the signing utility working before you start filling the form, because losing a part-filled webform to a DSC failure is a common and avoidable waste.
What does a negative acknowledgement mean and can part of my request still go through?
No part of it goes through. Where the information supplied is invalid or inconsistent, or where there is any code mismatch, the ICEGATE Shortship request is fully rejected and a negative acknowledgement is sent back to the user. There is no partial acceptance: a single bad code fails the whole request. The negative acknowledgement carries an error code from the published 101 to 147 range, and the correct response is to read that code and fix the specific defect rather than resubmit the same payload and hope.
Which official sources back this guide?
Update history
- First published.