Freight under control: the whole team works in one window
Replaced the old program—and kept its years of history
Sample data
Problem
Requests, trips, railcars, invoices and claims lived in different places: the old program could not keep up with the work, and some of the records were kept in spreadsheets. Getting a picture of the day was a manual job.
What we built
A record-keeping system built around how the team actually works. Requests, trips, railcars, stock, invoices, claims and client notifications—in one window. Reference data is synced with 1C automatically, and clients get an SMS about their cargo status without a manager being involved.
How it works
Request
A client inquiry is logged in the system and turns into a trip.
Trip and documents
Railcars, trucks, stock, shipping documents—in one place, not in five spreadsheets.
Client informed
SMS messages about the cargo's progress go out automatically—no more "where is my cargo" calls.
Money and claims
Invoices and claims are kept next to the trip—nothing gets lost in correspondence.
Sync with 1C
Reference data syncs on a schedule, with no manual re-entry.
The hardest part was the history: the old program had no way to hand over its data.
We pulled it out of the program's own exports, and even two exports from the same database turned out to be in different formats—we rewrote the parser as we went. The upside: the notification log from years of work moved across intact, and the team did not have to start from a "blank slate".
Same problem? Message the bot—we start with a review
Email us