Data Panda pulls your Trunkrs shipment and tracking data and lines it up with the rest of your webshop stack. From one place, we turn it into dashboards, automations, AI workflows and custom apps your fulfilment, customer service and finance teams use every day.
Trunkrs is a Dutch carrier based in Woerden, built around a single promise: a parcel collected at the webshop in the morning lands at the customer in the evening. It delivers in the Netherlands and in Flanders, and runs a daily schedule aimed at the hours when someone is actually home to take the parcel.
For a webshop, Trunkrs is where a sold order becomes a real shipment: a label, a tracking code, a delivery window and a status that moves from collected to in delivery to delivered. The portal answers the day-to-day questions well. The harder ones, like which webshop has the most failed first attempts, how Trunkrs delivery times compare to your other carriers, or what a late delivery costs you in customer-service tickets, sit across Trunkrs and the systems around it. Pulling shipments and statuses into a warehouse is how those answers stop being a portal export forwarded as a screenshot.
Shipments and statuses joined to the webshop, accounting and customer-service data the rest of the business already trusts.
Turn shipment statuses into the nudges customer service and finance would otherwise chase by hand.
Use the status history to predict where delivery will slip and where a ticket is about to land.
Small fulfilment, service and finance tools that sit on Trunkrs data instead of another portal export.
A list of concrete reports, automations and AI features we have built on Trunkrs data. Pick the one that matches your situation.
How does Trunkrs really compare to our other carriers on delivery time?
Trunkrs shipment statuses joined to your other carriers' tracking on the same order grain, with hours from collection to delivered per route. Operations sees where Trunkrs is the faster choice for an evening drop and where another carrier wins on a given postcode, instead of trusting the impression each carrier's own portal gives off.
Which deliveries are quietly generating customer-service tickets?
Trunkrs delivery statuses matched to service tickets on the same order, so a missed window or a stalled status lines up with the ticket it caused. Customer service sees which routes and postcodes drive repeat contacts, and stops reconstructing each case from a tracking screenshot the customer pasted in.
What is a failed first delivery attempt actually costing us?
Shipments with a failed first attempt counted per postcode and route, set against the redelivery and the service ticket each one tends to trigger. Finance and operations get a real number on first-attempt failure rather than treating every parcel as a flat shipping line on the invoice.
Trunkrs invoice cost set against parcels actually delivered, with redeliveries and returns split out. The shipping line on the P&L stops being one monthly number and becomes cost per parcel per route, next to the failed attempts that quietly inflate it.
Delivery promise tied back to conversion and repeat orders per webshop. Merchandising sees where an evening-delivery option lifts checkout and where late deliveries are costing repeat business on a given postcode.
On-time rate, failed first attempts and status stalls on one dashboard per route and webshop. Fulfilment and customer service read the same picture, so the morning stand-up is about which postcodes are slipping and which orders need a call, not whose screenshot is right.
Trunkrs statuses for each shipment flow back onto the matching Shopify order, so the fulfilment status moves with the real parcel rather than stopping at handed-to-carrier. Customer service answers a where-is-my-order question from the order itself, and the order is marked delivered when Trunkrs confirms it, not when the label was printed.
Shipments created for WooCommerce orders carry their Trunkrs tracking code and status back to the order, with the delivery window visible to the customer. The WooCommerce order reflects collected, in delivery and delivered without a plugin that has to be re-checked after every store update.
Each Lightspeed eCom order is matched to its Trunkrs shipment and delivery status in the warehouse, so on-time rate and failed attempts can be read per Lightspeed store and product category. The webshop manager sees which evening-delivery promises hold up and which postcodes need a different carrier.
Bol orders that you fulfil yourself and ship with Trunkrs get their delivery status lined up against the Bol service SLA in the warehouse. You see which Trunkrs deliveries risk a late mark on Bol before it lands, and the shipping cost sits next to the Bol payout so marketplace margin reflects the real fulfilment line.
Trunkrs invoices in Exact Online are matched to the parcels actually shipped and delivered in the same period, with redeliveries and undelivered returns pulled out. Finance closes the month with shipping cost tied to real volume per webshop, instead of approving a carrier invoice they cannot break down.
You keep the reporting tool you already have. We connect it to the warehouse where your Trunkrs data lives.
OAuth authentication. Read-only by default. We sign a DPA and your admin keeps the keys.
Data flows into your warehouse on your schedule. Near real time or nightly, your call. You own the data.
We build the first dashboard, workflow or AI feature with you, then hand over the keys. Or we stay on for ongoing delivery.
We set up the foundation. Your team builds on top.
Best fit Teams that already have a BI analyst or data engineer and want to own the build.
We build the whole thing, end to end.
Best fit Teams without in-house BI or dev capacity. You tell us what you need and we deliver it.
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.
Near real time for most operational systems. For heavier sources we schedule hourly or nightly. You pick based on what the reports need.
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.
The connector brings your Trunkrs shipments and their delivery statuses into the warehouse: the parcels you created, their tracking codes and the status events as they move from collected to in delivery to delivered. That is the slice that makes on-time rate, failed attempts and carrier comparison reportable. Pricing tables and operational routing internals are Trunkrs side, not part of this pull.
Yes. Each shipment carries the order and webshop it came from, so on-time rate, volume and failed attempts can be read per connected store as well as across the whole account. A Shopify shop and a WooCommerce shop on the same Trunkrs contract stay separable in the reporting rather than collapsing into one number.
Yes. Trunkrs delivers in both the Netherlands and Flanders, and the shipments and statuses come across the same way for either, so a Belgian and a Dutch route sit on the same dashboard. You can read on-time rate and failed attempts per country and per postcode rather than keeping two separate views.
We review your Trunkrs setup and the systems around it. Together we pick the first thing worth building.