Shipper's Letter of Instruction for Export Forwarders
For export-import, customs and transport documentation managers · Understand the problem

Shipper's Letter of Instruction for Export Forwarders: Illustrative customs query response and technical evidence review.
Quick answer: shippers letter of instruction
A shipper's letter of instruction is the exporter's written instruction to its forwarder covering export filing data, booking, insurance and release of documents. No US rule prescribes its form, but 15 CFR 30.3 makes the exporter answer for the data it supplies, and its signature block can serve as written authorization to file Electronic Export Information.
TL;DR — what you’ll learn
- No regulation prescribes an SLI form, yet 15 CFR 30.3(a)(3) lets a filer rely on data others furnish, so the exporter who signs the SLI carries accuracy risk.
- The SLI can authorize EEI filing only if its wording meets 30.3(f): responsibilities stated with particularity and the agent named as true and lawful agent.
- In routed exports the exporter supplies only the Appendix C fields, and the buyer's agent must file them exactly as given and return the ITN on request.
- Set SLI receipt at least one business day before the ocean documentation cut-off, since vessel EEI must be filed 24 hours before loading.
Topics: shippers letter of instruction · SLI fields · EEI responsibility · routed exports · forwarder written authorization EEI
All quantities, amounts, product codes and events are illustrative teaching examples.
The forwarder's booking desk gets a two-page PDF at 16:50 on a Thursday: a shipper's letter of instruction with the Schedule B box copied from last quarter's order, the value typed from a pro forma, and "originals to consignee" ticked although the payment term is documents against payment. By Saturday the container is on the water, the Electronic Export Information carries the wrong classification, and the bills of lading are on a courier to a buyer who has not paid.
Every one of those failures started on the SLI, the document that tells the forwarder what to file, what to book and whom to release to. Treat it as a controlled record with an owner for each field and a cut-off, and the forwarder files once, releases correctly and can show which party supplied what. Treat it as a cover sheet, and the exporter carries the liability for data it never checked.
- What this guide covers: what an SLI is and is not under US rules, the fields that feed the export filing, written authority, standard and routed exports, value at the port of export, release instructions, cut-offs and the Indian practice for exporter instructions to a customs broker.
- What it adds: a field-to-regulation map, a worked value conversion in dollars and rupees, a structured SLI payload and an onboarding checklist for exporters and forwarders.
An instruction letter with legal weight but no prescribed form
No US regulation prescribes an SLI form. The SLI is a commercial document in which the exporter tells its forwarder how to move and document a shipment; its legal weight comes from the Foreign Trade Regulations, which make the party supplying export data answerable for it, and from the authorisation language most SLI templates carry.
The definitions in 15 CFR 30.1 never use the phrase "shipper's letter of instruction". They define the authorized agent, the power of attorney and the written authorization, and they refer to "export shipping instructions" as one of the places a filing citation may appear. Since 15 September 2025, section 30.3 also states that Incoterms and other terms of sale do not determine the type of export transaction or its parties, because they have no regulatory basis.
That makes the SLI the evidence file for two questions an auditor will ask: who supplied each data element, and did the agent have authority to file. Our guide to EEI filing, AES and the ITN covers the filing itself, exemptions and penalties; this article stays with the instruction document that feeds it.
Mapping SLI boxes to the data elements the filing needs
Every SLI box that feeds Electronic Export Information should map to a numbered data element in 15 CFR 30.6, and each one needs a named owner on the exporter's side. Boxes that only steer the booking, such as insurance or document instructions, need an owner too, but they are commercial rather than regulatory.
Scroll horizontally to see all columns.
| SLI field | FTR data element | Usual source record | Exporter sign-off |
|---|---|---|---|
| USPPI name, address, contact and EIN | 30.6(a)(1) | Legal entity master | Export compliance lead |
| Ultimate consignee and type | 30.6(a)(3) and (a)(28) | Sales order ship-to and customer master | Order management, screened by compliance |
| Intermediate consignee | 30.6(b)(2) | Routing instructions | Logistics coordinator |
| State of origin and FTZ identifier | 30.6(a)(4) and (b)(3) | Shipping plant | Plant shipping supervisor |
| Schedule B or HTS number and description | 30.6(a)(12) and (a)(13) | Product classification record | Trade classification specialist |
| Domestic or foreign origin | 30.6(a)(11) | Item master origin field | Trade classification specialist |
| Quantity, unit and shipping weight | 30.6(a)(14) to (a)(16) | Packing list and scale ticket | Warehouse lead |
| Value at port of export | 30.6(a)(17) | Commercial invoice adjusted to the port | Billing or export finance |
| License code, ECCN, licence number | 30.6(a)(23), (b)(5), (b)(6) | Export control determination | Export control officer |
| Hazardous material indicator | 30.6(a)(21) | Safety data sheet and dangerous goods review | Dangerous goods certified person |
| Related party and routed indicators | 30.6(a)(10) and (a)(24) | Customer ownership data and sale terms | Export compliance lead |
The remaining boxes on most templates are instructions rather than data: freight prepaid or collect, whether the forwarder should insure and for how much, how many original bills to issue, who receives them, and which certificates to prepare. They do not reach AES, but they decide who gets paid and who can take the cargo, so they deserve the same owner-and-signature discipline.
Written authority: when an SLI doubles as the agent's mandate
A forwarder may file EEI only with a power of attorney or written authorization from a principal party in interest. Many SLI templates embed that authorization in the signature block, which is acceptable if the wording meets 15 CFR 30.3(f); a signature under a page of shipping boxes alone does not.
Section 30.3(f) says the authorization should specify the parties' responsibilities with particularity and state that the agent may act as the principal's true and lawful agent for creating and filing EEI under US law. Census's Appendix A to Part 30 gives a sample. Two operating patterns follow: a standing power of attorney held on file, with each SLI referring to it, or a per-shipment SLI that carries the full authorization text.
- Standing authority: one signed power of attorney per legal entity, renewed on a set cycle, with each SLI citing its reference and date. Easier to audit, but a stale signatory can survive a reorganisation.
- Per-shipment authority: authorization wording printed above every SLI signature. Self-contained, but only as good as the template version in use that day.
- Routed exception: in a routed export the foreign party authorizes the agent, and 30.3(f) states the USPPI need not give that agent a power of attorney or written authorization.
- Licensing authority: under 15 CFR 758.3(b), licensing responsibility moves to the foreign party's agent only if the foreign party assumes it in a writing given to the USPPI.
A shipper's letter of instruction authorizes a forwarder to file Electronic Export Information only when its signature block meets 15 CFR 30.3(f), naming the agent as true and lawful agent for creating and filing EEI; exporters should hold that wording in one controlled template and re-sign it at every signatory change or every 12 months.
Standard and routed exports change who fills which SLI boxes
In a standard export the USPPI gives its own forwarder the whole SLI. In a routed export, the foreign buyer's US agent files, and the USPPI supplies only the elements Appendix C to Part 30 assigns to it, so the SLI shrinks to a data hand-off plus release terms.
The September 2025 rule moved the routed split into Appendix C. The USPPI column covers its own identity, state of origin, origin indicator, classification, description, quantities, value, export information code, hazardous material indicator, in-bond code, licence data, ECCN, FTZ identifier and vehicle details where relevant. The agent column covers export date, consignees, destination, mode, carrier, ports, shipping weight, the routed indicator and the transportation reference number.
Scroll horizontally to see all columns.
| SLI section | Standard export: USPPI gives own forwarder | Routed export: USPPI gives buyer's agent |
|---|---|---|
| Exporter identity, origin and classification | Yes | Yes, per Appendix C USPPI column |
| Value, quantity and export information code | Yes | Yes |
| Licence code, ECCN and licence number | Yes | Yes; on request under 758.3(c) if the buyer assumed licensing in writing |
| Consignees, destination and foreign port | Yes | No; the agent reports them |
| Carrier, mode, port of export and weight | Yes, or left to the forwarder by instruction | No; the agent reports them |
| Written authority | USPPI to forwarder | Foreign party to agent; none needed from USPPI |
| What comes back | Copy of filed data on request, 30.3(c)(2)(iv) | On request: FPPI authorization, the Appendix C data filed, agent name and contact, export date and ITN, 30.3(e)(2) |
Routed exports usually arise on EXW or FCA sales where the buyer nominates the forwarder, which our EXW versus FCA comparison discusses from the contract side. Whatever the term, request the ITN and the filed Appendix C data on every routed shipment and compare them with your SLI, because the agent must file your data exactly as you gave it.
Turning an invoice price into the value the SLI must carry
The SLI value box should hold the value at the US port of export, not the invoice total. Under 15 CFR 30.6(a)(17), that is the selling price plus inland freight, insurance and other charges to the port, with loading on the exporting carrier and costs beyond the port taken out of a delivered price.
India uses a parallel concept. Section 14(1) of the Customs Act, 1962 values export goods at the transaction value for delivery at the time and place of exportation, so a shipping bill on a CIF sale also needs freight and insurance beyond the port separated from the price. The table below works both directions with illustrative figures.
Scroll horizontally to see all columns.
| Line | US exporter, Wichita to Rotterdam ($) | Indian exporter, Ludhiana to Felixstowe (₹) |
|---|---|---|
| Invoice price, CIF destination port | 46,250 | 38,40,000 |
| Inland haul to port, already inside price | 1,150 (rail to Houston) | 62,000 (road to Mundra) |
| Less ocean freight beyond the port | 2,900 | 2,15,000 |
| Less cargo insurance beyond the port | 55 | 4,600 |
| Less loading on the exporting carrier | 310 | Not separately deducted in this example |
| Declared value | 42,985 in EEI, whole dollars | 36,20,400 FOB on the shipping bill |
| Same goods sold EXW Wichita at 41,600 | 41,600 + 1,150 inland freight = 42,750 in EEI | Not applicable to this Indian example |
The EXW line shows why the SLI should carry the adjusted figure rather than leaving the forwarder to guess. The forwarder knows the ocean freight it booked; it does not know whether the inland haul sat inside the price or was billed separately. A $235 difference on one line rarely matters alone, but repeated across a year it is the pattern an export audit samples.
EEI value under 15 CFR 30.6(a)(17) is the selling price at the US port of export: for an illustrative $46,250 CIF Rotterdam invoice, subtracting $2,900 ocean freight, $55 insurance and $310 loading gives $42,985, reported in whole dollars, and the SLI value box should carry that adjusted figure.
Release and document instructions decide who can take the cargo
The SLI's document boxes control payment security. A wrong tick on the number of originals, the consignee line or the release method can hand the goods to a buyer who has not paid, and the forwarder will usually have followed the instruction exactly.
- Consignee line: "to order of" a named bank or the shipper for documentary collections and letters of credit; a named consignee only when the buyer has paid or the term is open account.
- Number of originals: state the full set, usually three, and who receives them; never "originals to consignee" when documents go through a bank.
- Release method: original bills, a surrendered bill or a sea waybill, chosen from the payment term; see our comparison of telex release and surrendered bills for the trade-offs.
- Freight terms: prepaid or collect, matching the Incoterm, so the bill does not show collect freight on a CIF sale.
- Insurance instruction: whether the forwarder should place cover, the insured amount and the clause set, or "no insurance" in writing.
- Hold condition: an explicit hold, such as "release only after shipper's written payment confirmation", where the exporter wants control after sailing.
Downstream, the forwarder turns these instructions into carrier shipping instructions, often as an X12 304 message; our note on EDI 304 shipping instructions covers that carrier-facing step. Errors on the SLI travel straight into that message and onto the bill of lading.
Cut-offs: when a late SLI turns into a late or wrong filing
The SLI must reach the forwarder early enough for the EEI to be filed and the ITN given to the carrier inside the 15 CFR 30.4(b)(2) deadlines: 24 hours before loading for vessel cargo, 2 hours before departure for air, and 1 hour before a truck reaches the border. Set your SLI cut-off backwards from the carrier's documentation cut-off, not from the sailing.
A practical rule is SLI receipt at least one business day before the carrier's documentation cut-off for ocean, and four working hours before the airline's acceptance cut-off for air. That leaves time to resolve an AES fatal error, which must be fixed before export on a predeparture filing. The trace below shows how a late SLI with a stale field produced a wrong filing that was accepted without complaint.
- Thu 16:50, forwarder inbox: SLI for order SO-77140 arrives with Schedule B 8483.40.5050 copied from a prior order and value $61,400 typed from pro forma PF-2219. Vessel documentation cut-off is Friday 15:00.
- Fri 09:10, forwarder AES session: EEI filed from the SLI; AES returns ITN X20261113004417 with no fatal error, because the wrong number is still a valid Schedule B code.
- Fri 13:40, carrier portal: shipping instructions and ITN submitted; container MRKU 552190-6 accepted for Saturday loading in Houston.
- Mon 10:25, exporter billing: final commercial invoice INV-90314 issued at $67,800 after a price revision, and the product team confirms the gearbox belongs under a different subheading.
- Mon 15:05, forwarder: correction transmitted under 30.9 after the exporter's revised SLI arrives; the file shows the original error came from the SLI, which supports the forwarder's reliance under 30.3(a)(3) and leaves the finding with the exporter.
Nothing in that trace was caught by AES, because both the stale code and the pro forma value were plausible. The control that works is upstream: block SLI release when the value differs from the posted invoice adjusted to the port, and require the classification field to come from the item master rather than free text.
India: exporter instructions to the customs broker and the shipping bill
India has no statutory SLI. The exporter instructs its customs broker and forwarder through a commercial shipping instruction and an authorisation, and the legal weight sits with the exporter's declaration on the shipping bill under Section 50 of the Customs Act, 1962.
Section 50(2) requires the exporter to subscribe to a declaration as to the truth of the shipping bill's contents. Section 50(3) makes the exporter ensure the accuracy and completeness of the information, the authenticity and validity of supporting documents, and compliance with any restriction or prohibition. Clearance then follows a Section 51 order permitting clearance and loading, which may be made electronically on risk evaluation; traders call it the let export order.
Scroll horizontally to see all columns.
| Concept | United States | India |
|---|---|---|
| Instruction document | SLI, commercial, no prescribed form | Shipping instruction and checklist approval, commercial, no prescribed form |
| Declaration that carries liability | EEI filed in AES; filer's duty under 30.3(a)(3) | Shipping bill declaration under Customs Act Section 50(2) and (3) |
| Agent's authority | Power of attorney or written authorization, 30.3(f) | Exporter's authorisation to a licensed customs broker |
| Agent's checks on the client | File as instructed; respond to AES messages, 30.3(d) | Verify IEC, GSTIN, identity and functioning at the declared address, CBLR 2018 regulation 10(n) |
| Agent's diligence on information | Reasonable reliance on furnished data | Due diligence on information given to the client, regulation 10(e); advise compliance, regulation 10(d) |
| Clearance to load | ITN or exemption citation given to the carrier | Section 51 order permitting clearance and loading |
| Record retention | Five years from export, 30.10(a) | Set by customs and GST record rules; not covered here |
Indian export instructions to a customs broker carry no prescribed form, but Customs Act Section 50(3) makes the exporter answer for the accuracy of every shipping bill field, and CBLR 2018 regulation 10(n) obliges the broker to verify the IEC, GSTIN and declared address before filing, ideally within one business day of onboarding.
The practical consequence mirrors the US. The exporter should approve the broker's shipping bill checklist against its own invoice, packing list and classification, and keep that approval with the shipment file. Our page on ICEGATE shipping bill reconciliation in the ERP covers matching the filed bill back to sales and GST records after clearance.
SLI checks a forwarding system enforces and ones a person signs
Structured SLIs let most field checks run as fixed rules at submission. Judgement stays with people for classification, licensing, routed-status decisions and anything read from a scanned or hand-amended document.
Scroll horizontally to see all columns.
| Check | Fixed rule at SLI submission | Software assists, a person decides |
|---|---|---|
| Classification number | Reject unless 10 digits and drawn from the item master | Classification specialist confirms new items |
| Value | Reject if value differs from the posted invoice adjusted to the port by more than $1 | Finance explains consignment or no-charge shipments |
| Licence data | Reject a blank licence code | Export control officer determines the licence authority |
| Routed status | Require the routed indicator to be answered yes or no | Compliance decides when buyer-nominated forwarding is truly routed |
| Authority | Block filing when no current power of attorney or template version is linked | Legal approves new authorization wording |
| Release instructions | Block "originals to consignee" when the order's payment term is a bank collection | Credit control approves any override |
| Scanned SLI from a new shipper | Route to manual intake; never auto-file | Text extraction pre-fills fields; a documentation clerk compares them with the PDF |
A structured payload makes those rules possible. The example below is an illustrative SLI record a forwarder portal could accept, with each regulatory field tagged to its 30.6 reference and the commercial instructions kept separate.
{
"sliId": "SLI-2026-11-0418",
"templateVersion": "SLI-T7 (authorization text approved 2026-03-02)",
"routedExport": false,
"ftr": {
"usppi": { "name": "Prairie Gear Works LLC", "ein": "XX-XXXXXXX", "ref": "30.6(a)(1)" },
"ultimateConsignee": { "name": "Rotterdam Drives BV", "type": "from AES code list", "ref": "30.6(a)(3), (a)(28)" },
"stateOfOrigin": { "value": "KS", "ref": "30.6(a)(4)" },
"lines": [
{ "scheduleB": "from item master", "originIndicator": "D",
"quantity": 24, "unit": "from Schedule B unit", "shippingWeightKg": 3180,
"valueAtPortUSD": 42985, "exportInfoCode": "from AES code list",
"licenseCode": "from export control determination", "eccn": "EAR99",
"ref": "30.6(a)(11)-(18), (a)(23), (b)(6)" }
],
"hazmat": { "value": false, "ref": "30.6(a)(21)" }
},
"commercial": {
"incoterm": "CIF Rotterdam, Incoterms 2020",
"freight": "prepaid",
"insurance": { "placeByForwarder": false },
"billOfLading": { "originals": 3, "consignee": "to order of shipper", "release": "originals only" },
"hold": "release documents to bank only"
},
"signedBy": { "name": "Export compliance lead", "date": "2026-11-12" }
}
Onboarding checklist for a new SLI process with your forwarder
Agree the SLI process once per forwarder and exporting entity, then audit it quarterly against a sample of filed shipments. The checklist below covers the decisions that should be settled before the first booking, not discovered during an export audit.
Scroll horizontally to see all columns.
| Decision | Owner | Evidence to keep | Review cycle |
|---|---|---|---|
| Authority model: standing power of attorney or per-shipment wording | Exporter's legal and compliance | Signed authority and template version | Annual and on signatory change |
| Field owners named for every SLI box | Export compliance lead | Field ownership matrix | On organisation change |
| SLI cut-off per mode and port | Logistics manager with forwarder | Written cut-off schedule | When carrier cut-offs change |
| Value method at port of export | Export finance | Worked examples per Incoterm used | Annual |
| Routed export handling | Export compliance lead | List of buyers who route, and any 758.3 writings | Quarterly |
| Return data from the filer | Documentation supervisor | ITN and filed data stored per shipment | Every shipment |
| Release rules linked to payment terms | Credit control | Template-to-term mapping | Quarterly |
| Five-year retention of SLIs and filings | Records manager | Retention schedule citing 30.10(a) | Annual |
If you are evaluating software that captures SLIs as structured records, enforces these checks and keeps the filing evidence together, you can outline your export volumes and forwarders through our request for proposal form. Related guides on export documents, filings and freight charges are collected in the Logistics and Supply Chain library.
Discuss this workflow
Describe your current systems, the recurring exception and the outcome you need. Keep shipment, customer and financial records out of the initial message.
Common operational questions
Practical answers for operations, engineering, and finance teams working on shippers letter of instruction in logistics & supply chain.
Is a shipper's letter of instruction a required government form?
Who is responsible for EEI data when the forwarder files from an SLI?
What does an exporter put on an SLI in a routed export?
Does India use a shipper's letter of instruction for exports?
References
Sources checked 13 November 2026. US and India statutory authorities and vendor documentation support platform facts; the worked examples and diagrams are original.
- US Census Bureau - Foreign Trade Regulations, 15 CFR Part 30, consolidated text revised 30 March 2026 (sections 30.1, 30.3, 30.4(b), 30.6(a)(17), 30.10 and Appendices A and C)Filer responsibilities, written authorization wording, routed export duties, filing deadlines by mode, value at port of export and five-year retention. Accessed 13 November 2026.
- Federal Register - Census Bureau final rule, Clarification of Filing Requirements Regarding In-Transit Shipments and Other FTR Provisions (2025-15493)Adds Appendix C on routed export data elements and the 30.3 statement that terms of sale have no regulatory basis; effective 15 September 2025. Accessed 13 November 2026.
- US Code of Federal Regulations - 15 CFR 30.3 (Cornell LII copy)Cross-check of 30.3(c), (e) and (f); eCFR blocked automated access. Accessed 13 November 2026.
- US Code of Federal Regulations - 15 CFR 758.3, responsibilities of parties to the transaction (Export Administration Regulations)Licensing responsibility in routed transactions moves to the foreign party's agent only on a writing; USPPI supplies ECCN or technical data on request. Accessed 13 November 2026.
- Government of India - Customs Act, 1962, sections 14(1), 50 and 51 (consolidated text published by the High Court of Tripura)Export value at time and place of exportation, exporter's declaration and accuracy duties, and the clearance order that may be made electronically; India Code refused automated access. Accessed 13 November 2026.
- CESTAT Mumbai - Customs Appeal No. 86792 of 2023, reproducing Customs Brokers Licensing Regulations, 2018, regulation 10(d), (e) and (n)Accessed 13 November 2026. Final order of 5 December 2024 on the tribunal's own site, quoting regulation 10(d) advice and reporting duty, 10(e) due diligence and 10(n) verification of IEC, GSTIN, client identity and functioning at the declared address.
- ASC X12 — EDI Supply Chain & Transportation Transaction Sets (204/210/214/856/940/945)US standard for electronic data interchange across shippers, 3PLs, and motor carriers.
- FMCSA — 49 CFR Part 395 Hours of Service & Electronic Logging Devices (ELD)US federal motor carrier dispatch and driver duty-status compliance mandate.
- ULIP & NIC GST E-Way Bill Portal — Unified Logistics & Rule 138 ComplianceIndian statutory goods-in-transit and multi-modal logistics verification framework.