Most teams shopping for PIM software start by asking which tool is “the best.” That is the wrong first question. The best PIM is the one that matches your catalog size, your channel mix, and the way your team already works. Pick on brand reputation alone, and you can end up paying enterprise rates for capabilities you never switch on.

Is managing product data across platforms starting to feel heavy? Are you trying to expand into new markets while keeping a large catalog accurate? Choosing the right product information management (PIM) software is central to growing an online store while keeping data accurate and your team’s workload manageable.

This guide breaks down what to look for in a PIM solution as your business and catalog grow. It covers what PIM does, the features that matter, how the leading platforms compare, a step-by-step way to choose, and the mistakes that derail most rollouts, whatever your industry or size.

What is product information management (PIM), and what does it do?

What is PIM software?

Product information management is the central hub for all your product data. A PIM collects, organizes, and distributes product information across every sales channel so the data stays accurate and current. It becomes the one reliable record for your catalog, which matters for both the customer experience and daily operations, keeping product details consistent, updates fast, and time-to-market short.

PIM benefits for eCommerce

A PIM brings concrete gains in eCommerce, operations, and marketing, including:

• Centralized data management that keeps large catalogs consistent across every platform
• Faster product launches, cutting time-to-market by up to 60%
• Real-time updates that keep data quality high and stale information out
• A better customer experience built on accurate, current, personalized product details
• Simpler SKU additions and integration with eCommerce platforms as you scale
• Faster localization, translating product information up to 70% faster for new markets
• Quicker customer quote generation, improving response time by around 67%
• Less manual work for product teams, which frees them for higher-value tasks
• Cleaner product data that improves search rankings and drives more traffic

With a working PIM in place, a business can respond to demand faster, run leaner, and stay flexible. For a deeper look at how PIM fits an eCommerce stack, download the free guide on PIM and eCommerce integration.

Is PIM the right choice for your business?

PIM vs ERP, MDM, CMS, CRM: understanding the differences

Many companies assume they already run software that does what a PIM does. They often confuse PIM with enterprise resource planning (ERP), master data management (MDM), a content management system (CMS), or customer relationship management (CRM).

Each one serves a distinct purpose:

• PIM manages and centralizes product-specific data so the customer experience stays consistent across channels
• ERP handles operational data such as finance, inventory, and HR to run day-to-day processes
• MDM manages all types of business data, like customer and supplier records, to keep one shared view across the organization
• CMS organizes website content such as articles and media so everything looks cohesive across digital platforms
• CRM manages customer interactions, tracking sales, service, and outreach to strengthen relationships

A PIM acts as the backbone of eCommerce operations, connecting product data from CRM, ERP, suppliers, and sales channels into one centralized record. It keeps product-specific information accurate, consistent, and accessible everywhere, from ERP to CRM to CMS. That single source cuts data duplication, holds consistency in place, and keeps systems in sync. The result: faster product launches, smoother operations, and a better customer experience across channels.

When to consider a PIM system

A PIM system is worth a serious look if your business is:

• Struggling with inconsistent product data across platforms
• Handling a high volume of SKUs
• Trying to keep frequent product updates accurate in real time
• Aiming for a consistent omnichannel experience to raise customer satisfaction

The global PIM software market is in strong double-digit growth, with several research firms putting the market in the high-teens to mid-twenties USD billions by 2026 and compound annual growth in the range of roughly 13 to 19% through the early 2030s, depending on scope and methodology (Mordor Intelligence, Fortune Business Insights, and SkyQuest PIM market reports). The direction of travel is clear even where the absolute figures vary: more catalogs, more channels, and more pressure on clean product data.

PIM features every eCommerce business should consider

Scalable PIM for a growing store

As your online store grows with new products and markets, a strong PIM should grow with it without slowdowns. Look for solutions that absorb rising SKU counts and new channels while holding speed and reliability.

Customization with open-source PIM platforms

Open-source PIM platforms like Pimcore and Akeneo give you room to tailor the software to your needs without vendor limits. If you have unusual requirements or an in-house development team, open-source can be the right fit. For teams that want help, our guide to Akeneo PIM for eCommerce walks through what a tailored build looks like in practice. For the best result, work with an agency that knows PIM development and support so every detail fits your business.

Integration capabilities for clean data flow

A PIM with broad third-party integration options, such as Sales Layer or Akeneo, connects directly to ERP, CRM, and eCommerce platforms. That keeps data moving across channels and every department working from the same numbers.

API-first PIM for real-time updates

If you need real-time data sharing across platforms, look for API-friendly PIMs like Informatica Product 360. This setup lets the PIM talk to other tools directly, which makes automated updates and workflows straightforward.

Multi-tenant capabilities for distributed teams

Multi-tenant PIMs let many users access and manage data at once, which matters for global brands. Teams in different locations can work in parallel without losing speed or accuracy.

Pricing: SaaS vs on-premises PIM

SaaS PIMs like Salsify ProductXM and Sales Layer suit businesses that want easy scalability and low maintenance. On-premises solutions give more control but usually carry higher setup and upkeep costs. A SaaS model simplifies budgeting by bundling hosting, licensing, and updates into one subscription. Even so, a PIM rollout is involved and can add costs: data migration, complex integrations, or customization can introduce extra fees, especially with specialized workflows or large data volumes.

Enterprise PIM is almost always custom-quoted. Annual contract values typically run from around $25,000 to $90,000 or more, and year-one implementation can match or exceed the license fee (inRiver, “How much does PIM software cost? A complete pricing guide”). Budget for the work, not just the seat.

Digital asset management (DAM) integration for rich media

If your business leans on visuals, choose a PIM with DAM capabilities. That lets you store and organize images, videos, and other media inside the PIM, holding a consistent brand look across channels.

Governance and data quality control

PIMs with governance features let you enforce data quality standards and assign user roles to keep records consistent. This helps large operations and businesses in regulated industries where data accuracy is non-negotiable.

Localization and multi-language support

If you are going global, choose a PIM that supports localization and multi-language content. This handles translations, regional pricing, and tailored product descriptions so your brand reads naturally to customers in every market.

How leading PIM solutions compare

Whatever the brand, most PIM systems aim to centralize and simplify product data. Where they differ is in the features built around that core: customization, integration options, scalability, and support for specific needs such as digital asset management and multi-tenant setups. Implementation detail sits on the Pimcore Magento integration and BigCommerce Pimcore integration pages.

Here is a quick read on standout options for different needs:

• For high flexibility, open-source platforms like Pimcore and Akeneo let you shape the software to your requirements
• For businesses leaning on ERP and CRM, Sales Layer and Akeneo offer strong third-party connectivity for clean data flow
• For real-time data sharing, Pimcore and Informatica Product 360 have strong API support, useful for syncing across a wider tech stack
• For multi-region teams, Salsify ProductXM and inRiver offer multi-tenant capabilities so teams manage data from one source
• For low-maintenance scale, SaaS options like Salsify ProductXM and Sales Layer give cloud scalability with lighter upkeep
• For visual-heavy catalogs, Pimberly and Contentserv ship DAM features for storing media right inside the PIM
• For regulated industries, Salsify and Akeneo lead on governance

If you want a wider view of the discipline before committing, our notes on product catalog management cover the data-hygiene work that pays off no matter which platform you pick. As of this writing, the “best PIM software” search results are led by review aggregators and vendors such as G2, Gartner reviews, Akeneo, and inRiver, which confirms this is a comparison-and-decision search, not a single-answer one (Google SERP data, G2 best PIM software listings).

How to choose the right PIM solution, step by step

Step 1: Define your eCommerce goals and data requirements

Start by writing down exactly what you want from a PIM. Clear goals keep the choice anchored to your day-to-day needs. Consider:

• The scale of your product data
• Your omnichannel requirements
• The level of customer personalization you need

Step 2: Assemble your cross-functional team

Get input from every key department, including marketing, sales, IT, and product management. This team helps identify which features serve each area and makes adoption across the business easier.

Step 3: Shortlist PIM vendors and schedule demos

With goals set, shortlist the vendors that meet your criteria. Use the comparison above as a starting point, or if you are still unsure, book a free consultation with one of our eCommerce specialists. Request demos and ask pointed questions, for example:

• How does your PIM handle product information for multiple channels?
• What integrations are available with our current ERP or CRM?
• Can it be customized to manage our data the way we need?

Step 4: Evaluate ROI and total cost of ownership

Look at every cost: subscription fees, support, training, and extras. Weigh those against the return, whether that is better data accuracy, faster time-to-market, or higher efficiency. That comparison tells you whether the investment makes sense.

Step 5: Run a pilot or test implementation

Before you commit fully, run a test phase. A pilot lets your team see how the PIM behaves in a real setting, surfaces issues early, and confirms the solution fits your eCommerce needs.

Common PIM mistakes and how to avoid them

Not prioritizing user training and change management

Rolling out a new PIM without a structured training program and change-management plan leads to friction. If users are not trained or ready for the switch, adoption stays low and efficiency suffers. Put a solid training program in place for everyone who will use the PIM. Clear guidelines and ongoing support go a long way toward a smooth transition across teams.

Choosing a one-size-fits-all solution

Every business is different, so a generic setup may not fit your needs. Look for a platform with customization options so you can adjust features to your industry and demands. That way the PIM supports your specific goals rather than covering only the basics.

Ignoring data migration complexity

Moving product data into a new PIM can be tricky and slow if it is not planned. Migration without preparation produces incomplete or inconsistent records that disrupt operations. Plan ahead: check data quality, confirm format compatibility, and test integration with other sources. A little preparation upfront makes the migration far smoother.

How to future-proof your PIM choice for eCommerce

As eCommerce changes, choosing a PIM that can grow is the difference between a system you keep and one you replace in two years. A few capabilities decide whether your PIM stays useful over time.

Cloud-based PIMs

Cloud-based PIMs are hosted online, so you get real-time updates and scale on demand: add SKUs, reach data from any device, and grow without hard limits. As the catalog expands, the PIM expands with it, keeping multichannel access steady.

Artificial intelligence and machine learning

AI now works like a fast assistant inside the PIM, automating repetitive tasks such as categorizing products or flagging inconsistencies. Recent industry analysis points to AI-assisted enrichment and predictive product content as the defining PIM trend, with a large share of companies using predictive tools to tune product content to customer behavior (AtroPIM, “Product information management trends shaping the market”). Machine learning also helps you understand customers, which supports more personalized experiences.

Product experience management (PXM)

PXM is about delivering consistent, tailored product content. It lets you control how product details appear on every channel, from social platforms to your store, so the brand stays cohesive wherever customers meet it.

Multi-domain support

If you manage more than product data, multi-domain support is worth considering. It lets you handle product, supplier, and customer data in one place, which saves time and keeps procurement, marketing, and other teams working from the same current information.

Composable and headless architectures

Composable and headless setups let you adapt quickly to new channels and technology shifts. Instead of being locked into one monolith, you get modular components you mix and match as needs change, which keeps you flexible in a fast-moving market.

How to implement PIM for successful eCommerce operations

Rolling out a PIM can look like a big task, but a clear plan keeps it manageable. Here is a practical step-by-step way to get a PIM up and running: For Shopify stores, the Shopify Plytix integration and Shopify Salsify integration pages cover what the connection involves.

1. Audit your existing product data sources to remove inaccuracies and standardize information for consistency
2. Identify the core PIM features your goals require, such as data management and multichannel distribution, to pick the right solution
3. Connect the PIM to ERP, CRM, eCommerce platforms, and other channels for clean data flow across tools
4. Train users on PIM functionality and data workflows to lift adoption and efficiency
5. Run a pilot, gather feedback, refine the setup, then tune for performance before a full launch

Launching a PIM is involved, and doing it right makes a real difference. Working with experienced PIM specialists can simplify the process with tailored advice, guidance through each phase, and help tuning the setup for the biggest impact on your operations.

Case studies: how PIM software drives real results

Not sure a PIM will move the needle for your business? Here is how scandiweb helped clients reach new results with tailored PIM solutions.

