Schedule D port codes: Port of Entry and Unlading Codes Explained

Key Points
- Schedule D port codes are four-character district and port identifiers that tell CBP which port processes an entry, for example 5301 for Houston, TX in district 53 Houston-Galveston.
- The CATAIR Entry Summary Create/Update chapter (September 2025) defines district/port of entry and port of unlading as 4 alphanumeric fields.
- Census maintains the master list, and CBP republishes it as ACE Appendix E, Schedule D US CBP Port Codes, dated February 3, 2026.
- A port code that disagrees with the manifest or the bonded location can reject the transmission or delay release.
- Schedule D is not Schedule B (export commodity codes) or Schedule C (country codes), and mixing them up is a data error.
On this page
- At a glance
- How are Schedule D port codes structured and where do they come from?
- Who selects Schedule D port codes and when?
- How are Schedule D port codes reported in ACE?
- Common Schedule D port code errors and what they cost
- How do Schedule D port codes relate to other entry data?
- Frequently asked questions
- What importers and brokers should do
- Key references
Schedule D port codes are the Census Bureau customs district and port codes, four characters made of a two-digit district plus a two-digit port, that customs brokers and importers report as the port of entry and port of unlading on CBP entries and manifests. The broker selects them while building the entry, and the port of entry code decides which CBP port processes the entry from release through entry summary review.
At a glance
- Full name: Census Bureau Schedule D District and Port Codes and Descriptions
- Who prepares or uses it: Customs brokers and self-filing importers on entries; carriers on manifests; CBP port staff reviewing the entry
- When in the lifecycle: Selected when the entry is built, reported at release and on the entry summary
- System or channel: ACE, through ABI entry and entry summary transmissions
- Format: 4 alphanumeric, district (two digits) plus port (two digits), for example 5301
- Governing authority: Census maintains the list; CBP republishes it as ACE Appendix E (February 3, 2026)
- Related terms: FIRMS code, SCAC code, IOR number, ultimate consignee number, entry type codes
How are Schedule D port codes structured and where do they come from?
Schedule D port codes are built by joining a two-digit customs district number to a two-digit port number, so the first two characters always identify the district. In port code 5301, Schedule D port code 5301, Houston, TX (seaport), the "53" is customs district 53 Houston-Galveston and the "01" is the Houston port within it. Other ports in the same district share the leading "53" but carry their own port digits, so confirm the exact code for the specific seaport, airport, or land crossing rather than assuming a district code covers every location.
The links in this article go to the primary documents: the Census code list, the CBP ACE appendix, and the CATAIR chapter themselves. Read the source. Census maintains the master list as the Census Bureau Schedule D District and Port Codes and Descriptions, and CBP republishes it for filers as CBP ACE Appendix E, Schedule D US CBP Port Codes (February 3, 2026). As of November 2026, the February 2026 appendix is the latest revision this article relies on; check the CBP CATAIR page for any later version before updating code tables.
Not Schedule B or Schedule C
Census publishes several schedules with similar names. Schedule B is the export commodity classification, and Schedule C is the country code list. Neither belongs in a port field, and a country or commodity code typed into a port field will fail validation or, worse, pass as an unintended port.
Who selects Schedule D port codes and when?
Schedule D port codes on an entry are selected by the filer, normally the customs broker, at the moment the entry is built, before transmission to CBP. The broker chooses two values: the district/port of entry, which is the port where the goods are entered, and the port of unlading, which is where the cargo came off the importing conveyance. These often match, as with an ocean shipment discharged and entered at port code 5301, but they differ when goods are unladen at one port and moved in bond to another for entry.
The broker should match the manifest. The carrier's manifest already names the port of unlading, and the port of entry must agree with where CBP will actually process the goods and where the cargo sits. Because the port of entry code routes the entry to a specific CBP port, choosing it is also choosing which port's staff will review the release and the entry summary.
How are Schedule D port codes reported in ACE?
Schedule D port codes are transmitted in ACE as two 4 alphanumeric data elements defined in the CATAIR Entry Summary Create/Update chapter (September 2025): district/port of entry and port of unlading. ACE validates each value against the Appendix E table, so a code that does not exist on the list is rejected at the data level.
The same fields appear across entry types. An entry type 01 (ACE entry summary type code 01, Consumption, Free and Dutiable) at Houston carries 5301 as its port of entry, and so does an entry type 03 (Consumption, AD/CVD) filed there, alongside its case number and deposit. An entry type 06 (Foreign Trade Zone consumption entry, including weekly estimated entries) and an entry type 11 (Informal, Free and Dutiable) also carry a port of entry. Confirm in the current CATAIR which port fields are mandatory or conditional for each entry type and transaction, because the requirements vary by record and filing scenario. For how the port relates to the entry number itself, see our guide to the 11-character CBP entry number.
Common Schedule D port code errors and what they cost
Schedule D port code errors cost time: a code that disagrees with the manifest or the bonded location can reject the transmission or delay release while CBP and the broker reconcile the data. The most frequent problems are:
- Manifest mismatch: the entry shows a port of unlading different from the one on the carrier's manifest, so the entry does not match the bill.
- Wrong port in the right district: the broker uses the district's main port when the goods were actually entered at a different airport, seaport, or crossing in that district.
- Bonded location conflict: the port of entry does not correspond to the port where the cargo's bonded facility sits.
- Stale code tables: software still using an older list instead of the February 3, 2026 Appendix E.
- Schedule confusion: a Schedule B or Schedule C value entered where a Schedule D port code belongs.
Corrections after release go through the normal entry summary correction process; confirm the available remedy and timing with CBP or in the current regulations on eCFR Title 19.
How do Schedule D port codes relate to other entry data?
Schedule D port codes work alongside several other identifiers, and CBP expects them to tell a consistent story about where the cargo is and who is responsible for it.
- FIRMS code: the Facilities Information and Resources Management System code identifies the bonded facility, pier, CES, or warehouse holding the goods. That facility must sit at the port reported as the port of entry. See our FIRMS code guide.
- SCAC code: the Standard Carrier Alpha Code identifies the importing carrier whose manifest names the port of unlading. See our SCAC code explainer.
- IOR number: the importer of record number identifies the party liable for duties. It does not change with the port, but the port determines which CBP office reviews that importer's entry.
- Ultimate consignee number: the EIN, SSN, or CBP-assigned number of the party on whose account goods are shipped, reported with the importer number regardless of port.
- CBP-assigned number: the importer identification number CBP issues via CBP Form 5106 to parties lacking an IRS EIN or SSN; it is an importer identifier, not a port or location code.
Frequently asked questions
What is the difference between port of entry and port of unlading?
Both are Schedule D port codes. The port of unlading is where cargo left the importing conveyance, as shown on the manifest; the port of entry is where the goods are entered and where CBP processes the entry. They match when goods are entered where they arrive and differ when cargo moves in bond first.
Where do I find the official list of Schedule D port codes?
Census maintains the master list of Schedule D port codes, and CBP republishes it as ACE Appendix E, Schedule D US CBP Port Codes, dated February 3, 2026, on its CATAIR page.
Is 5301 the code for all Houston imports?
No. Among Schedule D port codes, 5301 is the Houston, TX seaport in district 53 Houston-Galveston. Air cargo and other locations in the district use different port digits, so confirm the correct code in Appendix E.
Can a wrong Schedule D port code be fixed after release?
Usually the error is caught at transmission because ACE validates Schedule D port codes. If a valid but incorrect code is accepted, confirm the correction path with CBP at the processing port.
What importers and brokers should do
- Load the February 3, 2026 ACE Appendix E into entry software and check for later revisions on the CBP CATAIR page.
- Before transmitting, compare the port of unlading against the manifest and the port of entry against the FIRMS code of the holding facility.
- Keep Schedule B and Schedule C tables out of port-code dropdowns so the wrong schedule cannot be selected.
- Review rejected transmissions for port mismatches and feed fixes back into your entry document checklist.
Key references
- Census Bureau foreign trade program: home of the Schedule D District and Port Codes and Descriptions master list.
- CBP ACE CATAIR page: hosts ACE Appendix E, Schedule D US CBP Port Codes (February 3, 2026), and the Entry Summary Create/Update chapter (September 2025).
- CBP ports directory: contact details for the port that processes your entry.
- eCFR Title 19: current customs regulations for confirming correction procedures.
Working through tariffs on real entries? Create an account, then see plans for the full toolkit.