Answers to your OneChain questions.
Find the information you need to prepare your project: scope, deployment, integrations, security and AI.
Deployment and scope
How long does a OneChain deployment take?
The timeline depends on scope, exchanges to prepare and your team’s validations. The project separates configuration, potential integrations, partner onboarding, testing and launch. See the Deployment and support page to frame the steps.
Do all carriers need to be connected from day one?
No. OneChain can start on a priority scope without requiring a full carrier connection program. Integrations are added based on ROI, data maturity and IT constraints.
Should a TMS be rolled out in phases?
Design the full target first, then prove it on a first site, country or set of flows. The project manager and key users describe the current and target processes for that scope. Later phases build on the same target.
Which modules can be activated first?
Common starting points are transport tracking, rate management, invoice control, PO management, SOPs and reporting. The right order depends on the main business problem: visibility, cost, quality, suppliers or integration.
What questions should we ask before choosing TMS software?
Start with your transport scope, flows, partners and decisions to make more reliable. Then check system exchanges, security, launch support and conditions for future change. These answers help compare TMS software against your real project.
Integrations and data
Does OneChain connect to an ERP or WMS?
Yes, depending on the system and scope. The project scopes structured imports, an API or EDI/SFTP, then validates the version, process and responsibilities. See the Integrations page to prepare these exchanges.
How do forwarders and partners use the platform?
They can be onboarded on the platform, receive instructions, update statuses, upload documents or transmit information through integrated flows depending on maturity.
Does every forwarder need an API or EDI connection?
No. Depending on the partner and scope, collaboration runs through an integration, document exchange or direct use of the platform. An existing interface must be checked against the flows concerned. Agree with each branch on the information expected and how it will be sent.
Can OneChain data feed BI tools or internal agents?
Yes. API integrations and headless approaches are designed to connect OneChain to internal tools. Access is framed by organization, role and use case.
Security, compliance and AI
Where is OneChain data hosted?
The core application platform is hosted on AWS eu-west-1 in Ireland, within the European Union. Data is encrypted at rest and in transit.
How does OneChain organise security?
OneChain maintains an information security management system (ISMS), a security assurance plan and a risk assessment. These documents structure its practices and discussions with your security team.
Are AI features mandatory?
AI features are optional. You choose which use cases to activate and can disable them according to your requirements. They rely on data minimization and a no-PII policy for payloads.
Can OneChain connect to a customer SIEM?
Internal logs are structured and monitored. An export to your SIEM can be explored with your security team under a specific contractual arrangement.
Commercial model and support
How is pricing built?
Pricing depends on modules, volume, integrations and support level. The right starting point is a demo and scope framing rather than a generic price.
Who supports go-live?
The OneChain team supports configuration, testing, partner onboarding and adoption. Scoping separates go-live must-haves from improvements to plan later.
Can we get customer references?
Yes. Visit our Customer cases page for the Christofle testimonial and examples of how OneChain is used.
Enterprise, references and supplier qualification
Can you share a reference comparable to our sector?
The Customer cases page presents the public Christofle case and its scope. Share your sector, flows, scope complexity and expected level of evidence. We will frame the request and the appropriate exchange.
How should we prepare a supplier qualification?
Share the scope, steps, timeline and contacts in your procurement process. We will explain the public information, the topics to discuss with the team and the documents to review.
Which commitments and documents can you present?
We can discuss expectations around CSR, ethics, security, continuity and support. CO₂ reporting details transport emissions. Share your expectations so we can identify the documents relevant to your supplier review.
Need more detail?
Share your context with our team.