Freight Dispatch Board
204 in, 997 back, 214 at every stop, 210 at delivery
Overview
The whole freight EDI loop — tender, acknowledgement, dispatch, status, invoice
A tender arrives, somebody has to acknowledge it, a dispatcher has to work the load, the partner wants a status message at every stop, and an invoice goes out at the end. That loop normally lives inside a TMS costing five figures a year.
Here it runs end to end. A 204 lands in a watched folder, the 997 goes back within seconds, and the load becomes a row a dispatcher can work. Every status change emits a 214, and delivery raises the 210.
Engineering
How it was built
Frontend
- Angular dispatch board with per-load stops, references and status history
- Rejected tenders shown on the board with the reason, rather than dropped
Backend & services
- ASP.NET Core service driving the 204 to 997 to 214 to 210 loop
- Watched-folder transport: tenders picked up, parsed and moved out of the inbox
- 214 status codes derived from the stop rather than the load state
- 210 invoice raised at delivery with linehaul, stop-offs and fuel surcharge
- Every generated document re-parsed and envelope-validated before it is released
Integrations
- X12 204, 210, 214 and 997
- Envelope parsing and validation by the EDI X12 Toolkit library
Testing & verification
- 132 tests
- Sample interchanges written from the published ANSI X12 specification
Applied
Skills on this project
Next step
Ready to bring your project to life?
Schedule a free 30-minute strategy call with our team.
No sales call. You will talk to the engineer who would do the work, and you will get a written summary either way.