AlkOutlet.lv, kept since 2024
One of Latvia’s largest online alcohol retailers, part of a retail network in more than 45 cities, on a Magento 2 store we took over from the agency that held the account.

The storefront the store runs today, on the version kept current since the takeover.
How the account came to us
The agency let go of it.
The previous integrator released the engineer who had run it.
Their DevOps engineer called us.
The person running the store’s infrastructure passed our details to the client. No advertising behind this account.
The first job was a version upgrade.
Early 2024, and the version has been kept current with security patches as they publish, ever since.
Nearly three years, no incidents.
That is the whole claim, and it is dated.
The store as it runs today



What we hold
The keeping work on AlkOutlet.lv and how often each part runs
Security patches from Magento
applied as soon as they publish
Minor version upgrades
planned, never deferred past risk
Monitoring with automated failover and alerts that reach a person
always on
Hosting sized for Magento traffic spikes
sized, reviewed yearly
Real-time ERP stock synchronization and inventory management
live
Access control and one point of contact for development, operations and planning
standing
What PCI DSS covers here
The store we maintain passed PCI DSS certification in 2025. The certificate belongs to AlkOutlet, not to us. What we contribute is operational: hardening, access review, patching, monitoring, and the evidence a certification body asks to see.
One client named. The rest are named in their own reports.
Most of this firm’s work happens behind an agency’s name, by contract. That is the offer, not an accident, and it is why this page carries one story instead of four. The other thing it means: nothing here is anonymized and dressed up as a case study. When we cannot name a client, we say so instead of inventing a “mid-sized industrial manufacturer”.
What one account shows
Keeping, not rescuing
Nothing on this account started in a fire. It was taken over, brought up to date, and has been routine since — which is the outcome a merchant should be buying.
Where the integration work sits
The ERP stock sync, the payment module, the indexers and the cron calendar are named as work on their own page, with the rate beside them.
Whose hands are in it
One named engineer is accountable for the work, with Andris Stinka handling estimates, scheduling and client contact; the associates rule is what fills the bench out when the work gets bigger than the two.