Connect, Unify, Manage
your retail network.
Four steps. No replacement of your current systems. marql reads from your existing POS, ERP and e-commerce stack, normalises the data into one model, and gives every role in your chain a purpose-built operating view.
Morning briefing
Today · 08:30
Revenue vs plan target for the current month.
Gross margin across active stores. Review P&L if it keeps moving.
Average transaction value from connected POS data.
Average SKU lines per receipt. Below 2 can signal missed upsell.
Morning network briefing
Revenue vs. plan across all stores at 08:00, before the first coffee.
First anomaly flagged
Margin drop, stock spike or missed reconciliation. Caught before it costs you.
Task list pre-populated
Store managers see their action list from the first sync. No manual setup.
Your systems stay as they are
Your POS and ERP still run exactly as before. marql only reads.
How it works
See it all. Act on it. Prove it.
Connect
ERP · POS · E-commerce · 1C · Excel
Plug marql into your existing ERP, POS, accounting and e-commerce stack. No replacement, no rip-and-replace.
In the first 20-min call, we map your current stack and show what marql would connect first. No write-back to your systems by default.
- SAP / Oracle / 1C
- Square / iiko / R-Keeper
- Shopify / WooCommerce
- CSV export / REST API
Unify
One schema across the entire network
Scattered store-level data is consolidated into one unified chain model — sales, margin, stock, staff, customers, cash.
See the full data flow →- SKU mapping & deduplication
- Currency & VAT handling
- Cost & margin reconciliation
- Time-zone alignment
Manage
Owner · COO · Store manager · Franchise lead
Owners, COOs and store teams work from role-based views: clear KPIs, daily priorities, alerts and follow-through.
See all seven views →- Network KPI dashboard
- Daily action lists & alerts
- Store-level P&L view
- Role-based access per view
Repeat standards
Playbooks · Standards · Compliance
Roll out the same standards across stores and franchise units. Replicate winning playbooks without rebuilding reporting each time.
- Standardised playbooks
- Price & promo rollouts
- Compliance checklists
- Franchise audit tracking
Once your sources sync
What you see on Day 1
The first morning after your POS and accounting sync, your first live view is already populated. No dashboard configuration, no data engineering.
Morning network briefing
Revenue vs. plan across all stores at 08:00, before the first coffee.
First anomaly flagged
Margin drop, stock spike or missed reconciliation. Caught before it costs you.
Task list pre-populated
Store managers see their action list from the first sync. No manual setup.
Your systems stay as they are
Your POS and ERP still run exactly as before. marql only reads.
Built for every role
One network. Different working views.
The same unified data powers role-specific views. Everyone sees what they need — nothing they don't.
Owner / CEO
- Revenue and margin across all stores
- Which stores are profitable this month
- Anomalies flagged before month-end
- No analyst or spreadsheet required
COO / Operations
- Store-level P&L and daily ops status
- Compliance and checklist completion
- Franchise scorecard per unit
- Playbook rollout tracking
Store manager
- Today's task list from the morning sync
- Store revenue vs. chain average
- Stock alerts and reorder signals
- No access to other stores' data
Why teams choose marql
marql vs Power BI / custom BI
The question is not whether you can build reports. The question is how fast your network gets one operating model, one daily briefing and one set of actions the whole team can use.
| Criteria | marql | Power BI / custom BI |
|---|---|---|
| Retail operating model | Prebuilt KPI logic, anomaly rules and role-based views | You define the model, KPIs, permissions and maintenance from scratch |
| Mixed-system networks | Built for POS + ERP + e-commerce + CSV/API normalization | Each connector, mapping and reconciliation needs custom setup |
| Actionability | Daily briefing, alerts and task lists for owners, COOs and store managers | Mostly reporting unless your team builds the action layer separately |
| Ongoing maintenance | Read-only sync and one shared KPI model across the chain | Continuous BI upkeep whenever source systems, fields or logic change |
Common questions
Questions operators ask before going live.
No. marql connects on top of the systems you already run. We read data from your existing POS, ERP, accounting and e-commerce tools — nothing is replaced or migrated.
It depends on how many locations you run and how many systems we connect. We map your stack on the first call and tell you what the timeline looks like for you.
We support the most common stacks in your market: Square, Lightspeed, QuickBooks, Xero, SumUp, Stripe, Shopify, WooCommerce, Glovo, foodpanda — and any system that provides CSV exports or a REST API.
No by default. marql reads data from your systems to build the operating view. Write-back integrations (e.g. auto-restock orders) are available as an optional add-on.
Typically read-only API access or scheduled CSV exports. In the first call we identify what's available for your specific stack and what the fastest first connection would be.
That's fine. CSV and Excel are a supported first integration path. Many operators start from a scheduled export and connect live APIs as a second step.
Power BI requires a data engineer, a data model, and ongoing maintenance. marql ships with a purpose-built retail operating layer — the normalisation model, KPI definitions, anomaly rules and role-specific views are already built for retail networks. Nothing to model from scratch, against 3–6 months of a custom BI build.
Read-only access, owner-approved credentials. SSO available. AWS-hosted infrastructure, GDPR-ready processes. Data is tenant-isolated. No third-party AI model sees your raw store data.
BI waits for you to look. An operator looks by itself, and it does not stop at a chart: it prepares the action and measures the result in euros.
A chatbot has never seen your locations. marql reads your tills, your stock and your accounting directly, remembers how your business is set up, and every number shows its source.
Every answer carries its source and its sync time. If a number cannot be traced back to a connected system, it is not printed.
Every approved decision is measured in euros in the Impact Ledger. You can read back what each one was worth.
Ready to connect your first store?
No POS replacement. No commitment. Book a 20-min stack review and we'll show you what would connect first.