Freight forwarding automation: bookings, B/Ls, origin docs
Carrier bookings, draft B/L checks, EPA origin documents, and vessel tracking: paper and website work left outside NACCS, automated with AI and human review.
- Runs on your own PCs and servers
- Use Azure OpenAI, Amazon Bedrock, Google Vertex AI, or an in-house model
- Its engine is Descarty's open-source Dagu (GPL-3.0)

Common problems
Booking requests and shipping instructions arrive by email and are typed again into each carrier's website
More than half of B/L issuance and export permit notices still travel as email attachments
Errors in an EPA certificate of origin can cost the preferential tariff rate
Use cases in this industry
Track vessels and tell shippers about ETA changes
Poll carriers' tracking APIs for your B/Ls and containers and detect ETA changes. AI drafts what the change affects and the shipper notice; staff check it.
Manage free time, demurrage, and detention
Calculate each container's remaining free time from discharge, gate-out, and empty-return events, and alert staff as deadlines near. AI drafts pickup requests.
Read and cross-check import documents before filing
AI reads the invoice, packing list, and B/L and cross-checks goods, quantities, weights, and values. A customs specialist resolves mismatches before filing.
Enter carrier bookings and shipping instructions
AI reads booking requests and shipping instructions from shippers' emails. Approved details are entered on the carrier's site, and AI drafts the shipper reply.
Check draft B/Ls against shipping instructions
AI reads the draft B/L from the carrier and checks it item by item against the S/I, invoice, and packing list. Staff confirm differences with the shipper first.
Check EPA origin documents before import filing
AI reads EPA origin documents for imports and checks the exporter, invoice number, goods, and quantity against the invoice. A customs specialist reviews issues.
Declarations run through NACCS. The manual work sits before and after
Japan has 988 licensed customs brokers with 2,042 offices (April 1, 2025). 16,945 people work in customs brokerage, 8,372 of them licensed customs specialists (April 1, 2026).
Import and export declarations are almost entirely electronic through NACCS, Japan’s system for customs, port, and related private-sector procedures. In 2025, NACCS processed 99.9% of 226.8 million import permits and 37.38 million export permits. Data entered in an earlier step can be reused in later ones, which also cuts entry work. The seventh generation of NACCS went live in October 2025.
The manual work is in the exchanges between private businesses: shippers, forwarders, and carriers. Japan’s Ministry of Land, Infrastructure, Transport and Tourism (MLIT) describes container logistics procedures between private businesses as a mix of paper, phone, and email, analog and optimized company by company.
| Work | Screens and systems used | What stays manual |
|---|---|---|
| Bookings | Carrier websites, INTTRA, Cyber Port | Reading the shipper’s email and typing it again into each carrier’s website |
| Shipping instructions (S/I) and B/Ls | Carrier websites, email | Comparing the draft B/L with the S/I and the invoice |
| Import and export declarations | NACCS, customs software | Picking out what the declaration needs from invoices and packing lists |
| EPA preferential rates | Certificates of origin, origin declarations | Checking entries against the agreement’s requirements and the invoice |
| Vessel and container tracking | Carrier websites, tracking APIs, Cyber Port | Checking each carrier and telling shippers about ETA changes |
| Air cargo bookings | Airline websites, booking platforms | Entering bookings on each airline’s screens |
In air cargo, IATA says the electronic air waybill (e-AWB) is now used for more than two out of three shipments. For bookings, ANA began in June 2020 to take cargo space bookings through the website of cargo.one, a German booking platform.
Nearly half of bookings, and most B/Ls, still travel as email attachments
In MLIT’s 2024 survey of 472 companies, 47.0% of export bookings were digital and 45.0% went by email attachment. For B/L and waybill issuance, 62.3% went by email attachment, and for export permit notices, 54.4%. MLIT notes that roughly 60% or more of B/L and waybill issuance, export permit notices, and a few other steps are still not digitized.
Ways to connect by data already exist:
- e2open says its INTTRA network connects more than 100 ocean carriers and NVOCCs and handles bookings, shipping instructions, and VGM in one place
- DCSA, formed by ten of the largest ocean carriers, published the final versions of its Booking 2.0 and Bill of Lading 3.0 data exchange standards in February 2025
- MLIT’s Cyber Port (port logistics) exchanges procedures between private businesses as data, with 957 companies registered as of September 1, 2025
Even so, e2open notes that shippers often manage bookings and shipping instructions across dozens of carriers and NVOCCs, using multiple portals, email, or phone. Where a carrier isn’t connected, or a trade starts with a shipper’s email, someone still reads the request, types it into the carrier’s website, and sends the confirmation back to the shipper.
Checking the draft B/L a carrier sends is the same. Changing a B/L later can cost a fee; Maersk’s Japanese FAQ says B/L amendment fees vary by country.
NACCS connects by data, but its input starts as shippers’ documents
NACCS is adding support for international standards such as EDIFACT and XML and for links with private-sector systems. Cyber Port has connected directly to NACCS since March 2023, and MLIT says this can cut customs entry items by up to 80%.
MLIT also names, among the main users of that link, businesses that enter procedures and inquiries into NACCS by hand, through netNACCS and similar tools. An import declaration states the goods’ description, quantity, value, origin, and more, taken from the invoice and packing list the shipper sends.
Dedicated document-reading products exist as well. In February 2026, TradeWaltz added packing lists to the trade documents its AI-OCR reads, with output that can be passed to customs software.
Errors in EPA origin documents can cost the preferential rate
To claim an EPA preferential rate on imports whose total customs value exceeds 200,000 yen, the importer must submit or keep a certificate of origin, origin declaration, or origin statement (“origin documents”). Origin is shown by third-party certification, self-certification by an approved exporter, or self-declaration, and each agreement sets its own required entries.
Japan Customs states that origin documents that don’t meet these requirements will not qualify for the preferential rate except in limited cases, and asks importers to check before filing.
- Errors in items that tie the document to the declared goods, such as exporter and importer names or the invoice number, are in principle treated as minor if trade documents confirm the link
- Errors in items that show authenticity, such as seals or the issuing authority’s signature, make the certificate invalid except for very trivial matters
- Customs also publishes cases of procedural errors, such as how goods were described on a certificate of origin
For exports, a first-type certificate of origin is applied for by the exporter or producer through the Japan Chamber of Commerce and Industry’s (JCCI) online system. JCCI explains that the certificate is an official document, so applications by anyone other than the applicant company itself are restricted. Electronic issuance as a PDF or by data exchange is also available.
What to check before automating
- Whether a carrier’s website may be operated automatically: check each carrier’s terms. Some, such as ONE, prohibit scraping and similar access. Use an API, INTTRA, or Cyber Port first where the trade connects that way (Check the terms before you automate a website)
- What the shipper decides: shipment details and what the B/L says follow the shipper’s instructions. When a difference turns up, confirm with the shipper before correcting it
- What the customs specialist decides: what is declared, whether to claim a preferential rate, and how to treat errors in origin documents. Filing through NACCS stays with the specialist, as today
- Export control decisions: METI states that responsibility under the Foreign Exchange and Foreign Trade Act basically lies with the exporter. Export control classification and catch-all checks are not handed to AI
- Who applies for certificates of origin: applications for a first-type certificate by anyone other than the company itself are restricted, so no flow applies on an exporter’s behalf
- How each site signs in: carrier IDs, one-time passwords, and so on differ by site
What Kitewell does
Descarty’s Kitewell is integration and automation middleware that connects systems through APIs, files, databases, and screens.
- Operates carrier websites: on sites whose terms allow it, AI reads the screen and fills in booking and other screens. Operations that worked are remembered and repeated the same way on later runs
- Keeps going when screens change: when a remembered operation no longer fits the screen, AI reads the screen again, does the step, and remembers the new operation. If that still fails, the run stops, and AI looks into the cause and suggests the fix
- Starts from email: checks Gmail, Microsoft 365, or IMAP mail at set intervals and saves attachments from shippers and carriers
- Reads and cross-checks documents: AI reads invoices, packing lists, draft B/Ls, and origin documents as PDFs or images and shows differences item by item. The AI model is chosen per step
- People check where it matters: approval can be set on any step, such as before entering a booking or replying to a shipper. Requests reach Slack, Microsoft Teams, and email, and sending one back restarts the run from the chosen step
- Passwords stay out of AI’s hands: carrier site passwords are referenced by name and typed in without showing the value to the AI. When a one-time password is required, the run pauses until staff enter it
- Keeps the checking rules: how to check each agreement’s documents and each shipper’s exceptions can be kept in the project’s knowledge
- Every operation on record: each run keeps its logs, screenshots of the screens it filled in, and approval decisions
You can start from one piece of work, such as taking a booking request through entering it on the carrier’s site and confirming it to the customer. A demo shows how it runs, a free connection test confirms Kitewell reaches your systems, and a one-month PoC measures the result against success criteria agreed up front, before you license it for production. See From evaluation to production for details.
Sources
- Japan Customs: 9104 Current status of customs brokers (in Japanese)
- Japan Customs: 8101 Current status of customs specialists (in Japanese)
- NACCS Inc.: Business overview (in Japanese)
- NACCS Inc.: Corporate history (in Japanese)
- NACCS Inc.: NACCS Brochure (in Japanese and English)
- Ministry of Finance, Customs and Tariff Bureau: Customs Report, “Greater convenience through IT” (June 2026; in Japanese)
- Ministry of Finance, Customs and Tariff Bureau: Customs Report, “Data” (June 2026; in Japanese)
- MLIT: Cyber Port (port logistics): work carried out in fiscal 2024 (September 19, 2025; in Japanese)
- IATA: IATA ONE Record
- LNEWS: ANA starts cargo space bookings through cargo.one’s website (June 22, 2020; in Japanese)
- e2open: Simplify Bookings Across Carriers with Ocean Shipping Software
- DCSA: DCSA releases final versions of Booking 2.0 and Bill of Lading 3.0 standards (February 2025)
- Maersk: What are the fees for amending Bill of Lading details? (in Japanese)
- MLIT: Direct link between Cyber Port and NACCS starts on March 13, 2023 (December 14, 2022; in Japanese)
- Japan Customs: 1106 Items stated in an import declaration (in Japanese)
- LOGISTICS TODAY: TradeWaltz turns three trade documents into data with AI (February 13, 2026; in Japanese)
- Japan Customs: Important: please read before filing an import declaration that claims a preferential rate (in Japanese)
- Japan Customs: Rules of origin and certification procedures, 2-1 and 2-2 (in Japanese)
- Japan Customs: Cases of procedural errors under EPAs and GSP (in Japanese)
- JCCI: STEP 7: Applying for a certificate (in Japanese)
- JCCI: STEP 5: Company registration (in Japanese)
- JCCI: End of over-the-counter issuance of certificates of origin at eight JCCI offices (March 2, 2026; in Japanese)
- Ocean Network Express: ONE’s Term of Use
- METI: Overview of security export control (introductory seminar) (September 2026; in Japanese)
Frequently asked questions
- May a tool operate carriers' websites?
- It depends on each carrier's terms of use, and some carriers prohibit scraping and similar access. In the PoC, trades that connect through an API, INTTRA, or Cyber Port use those, and screen operation is limited to what the terms allow.
- Does it file declarations through NACCS?
- No. NACCS, Japan's customs and port system, already processes about 99.9% of import and export declarations electronically. Deciding what is declared and filing through NACCS stay with the licensed customs specialist, as today. Kitewell takes on the work before that: reading and cross-checking documents and dealing with carriers.
- Can AI decide export control classification or origin?
- No. Japan's Ministry of Economy, Trade and Industry states that responsibility under the Foreign Exchange and Foreign Trade Act basically lies with the exporter. Whether to claim a preferential rate and how to treat errors in origin documents are decided by the customs specialist. AI reads documents and points out missing entries and differences between documents, nothing more.
Use cases for any industry
Read invoices into the accounting system
AI reads incoming invoices, checks them against purchase orders, and records them in the accounting system. Invoices whose amounts differ wait for approval.
Create invoices and send them by email
Invoices are filled into your template from an Excel billing list and emailed once a person approves. AI first points out amounts far from last month's.
Research a list of prospects
For an Excel list of hundreds of companies, each one's business, locations, and size are collected from its website into its row, with a priority for sales.
Find missing clock-ins
Collect yesterday's clock-ins from the attendance system and, once HR approves, ask employees with missing entries to fix them in Teams.
Take in emailed invoices and draft the entries
Find unread email with an invoice attached, have AI read the amount, and record a draft ledger entry. Uncertain entries wait for accounting to confirm.
Review SaaS accounts
A SaaS account review matches each service's users to current staff. Collect each console's users, match them, and disable leavers only after approval.
Partner registration that starts on approval
A kintone approval starts the workflow by webhook. It looks up the tax registration number, AI matches it to the request, and a match enters the sales system.
Collect KPIs from SaaS tools into a weekly report
Collect figures from advertising, sales, support, and other SaaS tools, and produce a weekly report with week-on-week comparisons and likely causes of change.
Check supplier invoice registration numbers
Check your supplier master's registration numbers monthly through the NTA's Web-API, and list suppliers that were revoked, lapsed, or differ in name.
Prove Kitewell on your own systems
Try it free for 14 days on your own PC. To see it working first, ask for a 30-minute demo. There is also a one-month onboarding (¥500,000 before tax), where we build your first job together.
What the onboarding checks
- Which method connects each target system: API, file, database, or screen
- Whether Kitewell can work a system with no API through its screens, as a person would
- Whether AI relearns a step and processing continues when a screen changes
- Whether errors are handled as agreed: stop, notify, or retry
- Whether it runs in your environment, with the AI model you choose
- Whether processing time and AI usage cost fit daily operation
How the onboarding runs
- Week 1Requirements and success criteria
- Weeks 2 to 3Build
- Week 4Verify on production screens
- Final dayReport
One-month onboarding
- Length
- One month
- Cost
- ¥500,000 (tax excluded). Your staff build, with the developer beside them
- If you go on to a license
- The onboarding fee is credited to the first year's contract
- Without the onboarding
- At Team scale, start on Team monthly (¥14,800 per computer a month, tax excluded), and cancel in any month
You can try it first on your own PC, in the free 14-day trial.