Technodom: real-time updates for a successful Black Friday

Technodom, a top electronics retailer in Central Asia, needed a way to manage a vast catalog across multiple channels: 60,000 products, 15,000 attributes, and 4,000 categories. Implementing Akeneo PIM let Technodom run real-time updates and apply rapid price changes across the catalog for time-sensitive events like Black Friday. The result:

• Real-time updates applied discounts to 15,000 products instantly during Black Friday
• 20% increase in organic traffic from improved SEO and data consistency
• 11% lift in conversion rate from more accurate, timely product data

Byggmax: building customer trust with reliable stock and pricing

Byggmax, a major DIY retailer operating across three Nordic countries, needed a reliable PIM to give customers accurate stock and pricing on the website. With inRiver PIM, Byggmax gave customers real-time access to current product details, improving the experience and driving conversions. The result:

• Accurate product information raised conversions as customers trusted the data they saw
• A unified experience across all three countries for products, services, and support
• 99.8% operational uptime, backed by scandiweb’s 24/7 support across every channel

Rockar: pioneering online car sales with custom PIM

Rockar, an innovator in online car sales, needed a way to offer a fully online car-purchase journey for both manufacturers and dealers. scandiweb’s custom Pimcore-based platform let Rockar onboard clients quickly and offer flexible, multi-tenant checkout journeys without separate code bases. The result:

• Multi-tenant functionality enabled fast onboarding for new clients on a single code base
• Customizable checkout options improved the experience across diverse client needs
• Stronger platform efficiency supported a smooth online vehicle-purchase process, setting a new industry bar

Conclusion

Choosing the right PIM software changes how an eCommerce business runs. It brings cleaner data management, more consistent customer experiences, and steady distribution across every sales channel. Pick a PIM that maps to your business goals and you are set up to scale, reach new markets, and stay competitive. Implementation can get complex, so expert guidance helps a great deal: it keeps the setup smooth, protects your return, and positions you for the long term.

Frequently asked questions

What is the best PIM software?

The best PIM depends on your needs. Akeneo is known for ease of use and multi-language support. Pimcore is flexible with open-source options, and Salsify is strong on integrations for complex workflows. Match the choice to your catalog size, channels, and team.

How much does PIM software cost?

PIM pricing varies widely. Entry-level SaaS tools start around $99 a month, while enterprise contracts are custom-quoted and often run from roughly $25,000 to $90,000 or more a year, with year-one implementation that can match the license fee.

What is the difference between PIM and CRM?

A PIM manages product data, things like specs, attributes, images, and descriptions, so every channel shows consistent information. A CRM manages customer data and interactions across sales and service. They solve different problems and often work side by side.

What does a PIM do?

A PIM (product information management) system centralizes, enriches, and syncs product data across sales and marketing channels so information stays consistent and accurate everywhere customers see it.

Are there hidden costs with PIM software?

Yes. Extra costs can include data migration, support, and integrations. Cloud-based SaaS options usually include maintenance, while on-premises setups may add costs for setup and upkeep.

How do you implement PIM?

Start with an audit of your product data, define your goals for consistency, and decide which systems, such as ERP or CRM, you will integrate. Run a pilot to test compatibility, then train your team to manage and update the PIM. Partnering with experts streamlines the setup and helps every feature work together.

About scandiweb

scandiweb is an eCommerce agency offering full-service solutions, from web development and digital strategy to PIM implementation. With over 18 years of experience and a team of 500+ specialists, scandiweb has helped companies worldwide tighten operations, clean up product data, and improve customer experiences. scandiweb is an award-winning Akeneo partner and a recognized Platinum Partner of Pimcore.

Ready to put product data on a footing that scales with your catalog? Plan your PIM with scandiweb and choose a platform that fits your channels, your team, and your growth.

The post Best PIM Software: A Complete Guide for eCommerce Managers appeared first on scandiweb.

Product data rarely stays in one place. It starts in a spreadsheet, gets copied for the marketplace team, duplicated again for the translators, and within a year nobody can say for certain which version a customer actually sees on the page. A PIM-eCommerce integration is what closes that gap. It connects your Product Information Management system to your storefront, marketplaces, and downstream channels so the same product data shows up consistently everywhere – and getting it wrong is why so many catalog launches stall halfway through.

Most teams scoping this work land on the same four questions: which PIM fits our stack, how long the integration takes, what it costs, and what actually changes once it goes live. The sections below work through each one, with the timelines, patterns, and trade-offs the scandiweb integration team sees on Akeneo and Pimcore projects.

Overview

• A PIM-eCommerce integration connects your Product Information Management system to your storefront, marketplaces, and downstream channels so product data stays consistent everywhere.
• The global PIM market is on track to reach $31.98 billion by 2029 at a 15.4% CAGR, driven by AI-led enrichment, headless architectures, and marketplace expansion.
• Standard Akeneo integrations ship in 8 to 12 weeks. Complex Pimcore deployments with ERP, DAM, and multichannel run 4 to 12 months.

What is PIM-eCommerce integration?

PIM-eCommerce integration is the connection layer that moves enriched product data from a Product Information Management system into your eCommerce platform and other downstream channels. The PIM is the single source of truth for SKUs, attributes, images, descriptions, and translations. The integration pushes that data into Magento, Shopify, BigCommerce, or any marketplace your catalog needs to reach.

The integration usually moves data in three directions: PIM to storefront (product catalog, attributes, images), storefront to PIM (orders, returns, customer-driven attribute requests), and PIM to marketplaces (Amazon, eBay, Google Shopping feeds with channel-specific formatting).

How does a PIM connect to your eCommerce platform?

A PIM connects to your eCommerce platform through one of three integration patterns: a vendor-built connector, an API-led custom integration, or a middleware layer (iPaaS) that brokers data between both systems. The right choice depends on your platform, the complexity of your data model, and how much real-time sync your channels need.

Vendor connectors are the fastest path. Akeneo, Pimcore, and similar PIM vendors ship official connectors for Magento, Shopify, and SAP Commerce that handle the basic mapping out of the box. Standard Akeneo deployments with a single shop connection finish in 8 to 12 weeks (per Akeneo’s own deployment guidance).

Custom API integrations make sense when your data model has unusual attributes, when you sync more than one storefront, or when downstream channels need transformations the connector cannot handle. Most scandiweb Magento clients fall into this bucket.

Middleware patterns (using tools like MuleSoft, Boomi, or Pimcore’s own integration framework) work for enterprises running PIM alongside ERP, OMS, and DAM, where the integration is more about data orchestration than point-to-point sync.

What changed in PIM-eCommerce integration in 2026

Five shifts have reshaped how PIM-eCommerce integration works, and any team scoping a new project should account for all of them.

SaaS PIM is now the default

On-premise PIM is a legacy choice in 2026. SaaS deployments give you elastic storage as the catalog grows, automatic version upgrades, and 24/7 access without an internal infrastructure team. Akeneo and Pimcore both lead with SaaS tiers, and Gartner Peer Insights data shows Akeneo PIM at 4.7 out of 5 across 134 reviews and Pimcore at 4.1 across 10 reviews in the Product Information Management Solutions market.

Headless and composable architectures

Headless PIM decouples the data layer from the channel-specific frontend, so the same enriched product data can feed a Magento store, a Shopify B2B portal, an iOS app, and an Amazon feed without duplicating logic. This pattern is what makes scandiweb’s Pimcore connector for Magento work across multi-storefront accounts – one integration, many delivery surfaces.

AI-led enrichment in the PIM itself

Akeneo’s 2025-2026 releases added GenAI content generation for product descriptions, AI-powered attribute classification, and PX Insights for analytics – all in the Growth and Enterprise tiers. Pimcore added similar capabilities through its DataHub and Digital Experience platform. The practical effect: teams spend less time writing copy and more time on category strategy.

Channel-based pricing and offers

PIM systems now carry channel-specific pricing logic – the same SKU can show one price on the storefront, a different price on Amazon, and a marketplace-only promotion during seasonal events. The integration has to respect that conditional logic instead of pushing a flat price feed.

Real-time, not nightly, syndication

The old pattern was a nightly CSV export from PIM to storefront. The 2026 pattern is event-driven: a product update in the PIM fires a webhook, the storefront updates within seconds, and the customer sees current data on the next page load. Real-time sync is now the baseline for any retailer with marketplace exposure or fast-moving inventory.

PIM-eCommerce integration: a practical implementation playbook

The playbook below is what scandiweb’s PIM integration team runs on Akeneo and Pimcore projects for eCommerce clients across Adobe Commerce (Magento), Shopify, BigCommerce, and SAP. The order matters – swapping steps usually means rebuilding integration logic later.

1. Build a customer-centric data model

Start with what the customer needs to see, then work backward to the PIM schema. A buyer searching for “men’s wool overcoat 42R” needs material, fit, sleeve length, care instructions, size guide, and product images in a specific order. If your PIM schema does not carry those attributes natively, the integration will paper over the gap with custom mapping – which becomes maintenance debt within six months.

2. Organize and govern product data

Decide who owns each attribute. Merchandising owns category and price. Product marketing owns descriptions and translations. Operations owns dimensions and weight. Legal owns compliance copy. Without explicit ownership, attributes drift and the integration carries inconsistent data into every channel.

3. Use AI enrichment selectively

GenAI is excellent for first-pass descriptions, attribute classification on bulk SKU loads, and translation. It is a poor fit for brand-voice copy, regulatory descriptions, and high-AOV detail pages where buyers expect editorial polish. Use AI for the bottom 70% of the catalog and human writers for the top 30% – the integration should support both flows.

4. Choose your platform pairing carefully

The PIM-eCommerce platform pairing has a much bigger impact on total cost than the PIM choice alone. Akeneo with Shopify is a fast, vendor-supported pairing. Pimcore with Magento is the high-control option for complex catalogs. Pimcore with SAP Commerce is the enterprise-default for B2B distributors. See scandiweb’s best PIM software guide for the full pairing matrix.

5. Plan for evaluation, not just go-live

The integration is not finished at go-live. Run a 30-60-90 day evaluation against four KPIs: time to add a new SKU, time to launch on a new channel, attribute completeness, and content error rate. If any of those four trend in the wrong direction, the integration needs tuning, not a rebuild.

6. Align with SEO from day one

Product data is SEO data. The PIM attributes that feed structured data (schema.org/Product), faceted navigation, and on-page copy all influence organic rankings. Treat your Magento integration services brief as half-PIM, half-SEO when you scope the project.

PIM integration timeline and cost benchmarks in 2026

Three numbers anchor any 2026 PIM integration estimate.

Timeline benchmarks

• Akeneo, single storefront, standard data model: 8 to 12 weeks from kickoff to go-live (Akeneo’s own deployment guidance, validated across scandiweb projects).
• Pimcore, multi-channel, ERP-connected: 4 to 12 months depending on the number of source systems and data migration complexity.
• Custom API integration for enterprise Magento or SAP Commerce: 12 to 20 weeks when the PIM is new. 6 to 10 weeks when the PIM is already in production and only the integration layer is being built.

Cost drivers

The PIM license is rarely the dominant cost. Bigger drivers are the number of source systems (ERP, OMS, DAM, marketplaces), the data migration scope (how many legacy SKUs need cleansing), and the post-go-live evaluation period (most enterprise budgets underprovision this by 30 to 50%).

Market context

The global PIM market is projected to reach $31.98 billion by 2029 at a 15.4% CAGR, driven by marketplace expansion, AI enrichment adoption, and the shift from batch to event-driven integration. Vendor capability is consolidating around four leaders: Akeneo, Pimcore, Salsify, and Informatica – the integration choice in 2026 is less about which PIM and more about which integration pattern fits your data flow.

Frequently asked questions

What is the difference between a PIM and a CRM?

A PIM (Product Information Management) centralizes product data – attributes, descriptions, images, translations – and pushes it to your storefronts and marketplaces. A CRM (Customer Relationship Management) centralizes customer data – contact records, purchase history, support tickets – and powers marketing and sales workflows. Both can integrate with your eCommerce platform, but they solve different problems.

