A container from your supplier in Vietnam is on a hold at the port of Long Beach. The notice says the broker needs additional documentation on the country-of-origin claim. Your TMS has the booking, the bill of lading, and the customs entry. What it doesn't show is that the supplier already provided the origin certificate two months ago for the previous shipment, that there was a similar question on a March entry that you resolved by sending the production records, and that your broker's preferred contact at CBP for this kind of question is a specific officer who responds faster on Wednesdays.
Most international-trade operations have this shape. The TMS handles bookings, documents, and entries. The actual operational memory — the running threads with suppliers, brokers, freight forwarders, and customs authorities — usually lives in email, a couple of binders, and the trade compliance manager's working memory.
This post is about the layer that sits next to the TMS. The notes workspace that holds the conversational context, the classification reasoning, and the running threads that make a 4 PM customs question answerable in twenty minutes instead of two days.
What an import/export operation needs from a notes system
The shape:
- Per-shipment continuity — the running thread for each booking, the documents, the holds, the resolutions, the lessons learned
- Supplier and customer relationships — context that spans hundreds of shipments per partner over many years
- Broker, forwarder, and carrier relationships — who's reliable for what lane, who responds at what speed, who has the right contacts at which port
- Classification memory — the HTS codes you've used and why, the rulings you've referenced, the country-of-origin substantiation packages
- Compliance and trade-program memory — FTA qualifications, AD/CVD exposure, FDA filings, FCC rules for telecom, USMCA certifications, the duty-drawback claims still open
- Cross-shipment pattern recognition — every shipment from this supplier with the same recurring documentation issue, every entry through this port with the same examination pattern
- Reference material — the broker's standard procedures, country-specific guidance, the running notes on tariff changes that affect your products
Plus: the work is genuinely time-sensitive. A container on demurrage is bleeding money by the hour. The right notes need to be one search away. Adjacent operational shapes are in How to Use AI Notes for Fleet Management and AI Notes for Compliance and Audit Preparation.
A page-per-shipment shape, with supplier and code vaults alongside
In Docapybara, every shipment gets a markdown page. The convention varies by operation — PO-12834 / Shanghai → LAX / ETA 2026-05-03 works for most. Inside: the booking detail, the vendor confirmation, the documents, the running thread of any issues.
Separately, suppliers, brokers, customers, and HTS classifications get their own pages. A common shape:
Shipments → by year and month, with one page per shipmentSuppliers → one page per supplier with full contextCustomers → one page per customerBrokers & Forwarders → one page per partnerClassifications → one page per HTS code you regularly use, with the reasoning and any rulingsCompliance → by program — USMCA, AD/CVD, FDA, FCC, DrawbackCountry → one page per country you regularly source from or sell to, with current tariff context, regulatory flags, and recent guidance
Plain markdown means the pages stay searchable, copyable, and exportable. If the operation transitions to a new compliance manager or gets folded into a parent organization, the institutional memory comes with it as text anyone can read.
A live database for active shipments and the broker queue
Embed a :::database::: directive on the Active Shipments page. Six column types — text, number, date, select, checkbox, link — cover the work. A typical board:
| PO |
Supplier |
Origin |
Destination |
ETA |
Status |
Hold? |
Owner |
| PO-12834 |
Bay Tex Vietnam |
Haiphong |
LAX |
2026-05-03 |
At customs |
Yes — origin doc |
M. Liu |
| PO-12835 |
Lin Mfg China |
Shanghai |
LAX |
2026-05-08 |
In transit |
No |
M. Liu |
| PO-12836 |
DRC Mexico |
Veracruz |
Houston |
2026-05-01 |
At yard |
No |
A. Khan |
Sort by ETA, you see the next two weeks. Filter by hold status, you see what's at risk. Filter by owner, you see your individual queue.
The same shape works for the Broker Queue — a database of every open broker question, who it's with, what's pending, and the SLA. When the agent reads it, "what broker questions have been open more than three days?" gives you the escalation list.
The agent reads across years of shipments and classifications
Capy, the assistant inside the workspace, can read across every shipment, supplier, and classification when you ask. The kinds of questions trade compliance actually has to answer fast:
- "The container at Long Beach is on an origin-doc hold. Pull every prior origin documentation issue we've had with Bay Tex Vietnam and how we resolved each."
- "The customer is asking what HTS code we use for the new product line — what's the closest classification we already use, what's the reasoning, and is there a CBP ruling we've referenced?"
- "List every shipment from China in the last 90 days that's been examined at LAX, and any pattern in what triggered the examinations."
- "Draft a country-of-origin substantiation package for PO-12834 using the supplier's prior documentation, the production records, and the standard format for this lane."
The agent reads the relevant pages, drafts the package, you adjust. The compliance work that took an afternoon becomes an hour of reviewing what the workspace already knows. The agent-acts-on-docs idea behind that is laid out in Claude Code for Documents.
Recording the broker and supplier conversations that matter
Most broker calls don't need to be recorded. Some do. The post-hold debrief where the broker walks through what triggered the examination. The annual compliance review. The supplier conference call where you're trying to clarify a country-of-origin claim that has implications for the next year of shipments.
Audio with speaker labels keeps each speaker attributable on replay. Drop the recording on the relevant supplier or broker page. The transcript drops in alongside. When you're drafting a follow-up email or a substantiation package and you need the supplier's exact words on what their production process looks like, the answer is searchable text.
The recording question is a workflow choice — what's appropriate to record across jurisdictions, what consent looks like, what gets retained. For trade operations especially, there are export-control and confidentiality rules that may govern what can be recorded. Once your team has settled the policy, the workspace just holds whatever you decide to capture.
Old entries, rulings, and supplier docs
Trade operations accumulate paper by the year. Customs entries, broker invoices, supplier production records, FTA certificates, CBP rulings you've referenced, the original commercial invoices, the packing lists, the bills of lading, the OGA filings. They're useful when findable and a problem when not.
Drop the PDFs into the relevant shipment, supplier, or classification page. Each one converts to markdown automatically, which means the agent can read across them. When a CBP officer asks "what does the prior origin documentation for this product look like?", the agent pulls the relevant entries and the supplier docs as text. When the broker proposes a new HTS classification, the agent can pull the prior CBP rulings you've cited and check whether the reasoning still applies.
For a long-tenured trade operation, this is often the single highest-leverage day of work. The institutional memory locked in customs filings becomes searchable.
The tariff and regulation page that you actually update
Trade rules change constantly. Section 301 tariff lists update. AD/CVD orders get amended. FTA programs add or drop products. Country-specific guidance shifts. Most operations stay current through a combination of broker emails, trade-press subscriptions, and the compliance manager's diligent reading.
A Country page in the workspace is short but useful: current tariff context for the products you trade, recent regulatory changes, FTA qualification status, any export-control flags, contact info for the broker's local agent. Updates happen as the news comes in. The agent can do the routine work: "Read the broker's update from this week about the Vietnam tariff change. Update the Vietnam page with what changed and which of our products are affected."
The page becomes the running source of truth for what does our operation need to know about this country right now. When a sales rep asks whether the new tariff affects an upcoming order, the answer is one query away.
The compliance calendar that doesn't get away from you
Compliance is the part of trade work where forgetting becomes expensive in a way that shows up as penalties. AES filing missed. FDA prior notice late. ISF filed past 24 hours before vessel loading. USMCA certification not refreshed at year-end. The dates are scattered across emails from brokers, notices from agencies, and the compliance manager's calendar.
A :::database::: on the Compliance page with columns for entity, requirement, last completed, next due, status, owner gives you the running picture. Sort by next due, you see the next 90 days. When the agent reads it, "what compliance items are due in the next 60 days, by program?" returns the list. You assign owners, schedule the work, file the resulting documentation back to the workspace.
The workspace doesn't replace whatever official trade compliance system the broker or jurisdiction requires. It does mean the data isn't sitting in three different places when the audit notice arrives. The repeatable-procedure layer specifically is covered in Standard Operating Procedures, Without the Wiki Maintenance Tax.
Try Docapybara free
The fastest test: pick the shipment that's giving you the most active operational pain right now. Open Docapybara, create the shipment page, drop in the bill of lading, the commercial invoice, the supplier emails, and the broker's recent thread. Add the supplier's page if you don't have one. Try Docapybara free, bring one active shipment with a hold and a stack of prior entries from the same supplier, and see whether the workspace can hold the parts of trade work the TMS leaves on the floor.