Solvice connector

Use your Solvice data for reporting, automation and AI.

Data Panda pulls your Solvice plans and brings them together with the rest of your logistics stack. From one place, we turn the routes, schedules and stops into dashboards, automations, AI workflows and custom apps your dispatch, finance and field teams use every day.

About Solvice

The Ghent optimisation layer behind routes, rosters and pick waves.

Solvice is a Ghent company started in the mid-2010s by Christophe Van Huele after his PhD on combinatorial optimisation. The first proof point was a scheduling solution for UZ Leuven; from there the team built out an optimisation-as-a-service platform that names like Skedulo, Planon, Swapfiets, Strobbo, BAT and De Lijn now use to plan field work, deliveries and rosters.

For dispatch, fleet and operations, Solvice is not a TMS or a tracker. It is the brain that takes orders, stops, vehicles, drivers, time windows and skills and returns a plan: which van does which stops in which order, which shift covers which slot. The OnRoute, OnShift, OnPick and OnStock products sit on top of a VRP solver that handles fifty-plus constraints. The plans live inside Solvice job responses; the order, vehicle and customer detail behind them sits in your TMS, ERP, CRM and tracker. Pulling Solvice plans into a warehouse alongside that detail is how planned versus actual stops become a real KPI rather than two API exports nobody joined.

What your Solvice data is for

What you get once Solvice is connected.

Planning reporting

Planned routes, shifts and pick waves joined to the TMS, tracker and accounting data the rest of the business already trusts.

Planned versus real drive time per route and per driver
Stops planned, completed and rolled to next day
Vehicle and shift load across the week

Process automation

Turn Solvice plans and re-plans into the nudges dispatch, finance and customer service would otherwise chase by hand.

Push the day's planned stops into the driver app and the CRM
Trigger a re-plan when a new urgent order drops in the ERP
Notify customers of their booked time window from the optimised plan

AI workflows

Use plan history and stop outcomes to forecast load and tighten the next week's optimisation inputs.

Forecast next week's stop volume per region and per vehicle profile
Score time-window settings against missed-window rate
Flag drivers and routes whose actual time keeps drifting above plan

Custom apps on your data

Small dispatch, finance and field tools built on Solvice plans instead of another job-response export.

Dispatch cockpit with planned stops, ETAs and re-plan triggers
Cost-per-route view tying plan to driver hours and kilometres
Field-team board with the day's stop list and time windows

Use cases

Use cases we deliver with Solvice data.

A list of concrete reports, automations and AI features we have built on Solvice data. Pick the one that matches your situation.

Plan vs actual drive timeTime Solvice planned per route compared to the time the vehicle really drove.

Stops per routeStops planned and stops completed per route, per day.

Time-window violationsStops served outside their booked time window per region and per driver.

Vehicle loadShare of capacity used per vehicle across the planning horizon.

Shift coverageShifts planned, filled and short, with the rolling fill rate.

Re-plan frequencyHow often a route is re-optimised in-day per region and per cause.

Cost per routePlan-driven driver hours and kilometres tied to accounting cost.

Detour kilometresKilometres above the optimised plan, per route and per driver.

Skill match rateStops served by a driver carrying the required skill or certificate.

First-stop punctualityArrival time at the first stop versus the planned start window.

Rolled stopsStops not served on the planned day and the reason they slipped.

Plan stabilityHow much the morning plan changes by end of day, per region.

Real business questions

Answers you will finally get.

Where does the optimised plan stop matching the day on the road?

Planned drive time and stop sequence from Solvice joined to the actual positions and timestamps from the tracker, per route and per driver. Operations sees which routes drift the most, which time windows are systematically missed and whether the gap is a planning input issue or a real-world traffic and customer pattern, instead of arguing about it on the next day's stand-up.

What does a stop really cost us, plan-driven and post-route combined?

Driver hours and kilometres from the Solvice plan tied to the actual hours, fuel and accounting cost on the same route. Finance gets a defensible cost per stop and per region, so the conversation with a key customer about delivery pricing runs on numbers from your own data, not on a per-route average from the carrier portal.

Are we using the right vehicles, drivers and skills on the right work?

Vehicle capacity used and skill-match rate from the Solvice plan over the last quarter, broken out per vehicle profile and per driver. Dispatch sees which vans are systematically half empty, which qualified drivers are doing low-skill work and where the next round of fleet sizing or training should land.

Value for everyone in the organisation

Where each function gets value.

For finance leaders

Plan-driven driver hours and kilometres next to the booked accounting cost on the same route. Cost per stop and cost per region become a quarterly conversation with numbers behind them, not a back-of-envelope average to defend a price hike to a key customer.

For sales leaders

Plan and time-window data exposed on the customer record so the account manager can answer when a delivery is booked, why it landed in that slot and what a service-window change would do to the schedule, instead of pinging dispatch in chat.

For operations

Planned versus actual drive time, stops served, missed windows and re-plan frequency on one dashboard per dispatcher. Planning, depots and customer service read the same picture, so the morning huddle is about which routes need attention today, not about whose export is right.

