WorkflowContract Manufacturing (CDMO)

Export Documentation Check

Export documentation for pharmaceutical shipments, lined up field by field: agents read every paper, show the one value out of line, open the source record to say which paper is wrong, and keep release blocked until it agrees.

See one held shipment brought back into line ↓
Watch with transcript →
The problem

Each paper is right on its own and wrong beside the others

No single party writes the papers that travel with an export shipment of a client's tablets. The client writes the commercial invoice, the plant the packing list and forwarder instructions, QA a certificate of analysis per batch, and others the certificate of origin, the certificate of pharmaceutical product and the importer's permit. The trade compliance specialist opens them side by side and ticks a checklist, one shipment at a time.

A batch number typed from the previous order, or a permit issued for the other pack size, passes that check and is found by the destination market's customs and health inspector. The goods wait at the port, the importer pays storage, the client's supply in that market slips, and the next shipment gets a closer look. The checklist leaves no record of what was compared, so an auditor cannot see the distribution fields were confirmed.

Built forTrade compliance specialistsShipping coordinatorsQA release specialistsTrade compliance leads

The Problem Today

An export file spreads one shipment across papers from five issuers, and a one-digit slip between them is found at the border.

Compared by eye today

  • Invoice
  • Packing
  • CoAs
  • Permit
  • A permit for the other packThe importer's permit names blisters while the truck carries bottles
  • Corrections retyped from emailReplies arrive as attachments and free text, not fields

The Solution

  1. Every paper read into fieldsEach value with its page and passage, across ten documents
  2. The wrong paper namedThe pick list, pallet scans and packaging record settle which one is out
  3. The border inspector rehearsedA challenger reads the file as the destination market would
  4. Released by two peopleA release from hold is countersigned after the reasons are read

Built-in controls

  • A value out of line blocks release to the forwarder
  • Whoever placed the hold cannot countersign it
  • Outside answers change only fixed fields

What You Get

A wrong paper is caught at the plant's export desk, and the client's importer receives a file whose papers agree with each other and with the batches.

  • Importers answer in their own viewEach request and its status, without an email chain
  • A new market is a rule setClients add destinations without a new checklist to learn
  • Proof of what was comparedEach value carries its document, page and source record
Features

Export documentation features, from the field line-up to the release

Three batches of a client's tablets in bottles leave the plant by reefer for the client's licensed importer. Ten papers travel with them, and two disagree.

demoThe plant, the client, the importer, the forwarder, the markets and every value shown are sample data.

  1. 01Field line-up

    Export documentation lined up field by field across ten papers

    • One row per shared field. Consignee, product, pack, batches, quantity, expiry, weights, tariff code, temperature, permit and manufacturer each sit on one row, so the odd value stands out.
    • Fields a paper never carries. A certificate of pharmaceutical product has no pack size and a CoA no consignee, so those cells say so instead of passing as a match.
    • Each value opens its passage. Clicking a cell shows the rendered paper with the value highlighted, so the specialist trusts the cell without retyping it.
  2. 02Source record

    The pick list settles which document carries the wrong batch

    • Which paper is wrong. The source checker opens the pick list, the pallet scans and the packaging record, and names the client's invoice as the paper to correct.
    • The other batch explained. The number on the invoice belongs to a batch still in QC testing and never picked, so the request to the client names the batch that belongs on the line.
  3. 03Import permit

    Import permit checked against the pack the shipment carries

    • Pack and quantity covered. The permit covers the other registered pack, so the importer needs a permit that names bottles, before the goods reach its border.
    • Checked against the registration. The client's registration list shows both packs registered in that market, so the permit is the outlier and the product is not.
  4. 04Challenger

    Export shipping documents read as the destination's inspector would

    • Quantity added to the agents' request. The drafted request asked only for a bottle permit; the challenger saw the shipment was larger than the old permit allowed, so quantity became a required field.
    • Shelf life counted at import. Remaining shelf life is measured on the estimated import date in the booking, against the market's signed rule.
    • The certificate's age for a person. The certificate of pharmaceutical product passes now but will be too old for later shipments, so the specialist rules on asking early.
  5. 05Hold and requests

    Shipment held with reason codes and requests sent in fixed fields

    • Holding is immediate. The specialist's reason codes put the shipment on hold and the forwarder's booking with it, because holding is the safer direction.
    • Requests a person sends. The request agent drafts each one with its fields and due time, and only the specialist sends it.
  6. 06Importer view

    The importer answers with the permit number, pack, quantity and file

    • Fields the reply is checked on. Pack, quantity and validity are entered as fields, and each is checked against the shipment before anyone can accept it.
    • The importer's comment set apart. Free text from the importer is marked not compared, and the specialist must open it before the reply can be accepted.
  7. 07Replies

    Corrected papers accepted only after their files are opened

    • Opened before accepted. The specialist must have each attached file and comment open on screen before the accept button works, so a reply is read before it counts.
    • A failing reply stays out of line. When a field check fails, only an exception countersigned by the trade compliance lead can accept it, and the values stay marked.
  8. 08QA confirmation

    QA confirms each certificate of analysis names a dispositioned batch

    • Independent of the CoA signer. A QA release specialist who did not sign the certificates opens each one and confirms it belongs to a batch QA has dispositioned.
    • Release waits for that check. Trade compliance cannot release the file while the certificate confirmation is missing.
  9. 09Release

    A release from hold countersigned by the trade compliance lead

    • Two people on a release from hold. The lead opens the line-up and the hold reasons before countersigning, and the person who placed the hold can never be that second signer.
    • The file frozen at signature. The signed document file goes to the forwarder as it was signed, and later rule changes never rewrite it.

The shipping coordinator builds the file and can never release it

