Placeholder photoLiveUnder NDAroad freight transport in Europe
Freight management
Rate quoting and transport request management for a European road carrier, its partners and end customers.
Service
Partner websites under the partner's brand
We build websites through which partners sell your service under their own brand: the logo, language and price coefficient are determined by the site address, while calculations, requests and rules are shared in one system. Our basis is the system for a road freight carrier, live with the client.
Animation: three partner sites slide out of the system's site template, each gets its own logo and its own price bar of a different height, and lines run back to the shared template.
When you need it
Situations that bring people to us for this service.
Partners need their own site
A reseller wants to sell under their own brand, and a separate system for each is costly and awkward.
Partner prices are worked out by hand
Each partner has its own coefficient, and every quote for it is a separate spreadsheet.
Requests scatter
Orders from partners' customers arrive by email and get lost.
Different languages
Partners work in different countries, and the site needs each one's language.
What's included
Partnership model
What each partner has of its own (brand, language, prices) and what is shared (rules, requests, statuses).
Site by address
The logo, language and price coefficient are determined by the site address — without a separate copy of the system.
Shared calculation
One set of calculation rules for all sites, with the specific partner's coefficient.
Requests in one system
A request from a partner's customer has statuses with reasons, documents, PDFs and emails.
Roles
Visitor, end customer, reseller, carrier, administrator — each with their own permissions.
Interface languages
An interface in several languages; a partner site's language is set in its settings.
What you get
- A description of the partnership model and roles
- A shared system with settings for each partner
- Partner sites at their own addresses
- Shared requests and calculations
- Code and documentation that are open to you
The project path
From the first conversation to daily use
Every step ends with a decision: go on or stop. We don't start the next one until the previous one has given its answer.
- 01
Getting to know the task
You describe the process and what gets in the way. We reply by email with questions and arrange a call.
- 02
Discovery
We study the process with the people who work in it and write down what the system must change and how we will check it.
- 03
Prototype
We build a working prototype of the key scenario to test the idea on real data rather than on polished screens.
- 04
Pilot
We run the system in your real environment with agreed outcome criteria and a deadline. After the pilot we decide together whether to go further.
- 05
Launch and growth
We bring it to daily use: reliability, access rights, links to other software, documentation, support. Then we develop it based on user feedback.
Related case studies
Systems where we have already done this kind of work.
- Placeholder photo
Technology in these case studies
- REST API
- JWT
- Excel
Questions about this service
Does each partner need a separate system?
No. In the road freight case study a partner gets a site under their own brand — with their own logo, language and price coefficient — while the system is one.
Can a partner see other partners' requests?
Not if the permissions say so: each role sees and changes only what it is allowed to.
How many languages can there be?
In the carrier case study the interface works in five languages. The languages you need we decide during discovery.
More in “Websites”
- Corporate website developmentA website that makes clear what your company does and takes enquiries, with content your team updates without a developer.
- Online storesA catalogue, a cart, online payment and orders that don't get lost between the website, the warehouse and delivery.
- Landing pages and product pagesOne page for one product or offer: who it's for, what's inside and how to get in touch — clearly.
- Service websites with a price calculatorCustomers learn the price before they call, and the enquiry with its calculation is stored in the system with a status.
- Customer accounts and portalsA separate account for each role — customer, company, partner or supplier — with its own permissions and data.
- Multilingual websitesOne site in several languages — with correct tags for search and separate copy for different markets.
Have a project with no ready-made solution?
Describe it in a few sentences: how things work today and what gets in the way. We reply by email with questions on the next business day.
Get in touch