How long does a PIM-eCommerce integration take?

Standard Akeneo integrations with a single shop connection take 8 to 12 weeks. Complex Pimcore deployments with ERP, DAM, and multichannel syndication run 4 to 12 months. Custom API integrations for enterprise Magento or SAP Commerce typically take 12 to 20 weeks when the PIM is brand new.

Which PIM is best for Magento and Adobe Commerce?

Pimcore and Akeneo are both proven pairings with Magento (Adobe Commerce). Pimcore is the high-control choice for complex catalogs, B2B-heavy stores, and multi-storefront accounts. Akeneo is the faster, vendor-supported pairing when the data model is straightforward and the channel count is small. scandiweb’s Pimcore Connector for Magento 2 handles the multi-storefront and custom-attribute cases natively.

Do I need a PIM if I sell on Shopify?

If you sell 50 SKUs in one Shopify store, a PIM is overhead. If you sell 5,000 SKUs across Shopify, Amazon, eBay, and a B2B portal, a PIM saves more time than it costs within the first quarter. The breakeven is usually around 500 SKUs combined with two or more sales channels.

What does a PIM integration cost?

The license cost varies by vendor and tier (Akeneo starts low, Pimcore is open-source with a commercial enterprise tier, Salsify and Informatica are enterprise-priced). The implementation cost is typically 2 to 5 times the first-year license fee depending on integration complexity. The hidden cost is data migration – cleaning legacy SKUs before migration often accounts for 20 to 30% of the total project.

How does AI change PIM-eCommerce integration?

AI enrichment changes two things. First, it dramatically shortens the time to enrich bulk SKU loads – Akeneo’s GenAI generates first-pass product descriptions in seconds. Second, it shifts the integration’s role from “move data” to “validate and route AI-generated data” – the integration needs governance hooks so AI-enriched attributes get human review before they reach the storefront.

About this guide

Maintained by the scandiweb eCommerce team. Reviewed by Olha Cicek, Business Analyst.

Related reading from the scandiweb blog:

• How to choose the best PIM software – an unbiased buyer’s guide for eCommerce managers
• Akeneo PIM + Magento 2: connector, setup, and integration patterns
• Pimcore Connector for Magento 2 by scandiweb
• Product catalog management in 2026: tools, strategies, and what Pimcore/Akeneo partners actually use

Still weighing a vendor connector against a custom API build or full middleware? That call is usually the first thing worth mapping out. Tell us about your stack and the scandiweb team will talk through the integration approach that fits your Akeneo, Pimcore, or custom setup.

The post PIM and eCommerce Integration in 2026: A Complete Playbook appeared first on scandiweb.

Your catalog team is updating the same product attribute in three places this morning: the Magento admin, a marketplace feed, and a CSV bound for a printed catalog. Two of those updates will silently disagree by the time the day ends. That is the problem Akeneo PIM exists to solve, and the connector that links it to Magento 2 (Adobe Commerce) is what makes the solution real on a live store.

This guide walks through the Akeneo-Magento connector options on the market in 2026, the setup path scandiweb’s Akeneo team uses on real catalogs, and the integration patterns we have shipped for clients running into the four million-SKU mark.

Overview

• Akeneo PIM connects to Magento 2 through a connector module installed on the Magento side, talking to Akeneo via REST API.
• Three connector options exist in 2026: Akeneo’s official Community Edition, the Enterprise Edition, and partner-built alternatives like scandiweb’s connector.
• The connector handles category, attribute, product, and relationship sync, with completeness rules controlling what gets pushed.

Why Akeneo PIM matters for Magento 2

Magento 2’s native catalog management is built around the store admin’s UI. That works at small catalogs and one locale. As soon as you cross into multi-channel, multi-region, or multi-thousand-SKU territory, the four problems below appear at the same time.

Catalog management UX hits a ceiling

Magento’s product grid is fine for editing a few products at a time. It is not fine for a content team updating 8,000 SKUs across five locales. Akeneo’s interface is built for that workflow, with attribute-level completeness tracking, bulk editing, and locale-by-locale views.

Dedicated catalog teams need their own tooling

Large brands typically assign catalog ownership to a content team that should not have full Magento admin access. Giving them Akeneo instead means they can enrich products in detail without touching pricing, orders, or store configuration.

Multichannel sales need a single source of truth

If product data lives in Magento, syncing it to a marketplace, a print catalog, or a B2B portal means custom export jobs and reconciliation work. Akeneo flips the model: data lives in the PIM, and every channel pulls from there.

Completeness tracking is impossible without it

Akeneo’s completeness rules let the team see exactly which products are missing translations, certifications, or required attributes per channel. Magento has no equivalent. The team-level visibility this unlocks is often what makes the business case.

How does Akeneo integrate with Magento 2?

The integration runs through a connector module installed on the Magento side. The connector talks to Akeneo via the official Akeneo REST API, pulls product, attribute, and category data from the PIM, and writes it into Magento’s catalog tables. The Magento Akeneo integration page covers scope and data flow in production.

Ari, the AI agent for Magento, can install and configure a connector like this on a copy of your store, so you can check the synced catalog before anything reaches the live site.

The data flow is one-directional by default: Akeneo is the source of truth, Magento is the destination. The flow can be inverted in specific scenarios (for example, when an ERP pushes a baseline SKU set into Magento first and Akeneo enriches it), but the standard pattern keeps Akeneo upstream.

What the connector syncs:

• Product attributes and attribute groups
• Categories and category trees
• Products themselves, including configurable and bundle types
• Product relationships (related, upsell, cross-sell)
• Product media assets (with caveats on file-size handling)
• Completeness state, so only ready-to-publish products move

Sync runs as either a scheduled cron job or an on-demand trigger from the Akeneo side. Most production setups use a hybrid: catalog-wide sync overnight, on-demand for emergency price or copy updates.

Connector options in 2026

Three viable connector paths exist for an Akeneo-to-Magento integration in 2026. Pick by license, catalog size, and customisation appetite. On other platforms, see the commercetools Akeneo integration page.

Akeneo Connector Community Edition (free, open source)

Available on the Adobe Commerce Marketplace and on GitHub, this is the default starting point. MIT-licensed, no official Akeneo support. It works well up to roughly 50,000 SKUs and a single locale, then starts to show performance limits without custom tuning. Documentation lives at the Akeneo Help Center.

Akeneo Connector Enterprise Edition

Bundled with Akeneo Enterprise licenses only. Adds B2B-specific features, advanced asset management sync, and official Akeneo support. The right choice if you already pay for Akeneo Enterprise; otherwise it does not factor.

Partner-built connectors (scandiweb’s included)

For catalogs above 100,000 SKUs or with custom sync requirements (delta-only syncs, multi-region routing, asset CDN integration), the off-the-shelf connectors require enough customisation that a partner-built alternative often wins on cost and reliability. scandiweb’s connector ships with batched delta syncs, configurable completeness gates, and reduced data-transfer payloads.

Setup walkthrough: from zero to first sync

The five steps below are the canonical install path the scandiweb Akeneo team uses on new projects. They assume you have a working Akeneo instance (Community or Enterprise) and a Magento 2 environment with admin access.

Step 1: Verify prerequisites

Check the Akeneo prerequisites page for PHP version, Magento version, and Akeneo API version compatibility. Mismatches at this stage cause silent sync failures later.

Step 2: Configure websites, stores, and locales

Configure your Magento websites, stores, and store views first. Then mirror the locales in Akeneo. The connector maps locale-to-store-view based on these settings, and any drift between the two sides will create duplicate products or skipped translations.

Step 3: Install the connector module

Install via Composer (Community or Enterprise) or via the partner build’s install instructions. Run bin/magento setup:upgrade and the standard cache flush.

Step 4: Configure the API credentials and completeness rules

Generate an Akeneo API client, paste the credentials into Magento admin under Stores → Akeneo, and set the completeness threshold. The threshold controls which products are eligible for sync; setting it too low pushes incomplete products live, too high blocks the catalog entirely.

Step 5: Run the first sync and verify

Trigger an initial full sync. Confirm category tree, attributes, and a sample of products land correctly in Magento. Check the first multi-locale product specifically; the locale mapping is the most common point of failure.

Sync architecture and batching

The high-level sync model is simple: read from Akeneo, write to Magento. The complexity hides in batching, error handling, and incremental updates.

A naive sync pulls the full catalog every run. That works up to a few thousand SKUs. Past that, the catalog query alone becomes expensive, and the Magento indexer queue builds up faster than it drains. Production setups rely on delta syncs: Akeneo’s API exposes a updated filter, and the connector should ask only for products changed since the last sync.

Three batching settings matter most:

• Batch size per API call: 100 to 500 products is typical, depending on attribute count
• Parallelism: how many batches run concurrently against the Magento write side
• Image handling: whether assets sync inline (slow but consistent) or via an async media queue (faster, requires more orchestration)

For a catalog above 200,000 SKUs, async media handling becomes non-optional. scandiweb’s partner connector defaults to async with a configurable concurrency ceiling.

Why scandiweb built its own connector

On client work above 100,000 SKUs, the off-the-shelf connectors hit predictable walls: full-catalog syncs that take 14 hours, Magento indexers that fall behind, and asset payloads that exceed practical request sizes. The scandiweb Akeneo team’s connector was built to fix all three.

The connector has shipped on multiple large-catalog projects. One example: a scandiweb Akeneo case study documents a B2B catalog where the partner connector reduced full-sync time from 14 hours to 90 minutes, with delta syncs running in under 5 minutes. The project also earned recognition at Akeneo’s APS Summit as a top-3 Akeneo PIM implementation.

The connector is not a replacement for the official one on every project. For catalogs under 50,000 SKUs and single-locale stores, the Community Edition is genuinely fine. The partner build only pays off when scale or customisation demands it.

When should you choose Akeneo PIM for Magento 2?

Akeneo PIM is the right call when at least two of the following are true: your catalog is above 5,000 SKUs, you sell across more than two locales, you publish to more than two sales channels, or a dedicated catalog team owns product data full time. Below those thresholds, the Magento admin alone usually suffices.

For broader PIM evaluation including alternatives like Pimcore, Salsify, and inriver, see our PIM software comparison guide. For a deeper look at how PIM improves product information management workflows specifically, see our Akeneo workflows guide.

Frequently Asked Questions

Is Akeneo PIM free to use with Magento 2?

The Akeneo Community Edition and the Community connector are both free and open source. Akeneo Enterprise (which unlocks the Enterprise connector and B2B features) requires a paid subscription, priced based on user count and product volume.

How long does an Akeneo + Magento 2 integration take?

A standard integration on a catalog under 50,000 SKUs typically takes 6 to 10 weeks from kickoff to first production sync. Larger catalogs or multi-region setups add 4 to 12 weeks. The discovery and locale-mapping phase is often the longest single step.

Does the Akeneo connector sync product images?

Yes, both the Community and Enterprise connectors sync product media. The handling differs: Community ships with inline sync (simpler but slow on large catalogs), Enterprise and partner connectors use async media queues to avoid blocking the main sync.

Can I sync products from Magento back to Akeneo?

The default flow is one-directional, Akeneo to Magento. Reverse sync is possible but adds complexity and is usually only required when an ERP writes baseline SKUs into Magento that Akeneo then enriches.

Which Magento versions does the Akeneo connector support?

The current Akeneo Community connector supports Magento Open Source 2.4.x and Adobe Commerce 2.4.x. Check the Akeneo compatibility matrix before installing for the exact supported versions.

What happens if the sync fails mid-run?

Well-built connectors checkpoint progress and resume from the last successful batch. The Community Edition’s recovery behaviour is basic; production setups with high SKU counts typically need partner-level tooling for reliable resume-on-failure.

About this guide

Maintained by the scandiweb Akeneo team. Reviewed by Aigars Pavlovics, Executive Board. scandiweb is a Magento Solution Partner with a top-3 APS Akeneo Summit recognition for PIM implementation work.

