Connect your POS data. Measure real conversion by space.

Footfall without sales data is half the picture. KSI integrates ticket-level transaction data from your stores or mall tenants via PULL connectors — API, database, file export, or local collector — so you measure real conversion, revenue per m² and tenant performance.

KSI connects to your existing POS systems without requiring tenants or stores to make manual exports. Our connectors pull transaction data at the agreed frequency, normalize it into a standard model, and cross-reference it with footfall, dwell time and behavior data from your cameras.

Talk to a technical expertRequest a demo

The gap

Traffic data without sales data is incomplete.

Cameras tell you how many people enter, where they go, how long they stay and what friction they encounter. But without transaction data, you cannot measure what really matters: did they buy? How much? Which product? In which zone? KSI closes that gap.

Conversion without guessing

True conversion to sale — visitors that entered and bought — measured by store, zone, category and hour.

Revenue per m²

Overlay sales on your floor map to identify which areas generate revenue and which ones underperform.

Tenant benchmarking

Compare tenant performance across the same mall — who attracts traffic, who converts it, who underperforms.

Anomaly detection

Detect underreporting: sales that disappear after discounts, voids, employee meals or cash vs card inconsistencies.

How it connects

90% PULL-based connectors. No manual exports.

We do not wait for stores to send data. KSI connects directly to POS systems, databases or file outputs and pulls transactions at the agreed frequency. We handle the integration — the tenant or store does not need to invest technical effort.

YOUR TRANSACTION SOURCESKSI CONNECTORKSI PLATFORMSPACE-LEVEL ANALYTICSPOS API (cloud)SQL / local DBCSV / XML / TXT exportLocal collector (legacy POS)KSIConnectorPULL · NORMALIZEVALIDATE · DEDUPEKSI AIPlatformPOS + FOOTFALLBEHAVIOR + SPACEConversion by store & zoneSales per m² of floorCategory & tenantperformanceTraffic → dwell → ticketfunnel

POS API (cloud)

For modern cloud-based POS systems that expose a REST or GraphQL API. KSI calls the endpoint periodically with date-range parameters and ingests new transactions.

  • OAuth 2.0 / API key authentication
  • Configurable pull frequency (hourly, daily)
  • Incremental sync from last known state

SQL / database direct

Most common

For POS systems with a local SQL Server, MySQL, PostgreSQL or similar database. KSI connects with read-only credentials and queries only new transactions since the last sync.

  • Read-only access, no writes
  • Supports SQL Server, MySQL, PostgreSQL, Firebird, SQLite
  • Watermark-based incremental queries

File export (CSV / XML / TXT)

Many POS systems generate closing reports or flat files in a shared folder. KSI monitors the folder, reads new files as they appear, parses them and normalizes into the standard model.

  • Watches a local or network folder
  • Parses CSV, XML, TXT and fixed-width formats
  • Deduplication and idempotent ingestion

Local collector (legacy POS)

Legacy-compatible

For stores with legacy POS and no API or SQL access. A lightweight background service reads from the local POS data source and pushes normalized transactions over HTTPS to KSI cloud.

  • Background Windows/Linux service
  • Works without opening firewall inbound ports
  • Handles offline queuing and retry

Standard data model

What KSI captures from your POS.

KSI normalizes any source format into a standard transaction model. We agree in advance on exactly which fields are extracted — and we do not access anything beyond what is agreed.

Core transaction fields
  • Ticket ID
  • Store / tenant ID
  • POS terminal ID
  • Timestamp
  • Gross / net / tax amount
  • Discount amount
  • Payment method (cash, card, mobile)
  • Channel (in-store, online, delivery)
  • Item-level detail (SKU, description, qty, unit price, category)
Special event types
  • Refunds and returns
  • Voids / cancellations
  • Employee sales / internal consumption
  • Online / delivery orders
  • Layaway and deferred payments

For shopping malls

Understand every tenant. Act on real data.

Malls collect rent — often as a percentage of revenue. Without accurate, automatic sales capture, that calculation depends on tenants self-reporting. KSI replaces that with automated, verified data.

01

Automated revenue reporting

Replace manual or self-reported tenant sales statements with automatic data capture from POS. No missing months, no disputes.

02

Tenant performance benchmarking

Compare conversion rates, average ticket, revenue per visitor and sales per m² across all tenants in the same category.

03

Underreporting detection

Identify anomalies: tenants with high foot traffic but low declared sales, unusual void rates, or systematic cash-only transactions.

04

Leasing decisions backed by data

Know which locations generate real sales and which ones are carried by foot traffic alone — before renewing or repricing leases.

05

Campaign and event ROI

Measure the actual sales lift from marketing campaigns, seasonal events or layout changes across specific tenants and zones.

06

Real-time operational triggers

Set alerts when a tenant's hourly sales drop unexpectedly — enabling rapid response before the day is lost.

For retail chains

True conversion per store, zone and category.

Retail chains know their sales. What they rarely know is why: which stores convert better, which zones drive the basket, and what the actual funnel is from door entry to purchase.

01

Store-level conversion rate

Measure visitors that entered and bought — not just sales volume. Identify which stores convert well and which lose traffic before the checkout.

02

Zone-level sales density

Cross-reference POS data with floor heatmaps to measure revenue per m² and identify where store layout changes would have the highest impact.

03

Staff scheduling by traffic + sales

Align staffing to the hours where conversion is highest — not just traffic peaks. Reduce idle hours and capture missed sales.

04

Merchandising and planogram ROI

Measure whether a display change or product relocation actually increased category sales — with the before-and-after data to prove it.

05

Cross-store benchmarking

Compare the conversion funnel across all stores in the chain. Surface the specific steps where top performers differ from laggards.

06

Cart abandonment and queue impact

Quantify how much revenue is lost when queues are long. Correlate queue events with drop-off in final conversion to justify staffing investments.

Security & compliance

Data access that is limited, verified and compliant.

Agreed-scope access only

We define in advance exactly which fields are extracted. KSI does not access additional data without a new explicit agreement.

Encrypted in transit

All data transmission from local connectors to KSI cloud uses TLS 1.3. No data is stored at the connector level.

No personal data

Transaction data captured is commercial — amounts, categories, timestamps. No customer PII is required or stored.

Compliant architecture

KSI's cloud infrastructure is ISO 27001-aligned. Access to tenant data is role-gated and auditable.

Implementation

How a POS integration project runs.

  1. 1

    Scoping call: identify POS systems, source types and agreed data fields per tenant or store

  2. 2

    Connector selection: API, SQL, file or local collector — based on each POS environment

  3. 3

    Credentials provisioned with read-only access; integration built by our technical team

  4. 4

    Staging validation: first data pull reviewed against source, field mapping confirmed

  5. 5

    Go-live with 30-day monitoring; alerts configured for sync failures or data anomalies

Connect your sales data to your space data.

Tell us your POS systems and we will return a connector plan within 48 business hours.

Talk to a technical expertRequest a demo