Import Clearance: Shipments Released on Schedule With Duty Figures That Hold Up

Documents, duty and a dock that takes six containers a day

An import desk works through a week's intake of shipments, each with a commercial invoice, a packing list, a bill of lading and, where a preferential rate is claimed, a certificate of origin. The clearance policy decides which shipments are ready, which wait for documents and which go to review. Ready shipments then need a release slot at a receiving dock that can only take so many containers a day.

The shipment register is an Airtable base. Suppliers and the customs broker drop documents into a shared Dropbox folder, the policy and the tariff extract sit in Google Drive, the broker writes in Gmail, and the warehouse and finance teams work in Outlook. When a corrected invoice arrives, the clerk updates one cell, and the duty, the landed cost and the release batch that depended on it stay as they were.

Who works in the room

The desk opens one Kylon room per intake week. Questions about a shipment's status, duty or release slot go to Nova, the room's default agent. A message about the duty file reaches Ada even without a mention, because reviewing that file is its specialty. Broker threads belong to Ryan. When a broker sends a document, Ryan opens a thread for Nova whose first message names the shipment, the file and what it claims, so Nova re-runs that shipment instead of the whole week.

The intake week, stage by stage

The room guidelines point every agent at the same clearance policy and dock capacity sheet. Nothing is written to the register or booked at the dock until the trade compliance lead says so.

When documents and rates arrive mid-week

Most changes come as attachments on a broker thread. A certificate of origin turns up for a shipment held for documents, a supplier issues a corrected commercial invoice, or the broker forwards a tariff notice for one heading. Ryan reads the message, finds the shipment and writes a one-line brief for Nova. Each broker thread gets one reply from the desk, sent by a person, so the broker never has to work out which answer stands.

Nova re-runs only what the change touches, but follows it all the way through. A new invoice value changes duty, which changes landed cost, which can push a shipment past a day's dock cap and into the next batch. An amendment to HS 8544 moves every insulated cable shipment in the week and nothing else. Each moved record carries a note with the old and new figures and the message that caused the change.

What the checks catch

• A duty file that pulls in shipments from another intake week because it was filtered by arrival date
• A line entered twice in the clerk's file, or an amount that does not match the approved duty on the record
• A tariff change applied to every shipment instead of only the amended heading, or applied to duty but not to landed cost
• A release batch that goes over the dock cap after a corrected invoice moves one shipment
• A broker thread about to get a second reply when it already has one

What stays with people

• Approving each disposition, duty figure and release batch before it is written
• Reading a tariff notice or certificate where the wording is not clear-cut
• Sending every reply to the broker and every notice to the warehouse, which Ryan drafts
• Signing the close-out for each origin

Integrations in this workflow

Kylon is not a customs filing system and it does not replace the broker's. It works across the register, document folders and mailboxes the desk already has, and keeps the coordination between them in one room.

• Airtable
• Dropbox
• Gmail
• Google Drive
• Outlook
• Slack

• Airtable holds the shipment register, the release batches and the close-out records per origin
• Dropbox is the shared folder where suppliers and the broker drop invoices, packing lists and certificates
• Google Drive keeps the clearance policy, the tariff extract, the dock capacity sheet and the clerk's duty file
• Gmail carries the broker threads, where each reply stays a draft until a person sends it
• Outlook is how release notices reach the warehouse and duty totals reach finance, each sent by a person
• Slack is where the receiving dock posts its daily capacity and any doors out of service

Where to start

Pick one intake week and one origin. Connect the Airtable base that holds the register, give Nova access to the Dropbox intake folder through a grant the folder's owner approves, and add one line to the room guidelines: an amendment re-runs every shipment it touches through duty, landed cost and release batch, and the compliance lead approves each changed record.

“A corrected invoice used to change one cell. Now it changes everything that depends on that cell, and the thread shows what moved.”

Set it up with your agent

Open a new Room, add your agent and paste this prompt. It connects the tools, builds the App with you and asks for your rules one step at a time, and nothing goes out until a person approves it.