Thinking about an Akeneo + Magento integration on a real catalog? Get in touch with the scandiweb Akeneo team for a connector recommendation, a scope estimate, and a sync architecture review.

The post Akeneo PIM + Magento 2: Connector, Setup, and Integration Patterns appeared first on scandiweb.

If you are managing more than 1,000 SKUs across more than one sales channel, your own website, a marketplace, a wholesale portal, a print catalog, you have a product catalog management problem whether you call it that or not. The catch is that the cost of doing it badly is mostly invisible. Missed sales because the marketplace listing is stale, customer complaints because the size chart in the PDF does not match the website, support tickets because the warehouse SKU is wrong, all of it absorbed into general operating friction and never billed to a budget line.

Here is how scandiweb sets up product catalog management for clients. We are official partners with Pimcore and Akeneo, the two PIM platforms that show up in 80% of mid-market evaluations. We have shipped catalog migrations from 100 SKUs to 81,000+ SKUs. We have run the audit on enough catalogs to know which problems are real and which ones consultancies invent to sell more software.

Summary

• Product catalog management is the operational practice of standardizing product data across every channel where you sell. Below ~1,000 SKUs you can manage it in your eCommerce admin. Above ~5,000 SKUs and 2+ channels, you need a PIM (Product Information Management) system.
• The four PIM platforms worth seriously evaluating in 2026 are Pimcore, Akeneo, inRiver, and Plytix. Each fits a different size of business and integration shape, not a feature comparison decision.
• The single highest-ROI catalog discipline is enforcing unique, structured product descriptions (rather than reusing manufacturer copy) on the top revenue-generating 100 SKUs. The lift typically shows up in 60 to 90 days.

What is product catalog management?

Product catalog management is the operational practice of organizing, enriching, and syncing your product data so that the same product appears consistently, same name, same description, same images, same specifications, same pricing, across every sales channel where you sell. The discipline covers product information (the descriptive side), digital assets (images and video), pricing and inventory (the operational side), and channel syndication (the distribution side).

For small catalogs (under ~1,000 SKUs, 1 to 2 channels), this lives in your eCommerce platform’s admin. For mid-market catalogs (1,000 to 10,000 SKUs, 3+ channels), it usually needs a Product Information Management (PIM) system. For enterprise catalogs (10,000+ SKUs across multiple brands, markets, and languages), PIM plus Master Data Management plus Digital Asset Management becomes the standard stack.

Why product catalog management matters in eCommerce

Five operational costs of bad catalog management, in order of how often we see them on audits:

1. Wrong product attributes on marketplaces. Amazon and other marketplaces increasingly de-rank or de-list products with attribute mismatches. The cost is invisible until you check your marketplace traffic and find it has dropped 20% over six months.

2. Stale prices and stock levels across channels. Customer orders something that is out of stock, you cancel, customer leaves. The conversion-rate hit on the cancellation flow is much bigger than the lost order.

3. Duplicate or near-duplicate manufacturer descriptions. Hurts SEO on competitive SERPs where you compete against the same description on dozens of other sites. See our duplicate content and SEO guide for the full picture.

4. Internal teams maintaining the same data in multiple systems. Catalog, ERP, marketplace, print catalog, each system has its own copy, each goes out of sync over time, and the team manually reconciles.

5. Time-to-market for new products. Without a centralized PIM, launching a new SKU across 5 channels takes 5 separate workflows. With a PIM, the same launch is a single record update.

Key components of effective eCommerce catalog management

Product information and digital assets

The descriptive layer: names, descriptions, specifications, images, video, documentation. PIM systems centralize this layer so every channel pulls from one source. The single highest-leverage improvement most teams can make is enforcing a structured attribute schema (size, color, material, weight, dimensions, certifications) consistent across every SKU, so search and filter actually work.

Multi-channel syndication

The distribution layer: pushing the centralized product record to your eCommerce platform, marketplaces (Amazon, eBay), social commerce (Instagram Shop, TikTok Shop), Google Shopping feeds, print catalogs, and partner systems. Modern PIMs do this through pre-built channel connectors plus customizable feed templates. The integration work scales linearly with channel count.

Data quality and consistency

The governance layer: workflows for who can change what, approval gates before changes propagate to production, automated validation (no product without a primary image, no SKU without a price, no description under 50 words), and audit trails. Without governance, the PIM becomes another source of stale data instead of the cure for it.

Strategies for optimizing product catalog management

Standardize the attribute schema before the PIM tool choice

The most expensive PIM migration mistakes are caused by importing inconsistent attribute structures from legacy systems. Spend two weeks on attribute standardization (one schema across all product categories, no free-text where structured options exist, consistent units of measure) before touching a PIM evaluation. The platform choice matters much less than the discipline you import into it.

Enrich your top revenue SKUs first

The Pareto split holds on most catalogs: 80% of revenue from 20% of SKUs. Spend your enrichment budget on the top 100 SKUs first (unique descriptions, multiple images, video, structured specifications). Long-tail SKUs can stay on manufacturer descriptions or basic templating without meaningful revenue impact.

Personalize the catalog presentation, not the data

Personalization belongs in the presentation layer (recommendations, ranking, search results) rather than in the catalog itself. Keep one source of truth per product. Personalize how that product is shown per customer segment, not what the product record says. This separation makes the PIM scalable and the personalization auditable.

Choosing the right catalog management tool in 2026

Four PIM platforms dominate mid-market and enterprise evaluations. Honest comparison from scandiweb’s partner work with all four:

Pimcore

Open-source platform that combines PIM, Master Data Management, Digital Asset Management, and Customer Data Platform in one stack. Strongest fit for enterprises that want one platform to absorb multiple data domains and can fund implementation. scandiweb is an official Pimcore partner. We have shipped catalog migrations into Pimcore on B2B and complex multi-brand estates. Our Pimcore implementation service covers the standard rollout path.

Akeneo PIM

Focused PIM with strong Magento, Shopify, and BigCommerce connectors. Most common mid-market choice for B2C and B2B-light catalogs in the 5,000 to 50,000 SKU range. scandiweb is an official Akeneo partner. See our Akeneo + Magento 2 integration guide for the technical pattern we use on most projects.

inRiver PIM

Enterprise-focused PIM with strong manufacturing and distribution use cases. Best fit when your product data flows back to print catalogs, distributor systems, and trade portals in addition to your DTC channels.

Plytix PIM

Cloud-based PIM with strong ease-of-use and lower entry pricing than the enterprise alternatives. Best fit for small-to-mid market brands (1,000 to 10,000 SKUs) where speed of implementation outweighs feature depth.

How to pick the right PIM

Three questions that drive the decision more reliably than feature spreadsheets:

1. How many channels do you syndicate to? 2 to 3 channels: any PIM works. Consider Plytix or Akeneo. 5+ channels including B2B portals and marketplaces: Pimcore or inRiver.
2. How much non-product data lives alongside the catalog? If you also need to manage customer data, asset metadata, brand portals, and editorial content from the same platform, Pimcore is purpose-built for this. Otherwise a focused PIM (Akeneo, inRiver, Plytix) wins on simplicity.
3. What does your engineering team know? Pimcore is PHP/Symfony. Akeneo is PHP/Symfony. inRiver is .NET. Plytix is SaaS without backend code. Pick the platform your team or partner can support post-launch, not just the one that wins the demo.

Popular catalog management software options

Beyond the four above, the wider catalog management category includes Salsify (strong on syndication to retailers), Productsup (strong on marketplace feed management), Bluestone PIM, Contentserv, and the major eCommerce platforms’ native catalog tools (Shopify, BigCommerce, Adobe Commerce). For most mid-market merchants, the choice still narrows to Pimcore vs Akeneo. Our published Pimcore microservice case study documents how the platform absorbs catalog + commerce framework on a multi-brand vehicle sales operation.

Integrating catalog management with other eCommerce systems

Streamlining data flow with ERP, OMS, and eCommerce platforms

The standard PIM integration pattern: ERP is the system of record for SKU master data, cost, and stock. PIM is the system of record for product information, attributes, and assets. eCommerce platform and marketplaces are subscribers to both. Two-way sync (ERP and PIM) for the structured fields. One-way push (PIM to channels) for the descriptive fields. Get this topology right before any integration code, and the project ships on time. Platform-specific detail is on the Pimcore Magento integration, Magento Akeneo integration, and Shopify Salsify integration pages.

Improving customer experience through accurate catalog data

Catalog data quality shows up in the customer experience in three places: search and filter (broken if attribute schema is inconsistent), product comparison (impossible if specifications are unstructured), and rich snippets in SERPs (will not render if structured data is incomplete). The catalog discipline is the foundation. The customer-experience improvements are downstream effects.

How much does product catalog management cost in 2026?

PIM platform costs vary widely. Honest 2026 ranges:

• Plytix: from ~$1,000/month for entry tier. Scales by SKU count and channels.
• Akeneo Cloud: from ~$25,000/year for the SaaS edition. Community edition is free but requires self-hosting and meaningful engineering investment.
• Pimcore: open-source core is free. Commercial enterprise edition typically $30,000 to $100,000+/year depending on scope.
• inRiver: typically $50,000 to $200,000+/year for mid-market and enterprise deployments.

Implementation cost is typically 1 to 3× the annual platform cost in year one, dropping sharply in year two. The biggest cost variable is data-migration scope and channel integration count, not the platform fee. For projects that need both PIM + Akeneo deployment, see the standard Akeneo PIM implementation service scope.

Summary

Product catalog management is the operational discipline most eCommerce teams underinvest in until something breaks expensively. The fix is rarely the most expensive PIM in the evaluation. It is more often the platform that matches your team’s engineering capacity, your channel mix, and your data governance discipline. For most mid-market merchants between $5M and $200M revenue, Akeneo and Pimcore cover 80% of the realistic shortlist. Below that scale, Plytix is often the right answer. Above that scale, inRiver or Pimcore Enterprise enter the conversation.

About this guide

Maintained by the scandiweb commerce engineering team. Official Pimcore and Akeneo partner. We have shipped catalog management projects from 100 to 81,000+ SKUs across B2B, B2C, and multi-brand operations.

Frequently Asked Questions

What is product catalog management in 2026?

Product catalog management is the operational practice of standardizing product data, names, descriptions, specifications, images, pricing, across every channel where you sell. In 2026 the standard tool is a PIM (Product Information Management) system that centralizes the data and syndicates it to channels.

When does a business need a PIM system?

The two thresholds we use: above ~5,000 SKUs OR above ~3 sales channels. Below both thresholds, managing catalog in your eCommerce platform’s native admin is usually fine. Above either, the cost of bad catalog data starts to outweigh the cost of a PIM.

What is the difference between PIM and DAM?

PIM (Product Information Management) handles structured product data, attributes, specifications, descriptions, pricing. DAM (Digital Asset Management) handles unstructured digital files, images, video, documents, brand assets. Many platforms (Pimcore especially) combine both. For focused use cases the two are often separate systems.

How do I choose between Pimcore and Akeneo?

Pimcore if you also need to manage non-product data (customers, brand assets, editorial content) in the same platform, or if you operate across many product domains. Akeneo if you want a focused, easier-to-implement PIM and your existing eCommerce stack is Magento, Shopify, or BigCommerce.

What is the ROI of a PIM implementation?

Across scandiweb’s PIM projects the typical paybacks are: 20 to 40% reduction in time-to-market for new products, 15 to 30% reduction in support tickets related to product info errors, 5 to 15% revenue lift on marketplace channels from improved listing quality. Payback period typically 12 to 18 months.

Can ChatGPT or AI tools replace a PIM?

No. AI helps with generating descriptions, translating to multiple languages, and quality-checking attributes. The system of record problem (where does the canonical product data live) is not an AI problem. PIM + AI is the right pattern. AI without PIM creates more data sprawl, not less.

What does a catalog manager do?

The catalog manager owns product information governance: the attribute schema, the enrichment workflow for new products, the channel syndication rules, and the data quality monitoring. In smaller teams this role sits with the eCommerce manager. In mid-market and enterprise estates it is typically a dedicated role.

