In retail, the link between the head-office database and the stores carries sales, inventory, and campaign information. For that reason we cover this link together with the head-office SQL Server. Details on Nebim V3 ERP, Nebim V3 POS, and the store side are on the product pages.
When you need it
- Data transfer between the stores and the head office is delayed or breaks.
- The head-office system slows down at the start of campaigns and seasons.
- The head-office SQL Server has a backup, but nobody has ever tested restoring it.
- The head-office team connects to Nebim from home or from branches over an insecure path.
- You have no backup link plan for the case where a store's link goes down.
Scope
- Head-office SQL Server. We size and install SQL Server based on database size and user load. We schedule maintenance plans for indexes, statistics, and integrity checks.
- Head-office and store connectivity. We monitor the server, network, and database side where the data transfer runs, so that breaks and delays are noticed early. Store register data flows to head office over these links, so link quality affects sales directly. We set up store links over an IPsec tunnel, MPLS (the carrier's private line that does not go through the internet), or SD-WAN where there is no MPLS; the store link options are compared in one place. We recommend a second link with automatic takeover for critical stores.
- Access for head-office users. Head-office users connect to Nebim with SSL VPN, zero trust network access (ZTNA), or ARGE ZTNA. They reach only the resources they are authorized to use.
- Peak-season capacity. Before campaigns and seasons, we review capacity, backups, and link status against the previous period's measurements. We complete any changes before the period starts.
- Backup and disaster recovery. We copy SQL Server backups to a separate location, run restore tests, and report the result to you. We also prepare a recovery plan for losing the head-office site.
- e-Invoice and e-Ledger connectivity. For e-Invoice, e-Archive, and e-Ledger, the head-office server must reach your e-invoicing service provider; we prepare the network and server side of that access.
- Monitoring. We monitor the head-office server, SQL Server, backups, and store links; monitoring hours and response scope are set in the contract.
Out of scope and limits
We do not sell Nebim licenses or provide module setup or functional support, and we are not an official Nebim partner or reseller. The application settings for head-office-to-store data transfer, and which transactions a register can continue when the link is down, belong to your Nebim partner.
How we work
- We review the current state of the head-office SQL Server, the store links, the backups, and the access setup.
- We present the findings and decide link and capacity questions together, based on the store count and the link options.
- We build the setup and hand it over; a responsibility matrix agreed with your Nebim partner shows who does which task.
- After handover, we monitor connectivity, backup, and capacity status, and we share the measurements with you before peak periods.
Service models
- On ARGE Cloud, the head-office SQL Server runs in a virtual private cloud (VPC) dedicated to you; we build and operate it, and the stores connect to it.
- In your environment, you host the head-office server, and we handle setup, maintenance, store connectivity, and monitoring.
- As a setup that uses both, part of the head-office system runs on ARGE Cloud and part in your own server room; we draw the line together, based on data volume and store count.
Setup on ARGE Cloud
The Nebim head-office SQL Server runs on ARGE Cloud in a VPC dedicated to you; the platform is our own infrastructure in a data center in Istanbul. Store links reach the VPC over IPsec, MPLS, or SD-WAN, and a redundant firewall stands in front of it. Backups of the head-office database are kept in the isolated backup zone, separate from the VPC, and data on ARGE Cloud stays in Türkiye. Optionally, we build SQL Server as a high availability (HA) cluster and run a copy of the environment at a disaster recovery site (DR site).
Technologies we use: Microsoft SQL Server · Windows Server · IPsec · MPLS · SD-WAN · SSL VPN · ARGE ZTNA · ARGE Cloud
Frequently asked questions
Can a store keep selling if its internet link goes down? That depends on the application settings and is settled with your Nebim partner. Our part is the backup link plan for the store.
How do stores connect to the head office? They connect over IPsec, MPLS, or SD-WAN. Which one is used depends on the store count and the link options.
How do you prepare for campaigns and peak seasons? We review capacity against the measurements of the previous period. We complete the changes before the period starts.
How do you work with our Nebim partner? We work with a responsibility matrix: infrastructure is ours, and the application belongs to your partner. Who does which task is written down.