A Magento (Adobe Commerce) PIM integration fails in a handful of predictable places: the connector line does not match the Magento version, price and stock get authored in two systems, an import dies on attribute volume, a re-run duplicates products, or a website is mapped to the wrong channel. Each has a question attached, and each question has a published answer from some agencies and silence from others. Ask them in this order.
1. Which PIM, and is it already chosen?
If the PIM is not chosen, start with Bemeir's decision framework, which is the only agency-published threshold on this site: about 5,000 SKUs with meaningful attribute depth, with licence bands of 50,000 to 300,000 dollars a year for Akeneo Cloud Enterprise and 75,000 to 400,000 for Salsify. If Akeneo is chosen, the strongest published evidence is authorship of the connector, which Akeneo's README gives to Agence Dn'D. If Pimcore is chosen, the strongest published evidence is a build with a count, which scandiweb publishes at over 600,000 products for Wainbee and 81,000 entries for Rocket Industrial, and which basecom publishes as a Pimcore Strategic Partner with named cases on other storefronts.
2. Which connector, and which line?
The community connector's README pairs 105.x with Magento 2.4.7 and above, 104.x with 2.4.4 up to but not including 2.4.7 as bug fixes only, and 103.x as end of life. Ask which line the agency last shipped and on which patch. Two agencies here publish a connector by name: Agence Dn'D, credited in the README, and StrikeTru, which publishes its own Adobe Commerce connector with pricing and inventory among its fields. Neither publishes the line it last shipped, so the answer comes from the call. For Pimcore, Pimcore's own page describes a partner-built one-way connector for Magento 2 and Pimcore 5.2 and above, and scandiweb's page describes its own for Pimcore 10.x and Magento 2.4.x.
3. Who owns price and stock?
The README lists categories, families, attributes, options, product models, family variants and products as imports, and nothing else. On that module the ERP owns price and stock. StrikeTru's connector lists them as syncable from Akeneo, which is right only if Akeneo is the source. scandiweb's BK-Group case describes the ERP pushing B2B prices to Pimcore every few minutes, with Pimcore as middleware. Ask for a one-page field ownership map before the statement of work, and treat an agency that will not draw one as a risk.
4. Is there a named client with a count?
Two agencies publish one on a PIM-to-Magento build. scandiweb publishes Wainbee and Rocket Industrial with counts. StrikeTru publishes City Furniture at 100K+ SKUs with Akeneo feeding Magento, and Brickworks at 3,000+ SKUs on Adobe Commerce. Pixie Commerce publishes Trago Mills with a testimonial and the retailer's range of over 180,000 bargains, not a PIM count. basecom publishes dodenhof on Magento, Akeneo and SAP without a count. Induxx publishes Telenet and Veritas on Magento without counts. Dn'D, Netresearch, Bemeir and Perspective publish no named PIM-to-Magento client. An 81,000-record delivery and a 400-SKU pilot look identical on a logo wall, so ask for the count and the attribute and locale numbers behind it.
5. Does the vendor confirm the tier?
Three tiers on this site are on the vendor's own page: Dn'D's Gold badge and Induxx's Silver badge on Akeneo's directory, and scandiweb's Platinum on Pimcore's directory. StrikeTru's Silver, basecom's Bronze and Pixie's partner status are the agencies' own statements, because their directory pages did not load on the ledger date. Netresearch, Bemeir and Perspective publish no PIM tier. A directory entry takes a minute to check; check it on the day you sign.
6. One vendor or two?
Induxx publishes an Akeneo-only practice and expects a Magento team beside it. scandiweb, Netresearch and basecom publish the storefront and the PIM under one vendor. Perspective publishes a Magento-only team that names PIM among its integrations without a vendor. Neither model is wrong. The merchant with two vendors is the one brokering when an import fails, and the merchant with one vendor has one throat to choke and one invoice. Decide which you are before the shortlist, because it removes half of it.
7. What is published about money and time?
Perspective publishes $5,000 to $15,000 for basic stores, $20,000 to $50,000 and up for customized projects, and 2 to 8 weeks for a typical Magento 2 integration. Clutch lists scandiweb at $50 to $99 an hour with a $25,000 minimum. Bemeir publishes licence bands. StrikeTru publishes case durations, among them nine Adobe Commerce sites in 5 months for Brickworks. Nobody else publishes a number. The pricing guide puts those side by side with what the vendors publish about editions and licences.
What to ask for in writing
- The connector line last shipped to production and the Magento patch it ran on
- A field ownership map naming the owner of price, stock, media, categories and attribute options
- The attribute, locale and channel counts on the largest catalog delivered, and the client's name
- The rollback procedure for a failed import, naming akeneo_connector_entities or its Pimcore equivalent
- The website-to-channel mapping for every store view, before the first full export
- The vendor directory URL that shows the tier claimed