Product, software selection, data and installation
We have collected the questions that come up most in conversations, with their answers. If what you are looking for is not here, write to us directly.
Product and modules
What Mindpera does, how the modules relate to each other and what daily use looks like.
What exactly does Mindpera do?
Mindpera is decision software that brings the sales, stock, cost, capacity and demand data of a grocery chain into a single data model. It puts figures that sit separately in scattered systems onto a shared set of definitions and produces the same metric the same way on every screen. The aim is not to increase the number of reports but to reduce the number being argued over to a single source.
Are the modules separate products or parts of one system?
Modules can be taken separately but they are not separate products; they all use the same data warehouse and the same definition dictionary. That is why the turnover figure you see in Mind Stock and the turnover the allocation proposal uses come from the same calculation. Adding a module is not a new integration project — it opens new calculations and screens on top of the existing model.
Which module makes sense to start with?
The starting point is decided by which data already flows reliably and which decision is argued over most. If POS and sales data are solid, starting with Mind Ops gives the fastest return; if the problem is how product is spread across branches, Mind Send comes first; if it is margin and pricing, Mind Cost. Where the split of shelf and warehouse space is argued over, Mind Space is added.
How many products are there and what does each one cover?
There are six. Mind Ops covers daily sales and branch performance; Mind Send covers how much of a product goes to which branch; Mind Stock covers counts, expiry dates, turnover and dead stock; Mind Cost covers product-level cost and margin; and Mind Space covers planning branch space against demand. Mind Cam covers camera analytics.
Is there mobile use in the field?
Yes. The Capacitor-based mobile field app was designed for branch and warehouse teams to run counts, checks and task flows from a phone. It supports offline counting: when the connection drops, records are held on the device and transferred to the central data model once it returns. Counting does not stop in parts of the warehouse with no signal.
Does everyone see the same screens?
No. Permissions are role-based and follow the company and branch hierarchy; a store manager sees their own branch while a regional manager sees the branches in their region together. Fields containing personal data can also be masked by role, so employee identity is not exposed unnecessarily during performance analysis.
Which need maps to what
The matching questions that come up most when evaluating software: which module or service covers the need you have.
We are looking for inventory management software — does Mindpera cover that?
Yes. The Mind Stock module covers counting, variance analysis, expiry dates, turnover and dead stock tracking, and it comes with a mobile counting app that works offline in the field. What separates it from a classic stock tracking package is this: the stock figure sits in the same data model as sales, cost and allocation, so a count result flows straight into the cost and margin calculation.
Do you also provide an ERP?
No. Mindpera does not replace the ERP; it is decision software that connects to the ERP your grocery chain already uses. Purchasing, stock, sales and finance records stay in the ERP; Mindpera reads that data and brings it together with till data in one model. So you do not have to change your ERP, and the till and workflow in the branch stay as they are.
Can we use it as product costing software?
Yes. Mind Cost shows average cost and last purchase cost side by side and separates the gap into purchase batch, expense line and currency effect. In aisles that produce their own goods, such as the in-store bakery and deli, the same product calculates recipe cost with shrinkage, labour and overhead allocation; the standard-versus-actual variance is reported split by quantity and price.
Do you do store camera event tracking and video analysis?
Yes. In the Mind Ops module, events at the till, the entrance and the shelf are recorded with a timestamp and linked to the related sales record. Visitor count, density map and queue time are derived from the footage; conversion is calculated against that figure. Unusual movement and till events with no matching transaction raise an alert.
Can it be used as store management software?
The Mind Ops module was designed for exactly this: revenue, conversion, basket and campaign performance come from the same data model, daily check items land on an owner and escalate if they are not closed. It does not replace the POS software; the POS remains the record of transactions, and Mindpera reads its data to reconcile it and analyse performance.
Data and architecture
How data enters the system, where it is stored and in which layer the calculation happens.
How is data fed into the system?
Scheduled transfer jobs pull data from the source systems (ERP, till/POS, warehouse) and write it into a star-schema data warehouse. Depending on the interface the source offers, the transfer can be a database connection, an API or a file-based load. Every job logs its run time, the number of records processed and any error, so when a figure does not add up it can be traced back to what happened in which transfer.
How often is the data refreshed?
The frequency is set by the load the source system can carry and the rhythm of the decision. Sales and POS data typically refresh at intervals during the day, stock movements daily, and cost and accounting data in line with period closes. Each screen shows the last refresh time for the data it displays, so users know which moment the number belongs to.
Where are the KPIs calculated?
All KPI calculations run in stored procedures on the star-schema warehouse in SQL Server. Business logic is not spread across the application layer or an ORM; the Node.js service layer stays thin and mainly handles authorisation, passing parameters and returning results. Because of that separation, the calculation rule sits in one place and a change reaches every screen at once.
Can the same KPI come out differently on different screens?
It cannot, because every screen calls the same stored procedure; screens show the result of the calculation, not the calculation itself. A number that looks different usually means a different filter, a different date range or a different level of hierarchy. In that case the filter summary above the screen states plainly which slice was selected.
Can we migrate our historical data?
Yes, historical data migration is part of onboarding. How far back it can go depends on how far the source system holds data and whether the product and branch codes from that period map to today's codes. Mapping tables are defined for code changes and for merged or closed branches so that historical comparisons do not break. For seasonality-sensitive calculations such as demand forecasting, at least two years of history is recommended.
Are Turkey-specific requirements supported?
Yes. Accounting data running on the Uniform Chart of Accounts connects directly to the model, integrations with local POS systems are built, and the shifting religious holiday calendar is held as a separate attribute in the time dimension. Because holiday dates move each year, comparing against the same calendar week of the previous year is misleading; the system also offers that comparison on a period aligned to the holiday rather than the calendar week.
Installation and integration
Who does the installation, the infrastructure needed and working alongside your existing systems.
Who does the installation?
Our team does. In the first call we go through the ERP, till and warehouse systems you use; then our team comes to your branches, sets up the connections, configures the data model to your branch and department structure and hands the system over working. Data processing terms are written into the contract.
How is integration with our ERP and POS set up?
First we establish which interface the source system offers: database read access, an API or a scheduled file transfer. Then a mapping table is produced between your field names and the fields in the Mindpera data model; product, branch, customer and account codes are aligned at this stage. The integration is one-way — Mindpera does not write to the source systems, which remain the record of transactions.
What are the hardware requirements?
The infrastructure needed is agreed together in the first call, based on the systems you use, and our team does the installation. What is needed on your side is access to ERP and till data: database read access, an API or a scheduled file transfer, depending on the interface the source system offers.
Is our multi-company, multi-branch structure supported?
Yes. The system was designed multi-tenant and the company and branch hierarchy is defined inside the data model. Different legal entities can work on the same platform without seeing each other's data, while the consolidated view is opened only to roles that are entitled to it. Branch openings, closures and mergers are kept in the hierarchy history so that period-over-period comparisons do not break.
Commercial and support
How pricing works, what the demo process looks like, training, support scope and contract terms.
How is pricing structured?
Pricing is monthly and is set by the modules used and the branch and user scale. One-off work such as historical data migration and custom integration development is priced separately as an installation item. Before quoting a figure we work through your source systems and module scope together; the firm quote follows that conversation.
How does the demo process work?
The first conversation covers your existing systems, the decisions that are argued over most and the module scope you have in mind. We then run a live walkthrough of the relevant modules on a sample data set. If you wish, a preliminary study can be set up on a limited slice of your own data; a mutual non-disclosure agreement is signed at that stage. To start, an email to info@mindpera.com is enough.
Is training provided for our team?
Yes, and it is role-based. End users get screen and decision-flow training; managers get metric definitions and how to read the interpretation screens; the IT team gets data transfer jobs, log monitoring and permission management. Training happens at the end of onboarding and is repeated for the relevant team whenever a new module is switched on.
What does support cover?
Support covers application faults, problems in data transfer jobs, permission and user definitions, and questions about interpreting metrics. Requests are classified by priority, and for critical items a first response is given within 4 hours during working hours. Internal problems in your own source systems are outside support scope; in those cases we identify the finding and route it to the right party.
What are the support hours?
Standard support hours are Monday to Friday, 09:00-18:00. Tickets raised outside those hours enter the system and are queued at the start of the next working day. For customers that need an extended window, the scope and terms are defined separately in the contract.
How does the contract work?
The contract runs monthly; maintenance and version updates are included. It states the module scope, branch and user count, support level, data processing terms and termination conditions explicitly. When the contract ends, a defined process is run for exporting and then deleting the data.
How is KVKK compliance handled?
Fields containing personal data are protected by role-based masking and seen only by roles that need them to do their work. Who accessed which data and when is logged. In flows involving customer communication, IYS-compliant consent checks are applied and records without consent do not enter contact lists. The parties' responsibilities as data processor are defined in a written data processing annex.
Is your question not answered here?
You can put any technical or commercial question straight to the team that builds the product. There are no layers in between.