As published by the Port of Gothenburg, Railport Scandinavia links the port with 26 inland terminals, and just over 60% of containers arrive or leave by rail, with record rail-borne volume in 2025 (press release of 3 February 2026). The port's website carries booking, quote and terminal information. For a forwarder or haulier, a container move often means several legs and a terminal that can change.
LATYNEX Digital builds custom logistics software around that record. This page covers that work for Gothenburg businesses. The general service is at Logistics Software Development, and the market overview is at LATYNEX Digital for businesses in Gothenburg.
Typical industries
- Freight forwarders handling container imports and exports
- Hauliers and drayage operators
- Importers and exporters booking their own container moves
- Inland-terminal and depot operators
- Customs-clearance and documentation service firms
- Manufacturers with regular container flows
Common lead-handling problems
- Multi-leg quote-to-booking records spread across email
- Status typed by hand into client updates
- Inland terminal changes not reflected in the shipment record
- Documents and references that cannot be found when a client asks
Direct answer
If your Gothenburg business books container moves between the port and inland terminals by rail shuttle, LATYNEX can build the internal tool that holds the whole chain: the client request, the quote, the booking reference, the chosen terminal, the status of each leg and the related documents, with a change log for terminal and date changes and a client update generated from the record rather than retyped.
Why the global service page and the Gothenburg hub are not enough
The global Logistics Software Development page describes the service across modes, and the Gothenburg hub covers the market. A hinterland rail network changes what the record must express: a move is a chain of legs, the inland terminal is a variable, and a change to it has to reach the quote, the booking and the client. That is the specific design centre of this page.
What we configure and build
The tool is yours and follows your way of booking.
- A shipment record with request, quote, booking, terminal, leg status and documents in one place
- A change log: who altered a terminal or a date, when, and who was told
- Status fields your team updates once, with client-ready summaries generated from them
- Search and filters by client, container, terminal and booking reference
- Roles and an audit trail, plus a written handover
What needs API support or custom scope
Terminal, carrier and port information stays with those parties. We do not claim any booking API and have no integration with Railport, terminals or carriers. If a party offers an API, webhook or file exchange, we review it technically and scope a connection per project; where it does not, the record is updated by your team. Live tracking is not part of the standard scope.
What we do not do
LATYNEX does not book containers, does not operate as a forwarder, does not give customs or legal advice, names no client, and does not deliver in Swedish. Figures on this page are the port's own and are given as published.
How delivery actually works
LATYNEX Digital has no office in Gothenburg and does not claim one. We work with Gothenburg businesses remotely, over video calls and written updates, in English, with the same team and process as in every other market.
Questions
Do you have an office in Gothenburg?+
No. We work with businesses in Gothenburg remotely, over video calls and written updates, in English, and we do not imply a local presence.
Does the software book rail shuttles for us?+
No. It holds your own record of the request, quote and booking. Whether a booking can be sent from it depends on what the other party supports and is scoped separately.
Can you show live container tracking?+
Not as standard. We claim no integration with terminals or carriers; a status feed would be scoped per project, through an API or webhook where the system supports it, after technical review.
Can it replace our current TMS or forwarding system?+
Sometimes, but usually we first check whether a focused tool beside your current system solves the actual gap. We say which after the technical review.
Do you advise on customs or documentation rules?+
No. We do not give legal, customs or tax advice. Confirm requirements with your provider or adviser; we build the fields and document slots they specify.
How are you invoiced, and in what currency?+
In EUR, by Latynex Trade OÜ, a company registered in Estonia (EU). Tax treatment for a client in Sweden is confirmed on the quote, and we do not give tax advice.
What happens next
- 01
We talk through what you need
The problem, the people who will use it and what runs it today.
- 02
We write the scope
What is built first, what is deliberately left out and what needs a decision from you.
- 03
Price agreed in writing
One price for that scope, approved by you before any work starts.
- 04
We build in stages you can review
You see working software along the way, not a reveal at the end.
- 05
Test, hand over, document
Your code, your accounts and your domain, with documentation that lets someone else run it.
Who you would be working with
- Company · Who you would be working with
- LATYNEX Digital is a service line of Latynex Trade OÜ, a company registered in Estonia (EU). Contact: info@latynexdigital.com.
- How we work · Delivery
- Remote, in English, with the person who would run the project. No local office is implied in any market.
- How we work · Commercial terms
- One scope and one price, agreed in writing before work starts. Your accounts, code and domain stay yours; any access we use is granted by you and can be withdrawn.
There are no client case studies on this page, and none are implied. What LATYNEX has built and runs itself is on the portfolio, each system labelled by stage. Published prices are on the pricing page; anything not listed there is scoped and quoted after review.