Nathalie Bardin
Director General of YSEND. Corporate and publication responsibilities remain governed by the registered company structure.
About XMS Cloud
Build the operating flow before adding another dashboard.
XMS Cloud is logistics operations software for teams that need warehouse, transport, automation, client work, and billing to share one controlled context.
Corporate identity
XMS Cloud is a YSEND GROUP product.
YSEND GROUP is the public trading identity of the registered French company YSEND, which publishes and operates the XMS Cloud platform.
- Legal entity
- YSEND — SAS, trading as YSEND GROUP
- Registered office
- 357 Chemin des Iscles, 06700 Saint-Laurent-du-Var, France
- Registration
- SIREN 843 222 746 · SIRET 843 222 746 00029 · RCS Antibes
- Share capital
- €2,953,885.08
- VAT number
- FR12843222746
- Contact
- contact@ysendgroup.com
Leadership and operating footprint
Logistics operations between China and Europe.
Public registry and company information reviewed on 22 July 2026 identify the current governance and operating locations below.
HD HOLDING
Registered President of YSEND. The formal named website publication director remains subject to legal confirmation.
Saint-Laurent-du-Var
Registered head office and European operating base at 357 Chemin des Iscles, 06700 Saint-Laurent-du-Var.
Guangzhou
YSEND GROUP publishes an operating presence in Baiyun District, Guangzhou, supporting China-to-Europe logistics activity.
Partners: warehouse, carrier, integration, and automation partners are qualified against each engagement's region, account, equipment, and evidence requirements. Contact contact@ysendgroup.com for partnership review.
Product focus
Keep execution and evidence connected.
The platform follows demand from product and order identity through physical work, shipment, proof, cost, and settlement. It gives each role an appropriate surface without creating a separate source of truth for every device.
- Multi-client and multi-site warehouse execution.
- Shipper and carrier-facing transport operations.
- Human, robot, WCS, PLC, and workstation boundaries.
- Client self-service with explicit funding and authorization.
- Operational billing, audit, recovery, and tenant export.
How the product is delivered
Software platform, explicit implementation boundary.
The deployment identifies who operates each physical process and which warehouse, carrier, robot, or machine system remains authoritative.
XMS Cloud
Application modules, APIs, workflow state, audit, role surfaces, orchestration, and evidence contracts.
Customer or logistics partner
Sites, workforce, carrier contracts, physical execution, safety, operating procedures, and service commitments.
Shared project team
Configuration, integration, data migration, edge devices, automation qualification, testing, training, and cutover.
Delivery layers
Product capability, environment setup, and operating results.
Each layer has a different owner and is established at a different point in the implementation.
Platform capability
Application state, contracts, guards, workflows, interfaces, and automated tests ship with XMS Cloud.
Environment setup
Credentials, carrier accounts, equipment dialects, topology, operating policy, and support are configured for the site.
Measured results
Throughput, availability, implementation duration, and operating outcomes come from the deployed environment.
Operating model FAQ
Clarify the commercial boundary early.
Is XMS Cloud a software vendor or a logistics operator?
XMS Cloud provides logistics operations software. The customer, its 3PL, its carriers, or another contracted partner operates the physical process.
Can we use our own warehouses and carriers?
Yes. Run customer sites and carrier accounts, or connect partner-operated execution while preserving shared operational context.
Does XMS Cloud replace an existing WMS or TMS?
It can replace selected warehouse or transport systems, introduce one module first, or integrate systems that remain authoritative.
Who invoices transport and fulfilment services?
The contracted carrier, fulfilment operator, or service provider invoices physical services. Software, implementation, and third-party pass-through costs remain separately scoped.
Who owns operational data?
Data remains tenant-scoped and exportable. Ownership, controller and processor roles, retention, deletion, and exit obligations must be stated in customer and data-processing terms.
Start with the operation
Bring one flow that crosses a system boundary.
Review the work, owners, devices, exceptions, proof, and cost before selecting modules.