If you are evaluating Pimcore, Akeneo, or another PIM and want a 30-minute call with engineers who have implemented both on real client estates, scandiweb is an official Pimcore and Akeneo partner. Get in touch and we will walk through the platform fit for your catalog size, channel mix, and team.

The post Product Catalog Management in 2026: Tools, Strategies, and What Pimcore/Akeneo Partners Actually Use appeared first on scandiweb.

Scicon is the world’s leading manufacturer of bike bags—a pioneer in the cycling industry with a presence in over 40 countries. The brand is also the largest eyewear provider for the Tour de France teams in 2022.

scandiweb has been supporting Scicon since 2021 with an eCommerce Growth team. Currently, the company plans to fully optimize its eCommerce store. Part of the strategic roadmap we developed with them was upgrading their Magento (Adobe Commerce) platform and moving it to ReadyMage, improving their store’s page performance, and optimizing their product information management (PIM) system.

In this case study, we’ll focus on how we optimized their PIM setup.

Business needs

The client came to scandiweb with Akeneo PIM Community Edition already set up and several issues. The Akeneo connector they used was poorly built and failed to support important Akeneo PIM functionalities, including:

• URL synchronization through Akeneo and automatic redirect creation
• Image synchronization
• Category synchronization
• Product bulk action updates

With the client mostly interested in addressing the issues they were experiencing, our goal was to tackle their pain points and establish a solid synchronization between Akeneo PIM and the rest of their eCommerce ecosystem as well as to simplify the entire process for their internal team.

Approach and solution

The restrictions of the open-source Akeneo PIM edition, coupled with the troublesome connector the client used, posed several challenges when it came to resolving the synchronization issues and implementing custom functionalities. 

To address the synchronization issues and for us to have more control over the connector, we decided to replace the Webkul connector the client was using with our own solution—the scandiweb Akeneo PIM connector. 

scandiweb has been working with the Akeneo PIM since 2017, even before it had an official connector for Magento (Adobe Commerce). We like to be early adopters and go the extra mile to support our clients, so that’s what we did. We thoroughly mapped and leveraged Akeneo PIM’s functionalities to be able to customize them according to individual business needs. Our Akeneo PIM connector significantly extends Akeneo PIM’s functionalities and data exchange speed.

The custom scandiweb Akeneo PIM connector we used gave us much more freedom with custom solutions and allowed us to improve all the functionalities the client previously had issues with. 

With the client offering many different product types with diverse attributes, managing all of them for multiple store views was quite a complex process for them. But with the solution we implemented, we improved the attribute creation functionality and simplified the related processes for the client—significantly reducing the manual work involved in inputting product info and content in Magento (Adobe Commerce). 

Results

Scicon is now actively using Akeneo PIM for the creation of products, descriptions, attributes, and categories, as well as currency updates for multiple countries.

We successfully replaced the connector with the scandiweb Akeneo PIM connector and addressed all the previously identified issues, plus customizations. 

The following functionalities are seamlessly working now:

• URL synchronization through Akeneo and automatic redirect creation
• Image synchronization through Akeneo
• Category creation and synchronization through Akeneo
• Product bulk action updates
• Product attribute creation and management
• Overall data synchronization improvements & multiple daily backup configurations

With the client fully satisfied with our connector and custom solutions, they are interested in further custom Akeneo PIM improvements and process simplification for their internal team. And we are ready for the next steps to make that happen.

scandiweb is an award-winning Akeneo PIM partner. If you want even more reasons to build Akeneo PIM with us, read about our Akeneo PIM implementation program. Or get in touch with one of Akeneo PIM experts by sending us a message today.

The post Case Study: Seamless Synchronization and Custom Solutions with Akeneo PIM appeared first on scandiweb.

This is part four of the four-part crash course aiming to introduce teams and individuals to the Akeneo-Magento stack with a dedicated connector module. In a step-by-step manner, the guide allows to learn and get a practical experience with

• General set-up and basic entities,
• Data migration from Magento to Akeneo,
• Connector module functionality, import/export verification,
• Akeneo data manipulation using .csv files.

In this part, you will learn to modify/create new products, attributes, categories, etc. using .csv files and Akeneo import profiles. Additionally, you will find out how to use Akeneo’s export profiles to export data into a .csv file, edit it and then import it back into Akeneo.

Exporting Data

To gain a basic understanding, use Akeneo’s Category Export Profile, to export all categories into a .csv file:

You can export data by clicking on the export profile and clicking on the Export Now button.

Open Using Spreadsheet Software