Trade compliance checks, holds and releases, shipping assembles and corrects the plant's own papers, QA vouches for the certificates, and the lead countersigns and owns the rules.

Trade compliance specialists

Check each export file, hold it, request corrections and release it

  • The paper out of line, named
  • Replies as fields, not email
  • Past holds for this importer and market
Shipping coordinators

Build the pick list, packing list and forwarder instructions

  • The reason a shipment is on hold
  • Their own papers to correct, flagged
  • A booking status the truck can plan on
QA release specialists

Confirm export certificate lines against dispositioned batches

  • Each certificate opened from the release screen
  • A check kept apart from the CoA signer
  • A send-back with a reason code
Trade compliance leads

Countersign releases from hold and approve market rule changes

  • Hold reasons read before countersigning
  • Rule changes proposed from real holds
  • Loosened settings that wait for them

The source checker opens the pick list before it blames a paper

Document reader

Reads each paper into its fields, with the page and passage each value came from.

  • Marks an unreadable page for a person to open
Field liner

Lines up each shared field across the papers and marks the value out of line.

  • Never calls a row in line while a paper is unread
Source checker

Opens the pick list, pallet scans, packaging record, QA disposition or registration list to say which paper is wrong.

  • Never edits a document
  • Never decides the hold
Market rule checker

Applies the destination market's signed rule set: permit cover, shelf life at import, transport temperature, certificate age.

  • Never changes a rule or applies an unapproved one
Challenger

Reads the line-up and the agents' own drafts as the destination market's customs and health inspector.

  • Never closes a point without a source
  • Never decides
Request agent

Drafts structured requests to the importer and the client and a hold notice to the forwarder, and reads replies through fixed fields.

  • Never sends
  • Free text from outside changes nothing
Memory agent

Finds past holds for the importer and market, what fixed them, and proposes a rule from today's case.

  • No rule applies before the trade compliance lead approves it
More screens

A replaced permit put one more value out of line, on purpose

The line-up after the corrections, the client's own view, the proposed rule, the past holds, the export queue and the audit trail.

Back in line after the correctionsAccepting the new permit left the forwarder instructions naming the old one; the shipping coordinator issued a revision, and no value is out of line.
The client's export contact corrects the invoiceThe client's contact is shown its requests and shipments alone, and answers with a revision number, the batch picked for the line and its expiry.
A rule proposed from today's holdWhen a permit is replaced, check its quantity against the shipment: the memory agent proposes it, and it waits for the trade compliance lead.
What held this importer's shipments beforeAn expired permit, a two-digit expiry year and an unsigned CoA copy, each with what fixed it and the rule it left.
The export queue across four plantsShipments due to forwarders in the next ten days, by plant, client and market, with documents, values and status, and clean files signed in bulk on a sample.
The countersign's reason records that the lead opened the line-upThe hold, the requests, the accepted replies, QA's confirmation, the release and the countersign, each with who, why, the signature's meaning and the session.

demoSample data, from the working solution.

The plant never edits the client's invoice or the importer's permit

Releasing a held shipment aloneA release from hold waits for the trade compliance lead, who reads the hold reasons and the line-up first.
Correcting another party's paperThe client corrects its invoice and the importer its permit; the plant revises only its own packing list and instructions.
Changing a market's rulesRule sets are signed per market; the memory agent proposes, and the lead approves or rejects.
Accepting a reply that disagreesA reply with a failing check is accepted only as a named exception the lead countersigns, and its values stay out of line.
Confirming a certificateQA confirms each certificate of analysis against its disposition; the agents only show where it sits on the line-up.

The pallet labels scanned at dispatch can overrule the client's own invoice

The shipment's papersInvoice, packing list, CoAs, origin certificate, certificate of pharmaceutical product, permit and instructions.
Orders and pick listsThe batches allocated and picked, from the ERP.
Packaging records and pallet scansWhat was packed and staged for dispatch, from the eBR.
QA dispositionsWhich batches the plant's QA has dispositioned, behind each CoA.
Registration lists and rule setsThe client's registered packs and each market's signed rules.
Portal and booking repliesFixed-field answers from the client, the importer and the forwarder.

What export desks ask about export documentation

What export documentation does a pharmaceutical shipment need?

Export documentation for a medicine usually means the commercial invoice, the packing list, a certificate of analysis per batch, a certificate of origin, the certificate of pharmaceutical product, the importer's permit and the forwarder and transport instructions. Each destination market adds its own rules, held here as a signed rule set per market.

What is a certificate of pharmaceutical product?

A certificate in the WHO model format, issued by the exporting country's authority, stating the product, its license and the manufacturer's GMP status. The model has no pack-size field, so the line-up marks pack as not on that document, and a market rule checks how old the certificate is at import.

How does it decide which document is wrong?

It opens the records behind the papers: the pick list, the pallet labels scanned at staging, the packaging record, QA's disposition and the client's registration list. The paper that disagrees with those records is named, and a request goes to whoever issued it.

Who can release a shipment that was on hold?

The trade compliance specialist releases once every value is in line and QA has confirmed the certificates, and a second person, the trade compliance lead, countersigns after reading the hold reasons. The shipping coordinator who assembled the file cannot release it.

Which distribution fields does FDA expect on record?

FDA's rule on distribution records asks for the product's name, strength and dosage form, the consignee's name and address, the date and quantity shipped, and the lot number. Those are the first rows the line-up checks, and the signed file keeps the proof.

Does a clean file still get read?

Only clean files that already carry QA's certificate confirmation are offered for bulk signing, a share of them is drawn as a sample, and each sampled file must be opened before the group is signed.

Bring a shipment
that waited at a port.

Send the papers of one export file that was held, with its pick list, and we will line them up and name the paper that caused it.