Drop in a trading partner's guides and sample files. AI drafts the setup, Wildflower compiles it into fixed code and proves it on the samples, and the whole partner goes live in one step.
Pacific Cold's 9 filesSetup plan9 files from Pacific Cold → its setup plan
Welcome to Pacific Cold EDI.eml
PC 204 Load Tender 4010.pdf
PC 990 Tender Response 4010.pdf
PC 214 Shipment Status 4010.pdf
PC 210 Freight Invoice 4010.pdf
PC Acknowledgments 997 999.pdf
Sample 204 PC-559870.edi
Sample 214.edi
Sample 210.edi
204 inLoad tendersReady
990 outTender responsesReady
214 outShipment statusReady
210 outFreight invoicesReady
997 outAcknowledgmentsReady
997 inAcknowledgmentsReady
999 inImplementation acksReady
SFTPManaged SFTPChecked
Ready 7 of 7Go live
The usual way, turned around
Months of mapping, turned into one list and one Go live.
Usually
1A kickoff call, then a spec for every document.
2Mapping work, by a consultant or an EDI provider.
3Test files back and forth for weeks.
4A bill for every document after that.
In Wildflower
1You drop in the partner's guides and sample files.
2AI drafts the setup, and every rule names the file it came from.
3Wildflower compiles it into fixed code and proves it on the samples.
4One Go live turns the whole partner on.
AI's part ends with the draft. Every live file runs through the fixed code, the same way every time, so nothing is guessed while a load is moving.
Example · Pacific Cold
One partner's setup, stage by stage.
Bayline Transport, a reefer carrier in Stockton, has a new EDI customer: Pacific Cold, a cold-storage shipper in Oakland. On Monday, Nov 2, Pacific Cold's EDI analyst emails its packet. Here's the setup, from the files to Go live.
Pacific ColdAdd partnerReady 0/7
1Add partner
Drop in the nine files Pacific Cold sent.
In EDI partners, under Developer, you choose Add partner, pick the customer Pacific Cold and drop in what its EDI analyst emailed: the welcome email, five guides and three sample files.
Add partnerCustomer · Pacific Cold
EmailWelcome to Pacific Cold EDI.emlIDs, contacts and the server choice
Wildflower analyzes the packet, proves each supported document, and keeps traffic paused until Go live.
Create partner
PDF, Word, Excel, CSV, text, email, images and X12 all work. Every file is scanned, and passwords, keys and tokens are stripped before AI reads anything.
2Reading
Wildflower finds what the files ask for. Nothing more.
Of the eight documents Wildflower supports, Pacific Cold's files ask for seven. It doesn't add a document because it's common: the 990 in, for a partner that answers tenders you send, stays Not used, since Pacific Cold never answers one.
AI drafts each document's rules in a fixed vocabulary, never code, and each rule cites the file it came from. Wildflower's compiler checks the draft and turns it into fixed code: a release for each document. Where the files disagree or say nothing, the rule stays a question, and anything missing or unsupported can't go live.
Here's that fixed code on Thursday, reading Pacific Cold's first tender and writing the 214 and invoice Bayline sends back. Pick any line to see where it came from.
Stop 2Delivery · Pacific Cold Bakersfield3301 Distribution Way, Bakersfield, CA 93308Located
Freight18 pallets · 38,400 lb
Kept with Pacific Cold's files · interchange 000004817
Setup planReading setup material
204 inLoad tendersManaged SFTP · /inboundFound
Six more documents, each with its own drafted rules
4Needs your input
One question only Pacific Cold can answer.
Wildflower won't guess whether Pacific Cold sends changes and cancellations, so the 204 in waits as Needs input. It's Pacific Cold's call, so you press Share setup and send the link to Pacific Cold's EDI analyst. They sign in with their own email, see only Pacific Cold's setup, and answer.
Needs input · 204 inPacific Cold's 204 guide lists changes and cancellations as well as new tenders. Will Pacific Cold send those by EDI?
Share setup
A single-use linkwildflower.spokes.ai/invite?invitation=K7WD-P3XQCopy link
Their EDI analyst answers
Pacific Cold's EDI analyst“New tenders only. We phone in changes.”
Becomes a rule
204 in · from the answerNew tenders only.B2A.01 00 · Setup note from Pacific Cold's EDI analyst
Wildflower asks the smallest plain question it can: a missing ID, a sample, a credential, never “which X12 element”. Partners who'd rather answer by email get Questions for your EDI partner, with Copy questions.
Each document's fixed code runs on Pacific Cold's samples. The sample 204 becomes a preview of the job it would create, with nothing created. The 990, 214 and 210 Bayline would send are checked against the guides, and so is the SFTP connection.
Sample 204 PC-559870.edi → draft job previewNothing created
Go live rechecks the whole plan, then turns every document on together. Pacific Cold's EDI analyst could press it too, from the shared setup, with the same fresh sign-in check.
Everything is ready
Go live activates all 7 planned documents together. It does not release held files or replay past events.
Go liveAsks for a fresh sign-in check first.
LiveThe planned EDI documents and directions are active.
Setup planLive
All seven documents · Live
The partner link
Pacific Cold answers its own question. Through a link that opens Pacific Cold and nothing else.
The rest of Monday, on both screens. Pacific Cold's EDI analyst lands in one workspace, Partner setup for Pacific Cold; a second person, like a consultant or their network team, gets a link of their own.
Wildflower has drafted Pacific Cold's seven documents and needs one answer only Pacific Cold can give, so you press Share setup.
BTBayline Transport Search jobs, people, invoicesME
Pacific Cold's 204 guide lists changes and cancellations as well as new tenders. Will Pacific Cold send those by EDI?
From PC 204 Load Tender 4010.pdf
Questions for your EDI partnerCopy questions
9:12●●●● 5G ▮
‹ Sent
To Bayline TransportWelcome to Pacific Cold EDI8 attachments
Your office, on the webPacific Cold's EDI analystTry it
They can
Upload files and answer setup questions
Set up connections and keys
Run connection checks and document tests
Run that one partner, going live with a fresh sign-in check
They can't
See your other customers, partners, jobs, team or settings
Invite anyone else
Delete a connection or change which customer it is
The link
Single use: whoever opens it signs in with their own verified email, and the link is theirs
An unused link expires in 7 days
Access lasts up to 90 days
Suspend or revoke it any time; it stops on the next request
Where files travel
Managed SFTP to start. Their server or HTTPS when the guide says so.
Every new partner starts on its own managed SFTP account, with /inbound and /outbound folders. The guide decides when a document needs another route.
Managed SFTPPacific Cold
Hosted by Wildflower, one account per partner
Pacific Cold signs in with its public key; Wildflower can generate the key pair and show the private key once.
Their SFTP
Pacific Cold's own server
Wildflower signs in with a password or key it keeps write-only, checks the server's pinned host key, and proves it by uploading, renaming and deleting an empty test file.
HTTPS
Pacific Cold's own URL
Basic, bearer or an API-key header. A test request must pass before a document can use it.
One route per document, with no automatic fallback.
If the guide allows either side's server, managed SFTP stays.
If the guide requires the partner's SFTP or HTTPS, Wildflower sets that route up and tests it.
Thursday, Nov 5 · the first load
Pacific Cold's first tender, from the 204 to the invoice.
Pacific Cold tenders shipment PC-560218: 18 pallets, 38,400 lb, from its Oakland dock to its Bakersfield warehouse. AI plays no part: no live file is read, built, routed, accepted or rejected by AI.
Thursday at 8:02 AM, Pacific Cold's 204 for shipment PC-560218 becomes draft job R4N-8XC1, and a 997 tells Pacific Cold the file was readable.
BTBayline Transport Search jobs, people, invoicesNS
Every partner sees all eight. Every live file runs through fixed code.
Pacific Cold's plan uses seven; the rest stay Not used. Each document's screens show its citations, rules, samples, previews, releases and route, for anyone who wants them; nobody has to open them.
Document
What it does
Pacific Cold
204 in
Load tenderA tender becomes a draft job
In the plan
990 in
Tender responseA partner answers a tender you sent
Not used
990 out
Tender responseAccepting or declining the job answers the tender
In the plan
214 out
Shipment statusArrived, picked up, arrived, delivered, a problem
In the plan
210 out
Freight invoiceAn issued invoice goes out
In the plan
997 in
Functional acknowledgmentThe partner confirms your file was readable
In the plan
997 out
Functional acknowledgmentYou confirm the partner's file was readable
In the plan
999 in
Implementation acknowledgmentThe partner confirms your file against its guide
In the plan
Switches
Each partner has an Inbound and an Outbound switch, and each document its own. Off, files still arrive and are kept, and nothing changes. Back on, nothing replays; you pick held files in Review held.
Releases
Each document's rules are their own release. Changing the 210 can't touch the 204, and rolling back republishes a known-good release.
A new packet
When Pacific Cold sends new guides, Wildflower makes a new plan revision with a diff. It never overwrites what's live.
Beside the API
Pacific Cold sends EDI. Everyone else keeps their own way in.
EDI is an add-on beside the API. If a customer can call the API or take webhooks, that's still the better way in. EDI is here for the big customers that still require it.
