Data Panda brings your Starshipit 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.
Starshipit was started in Auckland in 2014 by George Plummer and Alex Webster, after Webster spent too many evenings juggling courier portals for his own retail brand. Today the platform serves over thirty thousand retailers across Australia, New Zealand, the UK and a growing international footprint, with deep coverage of APAC carriers most European shipping tools never plugged into: Australia Post, NZ Post, StarTrack, Aramex, Couriers Please, Post Haste, Sendle, alongside the global names like FedEx, UPS and DHL.
The point of pulling Starshipit into a warehouse is that the rate-shopping decision, the carrier service level and the returns-portal completion rate sit inside the order economics, and almost no merchant looks at them that way. A branded returns portal is only worth the build if you can see what share of returns finishes through it. A rate-shop rule is only earning if you can prove which orders skipped it. Next to Shopify, BigCommerce and the accounting ledger, Starshipit's shipment, carrier and returns data turns dispatch from a screen the warehouse logs into into a margin input the rest of the business can act on.
Carrier choice, label errors and returns-portal use sitting next to order margin.
Push the right carrier choice into Starshipit and let it generate the label.
Use Starshipit history to pick a carrier the dispatch desk would not have picked manually.
Internal tools on Starshipit data for the people who should not be logging into Starshipit.
A list of concrete reports, automations and AI features we have built on Starshipit data. Pick the one that matches your situation.
Are we rate-shopping, or always defaulting to one carrier?
Order-by-order, the carrier the rate-shop rule recommended against the carrier the dispatch desk picked. Shows the rules that fire reliably and the ones the warehouse silently overrides because the printer is already loaded with a different label stock.
Which carriers are quietly losing the dispatch cutoff?
Same-day dispatch cutoff attainment per carrier and per warehouse over rolling weeks, with the orders that missed flagged by reason. Identifies the carrier-warehouse combination where booking earlier in the day would clear an SLA breach without changing the carrier mix.
Is the branded returns portal earning the build cost?
Returns-portal completion rate against email-only and direct-to-customer-service return requests, by SKU and channel. Shows whether the portal is replacing the manual return flow or just sitting next to it while the support inbox keeps doing the work.
Shipping cost, label-error reprints and returns-portal economics tied to order margin. The dispatch line on the P&L breaks open into cost per carrier, per route and per warehouse instead of one monthly invoice.
Carrier choice and delivery speed visible per channel and product, so promotions that lean on next-day delivery can be tested against the actual SLA the carrier is hitting on that route.
Rate-shop adoption, cutoff-miss reasons and label-error rates per warehouse user. Carrier reviews and warehouse training decisions happen against shipment-level evidence, not against the dispatch lead's gut.
Shopify orders land in Starshipit with a carrier and service picked against your own contract rates, weight and destination. Tracking flows back into the Shopify order and the customer email, with the branded returns portal link replacing the manual return reply from customer service.
BigCommerce orders drop into Starshipit with the right rate-shop rule, customs paperwork for international destinations and the returns flow ready. The BigCommerce order record reflects delivery and return status without a fragile plug-in chain in between.
Carrier invoices, surcharges and return-shipping costs from Starshipit post in Exact Online against the right cost centre and VAT treatment. Shipping stops being a single monthly figure and becomes a ledger line traceable back to the orders and carriers it belongs to.
Shipment, delivery and exception events from Starshipit feed Klaviyo flows so the post-purchase journey reflects what the carrier did in the end, not the order date. The branded returns-portal link drops in at the right point in the flow instead of being buried in a generic confirmation mail.
These are the 6 tables we currently pull from Starshipit 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 Starshipit 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. Every shipment keeps the carrier, service level, surcharges, weight, destination and landed cost, including the APAC-specific carriers Starshipit was built around. That makes carrier-mix and route economics analysable at the level the dispatch desk negotiates on, not rolled up into one bucket.
Outbound shipments and the corresponding return requests link on the same order, with the portal-completion status recorded. That lets you see what share of returns finishes through the portal versus the support inbox, by SKU, channel and reason code.
We review your Starshipit setup and the systems around it. Together we pick the first thing worth building.