Data Panda brings your FDT Sellus 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.
FDT Sellus is the combined POS and back-office platform from FDT System AB, a Luleå-based retail software house that has built tools for shopkeepers since 1979 and is now part of Total Specific Solutions. Sellus is the modern, web-based successor inside the FDT portfolio and runs in both online and offline mode at the till, so a card swipe still works when the connection drops. The system is most at home in Nordic specialty chains: white goods, consumer electronics, sport, pool and spa.
Inside Sellus you have orders, invoices, articles, customers, suppliers, inventory positions, payment splits and the integrations the chain layers on top, from Klarna at the till to the accounting package in the back office. That covers the day-to-day, but the questions a buyer or a chain controller ask sit across Sellus and the rest of the stack: marketing, ecom, accounting, supplier portals. Pulling Sellus into a warehouse is where those reports stop needing a manual export.
Margin, stock and sales performance in a single view instead of three Sellus screens.
Turn till data and stock events into timely actions in the rest of the stack.
Use sales and inventory history to sharpen buying and clienteling decisions.
Shop-floor and head-office tools that replace the export-and-mail-around routine.
A list of concrete reports, automations and AI features we have built on FDT Sellus data. Pick the one that matches your situation.
Which articles are making money per shop?
Sale lines joined to article cost and current landed cost, split by shop and category. Shows which white goods or electronics carry the chain and which ones sell well but leave nothing once the supplier invoice is in.
Where is inventory drifting between vestigingen?
Stock on hand per shop against sell-through rate per shop. Surfaces the article that is moving in one location and gathering dust in another, so a transfer goes out instead of a fresh purchase order.
Does the end-of-day reconcile to the accounting ledger without a spreadsheet?
Register totals, payment-type splits including Klarna, and refunds pushed daily into Fortnox or Visma e-conomic as structured journal lines. The bookkeeper opens a clean day, not a tab full of Sellus exports.
Daily till reconciliation with the accounting ledger, not a month-end catch-up. Real margin per shop after supplier invoices, Klarna fees and markdowns, ready on the first of the month.
Buyers see margin, cover and supplier lead time in one screen, so reorder decisions sit on numbers instead of gut feel. Shop managers see today against plan before the afternoon rush.
Inventory drift between vestigingen, dead stock and supplier fill rate surface before they hurt. Transfers replace a second purchase order when the same article already sits in another shop.
Register totals, payment types and refunds from FDT Sellus land daily in Fortnox as journal entries with the right VAT split. The end-of-day reconciles on its own, and the bookkeeper stops chasing exports to close the month.
Klarna settlement files are matched to the Sellus baskets that sourced them, so fee, refund and chargeback lines hang on the right order. The finance team sees Klarna net revenue per shop without a manual reconciliation in Excel.
For chains running Sellus in the shops and Shopify online, Data Panda stitches the same customer, article and order across both. Sales, returns and loyalty reporting hold up at chain level instead of living in two disconnected dashboards.
Customer purchase history from the till flows into Klaviyo as profile properties and events. In-store buyers receive campaigns based on what they bought in the shop, not just what they clicked, and flows stop treating a shop-only customer as a cold lead.
Enriched product records from Akeneo flow into Sellus articles, with the same descriptions, attributes and media the webshop uses. Staff on the floor see the same product story the customer saw online, and catalogue updates stop being a double data-entry job.
These are the 16 tables we currently pull from FDT Sellus 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 FDT Sellus 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.
We review your FDT Sellus setup and the systems around it. Together we pick the first thing worth building.