Ideas

What you can automate with Solvice.

Pair with TraxGo

Compare Solvice plans against TraxGo positions per route

The route Solvice planned for the day flows into the warehouse alongside the TraxGo positions the van really drove, joined on plate and on stop. Dispatch sees per route where the driver took a detour, where a customer kept the van waiting and where the planning input itself was off, instead of cross-reading two portals on Tuesday morning. Belgian fleet, Belgian planner, one picture.

Pair with MS Dynamics 365 Business Central

Feed Business Central sales orders into the Solvice plan

Sales orders booked in Business Central with delivery address, weight, time window and service requirements flow into Solvice as the planning input for the next route round, and the optimised stop sequence comes back onto the order record. Dispatch stops re-keying tomorrow's deliveries from a Business Central report into a planning sheet, and finance has the planned route already attached to the order it bills.

Pair with HubSpot

Plan field-service appointments from HubSpot deals into Solvice

Field-service appointments booked on a HubSpot deal flow into Solvice as planning input with the customer address, the required skill and the agreed time window, and the planned slot lands back on the deal as a logged activity. Sales and dispatch stop arguing about whether tomorrow's installation was promised at 09:00 or 14:00, and the customer hears the same window from both sides.

Pair with Exact Online

Tie Solvice plan hours and kilometres to Exact Online cost per route

Driver hours and kilometres from the Solvice plan are matched to driver wages, vehicle leasing and fuel-card cost in Exact Online on the same route and date, so cost per route and cost per stop are a real ledger-backed number. Finance closes the month with a defensible per-route cost feeding the customer-margin view, not a flat fleet average split across deliveries.

Your existing tools

Your data lands in a warehouse. Your BI tools read from it.

You keep the reporting tool you already have. We connect it to the warehouse where your Solvice data lives.

Power BI Microsoft

Fabric Microsoft

Snowflake Data warehouse

BigQuery Google

Tableau Visualisation

Excel Sheets & pivots

Three steps

From Solvice to answers in three steps.

Connect securely

OAuth authentication. Read-only by default. We sign a DPA and your admin keeps the keys.

Land in your warehouse

Data flows into your warehouse on your schedule. Near real time or nightly, your call. You own the data.

Reporting, automation, AI

We build the first dashboard, workflow or AI feature with you, then hand over the keys. Or we stay on for ongoing delivery.

Two ways to work with us

Pick the track that fits how you work.

Track 01

Self-serve

We set up the foundation. Your team builds on top.

Solvice connector configured and running
Warehouse set up in your cloud account
Clean access for your Power BI, Fabric or Tableau team
Documentation on what's in the data model
Sync monitoring so you're warned before reports break

Best fit Teams that already have a BI analyst or data engineer and want to own the build.

Track 02

Done for you

We build the whole thing, end to end.

Everything in Self-serve
Dashboards built to the questions your team actually asks
Automations between your systems
AI workflows scoped to real tasks your team runs
Custom apps where a dashboard does not cut it
Ongoing delivery at a pace that fits your team

Best fit Teams without in-house BI or dev capacity. You tell us what you need and we deliver it.

Before you book

Frequently asked questions.

Who owns the data?

You do. It lands in your warehouse, on your cloud account. We don't resell or aggregate it. If you stop working with us, the warehouse stays yours and keeps running.

How fresh is the data?

Near real time for most operational systems. For heavier sources we schedule hourly or nightly. You pick based on what the reports need.

Do I need a warehouse already?

No. If you don't have one, we help you pick one and set it up as part of the first delivery. Common starting points are Snowflake, Microsoft Fabric, or a small Postgres start.

Which Solvice data does the connector pull today?

The connector brings Solvice job results into the warehouse: the optimised plans returned by the VRP and scheduling solvers, with the stop sequence per route, the assigned vehicle and driver, planned drive time and the time window for each stop. The plan side is what the connector exposes; the order, vehicle and customer master data behind those plans usually lives in your TMS, ERP or CRM and is joined to the Solvice plan in the warehouse.

How does Solvice fit next to a TMS or a fleet tracker?

Solvice is the optimisation layer, not a TMS and not a tracker. The TMS or order system holds the orders to deliver and the customer detail; the tracker (TraxGo and the rest) records what the vehicle really did. Solvice sits between them and decides which stop goes on which route in which order. The value of pulling Solvice into a warehouse is that planned routes finally land next to the order they came from and the position trace they produced.

We use OnRoute, OnShift and the VRP API. Does the connector keep them apart?

Yes. Plans from the route-optimisation side (OnRoute, VRP solver) and plans from the workforce-scheduling side (OnShift) stay in their own grain in the warehouse: route, stop and driver for the routing plans; shift, slot and resource for the scheduling plans. Dispatch reporting joins them where it makes sense (which driver is on shift today and on which route), without forcing one schema on both.

GDPR-compliant

Data stays in the EU

You own the warehouse

A first deliverable live in four to six weeks.

We review your Solvice setup and the systems around it. Together we pick the first thing worth building.

Book a call See our other connectors