Automating US-to-Canada Rescue Dog Import Compliance

Tens of thousands of adoptable dogs are euthanized every year in Texas shelters, while rescues in Canada’s Maritime provinces can’t keep enough dogs in stock to meet demand. The supply and the demand are obvious. The thing standing between them is paperwork.

We built the platform rescues use to handle their own paperwork—consolidating a rescue network’s scattered intake and compliance process into one system, and automating the Canadian import declarations.

The Challenge

The rescue coordinators we worked with run a steady stream of transports from Texas to the Maritimes. Every dog crossing into Canada requires CBSA filings, CFIA health documentation, and customs accounting—and one missed form can hold up an entire transport of animals.

The way that work actually got done was a patchwork. Adopter and foster applications came in through a stack of separate JotForms. Dog profiles, medical records, and trip manifests lived in Google Docs and spreadsheets. Coordination happened in Facebook groups and message threads. Nothing talked to anything else, so the same dog’s information was re-entered by hand at every stage—and every re-entry was a chance to transpose a vaccination date, drop a microchip number, or miss a required field that the border would later reject.

They didn’t need another form. They needed the whole thing to be one system.

Our Approach

We started by aggregating their data sources rather than replacing their process overnight. The dozen-plus JotForms became structured intake flows in one application. The spreadsheets and Google Docs became first-class records—dogs, trips, consignments, fosters, and adopters—all in one tenant-isolated platform, each dog carried once and referenced everywhere.

With the data unified, the compliance layer became possible. The core insight is that a border declaration is just a transformation of data you already have. Once a dog’s identity, medical history, and trip details live in one place, generating the government message is a mapping problem—not a re-typing problem.

We built that mapping to the real CBSA formats: the Integrated Import Declaration (IID / Single Window Service Option 911) as an EDIFACT message, and the ACI eManifest for advance notice of the conveyance itself. Uploaded documents—rabies certificates, health certificates, permits—are attached to the declaration as LPCO image submissions rather than emailed around.

AI does real work in the pipeline, too. Rabies and health certificates arrive as photos and scanned PDFs; we run document extraction over them to pull expiry dates, vaccine brand, and lot numbers into structured fields, so a coordinator confirms data instead of transcribing it.

The Solution

The result is a single platform that manages the full import lifecycle:

• Unified intake and profiles — dogs, medical records, photos, and transport readiness in one place, replacing the JotForm-and-spreadsheet sprawl.
• Trip and consignment planning — dogs grouped into transports and grouped again by Canadian importer, with the compliance state of each consignment tracked explicitly.
• Automated declaration generation — IID and ACI eManifest messages built from the platform’s own data, in the exact EDI formats CBSA expects.
• Document intelligence — OCR extraction from uploaded certificates so paperwork becomes clean, validated records.
• Credit-based billing — simple per-dog pricing for rescues.

The strategic point is bigger than one rescue. The declaration pipeline—pre-submission validation, EDI generation, and response handling—is the same machinery any importer needs. Dogs are the first vertical; the technical layer generalizes to anyone filing across the border.

Status

The platform is built and in production use for managing dogs, trips, consignments, fosters, and billing. The CBSA EDI pipeline—declaration generation, submission transport, and response parsing—is built, and we are completing electronic-data-interchange certification with CBSA’s Technical Commercial Client Unit (TCCU) ahead of the network’s first live production crossing. We have not yet filed a live declaration; that milestone is imminent, and this case study will be expanded with named results once the first crossing is complete.

The Result

Before the platform, compliance for every transport meant a dozen disconnected tools and hand-re-entered data at every step. After, it’s one system: intake, profiles, trip planning, and border declarations generated from a single source of truth.

PawPassage is a Molitio product. Explore the platform at pawpassage.com.