Data Panda brings your Paylogic Shopping data together with the data from the rest of your festival or event organisation. From one place, we turn it into dashboards, automations, AI workflows and custom apps your ticketing, marketing and finance teams use every day.
Paylogic was founded in Amsterdam in the mid-2000s and grew up serving Dutch and European festival organisers, with Awakenings, Dour Festival and Amsterdam Dance Event among the named cases on its own site. The company sat under Vivendi's See Tickets from 2018 until June 2024, when CTS Eventim closed its acquisition of the See Tickets group and brought Paylogic under the Eventim umbrella alongside Eventim B2B.
Paylogic Shopping is the storefront and order layer of the platform: a RESTful service that exposes events, products, orders, tickets, consumers and storefronts to the festival's own website and apps. For an organiser, it is the system of record for what was sold around the show, not just the headline ticket. Hard tickets, day passes, weekend passes, parking, camping packages, lockers, merchandise and food and drink vouchers all flow through the same product catalogue and the same order. Pulling that into a warehouse is how attach rate per ticket type, redemption gap on prepaid vouchers and the real margin on a camping bundle stop being PDF reports passed around the week after the festival closes.
Ticket sales, extras attach rate and channel mix in one place, split by event, ticket type and storefront.
Turn order and ticket events into the nudges and bookings your team would otherwise do by hand.
Use ticket, product and consumer history to forecast demand and tighten the next on-sale.
Small ticketing, marketing and on-site tools that sit on Paylogic Shopping data instead of another export.
A list of concrete reports, automations and AI features we have built on Paylogic Shopping data. Pick the one that matches your situation.
How does sales pace per event compare to the same point last year?
Tickets sold per day per event, plotted against the same day relative to the show last edition, split per ticket type and per storefront. Marketing and ticketing see in time where a tier is lagging the curve, in time to push a soft-sale or move spend, instead of finding it back at the post-mortem.
What is the attach rate of parking, camping and merch on each ticket type?
Share of orders per ticket type that also carry parking, a locker, a camping pitch or merchandise, with revenue per attendee broken out next to the ticket itself. The team sees which weekend or VIP tier pulls extras and which one only sells the bare ticket, so the next bundle is built on what the buyer already chose, not on a hunch.
How big is the gap between vouchers sold and vouchers redeemed?
Prepaid food and drink vouchers sold through Paylogic Shopping versus the redemptions that came back from the on-site POS, per outlet and per day of the festival. Finance sees the unredeemed balance that lands as breakage and operations sees which bar or food stand has a queue mismatch worth fixing for the next day.
Order revenue, VAT and any tourist tax per event, with refunds, chargebacks and voucher breakage booked as separate lines instead of folded into one ticketing total. The post-festival close runs on a single warehouse view rather than a stack of CSV exports.
B2B and sponsor allotment usage per partner per event, plus the lapsed-buyer list ranked by spend last edition. Account managers approach renewals with the actual numbers their counterpart at the festival saw, not with what was promised at signing.
Capacity used per ticket type, per camping pitch and per parking lot in the run-up to the show, joined to voucher redemption per outlet during the show. The site team sees the bottleneck before it forms instead of after the second night.
Each Paylogic order, ticket type and consent flag flows into Klaviyo as a profile and event, with weekend versus day, VIP versus general and country segment attached. The on-sale teaser, the pre-festival logistics email and the lapsed-buyer winback all run on what the consumer bought, instead of on a list pulled the week before send.
Each night, Paylogic order revenue lands in Exact Online split across ticket revenue, parking, camping, merchandise and food and drink vouchers, with VAT per rate and refunds posted as their own lines. Finance closes the festival period on a ledger that already reflects breakage on unredeemed vouchers, instead of reclassing a single ticketing line after the fact.
Sponsor and B2B accounts that draw on a Paylogic allotment land in HubSpot as companies and deals, with the allotment claimed per event and the order value attached. Account management runs sponsor renewals on what each partner used across the season, rather than on the figure quoted at signing.
Paylogic orders that include a partner-hotel package are paired with the corresponding Mews reservation, so the festival and the hotel see the same guest, the same nights and the same package status. Both sides reconcile the package at the end of the weekend instead of trading PDF lists by email on the Monday after.
These are the 5 tables we currently pull from Paylogic Shopping 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 Paylogic Shopping 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.
Each Paylogic Shopping product on an order lands in the warehouse as its own line, with its own product type, price, VAT rate and quantity. Hard tickets, day passes, parking, camping pitches, lockers, merchandise and food and drink vouchers stay split, so attach rate, breakage and revenue mix by category are first-class numbers rather than something reverse-engineered from a single ticket total.
Paylogic Shopping carries the consumer object separately from the order, with the personalisation, transfer and resale events kept on the ticket itself. The warehouse keeps the buyer, the current holder and the transfer history together, so resale activity per event is visible per ticket type rather than as a single platform-wide figure.
The Shopping API is unchanged by ownership: events, products, orders, tickets, consumers and storefronts remain the same resources we connect to. The acquisition closed in June 2024 and Paylogic continues as a branded platform inside the Eventim group. We monitor the API for breaking changes the same way we do for any vendor under active development.
We review your Paylogic Shopping setup and the systems around it. Together we pick the first thing worth building.