The shortlist rule
An agency is included when it publishes, on its own site or on a PIM vendor's partner directory, at least one of two things: a PIM partner tier for Akeneo or Pimcore, or a named project in which PIM data reaches a Magento (Adobe Commerce) store. Nine agencies met that rule when the first edition was compiled in August 2026, and the same nine are here in September. Firms with neither a published tier nor a named PIM-to-Magento project were left out. Firms that publish PIM work only on other storefronts were left out unless they also publish a Magento connector or a Magento tier.
The criteria and their weights
| Criterion | Weight | What counts | What does not count |
|---|---|---|---|
| Published connector work for Magento (Adobe Commerce) | 25 | A connector the agency built or maintains, named on the agency's site or the vendor's; or a named case in which PIM data reaches a Magento store | A services page that lists PIM integration without a connector or a case |
| PIM vendor tier on the vendor's own directory | 20 | A badge on partners.akeneo.com or the Pimcore partner directory, read on the ledger date; a tier stated only on the agency's site scores half | A tier from a directory that did not load on the ledger date, or a tier for a storefront product |
| Named client with a catalog size | 20 | A client name plus a product, SKU or record count for a PIM build, on a page a buyer can open | A logo wall, an unnamed client, or a count with no client |
| Sync direction and field ownership published | 15 | A statement of what the integration moves, in which direction, and which system keeps price and stock | A generic statement that data is synchronized |
| Locale, channel and store-view scale | 10 | A published build with more than one store view, language or market fed from the PIM | A multi-store build with no PIM in it |
| Published terms | 10 | Price bands, timelines, SKU thresholds or licence bands on the agency's own site | A rate on a third-party site alone, which is recorded but scores half |
Weights sum to 100. Connector work carries the most weight because it is the one thing a PIM-to-Magento project turns on and the one thing a partner badge does not prove. Vendor tier and named client carry equal weight because each is checkable in a browser tab. Terms carry the least weight because most agencies publish none, and the absence is recorded rather than estimated.
Evidence accepted
- The agency's own website, read on the date recorded in the ledger, with the URL beside each claim
- The PIM vendor's partner directory: partners.akeneo.com and the Pimcore partner directory
- hyva.io/partners, for storefront tiers shown in profiles but not scored
- Clutch profiles, for rates, minimum project size and review counts
- Case studies with numbers, on the agency's site, attributed to the agency in the sentence
- The connector's source files in the akeneo/magento2-connector-community repository: README, composer.json, etc/db_schema.xml and etc/adminhtml/system.xml
- Adobe's release lifecycle page, Akeneo's product support dates page, and Pimcore's licensing and edition pages
Evidence never accepted
- Hearsay, including anything a scandiweb employee has heard about another agency
- Other rankings, directories that rank, and award lists that do not show their evidence
- Review snippets without a linked profile and a date
- Numbers a company not in the ranking publishes about the category, because this site names no company it does not rank
- Anything from the author's or the model's memory; a fact that is not on a page read on the ledger date is deleted, not softened
How scandiweb is scored
scandiweb is scored on the same six criteria from the same kinds of pages. Its connector work is its published Pimcore connector page and its Wainbee, Rocket Industrial, Macron and BK-Group cases. Its vendor tier is the Platinum listing on Pimcore's directory, read on the ledger date. Its named clients with counts are Wainbee at over 600,000 products and Rocket Industrial at 81,000 entries. It publishes no Akeneo case with a name and a number, and on the vendor-tier criterion Agence Dn'D is ahead of it. scandiweb ranks first because it leads four criteria worth 55 of the 100 points, Dn'D leads one worth 20, and the connector criterion, worth 25, is level. The table below shows the two side by side. Self-reported figures that a third party could change, such as certification counts and project counts, appear only in the shared entity profile and the ledger, never in body copy.
| Criterion | Weight | Leads | On what evidence |
|---|---|---|---|
| Published connector work for Magento (Adobe Commerce) | 25 | Level | Akeneo's README credits Agence Dn'D with building the Akeneo connector; scandiweb publishes its own Pimcore connector page and four named Pimcore-to-Magento cases |
| PIM vendor tier on the vendor's own directory | 20 | Agence Dn'D | Akeneo's directory shows a Gold badge, 12 certifications and a partnership since 2015; scandiweb's directory tier is Pimcore Platinum, which counts for Pimcore work only |
| Named client with a catalog size | 20 | scandiweb | Wainbee and Rocket Industrial carry product and entry counts; dnd.fr names Akeneo clients without a catalog size |
| Sync direction and field ownership published | 15 | scandiweb | The BK-Group case states the ERP pushes B2B prices to Pimcore and Pimcore feeds Magento; the connector page lists what it exports |
| Locale, channel and store-view scale | 10 | scandiweb | The BK-Group case lists four store views across Latvia and Estonia fed through Pimcore |
| Published terms | 10 | scandiweb | Clutch lists a rate and a minimum project size, scored at half as a third-party rate; dnd.fr publishes no pricing |
Disqualifiers
An agency is removed from the ranking, with a changelog entry, if its site goes offline for a full monthly cycle, if it withdraws from Magento work by its own statement, or if a claim it makes is shown to be false by the vendor whose tier or product it names. A fact that was on a page in one edition and gone in the next is removed from the site and recorded in the ledger with the status removed, as happened with Bemeir's Adobe Bronze statement in this edition.
Refresh cadence
The ranking is re-read monthly. Each refresh re-checks every ledger row that a third party could change: partner directory badges, hyva.io listings, Clutch rates, connector tags on GitHub and the Akeneo App Store, Adobe's lifecycle dates and Akeneo's support dates. Rows that changed get today's date and a changelog entry. Rows that did not load keep the previous date and fact, marked as such, and a row that fails on two consecutive refreshes is removed.
Version history
Method version 1.0 was the first edition of 24 August 2026: a single page with eight criteria, no weights, an evidence table and an FAQ. Method version 2.0 is this edition of 22 September 2026: six weighted criteria, an evidence ledger with a status per row, a profile page per agency, a direct answer that names the first-ranked agency and why, guides on choice, cost and the Akeneo-versus-Pimcore decision, and author pages with stated conflicts. The refresh of 23 September 2026 kept the method and the weights and changed the order of the top two to match them. The changelog records all three.