How do we get certificates of analysis and other supplier documents onto every shipment?
How do you get certificates of analysis onto every shipment?
It is Tuesday afternoon at a specialty chemicals plant. A tanker of solvent is due to load at 7:00 a.m. Wednesday for a coatings customer. The customer's receiving rules are clear: no certificate of analysis for the lot, no unloading. The quality lab has finished testing, but the COA has not been sent. Separately, a supplier's inbound shipment of an additive arrived that morning without its COA, so the warehouse has put it on hold. The logistics coordinator has two documents to chase, three people to ask and a growing list of other loads.
To get certificates of analysis and other supplier documents onto every shipment, write down which documents each shipment needs, name who owns each one and when it is due, request them as soon as the load is planned, follow up in the same thread by email and phone until someone answers, and attach each document to the shipment record once it arrives. Missing documents become a problem only when nobody notices until the driver is at the dock. A clear list, owners and a chase routine move that moment to a day earlier.
COAs are the sharpest example, because customers in chemicals, food, plastics, metals and pharmaceuticals often refuse freight without one. But the same approach works for packing lists, commercial invoices, safety data sheets, certificates of origin and any other document a customer, carrier or broker expects.
Why documents go missing
Documents rarely go missing because nobody cares. They go missing because:
- Nobody wrote down which documents each customer needs.
- The document belongs to a different team, such as quality or export, that does not see the shipping schedule.
- The request went to a general inbox and nobody owned it.
- The supplier sent the COA for the right product but the wrong lot.
- The document arrived but was saved on someone's desktop, not with the load.
Each cause has a fix, and none of them requires new paperwork. They require a list, an owner, a deadline and a place to file.
What "every shipment" really means
"Every shipment" sounds simple, but most plants have exceptions. One customer wants a COA on every load; another wants it only for new lots; a third reads it from a supplier portal. Write those rules down per customer. A shipment that needs no COA should be just as clear as one that does, so nobody wastes time chasing a document the customer never asked for.
Want to map it for your shipments?
Let's review which documents your shipments need and who sends them today. You don't need to prepare anything: Cartage maps the workflow with you on the call.
See it on your own loads. Wilson, by Cartage, is an AI logistics agent that quotes, books, tracks, audits and pays for freight with your approved carriers.
Book a demo →Which documents should travel with a shipment, and who owns them?
Each document has a different owner, a different trigger and a different deadline. Treat them as separate tasks on the same shipment, not as one "paperwork" step.
The common documents
| Document | What it proves | Usual owner | When it is needed |
|---|---|---|---|
| Certificate of analysis (COA) | The lot meets the agreed specification | Quality lab or the supplier's quality team | Before pickup or before unloading |
| Bill of lading | The contract of carriage and what was tendered | Shipper's warehouse or logistics team | At pickup |
| Packing list | What is in each package or pallet | Warehouse | At pickup, often with the freight |
| Commercial invoice | Value and terms for cross-border freight | Export or finance team | Before the border crossing |
| Certificate of origin | Where goods were made, for trade rules | Export team or supplier | Before the border crossing |
| Safety data sheet (SDS) | Hazards and handling for a chemical | Quality or regulatory team | With hazardous or chemical freight |
| Lot or batch traceability record | Which lots are on the load | Warehouse or quality | At pickup |
| Proof of delivery (POD) | The freight was received, with any exceptions | Carrier | After delivery |
Not every shipment needs all of these. The point of the table is to make ownership visible. When the COA is late, the logistics coordinator should know immediately that the quality lab owns it, not spend twenty minutes finding out.
Inbound and outbound COAs
There are two COA flows, and they are often confused.
- Outbound: the company's own quality lab issues a COA for each lot it ships. The customer needs it before it will accept the freight.
- Inbound: suppliers send a COA for each lot they ship to the company. The company's receiving team needs it before releasing the material into production.
The chase is similar in both cases, but the people differ. Outbound COAs are chased internally. Inbound COAs are chased from suppliers, often by someone in purchasing or quality who is also handling a dozen other tasks. For more on inbound coordination, see how a food manufacturer should coordinate inbound supplier freight.
Documents that depend on lot numbers
A COA is tied to a specific lot. So is a traceability record. If the shipment does not carry a lot number, the right COA cannot be matched. That makes the lot number a required field on the order itself. An order that reaches logistics without a lot number for a COA customer is incomplete and should not be booked until the lot is known.
How should a team chase missing documents until someone answers?
Chase documents on a fixed schedule tied to pickup, in the same thread, by email first and phone next, with a clear escalation point. The worst chase is the one that starts at 6:30 a.m. on the day of pickup.
The chase timeline
Consider a hypothetical outbound load that picks up Thursday at 8:00 a.m. for a customer that requires a COA before unloading.
| When | Action | Channel |
|---|---|---|
| Monday, when the load is planned | Request the COA for the lot from the quality lab | Email or the team's chat |
| Tuesday, end of day | First follow-up in the same thread if no reply | Same thread |
| Wednesday, midday | Second follow-up; call if the owner does not reply | Phone and the same thread |
| Wednesday, 3:00 p.m. | Escalate to the logistics manager with what was asked and when | Chat or email |
| Thursday, before pickup | Confirm the COA is attached and sent, or that the team has decided how to proceed | Email to the customer and the carrier as required |
The same timeline works for inbound COAs from suppliers. Replace the quality lab with the supplier's contact and move the deadline to before receiving.
What a good request says
A request that can be answered in one reply saves a round of follow-ups. Include:
- The order number, customer and ship date.
- The product and the lot number.
- The document needed and the format the customer expects.
- The deadline, stated as a date and time, with the reason.
- Where to send it, and that a reply in the same thread is fine.
A hypothetical request might read: "COA needed for lot 24-1187, solvent, order 55102, shipping Thursday 8:00 a.m. to a coatings customer that will not unload without it. Please reply with the PDF by Wednesday noon."
Following up without starting over
Each follow-up should go in the same thread, so the person sees the original request and the history. A new email with a new subject line looks like a new task and gets triaged again. Short, specific follow-ups work best: "Still need the COA for lot 24-1187, ships Thursday 8:00 a.m." If email gets no answer, a phone call is often faster, especially with suppliers whose inboxes are full.
When to escalate
Escalate when the document cannot arrive in time without someone stepping in. Escalation is not a complaint; it gives the manager what they need to decide: what was asked, of whom, when, how many times, and what happens if the document does not arrive. The manager might call the supplier's account manager, ask the customer whether the load can ship with the COA to follow, or move the pickup.
Keep supplier contacts current
Most chases slow down because the team is asking the wrong person. Keep a contact for each supplier and each document type: who sends COAs, who sends packing lists, who answers when the first contact is out. Update it every time a reply comes from someone new. A current contact list turns a two-day chase into a single email, and it means the next coordinator does not have to rebuild it from old threads.
Mistakes that slow the chase
Mistake 1: Waiting for the pickup day. Documents requested the day of pickup arrive after the truck leaves, or not at all.
Mistake 2: Sending requests to a general inbox. Ask a named person. If the supplier only has a general address, find a person on the first exchange and keep their contact.
Mistake 3: Accepting the wrong lot. Check the lot number on every COA against the shipment. A mismatched COA can be rejected by the customer after the freight has traveled.
Mistake 4: Chasing in private. If the coordinator chases from a personal inbox, nobody else can see where things stand when they are out. Keep the chase visible to the team.
Mistake 5: Shipping silently without the document. If the team decides to ship without a COA, tell the customer before the truck arrives, not after it is turned away.
How should documents be filed and attached to the shipment?
File every document on the shipment it belongs to, named and matched by order and lot, the moment it arrives. A document that exists somewhere is not the same as a document the team can find.
What to attach and how to name it
Attach each document to the shipment record, not to a folder by date. Name files so a person can tell what they are without opening them: document type, order number, lot number. Keep the latest version clearly marked if a document is reissued. For a broader approach to filing, see how to organize BOLs, PODs and freight documents so you can find them.
Who needs a copy
Different parties need different documents:
- The customer usually needs the COA and the packing list, sometimes before pickup.
- The carrier needs the BOL and sometimes the packing list or SDS.
- The customs broker needs the commercial invoice, packing list and any certificates for a cross-border load.
- The company's own team needs everything, on one record.
Send each party what it needs, from the shipment record, so every copy is the same version.
Customer portals
Some customers want documents uploaded to their own supplier portal. That is a separate task with its own owner, because each portal has its own login and format. Write down which customers require a portal upload, and who on the team does it, so it does not fall between logistics and quality.
Keep the request and the document together
The request, every follow-up, the reply and the attached file should sit on the same shipment. When a customer later says "we never got the COA," the team can show when it was sent, to whom and which version. When an auditor asks for traceability on a lot, the COA, packing list and BOL for that lot are all in one place.
Which checklist keeps the right documents on every shipment?
One checklist per shipment, agreed by logistics, quality and customer service, keeps documents from falling between teams. It also gives a new coordinator a clear picture of what "done" means for each load.
A document checklist per shipment
| Item | Question to answer | Owner |
|---|---|---|
| Required documents | Which documents does this customer, product and lane need? | Logistics with quality |
| Lot numbers | Is the lot on the order for every COA product? | Customer service or warehouse |
| COA source | Does the quality lab or a supplier issue it? | Quality |
| Due time | When must each document be in hand before pickup? | Logistics |
| Request sent | Was each document requested, and to whom? | Logistics |
| Follow-ups | Were follow-ups sent in the same thread, and calls made? | Logistics |
| Escalation | Who decides if a document will not arrive in time? | Logistics manager |
| Lot match | Does each COA match the lot on the shipment? | Quality or logistics |
| Filing | Is each document attached to the shipment record? | Logistics |
| Distribution | Did the customer, carrier and broker get what they need? | Logistics |
| Portal uploads | Which customers need a portal upload, and who does it? | Customer service or quality |
| After delivery | Is the POD attached next to the shipping documents? | Logistics |
What to do when a document is late
Late documents need a decision, and the decision should be written down before the situation arises. The table below is hypothetical. It shows a format, not a rule any customer must follow.
| Situation | Who decides | Typical next step |
|---|---|---|
| COA not received, pickup tomorrow | Logistics manager with quality | Call the owner; ask the customer whether the COA can follow by email |
| COA received for the wrong lot | Quality | Reject it, request the correct lot's COA and hold it from the customer |
| Supplier has not answered two follow-ups | Purchasing or quality | Call the supplier's main contact and escalate inside the team |
| Commercial invoice missing for a cross-border load | Export or finance | Hold the border paperwork until the broker has it |
| Packing list does not match the staged pallets | Warehouse | Recount, correct the packing list and resend it |
| Customer requires a portal upload | Named team member | Upload from the shipment record and note it on the load |
Measure what the chase costs
Track a few simple numbers for a month: how many shipments needed a COA, how many COAs arrived before the first follow-up, how many needed an escalation and how many loads were delayed or refused because a document was missing. Those numbers show which suppliers and which internal teams need a different arrangement, such as sending COAs automatically when a lot is released. They also show how much coordinator time goes into chasing paper instead of moving freight.
Agree the list with customers
Many document problems start with an unclear requirement. Ask strict customers to confirm in writing which documents they need, in which format, sent to whom and by when. A one-page agreement prevents loads from being turned away over a document nobody knew was required. Review it once a year, or whenever the customer changes its receiving rules.
Roll it out in stages
Start with the customers that turn freight away without a COA. Write their document lists, name the owners and run the chase routine for a few weeks. Then add customers whose requirements are softer. Teams that try to document every customer at once usually stall; teams that start with the strictest customers fix the problem where it costs the most. For the related task of getting the BOL in hand before the truck arrives, see how to request missing bills of lading before pickup.
How does Wilson, by Cartage, get COAs and supplier documents onto every shipment?
Wilson, by Cartage, is an AI logistics agent that can request, chase, file and attach any document configured in the workflow, including certificates of analysis, and it tells the team when a document is still missing. Traditional logistics software gives teams information. Wilson executes the work required to move shipments forward. Think of it as a free logistics department: what big shippers build over years, Wilson does from day one, in four parts.
The labor. Wilson does the work from the first quote to the final POD: quotes, bookings, paperwork, tracking and follow-ups, by email, phone calls, texts, WhatsApp, Slack and Microsoft Teams. For documents, the company configures which ones each shipment needs and who sends them. Wilson requests each one, follows up in the same thread and by phone until it gets an answer, files what arrives and attaches it to the shipment. When the owner is someone on the company's own team, Wilson follows up in the channel that person normally uses, with short follow-ups in the same thread, then escalates to the team. If a deadline passes and a document is still missing, Wilson flags it.
When an order is missing a detail a document depends on, such as a lot number, Wilson does not book it. It holds the order as pending, asks for the missing detail and tells the team. It never invents the value.
Wilson generates documents such as the bill of lading, commercial invoice, packing list, packing slips and pallet labels. On cross-border loads it helps run the customs paperwork under a customer-specific SOP and sends the information to the customer's customs broker. Wilson is not a customs broker and does not clear customs. Wilson also does not upload documents to customer portals; those uploads stay with the team.
The data. Wilson keeps every order, load, quote, rate, document and contact on record as it works, connected to the company's ERP. Wilson replaces the TMS for freight execution and connects to the company's ERP. Every request, follow-up, document and change is kept in the shipment's change history, so the team can see who was asked for what and when. Wilson works with SAP, NetSuite, Microsoft Dynamics 365, Oracle, Infor, Epicor, Sage, Acumatica and other ERP environments, with the exact connection depending on the customer's data flow and scope.
The network. Wilson gets better freight rates on every lane because the shipper's volume counts with every other Wilson customer's. The network includes carriers and brokers, and the company still approves who hauls its freight.
The payments. Wilson audits every carrier invoice against the rate confirmation and the POD before money moves, then pays carriers from the Wilson Wallet. Invoices over the agreed rate or outside the rules wait for a person.
Control stays with the company. Wilson starts with assisted execution, the company sets approval limits, and routine actions can run automatically within those rules as the workflow is proven.
Pricing
Wilson is free on Wilson's network: the shipper pays the freight rate and nothing on top. When a shipper keeps its own carriers, the fee is 2% to 0.5% of what Wilson pays them, falling with volume. There are no seat fees, no setup cost and no contract. Timing depends on scope: most teams start on a few lanes and expand from there.
FAQs
Can Wilson chase COAs and other documents from our vendors?
Yes. Wilson, by Cartage, an AI logistics agent, can request, chase, file and attach any document configured in the workflow, including COAs from vendors and suppliers. It follows up in the same thread by email and phone until it gets an answer, attaches the document to the shipment and tells the team if a document is still missing near the deadline.
How do we make sure every shipment has a certificate of analysis?
Write a document list per customer and product, make the lot number a required field on the order, request the COA when the load is planned and follow up on a fixed schedule before pickup. Attach the COA to the shipment record and check the lot number before sending it.
Who should own the COA, logistics or quality?
Quality usually issues and approves the COA, and logistics usually makes sure it reaches the shipment and the customer on time. Writing both roles down prevents the document from falling between the two teams.
What if the COA is for the wrong lot?
Treat it as missing. Ask the sender for the correct COA, keep the wrong one out of the customer's hands and check every COA against the lot on the shipment before it goes out.
Does Wilson upload documents to customer portals?
No. Wilson requests, chases, files and attaches documents, and can send them by email, but it does not upload documents to customer portals. Those uploads stay with the team.
Can Wilson create the commercial invoice and packing list?
Yes. Wilson generates documents such as the BOL, commercial invoice and packing list. On cross-border loads it sends the information to the customer's customs broker; Wilson is not a customs broker and does not clear customs.
What happens if an order is missing the lot number?
Wilson does not book it. It holds the order as pending, asks for the lot number, tells the team and never invents the value.
How early should we request supplier documents?
As soon as the load is planned. A request two or three days before pickup leaves time for a follow-up, a phone call and an escalation. Requests made on the day of pickup often arrive too late.
Where should shipping documents be stored?
On the shipment record, named by document type, order and lot. That way the COA, BOL, packing list and POD for one load sit together and can be found in one search.
Can Wilson follow up with our own quality team?
Yes. Wilson follows up with people on the company's own team in the channel they normally use, such as email, Slack or Microsoft Teams, with short follow-ups in the same thread, then escalates to the team.
Sources
- Cartage, Wilson product FAQ and product scope, October 2026: https://cartage.ai
Let's review which documents your shipments need and who sends them today. You don't need to prepare anything: Cartage maps the workflow with you on the call.
