New Data Panda connectors in June 2026

In June 2026, we added seven Data Panda connectors: Centric Software, FishTalk, Paylogic Reporting, PTV Route Optimiser, Rackbeat, SoftTouch and Twinfield.

No long technical list. Below you will find what each connector can help with in practice, and what to watch when you connect that source to your data layer.

Centric Software: target cost, samples and suppliers per collection

Centric Software is useful for brands and retailers that manage product development in PLM. Decisions about style, material, target cost, supplier and timing are often made there long before anything appears in ERP or accounting.

Useful checks: target cost versus expected purchase cost, delayed samples, suppliers that miss deadlines, and collections that move too late towards purchasing. Tip: do not connect Centric only to sales reporting. Put it next to ERP and finance as well, so you see earlier where margin is already under pressure during product development.

FishTalk: batch cost, growth and harvest timing

FishTalk sits in the world of aquaculture. Think production planning, biological growth, harvest moments, cost and traceability.

When you combine FishTalk data with finance, stock, sales or quality data, you can report much more clearly on cost per batch, plan versus actual and biological performance per site or cycle. Tip: do not start with every possible field. Start with batch, site, period, volume and cost. That already gives you a useful first model.

Paylogic Reporting: sales pace, revenue and refunds per event

For festivals, venues and event organisers, Paylogic Reporting is useful because ticket data is often viewed event by event or edition by edition. That works fine for one event. Once you want to compare several editions, ticket types or sales channels, exports quickly become annoying.

With Paylogic data in your data layer, you can compare sales pace with previous editions, follow refunds, report revenue per ticket type, and put ticketing next to marketing spend or accounting. Tip: always keep event, edition, ticket type and sales channel as dimensions. Otherwise you lose the detail event teams actually use.

PTV Route Optimiser: planned route versus real delivery cost

PTV Route Optimiser helps transport and logistics teams plan routes and assign orders to vehicles. For reporting, it becomes most useful when you put planning next to execution.

Then you can compare planned kilometers with driven kilometers, link delivery cost to customers or regions, and spot deviations per route. Tip: combine PTV with order data and invoicing. Only then do you see whether a route was not just well planned, but also profitable.

Rackbeat: stock value, backorders and purchasing needs

Rackbeat covers stock, purchasing, sales orders, receipts and shipments. For SMEs, it is often a core system: the stock tool knows what physically moves, accounting knows what was booked, and sales knows what customers ordered.

With Rackbeat data in your warehouse, you can report stock value, rotation, backorders, purchasing needs and sales data together. Tip: agree early which codes are leading for product, location and order. If those definitions are unclear, you will get a lot of discussion later about numbers that should be saying the same thing.

SoftTouch: combine sales lines, customers and payments

SoftTouch is relevant when sales, stock, customers, payments or POS data sit in one operational system. Those systems often run the daily operation well, while reporting around them still depends too much on exports.

A connector helps you pull that data out without disturbing the daily work. After that, sales lines, customers, products or payments can sit next to finance, webshop data or planning. Tip: start with one report that is made manually today. That is usually the fastest way to show value.

Twinfield: budget, margin and cash flow from journal lines

Twinfield is Wolters Kluwer's cloud accounting platform. For data work, the useful part is often in the journal lines and dimensions: general ledger account, customer, supplier, cost centre, project or administration.

If you only take totals, you miss a lot of context. With the right dimensions, you can show budget versus actuals per cost centre, calculate margin per customer, consolidate administrations and follow open items more closely. Tip: read dimensions properly from the start. That is the difference between a basic financial overview and reporting finance can actually steer on.

Start with the weekly report that costs time

A connector by itself solves very little. First pick one question your team loses time on every week.

• Which events are behind the sales plan?
• Where is product margin already under pressure before the first purchase order?
• Which routes cost more than expected?
• Which products create backorders or too much stock?
• Which cost centres are drifting away from budget?

Those are small questions, but they force the right definitions. And that is usually where the work sits: not in pulling data, but in agreeing what a customer, order, batch, route or cost centre actually means.

From one source to one useful report

We like to start small: one source, one question, one report or check. First we land the raw data. Then we agree the definitions. Only after that do we build the dashboard, workflow or internal app.

That way you quickly see whether the numbers make sense, and you avoid spending months on a data model nobody uses. If you use one of these systems and want to know where to start, we are happy to have a look. Often one good question is enough to make the first integration concrete.