Data Panda brings your Shypple data together with the data from the rest of your business. From one place, we turn it into dashboards, automations, AI workflows and custom apps your team uses every day.
Shypple was founded in 2016 in Rotterdam by Jarell Habets and Amir Bornaee, after Habets spent an internship inside a traditional forwarding office and walked out convinced the booking, the quote and the tracking belonged on a screen instead of in a mailbox. The platform now runs ocean, air and rail bookings for more than three thousand shippers, with offices in Rotterdam, Antwerp, Amsterdam, Hong Kong, Shenzhen, Shanghai and the Central American hubs that came in with the 2021 Milestone acquisition for perishables.
The reason to pull Shypple into a warehouse is that the portal answers operational questions on its own terms, while finance, procurement and customer service ask them in the order grain. Container number, vessel, ETA, actual time of arrival, cost per CBM, demurrage exposure and document status land next to the purchase order in the ERP, the SKU in the WMS and the customer order in the webshop. The forwarder stops being a separate tab people open when something is late, and becomes a column in the landed-cost calculation.
Container ETAs, transit-time variance and cost per CBM next to the purchase orders they cover.
Turn Shypple events into the nudges procurement, finance and customer service would otherwise chase by hand.
Use Shypple history to predict where the next ETA will slip and which lanes are about to cost demurrage.
Internal tools for procurement, finance and customer service on the same Shypple feed.
A list of concrete reports, automations and AI features we have built on Shypple data. Pick the one that matches your situation.
Which lanes are quietly costing us demurrage every quarter?
Containers per lane that breach the free-time clause at the port of discharge, with the demurrage day-rate and the carrier name attached. Procurement and finance see the lanes where the port pickup window is the actual problem and where the carrier itself is slow, instead of writing off the demurrage line as a cost of doing business.
How much does the gap between portal ETA and actual arrival cost us?
Hours between the ETA shown in Shypple at booking and the actual time of arrival logged at the quay, per carrier and per lane, against the demurrage and stock-out cost on the same shipment. The forwarder conversation moves from a complaint about late ships to a number per carrier per quarter.
Which suppliers are paying for half-empty containers?
CBM filled per booked container per supplier and per lane, against the freight cost on the same booking. The procurement team sees the suppliers where consolidation could land a real cost cut and the lanes where a smaller container size would beat a part-filled FCL.
Freight cost, duty and handling rolled into a real landed cost per SKU, with demurrage and detention as their own line. The forwarder invoice stops being a monthly lump and becomes a per-shipment number that ties back to the order it covers.
Promised delivery dates against the actual ETA Shypple reports per lane and per carrier. Sales sets customer expectations on the same numbers ops works on, and the next-week promise stops being a guess.
Live container status, lane reliability and carrier on-time rate in one view. Ops walks into the weekly carrier review with the actual ETA-versus-actual gap on the table, not a portal screenshot.
Container ETAs from Shypple flow into the Monta inbound forecast on the SKU level, so the 3PL knows what is landing this week and on which vessel. Pick capacity and dock-door planning move with the actual ocean schedule, instead of with the supplier's original ship-date guess.
Shypple invoices for ocean, air and rail bookings post in Exact Online against the right cost centre, with freight, demurrage and handling on their own GL lines. Finance closes the freight ledger with each carrier either in tolerance or flagged with the exact delta, instead of comparing a portal export against a PDF invoice.
Each Shypple booking links back to the Business Central purchase order it covers, so the receipt date on the PO moves with the live container ETA. Procurement sees which orders are slipping before the supplier calls, and the inbound module lines up with the dock-door schedule that ops is planning around.
Shypple shipment status lands in Lobster as IFTSTA messages to the trading partners that expect EDI, and inbound IFCSUM consolidation messages from upstream forwarders flow into the same Shypple booking record. The forwarding view stops at one screen even when half the upstream chain is still on EDI.
These are the 6 tables we currently pull from Shypple into your warehouse. Query them directly in SQL, join them to the rest of your stack, or build reports on top.
Missing a table you need? We can extend the sync. Tell us what is missing and we will build it for you.
You keep the reporting tool you already have. We connect it to the warehouse where your Shypple 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.
Yes. Shypple books ocean, air and rail shipments on one platform, and each booking lands in the warehouse with its mode, carrier, container or air-waybill number, route, planned and actual transit dates and the cost lines attached. Reports on lane mix, transit-time variance and cost per CBM work across modes on the same grain.
Perishable bookings, brought in with the 2021 Milestone acquisition, carry the same shipment fields plus the cold-chain attributes the trade needs (temperature setpoint, reefer container number, port-of-loading inspection status). Cold-chain reporting joins to the SKU and the customer order the same way dry freight does.
We review your Shypple setup and the systems around it. Together we pick the first thing worth building.