Important: When we import data back into Akeneo, it will expect a .csv file in a specific format ( ; as a field separator, and " as a string delimiter). Some spreadsheet apps can’t export .csv in that format (e. g. Google Sheets), please avoid using those apps. (For the purposes of this guide we will be using Libre Office Writer.)

Open the exported .csv file using any spreadsheet app supporting the mentioned format.

Configure The Spreadsheet

The main thing you need to know is the Separator type (also known as Delimiter). In the case of Akeneo-exported .csv files, the delimiter is a semicolon ( ; ), and the string delimiter is a double quote( “ ):

Expected result: After opening the file, you should see something like this

Components of the export file

The top row is a header row, containing information about the fields. 

Since this is a category export, the fields are as follows:

• code – a unique identifier value for each category
• label(s) – category labels for each locale
• parent – a commonly used value referencing the parent category’s code.

CSV import

Editing and adding fields is covered in later sections of the current guide. For now, we will save the file and check if we can import it into Akeneo:

• Save the file and in Akeneo
• Go to Imports, choose the category imports profile and import into Akeneo:

Why Manipulate Data This Way

This may sometimes be a faster and simpler way of making changes, even though the option of bulk-editing products directly in Akeneo remains.  

For example, you need to increase all prices by 20%. All you have to do is export all products in a spreadsheet, apply a function to make changes, and then import back the modified file.

Or, perhaps, you need to write multiple translations for product descriptions. Doing it directly in Akeneo requires a lot of clicking: choose a product > select locale > update the values > save >select different locale etc. By using the .csv approach, you can make an export profile that only exports the fields you need, and have all the fields easily modifiable in the spreadsheet app.

Create New Categories

Open the exports tab in Akeneo and choose .csv Category Export Profile. In case none are available, create one.

Open the exported file in a spreadsheet app.

Scroll down and create a new category – that is a child of the master category. Call it  Test Category.

Add some sub-categories under the new test category.

All other categories can be removed from the file since they are not being modified. This is recommended in order to avoid importing old data (i.e., while you are working on the spreadsheet, someone else may modify a different set of categories; thus, your import may rewrite someone else’s newly added values).

Expected result: The spreadsheet should now look like this

From here you can save the file and import it back into Akeneo using a .csv Category Import Profile. When the import is complete, go to Settings > Categories and verify that the new categories are imported:

Create New Attribute

Export the attributes the same way as you did with categories in the section above. 

Open the exported file using the spreadsheet app. This time you will notice there are a lot more columns:

While most of these are optional, the required fields for a new attribute are:

• code
• group
• type

For the purposes of this guide, we will remove all columns in the file, leaving only the required ones, plus label-en_US. 

Additionally, remove all exported attributes, since we won’t be updating any of those.

The resulting file should now only contain the header row:

Add a new simple select test attribute, set the group to marketing, and set type to pim_catalog_simpleselect (for a list of available types, check Akeneo Documentation):

Save the file, and import it back into Akeneo, same as before – using the attribute import profile. When the import is complete, the new attribute can be found in Settings > Attributes: 

Add Attribute Options

In part 3 of this guide, we have covered adding simple select attributes. Now we will add some options to the attribute.

Go to Exports, and this time do a csv attribute option export.

Open the resulting file in your spreadsheet app.

Remove all rows except the header row.

Add three new options named ‘first’, ‘second’ and ‘third’.

In the ‘attribute’ column you have to reference the code of your test attribute: test_attribute.

Leave sort_order empty:

Save the file, and import it back into Akeneo. 

Expected result: The test attribute should now have the new options.

Working with Product Models and Products

So far we have covered some basic things you can do with .csv imports. This is important for learning, but, truth be told, in most cases doing things like adding categories and attribute options is faster and easier using Akeneo’s user interface.

In this section, we will take the next steps to further understand working with .csv exports.

Bulk Price Update Example:

In the Why Manipulate Data This Way section above we mentioned an example of using .csv exports to increase all product prices by 20%. This is what we’ll be doing in this section.

Same as previously, we need to export product data using Akeneo’s export profile. But first, let’s edit the profile settings to only export the fields we need. 

Open the export profile editor.

Go to the Content tab and set the product export conditions. The goal is to export all products with only one attribute: price.

When this is done, save the profile, export, and open it:

As you can see, some products have a price set, others are empty. This part boils down to your ability to use the spreadsheet app, and as we know those apps can do almost anything. You can take a look at this article for some pointers on how to increase all prices by using “Paste Special“ functionality.

Once the prices are updated, import them back into Akeneo and check the result.

Add New Product Model

Make a product model export, and open it in the spreadsheet app.

Out of the multiple columns available for product models only three are required:

• code (unique identifier);
• family_variant (code of the family variant – these codes can be viewed when exporting family variants);
• parent (a reference to product model – used when adding variants for a product model);

Other notable fields:

• categories (list of comma-separated category codes);
• name
• description-<locale_code>;
• variation_name-<locale_code>;
• price;

Let’s add a test product model. Edit the spreadsheet to only keep the required fields and the notable fields mentioned above.

Add the product model under one of the categories you have made earlier (sub_category_1).

Add some product variants. Because the family variant is clothing_color_size, you also need to provide a color attribute as it is required in the family variant:

Here, in the ‘color’ attribute, you must set a code referencing one of the options of the color attribute:

With this information you can fill the product model fields:

Save the spreadsheet, import it into Akeneo, and find the products in the product list.

Add New Product

Make a product export and open it in your spreadsheet app.

Products may have multiple attributes, but the fields required when creating a product are:

• sku;
• enabled (1 or 0, depending on whether the product will be active);
• family (a reference to a family code);
• parent (has to be set if it is a configurable product);

Let’s add some new products for our product model we created in the previous section.

As our model was a 2-axis product, we must reference a size attribute code as well:

Expected result: When you import this into Akeneo, you should see the new products:

Have you found this information helpful? Make sure to check out the rest of the guide: pt.1, pt.2, and pt.3. Do you consider implementing Akeneo PIM in your business? Let us help you! Any questions? Feel free to get in touch: book a free consultation or schedule a call!

The post Akeneo Crash Course, Pt.4: Data Handling via CSV Files appeared first on scandiweb.

This is part three of the four-part crash course aiming to introduce teams and individuals to the Akeneo-Magento stack with a dedicated connector module. In a step-by-step manner, the guide allows to learn and get a practical experience with

• General set-up and basic entities,
• Data migration from Magento to Akeneo,
• Connector module functionality, import/export verification,
• Akeneo data manipulation using .csv files.

In this part you will learn to create, move and delete products, attributes, and categories within an Akeneo-enabled Magento 2 store, using a dedicated connector module.

Note: To proceed with this guide, you will need a Magento 2 store connected with Akeneo PIM (see pt.1 of this guide for set-up instructions).

Test Attribute Imports

Add Attribute

In Akeneo go to Settings > Attributes and create a new Text attribute. 

Give it a code, assign it to a group and add a label. 

Save the attribute.

Run the attribute import command: bin/magento akeneoimport:attribute.

After the import is complete, in Magento, go to Stores > Attributes > Product and verify that the newly created attribute has been imported correctly.

Add Attribute to Product Family (Attribute Set)

In Akeneo open Settings > Families and select any family (e.g., Webcams). 

Add the newly created attribute. 

Save the family.

Run the attribute import command.

Expected result: In Magento, opening any product that belongs to the Webcam Attribute Set, you should see an empty field with the new attribute:

Delete Attribute

Go back to Akeneo and delete the attribute.

Run the attribute import command.

At the top of the command log, a message should appear signaling the attribute’s soft delete:

Now the ‘test’ attribute is marked for deletion. 

To delete it completely, go to Profile > Connector > Trash System, click View Attribute, and delete it from there.

Test Attribute Option Imports

Add Attribute

In Akeneo, go to Settings > Attributes and create a new Simple select attribute.

Give it a code, assign it to a group and add a label. 

Save the attribute.

Open the Options tab, add some options to the attribute, and save the attribute.

Add Attribute to Family

Go to Settings > Families, open a family and go to Attributes tab. 

Add the attribute to the family and save the attribute.

Import Attribute into Magento

From the Magento root folder, execute the following commands:

• bin/magento akeneoimport:attribute
• bin/magento akeneoimport:attribute-option

Expected result: In Magento, when you go to Stores > Attributes > Product, you should see that the new attribute is visible.

You can click it to reveal more information.

Additionally, when you open the category where the new attribute was added, and open any product, you should see a new field with the new attribute.

Delete Attribute Option

In Akeneo, go to Settings > Attributes , select an attribute, go to Options tab, and remove an option.

From the Magento root folder, execute the following command: bin/magento akeneoimport:attribute-option.

In the command log, a message should appear signaling the option’s soft delete:

Now the attribute option is marked for deletion. 

To delete it completely, go to Profile > Connector > Trash System, click View Attributes List, and delete the option.

Test Category Imports

Add Category

In Akeneo, open Settings > Categories, right-click on Master catalog and choose Create to add a new category.

In the Node Values section, give the category some labels, and Save.

Add Products to Category

Go to Products, choose one and in the Categories section, add the product to your new category.

Import Category

From the Magento root folder, execute the following commands:

• bin/magento akeneoimport:category
• bin/magento akeneoimport:product

Expected result: In Magento, when you open Products > Inventory > Category, you should see your new category.

The individual products that you add can now be found within the category. 

To check if the product was added to the category, go to Product Details.

Move Category

In Akeneo, go to Settings > Categories and drag our new category under a different parent.

Run the category import command: bin/magento akeneoimport:category.

Expected result: In Magento, check Products > Inventory > Categories – the category should have moved to the new location:

Delete Category

In Akeneo, go back to Settings > Categories. 

Open your category and delete it.

Run the category import command:bin/magento akeneoimport:category.

In the command log, a message should appear signaling the category is marked for deletion:

To delete it completely, go to ‘Profile’ > ‘Connector’ > Trash System, and delete it from there.

Test Product Imports

Add Simple Product

In Akeneo, go to Products and create a new product.

Enter a SKU and select a Product Family. 

Fill all the required fields (Name, Price, etc.) and optionally populate some of the other fields. Make sure that the product completeness is 100.

Don’t forget to switch to German and French locales and populate all the required locale-specific fields.

Open the Categories section and select at least one category.

Add Configurable Product

In the Products page, create a new product, but this time, instead of Product, choose Product model.

Give the product a Code, choose a Family and Variant.

Same as for the Simple Product, fill all the required fields. 

Add some product variants:

Make sure the Completion is 100 for all locales.

Open the Categories section and select at least one category.

Import New Products into Magento

From the Magento root folder, execute the following command: bin/mangento akeneoimport:product.

In Magento, open Products > Inventory > Catalog and verify that the new simple product was imported successfully, and that attribute values are correct for each locale.

For the configurable product, you should see something like this:

The main Configurable Product and a Simple Product for each Variant.

Same as for the simple product, you can verify that all attribute values were set correctly for each locale.

Test Product Deletion

From the Magento root directory execute the command: bin/magento akeneoimport:product-deletion

If everything worked correctly, then you should see no products getting soft deleted.

You can test it further by deleting a product in Akeneo and running the akeneoimport:product-deletion command again. This should produce the following result:

Have you found this information helpful? Make sure to check out the rest of the guide: pt.1, pt.2, and pt.4. Do you consider implementing Akeneo PIM in your business? Let us help you! Any questions? Feel free to get in touch: book a free consultation or schedule a call!

Related articles:

Magento Series: Working with Product Attributes

The post Akeneo Crash Course, Pt.3: Connector Functionality appeared first on scandiweb.

This is part two of the four-part crash course aiming to introduce teams and individuals to the Akeneo-Magento stack with a dedicated connector module. In a step-by-step manner, the guide allows to learn and get a practical experience with

• General set-up and basic entities,
• Data migration from Magento to Akeneo,
• Connector module functionality, import/export verification,
• Akeneo data manipulation using .csv files.

In this part, you will learn to transfer data between Akeneo and Magento using default import/export functionality.

Note: Before proceeding, make sure you have completed pt.1 of the current guide.

In Akeneo, set up some products with 100% completion.

Import them into Magento: bin/magento akeneoimport:product.

Reset Akeneo:

Open terminal in Akeneo root directory.

Remove all Akeneo containers: docker-compose down.

Start a fresh Akeneo: make prod.

Make a new Akeneo admin user (user: admin, password: admin):

docker-compose run --rm php php bin/console pim:user:create admin admin support@example.com Admin Admin en_US --admin -n --env=prod

Run the job daemon:

docker-compose run --rm php php bin/console akeneo:batch:job-queue-consumer-daemon

Export data from Magento:

Execute Magento import commands:

• bin/magento akeneoexport:attribute
• bin/magento akeneoexport:category
• bin/magento akeneoexport:config
• bin/magento akeneoexport:product

To find folders with CSV exports, go to <M2 root>/var/akeneo/export.

Import data into Akeneo:

The exports directory contains the following folders:

• attribute_groups  
• attribute_options  
• attributes  
• category  
• channels  
• currency  
• family  
• family_variant  
• locales  
• product  
• product_model

For each of these, you need to create an import file.

• To do it manually in Akeneo, go to 
  • Imports > create import profile 
• To do it by running a SQL query: from Akeneo root directory, log into MySQL
  • docker-compose exec mysql mysql -u akeneo_pim -pakeneo_pim
  • And execute the following query:

USE akeneo_pim; INSERT INTO `akeneo_batch_job_instance` (`code`, `label`, `job_name`, `status`, `connector`, `raw_parameters`, `type`) VALUES 
('csv_product_import', 'Demo CSV product import', 'csv_product_import', '0', 'Akeneo CSV Connector', 'a:17:{s:8:\"filePath\";s:16:\"/tmp/product.csv\";s:9:\"delimiter\";s:1:\";\";s:9:\"enclosure\";s:1:\"\"\";s:6:\"escape\";s:1:\"\\\";s:10:\"withHeader\";b:1;s:13:\"uploadAllowed\";b:1;s:25:\"invalid_items_file_format\";s:3:\"csv\";s:14:\"user_to_notify\";N;s:21:\"is_user_authenticated\";b:0;s:16:\"decimalSeparator\";s:1:\".\";s:10:\"dateFormat\";s:10:\"yyyy-MM-dd\";s:7:\"enabled\";b:1;s:16:\"categoriesColumn\";s:10:\"categories\";s:12:\"familyColumn\";s:6:\"family\";s:12:\"groupsColumn\";s:6:\"groups\";s:17:\"enabledComparison\";b:1;s:18:\"realTimeVersioning\";b:1;}', 'import'), 
('csv_product_model_import', 'Demo CSV product model import', 'csv_product_model_import', '0', 'Akeneo CSV Connector', 'a:16:{s:8:\"filePath\";s:22:\"/tmp/product_model.csv\";s:9:\"delimiter\";s:1:\";\";s:9:\"enclosure\";s:1:\"\"\";s:6:\"escape\";s:1:\"\\\";s:10:\"withHeader\";b:1;s:13:\"uploadAllowed\";b:1;s:25:\"invalid_items_file_format\";s:3:\"csv\";s:14:\"user_to_notify\";N;s:21:\"is_user_authenticated\";b:0;s:16:\"decimalSeparator\";s:1:\".\";s:10:\"dateFormat\";s:10:\"yyyy-MM-dd\";s:7:\"enabled\";b:1;s:16:\"categoriesColumn\";s:10:\"categories\";s:19:\"familyVariantColumn\";s:13:\"familyVariant\";s:17:\"enabledComparison\";b:1;s:18:\"realTimeVersioning\";b:1;}', 'import'), 
('csv_product_export', 'Demo CSV product export', 'csv_product_export', '0', 'Akeneo CSV Connector', 'a:10:{s:8:\"filePath\";s:38:\"/tmp/export_%job_label%_%datetime%.csv\";s:9:\"delimiter\";s:1:\";\";s:9:\"enclosure\";s:1:\"\"\";s:10:\"withHeader\";b:1;s:14:\"user_to_notify\";N;s:21:\"is_user_authenticated\";b:0;s:16:\"decimalSeparator\";s:1:\".\";s:10:\"dateFormat\";s:10:\"yyyy-MM-dd\";s:10:\"with_media\";b:1;s:7:\"filters\";a:2:{s:4:\"data\";a:3:{i:0;a:3:{s:5:\"field\";s:7:\"enabled\";s:8:\"operator\";s:1:\"=\";s:5:\"value\";b:1;}i:1;a:3:{s:5:\"field\";s:10:\"categories\";s:8:\"operator\";s:11:\"IN CHILDREN\";s:5:\"value\";a:1:{i:0;s:6:\"master\";}}i:2;a:4:{s:5:\"field\";s:12:\"completeness\";s:8:\"operator\";s:2:\">=\";s:5:\"value\";i:100;s:7:\"context\";a:1:{s:7:\"locales\";a:3:{i:0;s:5:\"fr_FR\";i:1;s:5:\"en_US\";i:2;s:5:\"de_DE\";}}}}s:9:\"structure\";a:2:{s:5:\"scope\";s:6:\"mobile\";s:7:\"locales\";a:3:{i:0;s:5:\"fr_FR\";i:1;s:5:\"en_US\";i:2;s:5:\"de_DE\";}}}}', 'export'), 
('csv_product_model_export', 'Demo CSV product model export', 'csv_product_model_export', '0', 'Akeneo CSV Connector', 'a:10:{s:8:\"filePath\";s:38:\"/tmp/export_%job_label%_%datetime%.csv\";s:9:\"delimiter\";s:1:\";\";s:9:\"enclosure\";s:1:\"\"\";s:10:\"withHeader\";b:1;s:14:\"user_to_notify\";N;s:21:\"is_user_authenticated\";b:0;s:16:\"decimalSeparator\";s:1:\".\";s:10:\"dateFormat\";s:10:\"yyyy-MM-dd\";s:10:\"with_media\";b:1;s:7:\"filters\";a:2:{s:4:\"data\";a:0:{}s:9:\"structure\";a:2:{s:5:\"scope\";s:6:\"mobile\";s:7:\"locales\";a:3:{i:0;s:5:\"fr_FR\";i:1;s:5:\"en_US\";i:2;s:5:\"de_DE\";}}}}', 'export'), 
('csv_category_import', 'Demo CSV category import', 'csv_category_import', '0', 'Akeneo CSV Connector', 'a:9:{s:8:\"filePath\";s:17:\"/tmp/category.csv\";s:9:\"delimiter\";s:1:\";\";s:9:\"enclosure\";s:1:\"\"\";s:6:\"escape\";s:1:\"\\\";s:10:\"withHeader\";b:1;s:13:\"uploadAllowed\";b:1;s:25:\"invalid_items_file_format\";s:3:\"csv\";s:14:\"user_to_notify\";N;s:21:\"is_user_authenticated\";b:0;}', 'import'), 
('csv_category_export', 'Demo CSV category export', 'csv_category_export', '0', 'Akeneo CSV Connector', 'a:6:{s:8:\"filePath\";s:17:\"/tmp/category.csv\";s:9:\"delimiter\";s:1:\";\";s:9:\"enclosure\";s:1:\"\"\";s:10:\"withHeader\";b:1;s:14:\"user_to_notify\";N;s:21:\"is_user_authenticated\";b:0;}', 'export'), 
('csv_association_type_import', 'Demo CSV association type import', 'csv_association_type_import', '0', 'Akeneo CSV Connector', 'a:9:{s:8:\"filePath\";s:25:\"/tmp/association_type.csv\";s:9:\"delimiter\";s:1:\";\";s:9:\"enclosure\";s:1:\"\"\";s:6:\"escape\";s:1:\"\\\";s:10:\"withHeader\";b:1;s:13:\"uploadAllowed\";b:1;s:25:\"invalid_items_file_format\";s:3:\"csv\";s:14:\"user_to_notify\";N;s:21:\"is_user_authenticated\";b:0;}', 'import'), 
('csv_association_type_export', 'Demo CSV association type export', 'csv_association_type_export', '0', 'Akeneo CSV Connector', 'a:6:{s:8:\"filePath\";s:25:\"/tmp/association_type.csv\";s:9:\"delimiter\";s:1:\";\";s:9:\"enclosure\";s:1:\"\"\";s:10:\"withHeader\";b:1;s:14:\"user_to_notify\";N;s:21:\"is_user_authenticated\";b:0;}', 'export'), 
('csv_attribute_import', 'Demo CSV attribute import', 'csv_attribute_import', '0', 'Akeneo CSV Connector', 'a:9:{s:8:\"filePath\";s:18:\"/tmp/attribute.csv\";s:9:\"delimiter\";s:1:\";\";s:9:\"enclosure\";s:1:\"\"\";s:6:\"escape\";s:1:\"\\\";s:10:\"withHeader\";b:1;s:13:\"uploadAllowed\";b:1;s:25:\"invalid_items_file_format\";s:3:\"csv\";s:14:\"user_to_notify\";N;s:21:\"is_user_authenticated\";b:0;}', 'import'), 
('csv_attribute_export', 'Demo CSV attribute export', 'csv_attribute_export', '0', 'Akeneo CSV Connector', 'a:6:{s:8:\"filePath\";s:18:\"/tmp/attribute.csv\";s:9:\"delimiter\";s:1:\";\";s:9:\"enclosure\";s:1:\"\"\";s:10:\"withHeader\";b:1;s:14:\"user_to_notify\";N;s:21:\"is_user_authenticated\";b:0;}', 'export'), 
('csv_attribute_option_import', 'Demo CSV option import', 'csv_attribute_option_import', '0', 'Akeneo CSV Connector', 'a:9:{s:8:\"filePath\";s:15:\"/tmp/option.csv\";s:9:\"delimiter\";s:1:\";\";s:9:\"enclosure\";s:1:\"\"\";s:6:\"escape\";s:1:\"\\\";s:10:\"withHeader\";b:1;s:13:\"uploadAllowed\";b:1;s:25:\"invalid_items_file_format\";s:3:\"csv\";s:14:\"user_to_notify\";N;s:21:\"is_user_authenticated\";b:0;}', 'import'), 
('csv_family_import', 'Demo CSV family import', 'csv_family_import', '0', 'Akeneo CSV Connector', 'a:9:{s:8:\"filePath\";s:15:\"/tmp/family.csv\";s:9:\"delimiter\";s:1:\";\";s:9:\"enclosure\";s:1:\"\"\";s:6:\"escape\";s:1:\"\\\";s:10:\"withHeader\";b:1;s:13:\"uploadAllowed\";b:1;s:25:\"invalid_items_file_format\";s:3:\"csv\";s:14:\"user_to_notify\";N;s:21:\"is_user_authenticated\";b:0;}', 'import'), 
('csv_family_variant_import', 'Demo CSV family variant import', 'csv_family_variant_import', '0', 'Akeneo CSV Connector', 'a:9:{s:8:\"filePath\";s:23:\"/tmp/family_variant.csv\";s:9:\"delimiter\";s:1:\";\";s:9:\"enclosure\";s:1:\"\"\";s:6:\"escape\";s:1:\"\\\";s:10:\"withHeader\";b:1;s:13:\"uploadAllowed\";b:1;s:25:\"invalid_items_file_format\";s:3:\"csv\";s:14:\"user_to_notify\";N;s:21:\"is_user_authenticated\";b:0;}', 'import'), 
('csv_attribute_option_export', 'Demo CSV option export', 'csv_attribute_option_export', '0', 'Akeneo CSV Connector', 'a:6:{s:8:\"filePath\";s:15:\"/tmp/option.csv\";s:9:\"delimiter\";s:1:\";\";s:9:\"enclosure\";s:1:\"\"\";s:10:\"withHeader\";b:1;s:14:\"user_to_notify\";N;s:21:\"is_user_authenticated\";b:0;}', 'export'), 
('csv_product_quick_export2', 'CSV product quick export', 'csv_product_quick_export', '0', 'Akeneo CSV Connector', 'a:14:{s:8:\"filePath\";s:38:\"/tmp/export_%job_label%_%datetime%.csv\";s:9:\"delimiter\";s:1:\";\";s:9:\"enclosure\";s:1:\"\"\";s:10:\"withHeader\";b:1;s:14:\"user_to_notify\";N;s:21:\"is_user_authenticated\";b:0;s:7:\"filters\";N;s:19:\"selected_properties\";N;s:10:\"with_media\";b:1;s:6:\"locale\";N;s:5:\"scope\";N;s:9:\"ui_locale\";N;s:15:\"filePathProduct\";s:54:\"/tmp/1_products_export_%locale%_%scope%_%datetime%.csv\";s:20:\"filePathProductModel\";s:60:\"/tmp/2_product_models_export_%locale%_%scope%_%datetime%.csv\";}', 'quick_export'), 
('csv_product_grid_context_quick_export2', 'CSV product quick export grid context', 'csv_product_grid_context_quick_export', '0', 'Akeneo CSV Connector', 'a:14:{s:8:\"filePath\";s:38:\"/tmp/export_%job_label%_%datetime%.csv\";s:9:\"delimiter\";s:1:\";\";s:9:\"enclosure\";s:1:\"\"\";s:10:\"withHeader\";b:1;s:14:\"user_to_notify\";N;s:21:\"is_user_authenticated\";b:0;s:7:\"filters\";N;s:19:\"selected_properties\";N;s:10:\"with_media\";b:1;s:6:\"locale\";N;s:5:\"scope\";N;s:9:\"ui_locale\";N;s:15:\"filePathProduct\";s:67:\"/tmp/1_products_export_grid_context_%locale%_%scope%_%datetime%.csv\";s:20:\"filePathProductModel\";s:73:\"/tmp/2_product_models_export_grid_context_%locale%_%scope%_%datetime%.csv\";}', 'quick_export'), 
('csv_family_export', 'Demo CSV family export', 'csv_family_export', '0', 'Akeneo CSV Connector', 'a:6:{s:8:\"filePath\";s:15:\"/tmp/family.csv\";s:9:\"delimiter\";s:1:\";\";s:9:\"enclosure\";s:1:\"\"\";s:10:\"withHeader\";b:1;s:14:\"user_to_notify\";N;s:21:\"is_user_authenticated\";b:0;}', 'export'), 
('csv_family_variant_export', 'Demo CSV family variant export', 'csv_family_variant_export', '0', 'Akeneo CSV Connector', 'a:6:{s:8:\"filePath\";s:23:\"/tmp/family_variant.csv\";s:9:\"delimiter\";s:1:\";\";s:9:\"enclosure\";s:1:\"\"\";s:10:\"withHeader\";b:1;s:14:\"user_to_notify\";N;s:21:\"is_user_authenticated\";b:0;}', 'export'), 
('csv_channel_export', 'Demo CSV channel export', 'csv_channel_export', '0', 'Akeneo CSV Connector', 'a:6:{s:8:\"filePath\";s:38:\"/tmp/export_%job_label%_%datetime%.csv\";s:9:\"delimiter\";s:1:\";\";s:9:\"enclosure\";s:1:\"\"\";s:10:\"withHeader\";b:1;s:14:\"user_to_notify\";N;s:21:\"is_user_authenticated\";b:0;}', 'export'), 
('csv_currency_export', 'Demo CSV currency export', 'csv_currency_export', '0', 'Akeneo CSV Connector', 'a:6:{s:8:\"filePath\";s:38:\"/tmp/export_%job_label%_%datetime%.csv\";s:9:\"delimiter\";s:1:\";\";s:9:\"enclosure\";s:1:\"\"\";s:10:\"withHeader\";b:1;s:14:\"user_to_notify\";N;s:21:\"is_user_authenticated\";b:0;}', 'export'), 
('csv_locale_export', 'Demo CSV locale export', 'csv_locale_export', '0', 'Akeneo CSV Connector', 'a:6:{s:8:\"filePath\";s:38:\"/tmp/export_%job_label%_%datetime%.csv\";s:9:\"delimiter\";s:1:\";\";s:9:\"enclosure\";s:1:\"\"\";s:10:\"withHeader\";b:1;s:14:\"user_to_notify\";N;s:21:\"is_user_authenticated\";b:0;}', 'export'), 
('csv_attribute_group_export', 'Demo CSV attribute group export', 'csv_attribute_group_export', '0', 'Akeneo CSV Connector', 'a:6:{s:8:\"filePath\";s:38:\"/tmp/export_%job_label%_%datetime%.csv\";s:9:\"delimiter\";s:1:\";\";s:9:\"enclosure\";s:1:\"\"\";s:10:\"withHeader\";b:1;s:14:\"user_to_notify\";N;s:21:\"is_user_authenticated\";b:0;}', 'export'), 
('csv_currency_import', 'Demo CSV currency import', 'csv_currency_import', '0', 'Akeneo CSV Connector', 'a:9:{s:8:\"filePath\";N;s:9:\"delimiter\";s:1:\";\";s:9:\"enclosure\";s:1:\"\"\";s:6:\"escape\";s:1:\"\\\";s:10:\"withHeader\";b:1;s:13:\"uploadAllowed\";b:1;s:25:\"invalid_items_file_format\";s:3:\"csv\";s:14:\"user_to_notify\";N;s:21:\"is_user_authenticated\";b:0;}', 'import'), 
('csv_channel_import', 'Demo CSV channel import', 'csv_channel_import', '0', 'Akeneo CSV Connector', 'a:9:{s:8:\"filePath\";N;s:9:\"delimiter\";s:1:\";\";s:9:\"enclosure\";s:1:\"\"\";s:6:\"escape\";s:1:\"\\\";s:10:\"withHeader\";b:1;s:13:\"uploadAllowed\";b:1;s:25:\"invalid_items_file_format\";s:3:\"csv\";s:14:\"user_to_notify\";N;s:21:\"is_user_authenticated\";b:0;}', 'import'), 
('csv_locale_import', 'Demo CSV locale import', 'csv_locale_import', '0', 'Akeneo CSV Connector', 'a:9:{s:8:\"filePath\";N;s:9:\"delimiter\";s:1:\";\";s:9:\"enclosure\";s:1:\"\"\";s:6:\"escape\";s:1:\"\\\";s:10:\"withHeader\";b:1;s:13:\"uploadAllowed\";b:1;s:25:\"invalid_items_file_format\";s:3:\"csv\";s:14:\"user_to_notify\";N;s:21:\"is_user_authenticated\";b:0;}', 'import'), 
('csv_attribute_group_import', 'Demo CSV attribute_group import', 'csv_attribute_group_import', '0', 'Akeneo CSV Connector', 'a:9:{s:8:\"filePath\";N;s:9:\"delimiter\";s:1:\";\";s:9:\"enclosure\";s:1:\"\"\";s:6:\"escape\";s:1:\"\\\";s:10:\"withHeader\";b:1;s:13:\"uploadAllowed\";b:1;s:25:\"invalid_items_file_format\";s:3:\"csv\";s:14:\"user_to_notify\";N;s:21:\"is_user_authenticated\";b:0;}', 'import');

Expected result: After adding the profiles, your imports page should look similar to this:

Now you can start importing data from your exports. You must however do it in a specific order:

1. currency
2. locales
3. category
4. channels
5. attribute_groups
6. attributes
7. attribute_options
8. family
9. family_variant
10. product_model
11. product

Select the  appropriate import profile (i.e. for Currency select Demo CSV currency import) and upload the .csv file from your exports folder (for Currency – <M2 root>/var/akeneo/export/currency/<currencyexport>.csv).

When all is imported, open the products section, mass-select all products, and set the price attribute. 

Connect Akeneo with Magento:

In Akeneo open System > Connections and create a new connection, setting the flow type as Data Destination.

After creating the connection, in Magento go to ‘Profile’ > ‘Connector’ > Configuration, and fill in the new credentials.

Clear Magento cache and test the connection.

Verify That All Products Were Imported Correctly

Follow the steps listed under the section Test Product Deletion in pt. 3 of this guide.

Have you found this information helpful? Make sure to check out the rest of the guide: pt.1, pt.3, and pt.4. Do you consider implementing Akeneo PIM in your business? Let us help you! Any questions? Feel free to get in touch: book a free consultation or schedule a call!

The post Akeneo Crash Course, Pt.2: Magento Data Export appeared first on scandiweb.

Knowledge transfer is critical when trying to master new complex tools within a limited time. Such was the case when a few of our staff needed a fast-track introduction to the Akeneo-Magento stack with a dedicated connector module, to take over a live project. This need manifested in developing a set of internal documentation pages, and later became the prerequisite for creating this guide.

This is part one of the four-part crash course, meant to help teams and individuals gain an understanding of basic entities, tools, and processes involved in operating the tech stack mentioned above. Follow through in a step-by-step manner to learn and get practical experience with:

• General set-up and basic entities,
• Data migration from Magento to Akeneo,
• Connector module functionality, import/export verification,
• Akeneo data manipulation using .csv files.

Notes: 

The current guide is based on a real-life Magento project, making use of our own proprietary Magento-Akeneo connector module. Thus, certain project-specific details had to be generalized in order to present more universal instruction. An example of this is a mentioning of a path starting with “Profile > Connector > …”, where ‘Profile’ refers to your Magento profile, and ‘Connector’ – to the connector module you are using.

As for the connector module, a quick search around the Internet should present you with multiple options to choose from. Pick the one you prefer, and follow along.

In this part, you will learn how to set up clean Akeneo and Magento instances, as well as sync some of the default entities.

Magento 2 Setup

1. Set up Magento 2.1 (Community) locally without sample data.
2. Install Magento-Akeneo connector module.

Note: Ensure version compatibility between Magento and the Magento-Akeneo connector.

The command to install clean DB with admin user:

php bin/magento setup:install --base-url=http://example-project.host/ \
--db-host=127.0.0.1 --db-name=test_example-project --db-user=root --db-password=root \
--admin-firstname=exampleName --admin-lastname=exampleLastname --admin-email=test@example.com\
--admin-user=exampleUser --admin-password=examplePassword --language=en_US \
--currency=USD --timezone=America/Chicago --use-rewrites=1

Akeneo Setup

Make sure Docker is installed and running locally.

Use Akeneo Community Edition Docker version setup guide (not manual): https://docs.akeneo.com/4.0/install_pim/docker/installation_docker.html.

Use make dev to import Akeneo sample data.

Execute the necessary command from the guide above to launch a consumer daemon.

Expected result: You should have a working instance of Akeneo PIM with a URL http://127.0.0.1:8080/  and credentials: admin/admin.

Connect M2 and Akeneo

Create Akeneo API access to allow using it from M2.

Enter this API access in M2 under ‘Profile’ > ‘Connector’ > Configuration -> API Configurations. Save the configuration, and click “Test Connection”.

In the General section, set the channel to “Ecommerce”.

Note: Akeneo has a case-sensitive Akeneo channel code.

Akeneo Connection Guide: https://help.akeneo.com/pim/serenity/articles/what-is-a-connection.html

Akeneo Sample Data Fix

Remove attribute “collection” from Akeneo.

Quick guide: https://webkul.com/blog/how-to-create-attributes-in-akeneo/

Execute M2 Import Commands

• php bin/magento akeneoimport:attribute
• php bin/magento akeneoimport:attribute-option
• php bin/magento akeneoimport:category
• php bin/magento akeneoimport:product

To monitor the process, check import logs: ‘Profile’ > ‘Connector’ > Import logs.

Expected result: Once the import is complete, the following should be created and imported from the Akeneo sample data:

• products
• categories 
• attributes
• attribute options
• attribute sets
• attribute groups

Fix Akeneo Products Completeness

Find which attributes are required and, using bulk update, fill them for all products. 100% on more than 500 products should be enough. 

Try importing products back into Akeneo.

Akeneo completeness guide: https://help.akeneo.com/pim/v4/articles/what-is-the-completeness.html

Akeneo bulk action guide: https://help.akeneo.com/pim/v4/articles/product-mass-actions.html

Important: Bulk update requires a running queue job daemon.

Example:

Previously there were 34 simple and 15 configurable products, now there should be 829 simple and 20 configurable.

Create New TEXT Attribute

Create a new Akeneo Group “Test_group”.

Under “Test_group” create a new Akeneo Text Attribute “Report” with “Value per locale” enabled.

Under the Family “Camcorders” add an attribute “Report”, and make it required for all channels.

Find all “Camcorders” products and fill in the “Report” attribute.

Repeat products import into M2 and check if Magento products received this value:

• It will throw an error that the attribute is missing. 
• Execute the attribute import, clean the M2 cache, and then execute the product import.

Akeneo Attributes Guide: https://help.akeneo.com/pim/serenity/articles/manage-your-attributes.html

Akeneo Attribute Groups Guide: https://help.akeneo.com/pim/serenity/articles/manage-your-attribute-groups.html

Akeneo Families Guide: https://help.akeneo.com/pim/serenity/articles/manage-your-families.html

Create New DROPDOWN Attribute

Under the “Test_group“ create a new Akeneo Dropdown Attribute “Version” with option codes “21“, “22“, “23“ and labels “Magento 2.1“, “Magento 2.2.“, “Magento 2.3“.

Add the “Version” attribute to the Family “Digital Cameras” and make sure it is required for all channels.

Choose ONE “Digital Cameras” product and fill ALL required attributes.

Repeat attributes import and attributes options import

• Clear cache
• Import products into M2
• Check if Magento products received this value.  

Find this product in Magento and check if “Version“ was correctly imported.

Create New Family With Family Variant

Create the new Akeneo Family “T-Shirt“.

Assign attributes “price”, “name”, “description”, “color”, “size”.

Create 1-axis Family Variant “T-Shirt Basic“ with color and size as “configurable” attributes.

Make “name“ editable on the parent product level, and “description” – on the child product level.

Create a new Product Model with a Family Variant “T-Shirt Basic“.

Fill description.

Create a new child product with Size: L and Color: Black, and another with Size: M and Color: Red.

Fill name that contains a specific product size and color.

Add the product to some random categories.

Repeat attributes import

• Clear cache
• Import products into M2
• Check if these products appeared in Magento as configurable.

Important: Each product needs to be added to some category, otherwise, it will be skipped during the import to M2.

Akeneo Product Creation Guide: https://help.akeneo.com/pim/serenity/articles/create-a-product.html

Akeneo Add Variant Guide: https://help.akeneo.com/pim/serenity/articles/enrich-products-variants.html#add-a-variant

Create New FR and DE Magento Stores

Set up base settings:

In Magento go to Stores > Configuration and select Main website as the store view.

Go to General > Currency setup and set Allowed Currencies to EUR and USD.

Create and configure two new store views:

Go to Stores > All Stores and create two new store views: one for France and one for Germany.

Go back to Stores > Configuration and select French store as store view.

Under Locale Options, set the store view’s Locale to French(France).

Open General > Currency Setup and set the Default Display Currency to EUR.

Repeat the steps for the German view, except set the locale to German(Germany).

Set up product-locale-specific data in the Akeneo:

Open the Products section in Akeneo and set the locale to French.

Same as in the “Fix products completeness” section above – using bulk actions, set product descriptions and prices.

Important: Bulk update requires a running queue job daemon.

Switch the locale to German and repeat the previous step.

Import into Magento:

Run bin\magento akeneoimport:product.

Clear Magento Cache.

Expected result:

• When opening a product in edit mode and switching between the newly created store views: you should see that product descriptions change accordingly.
• When switching to FR / DE store views in the front-end: currency should change from  USD to EUR. Changes should also occur in product descriptions and category names in the navigation bar.

Note: If you don’t see any products displayed on frontend, go to Stores > Configuration > Catalog > Inventory > Stock Options and set Display out of stock items to true.

Have you found this information helpful? Make sure to check out the rest of the guide: pt.2, pt.3, and pt.4. Do you consider implementing Akeneo PIM in your business? Let us help you! Any questions? Feel free to get in touch: book a free consultation or schedule a call!

The post Akeneo Crash Course, Pt.1: Basic Setup appeared first on scandiweb.

We’re delighted and honored to announce that Scandiweb has been awarded among TOP 3 Akeneo PIM implementations in the world at APS Akeneo summit 2020! The name of the nomination is “Rising Star”, and it applies to the first Akeneo projects launched by official Akeneo partners.

This year we competed against 50+ agencies from around the globe, and the project that got us to the frontline was technodom.kz – a large home electronics retailer, whose eCommerce store we rebuilt and re-platformed to Akeneo in 2019.

Project recap

The project was a complex build, involving migration and reengineering of the client’s existing e-store. The resource was migrated from Hybris to Magento with PWA, relying heavily on Akeneo PIM. We’ve documented the process in detail in a dedicated case study, so for the current scope let’s go over a handful of the project’s key highlights for reference:

• 120 000 SKU’s
• 15 000 attributes
• 3000 new products per month
• 84 physical stores
• $800M overall annual gross – $100M online revenue

Given the scale and complexity, the Akeneo PIM Enterprise edition was the tool employed to manage all the stock and price information, and it handled the task remarkably well!

Implementation highlights include:

• Brand new API data bridge between Akeneo and Magento 2 – heavily optimized performance & speed.
• Delta sync functionality allowing to sync only data which have had changes since
  the last sync.
• Custom attributes allowing to define category SEO meta title and description
  within Akeneo.
• Custom attributes supporting business functionality e.g. marking products having specific delivery logic.

Results/improvements (spoiler – it’s stunning):

• 3x faster data turnaround to production.
• Immediate minor data change sync.
• Automatic quality & completion validation depending on the product family.
• Designed and introduced multiple Data team roles defining necessary access rights.
• Any updates are logged and can be traced to a specific user, timestamp, and change itself.
• No manual work between systems. New products are synced from 1C to Akeneo automatically. Completed products are included in the sync automatically.
• Centralized system! Single source of truth. No spreadsheets.
• Various data sync options – full or delta product, specific family, a separate category, attribute, and product sync.

The award

Akeneo PIM is still a relatively new product, however, it’s already sending ripples through the eCommerce industry. Their annual partners-only summits reflect the dynamic, hosting a growing array of projects and brands from across the world. 

Don’t miss the full highlights report of the summit, sharing insights into this year’s agenda, and announcing the winners!

2020 was the first year Scandiweb participated in the contest, and it fell into place nicely: 

• In 2019 Scandiweb received official Akeneo training.
• The same year, we launched technodom.kz, incorporating Akeneo PIM as one of the core elements.
• Shortly after the Go-live, an Akeneo newsletter announced a competition for the best implementation.

So, we didn’t think twice to apply.

The result? Our work was thoroughly evaluated and our effort was recognized as one of the world’s top Akeneo PIM implementations of 2019. Very much appreciated, this award is a truly great addition to Scandiweb’s legacy and an immense motivation for our future accomplishments.

Big thanks to the Akeneo team for their great work, to the contest jury for the acknowledgment, to Technodom for entrusting us with the project, and to the Scandiweb team for making it a reality!

Curious to learn more about the project that got us the award? Read the full story and discover the challenges, the solutions, and the impact of this work. 

Are you looking to implement an Akeneo solution for your own business? Need help from a Magento expert team? Feel free to get in touch with us for further questions, or to schedule a free consultation!

The post Awesome news from APS Akeneo summit 2020! appeared first on scandiweb.