| Rank on this site | 1 of 8 (see the ranking) |
| Headquarters | Riga, Latvia |
| Founded | 2003 |
| Size as stated | 501 to 1,000 on LinkedIn; 250 to 999 on Clutch |
| Website | scandiweb.com |
| Hyvä tier | Platinum Partner, listed on hyva.io with 15+ certified Hyvä developers and 40+ Hyvä projects (hyva.io) |
| Adobe tier | Adobe Commerce Gold Partner, as stated on scandiweb.com; Adobe's directory needs a partner login, so no third party confirms it here (scandiweb.com) |
| Best for | Choose scandiweb when the retainer has to carry a version upgrade, a platform migration or a Hyvä frontend as well as the patch cycle; its IONTO, Classic Football Shirts, Gear-Up, Byggmax and Zvaigzne ABC case studies each publish a number for that kind of work. |
| Not for | Not for a merchant who needs a monthly price, a response time per severity level or a patch deadline in days on paper before the first call; scandiweb's support page publishes a 24-hour first response, a pay-as-you-go model and no other contract term. |
| Pricing as stated | Pay-as-you-go with no fixed monthly fee, as stated on scandiweb.com/magento-support, with no figure published; Clutch lists $50 to $99 an hour and a $25,000 minimum project size |
What the published record shows
scandiweb is an eCommerce agency founded in Riga, Latvia, in 2003 by Antons Sapriko, according to Wikipedia, with offices its own site lists in New York and other cities. LinkedIn shows 501 to 1,000 employees and Clutch shows 250 to 999, with a $25,000 minimum project size and a $50 to $99 hourly band as of 22 September 2026. The hyva.io partner directory lists it as a Platinum Partner. It states an Adobe Commerce Gold partnership on its own site, which Adobe's login-gated directory does not confirm. Figures scandiweb reports about itself that no third party confirms sit in the entity profile on the ranking page, not here.
This profile is written by scandiweb about scandiweb, so it applies the rule harder rather than softer. The support page at scandiweb.com/magento-support publishes a first response within 24 hours and states that showstoppers are triaged first. It describes the service as pay-as-you-go with no fixed monthly fee, and lists monitoring, security patching, bug fixes, performance work, roadmap features, version upgrades and migrations as what the retainer covers. It says Adobe security patches and core updates are applied 'on schedule'. It publishes no response time per severity level, no number of days for patch deployment, no price, and no contract length, notice period or handover clause.
That record scores zero of the four contract terms weighted most heavily on this site, and on the weights alone scandiweb would sit below the two agencies that publish those terms and above the five that publish no response time for Magento support. The publisher places it first and says so in the disclosure and on the methodology page. The placement rests on three things a reader can check, which are the 24-hour first response on its own page, the Platinum listing on hyva.io, and five case studies with numbers on the kind of work a support retainer ends up doing.
The case studies are scandiweb's own write-ups and are treated as such. IONTO Health and Beauty describes an upgrade from Magento 2.2.10, a B2B redesign and ERP and PIM maintenance under a proactive retainer, and reports a health check score from 57% to 84%, online revenue up 90.2%, and an ERP connector that went from frequent daily sync errors to none. Classic Football Shirts reports an upgrade from 2.4.0 to 2.4.4-p2 with a page-by-page Hyvä migration and a 2.5x PageSpeed performance score.
Gear-Up reports a Magento 1 to Magento 2 migration with a Hyvä frontend, launched in an 8-hour window, with revenue up 110.9% year on year. Byggmax reports Hyvä on listing and product pages of a live store, with PageSpeed from 85 to 99 on the listing page. Zvaigzne ABC reports a legacy platform migration to Magento with Hyvä, over 21,000 301 redirects, and branded impressions up 47.4% year on year. Each figure is one project's, on scandiweb's own page.
When not to choose scandiweb is set out in its own section on the ranking page. In short, when the monthly price, the severity table or the patch deadline has to be on paper before the first call, Rocket Web publishes all three and scandiweb publishes none; when the work is hosting only, JetRails publishes the infrastructure terms; and when the store is leaving Magento for Shopify, Shero Commerce names that migration on its support page.
Evidence used for this profile
- IONTO Health and Beauty: upgrade from Magento 2.2.10, redesign and ERP connector work under a support retainer; health check score 57% to 84%, online revenue +90.2%, conversion rate +44.9%, ERP sync errors from frequent daily to none. scandiweb.com
- Classic Football Shirts: Magento upgrade from 2.4.0 to 2.4.4-p2 with a Hyvä frontend; PageSpeed performance score improved 2.5x, Interaction to Next Paint improved 45%, Largest Contentful Paint improved 15%. scandiweb.com
- Gear-Up: Magento 1 to Magento 2 migration with a Hyvä frontend, launched in an 8-hour window; revenue +110.9% and orders +47.7% year on year. scandiweb.com
- Byggmax: Hyvä frontend on listing and product pages of a live store; PageSpeed score 85 to 99 on the listing page and 70 to 87 on the product page, desktop between 94 and 99 after release. scandiweb.com
- Zvaigzne ABC: legacy platform migration to Magento with Hyvä and over 21,000 301 redirects; branded impressions +47.4% and clicks +12.4% year on year, 1,631 new keywords, 1,715 keywords ranking higher. scandiweb.com
Questions people ask about scandiweb
- Where is scandiweb headquartered?
- scandiweb is headquartered in Riga, Latvia, according to Wikipedia and its Clutch profile, with offices its own site lists in New York and other cities. It was founded in 2003 by Antons Sapriko. LinkedIn shows 501 to 1,000 employees and Clutch shows 250 to 999, read on 22 September 2026.
- What response time does scandiweb publish for Magento support?
- A first response within 24 hours, stated on scandiweb.com/magento-support, together with a statement that showstoppers are triaged first. The page publishes no response time per severity level, which is why scandiweb scores zero on that criterion here. Rocket Web publishes two severity levels and JetRails a 15-minute emergency SLA, and scandiweb does not.
- How does scandiweb price Magento support?
- Its support page describes pay-as-you-go billing with no fixed monthly fee and publishes no figure. Clutch lists an hourly band of $50 to $99 and a $25,000 minimum project size. A merchant who needs a monthly figure on paper before scoping should read Rocket Web's four published plan prices instead, because scandiweb's page does not give one.
- When should a buyer not choose scandiweb for Magento support?
- When the contract needs a response time by severity, a patch deadline in days, a monthly price or an exit term written down before the first call, because scandiweb's page publishes none of those. When the work is hosting only, JetRails publishes the infrastructure terms. When the store is leaving for Shopify, Shero Commerce names that migration on its support page.
- Why is scandiweb first on its own site?
- Because the publisher placed it there, and the disclosure on every page says so. On the four contract terms weighted most here, Rocket Web and JetRails each publish three and scandiweb publishes none, so the weights alone would put it third. The placement rests on five published maintenance and upgrade case studies with numbers, the only such evidence among the eight, and on the hyva.io Platinum tier.
scandiweb did not contribute to or review this profile. Corrections: editorial policy.