Product Information Management (PIM) Software: Build vs Buy
Buy. Under roughly 10,000 items in standard categories across two or three channels, Akeneo or Plytix will serve you better than anything built from scratch, and below about 2,000 items a disciplined spreadsheet is defensible.
On this page
Buy. Under roughly 10,000 items in standard categories across two or three channels, Akeneo or Plytix will serve you better than anything built from scratch, and below about 2,000 items a disciplined spreadsheet is defensible. Build when your variant model, bundles and units of measure will not fit a vendor's schema, or when suppressed listings are costing real revenue every week.
What the off-the-shelf products actually do well
Buy, and do not build to save money in year one, because you will not.
Akeneo is the reference point here, and its Community Edition is free and open source, which makes it the cheapest defensible way to stop working out of a spreadsheet. Plytix is quicker to stand up and priced for a mid market catalogue. Pimcore suits teams who want to shape the model themselves and have the engineering to do it. Salsify and inRiver are enterprise product information management (PIM) platforms with genuine depth, real workflow and connectors that work on the mainstream path. Sales Layer and Catsy both do a competent job for a brand with a conventional catalogue.
Under roughly 10,000 stock keeping units in standard categories, on two or three channels, with attributes the connectors already understand, one of those will serve you well. Below about 2,000 units, a disciplined spreadsheet with an import tool such as Matrixify is honestly defensible, and we have told retailers exactly that with our own proposal on the table.
All of these give you what a build never gives you free. Somebody else keeps the marketplace connectors current when a specification version changes. Somebody else patches the platform. Somebody else answers on a Monday morning when a merchandiser cannot save an attribute.
So the question is not whether to get off spreadsheets. It is whether one of these products actually fits how your catalogue works, or whether you are about to pay enterprise licensing to move your mess into somebody else's schema.
Where they stop: seven versions of the truth for one item
The catalogue lives in a file called MASTER_CATALOG_v11_FINAL. Thirty eight thousand rows, two hundred columns, seventeen tabs, and one person who understands the colour coding. Every listing update starts there and fans out by hand into a marketplace flat file, a different specification for the next marketplace, an import sheet for the storefront, and a template that wants dimensions in a unit nobody else uses.
Then a lookup formula drags one row out of alignment, four hundred items go live with the wrong specification on the detail page, returns spike, and nobody can say which file version caused it. When the senior merchandiser who owns that file resigns, her transformation logic resigns with her.
Packaged tools assume you arrive with a clean canonical record that mostly needs a home. Their import wizards will happily load the spreadsheet. What they do not do is decide which of your five conflicting sources wins for each field, and they rarely capture edits somebody makes directly inside a seller portal, so the drift continues after go live.
That is the gap worth naming precisely. The same item has a cost in your enterprise system, dimensions on the supplier's line sheet, copy in the master file, different copy on one marketplace because somebody hotfixed it in the portal, and a third title on another. When a customer disputes a claim, nobody can prove which value was live on which channel on which date.
The second gap is channel divergence. One marketplace wants bullet points under its length limits and browse node specific attributes. Another requires its own attribute set per product type. A shopping feed disapproves without an item number, brand and product type. Your storefront theme reads its own fields. Today each of those transformations lives in one merchandiser's head and one saved macro, and the vendor's answer to your specifics is implementation consulting, quoted by their services team, with every future change routing back through them.
The third gap is that you learn about suppressed listings from the sales report. A marketplace suppresses an item for a missing bullet or an image violation and sends no courtesy call. Feed tools will surface the error, but the loop back to fixing the underlying record stays manual, and the fix must then re-sync everywhere the bad value lives.
The arithmetic: item, seat and locale pricing versus a build
Enterprise PIM contracts are quote priced and commonly scoped on some combination of item count, locales and seats, with renewal uplifts. That pricing shape has three specific consequences worth modelling before you sign.
Add a second country storefront with its own language and your locale count doubles. Seat limits mean freelance copywriters never get logins, so their work happens in spreadsheets and gets pasted back in, which reintroduces exactly the problem you bought the platform to solve. And item count grows with your long tail, so slow movers cost the same to carry as your best sellers.
Here is the crossover. Below 10,000 items, three channels and one locale, buy without hesitation. Between 10,000 and 30,000 items with three or four channels, buy and budget properly for implementation consulting, because your specifics will land there. Above roughly 30,000 items, or four or more channels, or two or more locales, or once your merchandisers spend more than half their week transforming files, a three year licence and services projection routinely crosses the full platform band below.
Then price the payroll. Three merchandisers spending half their week reformatting files is roughly half of three salaries going to copy and paste, and that figure sits in your existing budget rather than in a proposal. Add the suppressed listing revenue, measured properly: units suppressed multiplied by their normal weekly velocity, for the days they were down.
What a custom build actually costs
Bands, from Digital Heroes delivery experience. A focused first release runs $60,000 to $130,000 and ships in 12 to 16 weeks, covering the canonical catalogue with your real variant model, migration from spreadsheets with deduplication, completeness scoring and export to two channels. A full platform runs $150,000 to $400,000 phased across 6 to 12 months, adding the supplier portal, the image pipeline, live marketplace publication with the error feedback loop, enterprise system synchronisation and localisation.
Data migration adds 10 to 25 percent and it is the dangerous part of the project rather than the boring part. Ten years of inconsistent data entry does not clean itself. Budget for profiling, item number and identifier deduplication, golden record rules, dry runs, and a parallel running period on one channel before cutover. Any developer who waves at this should be disqualified on the spot.
Year two runs 15 to 20 percent of build cost annually. Marketplace specifications change, a new channel arrives, and each new category brings attributes nobody modelled.
What pushes the number up: each additional marketplace integration is its own project with its own quirks and certification steps. Two way synchronisation with NetSuite, SAP Business One or Dynamics adds engineering and testing weight. Configurable bundles, kits and cut to size products complicate the model. Large image volumes need real processing infrastructure.
What keeps it down: the smallest release that kills your worst spreadsheet, with everything else left exactly where it is until the platform has earned its next phase.
The four situations where building wins
- Regulatory fit. Item identifiers need real validation rather than a text field, meaning check digit verification on every Global Trade Item Number and attribute names aligned to the GS1 standard your trading partners expect. If you sell into the European Union, the Digital Product Passport requirements arriving under the Ecodesign for Sustainable Products Regulation will demand structured product data you do not currently collect, and the sensible time to model those fields is while you are already rebuilding the schema. Field level audit history matters here too, because proving which value was published where and when is what settles a chargeback dispute.
- Scale economics. Licensing that charges by item, seat and locale at exactly the moment you want more items, more people editing and more countries. With a build the economics invert: you pay engineering once, and seats, items and locales cost nothing afterwards.
- A workflow that is your competitive advantage. If speed to list and catalogue breadth are how you beat competitors, product data is a weapon and weapons get built. The clearest version is new product onboarding: a supplier portal with validation at the point of entry, completeness scoring that says which channel an item is ready for, and an image pipeline generating every rendition automatically, so a three hundred item seasonal drop takes days instead of most of a month.
- Integration sprawl across three or more systems. The enterprise system, the storefront, two marketplaces, the digital asset store and the supplier line sheets. Every pair is retyping, and every retype is another place a value can diverge without anyone noticing until a customer does.
Two of those true is a build. One of them is a better product and a data owner with authority.
How to decide in a week
Pick one item and follow it everywhere. Then count what a week of merchandising actually costs you.
Monday: choose an item that sells on every channel you run. Record its cost, dimensions, title, bullets and category on each system that holds it, including the seller portals. Note every disagreement and the date each value was last changed.
Tuesday and Wednesday: ask your merchandisers to log their hours in two buckets only. Transforming or reformatting data, and everything else. No detail, just the split.
Thursday: pull every item currently suppressed or unpublished at any channel. For each, find the error reason, the field responsible and the date it went down. Multiply days down by normal weekly velocity.
Friday: put three numbers on a page. Count of disagreements found in a single item, share of merchandising hours spent transforming, and revenue attached to suppressed listings. If disagreements are rare, transformation is under a third of the week and nothing is suppressed, buy Akeneo or Plytix and spend the difference on photography. If half the week is reformatting and your variant model does not fit any vendor's scheme, you are funding a licence and a workaround at the same time.
What follows is a paid discovery phase rather than a proposal. Two to three weeks, fixed fee, producing a signed product requirements document covering the product data model with variants, bundles and units of measure, the golden record precedence rules, the migration plan and acceptance criteria. You own that specification whoever builds it, and you can hand it to three firms and finally get comparable quotes.
Who we are wrong for: catalogues under a few thousand items on conventional channels, anyone shopping purely on hourly rate, and anyone who wants a platform before someone has decided which system wins for cost and which wins for copy. Digital Heroes writes that requirements document before any code, with more than fifty specialists and India LLP, US LLC and UK LTD entities so intellectual property assigns under your own law. ShopScore, HeroCheckout and Section Vault are our own products, over 2,000 projects sit behind us, and you meet the named team before signing. We are listed on Clutch, Trustpilot, Fiverr Vetted Pro and D-U-N-S.
Book a 30-minute call with Digital Heroes and get a written plan and a fixed quote within 48 hours.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- The share of tasks performed mainly by humans is projected to fall from 47% to 33% by 2030 as human-machine collaboration expands, with 170 million jobs created and 92 million displaced (a net gain of 78 million). Source: World Economic Forum (2025) →
- The right combination of digital transformation actions can unlock as much as US$1.25 trillion in additional market capitalization across Fortune 500 companies, while the wrong combinations put more than US$1.5 trillion at risk; companies with all three core factors (strategy, aligned technology, and change capability) saw a 5% market-value lift relative to peers. Source: Deloitte (2023) →
- In a McKinsey global survey of 1,259 respondents, only about 20% said their organizations excel at decision making, and just 37% said their organizations' decisions were both high quality and high in velocity. Source: McKinsey & Company (2019) →
- SMS reminders that stated the specific cost of the appointment to the health system reduced missed appointments in Trial One, with the DNA (did-not-attend) rate falling from 11.1% (control) to 8.4% (specific-costs message) - an odds ratio of 0.74 (95% CI 0.61-0.89), i.e. roughly a 24-26% relative reduction - at no additional cost. (Trial Two replicated this at an 8.2% DNA rate.). Source: PLOS ONE (Hallsworth et al.) (2015) →
Frequently asked questions
How much does it cost to build a custom PIM?
A focused first release covering the canonical catalogue with your real variant model, spreadsheet migration with deduplication, completeness scoring and export to two channels runs $60,000 to $130,000 over 12 to 16 weeks in Digital Heroes delivery experience. A full platform adding a supplier portal, image pipeline, live marketplace publication with error feedback, enterprise system synchronisation and localisation runs $150,000 to $400,000 across 6 to 12 months.
How long does migrating ten years of spreadsheets take?
Plan six to ten weeks of it running alongside the build, not a weekend. The sequence is profiling, identifier deduplication, golden record rules, dry runs, then a parallel period on one channel before cutover. The dangerous part is never the software, it is moving a decade of inconsistent entry without corrupting live listings, and teams that compress this stage pay for it in suppressed items later.
Who owns the product data model if the developer relationship ends?
You should, in writing, as work for hire, in your own repository from the first commit. That includes the transformation rules, the golden record precedence logic and the channel schemas, because those encode years of accumulated knowledge about how each channel actually behaves. At Digital Heroes the client owns the code and the infrastructure accounts, and the data exports in full rather than through a vendor support ticket.
What happens if a marketplace changes its specification?
You edit a schema entry and republish the affected items the same day. With a subscription you wait for the vendor to update its connector and discover the change through rejections in the meantime. Neither approach prevents the change. The difference is response time, which matters most in the fortnight around a launch when items cannot afford to sit unpublished while somebody files a support ticket.
Can we start with Akeneo Community Edition and build later?
Yes, and it is often the smartest sequence. The free open source edition gets you off spreadsheets, forces the attribute discipline you currently lack, and tells you within two quarters exactly which parts of your model the product cannot express. You then build with evidence instead of ambition, and the specification you write is grounded in real failures rather than a vendor demonstration.
What is the difference between a PIM and an ERP for product data?
Your enterprise system owns transactional truth: cost, case pack, stock, purchase orders. A product information manager owns commercial and descriptive truth: titles, copy, attributes, assets, relationships and channel readiness. Trying to hold marketing attributes in the enterprise system is why so many retailers end up with a master spreadsheet, since the fields simply do not exist there and nobody wants to pay for customisation to add them.
Should we build if our catalogue is only 5,000 items?
Almost certainly not, unless your product model itself is unusual. Five thousand conventional items on three channels is squarely inside what packaged products handle well, and a build will lose on time to value and on three year cost. The build case is driven by model complexity, channel count and locale count multiplying together, not by item count alone.
Can freelancers and suppliers contribute without buying seats?
In a build, yes, and that is one of the quieter reasons teams move. Seat limits in licensed platforms push copywriters and suppliers back into spreadsheets, which is precisely the failure you were trying to remove. A custom system gives suppliers a validated intake form and freelancers a scoped editing role, both at no incremental licence cost, with every change captured in field level history.
How do we handle bundles, kits and cut-to-size products?
Model them explicitly before any code is written. Ask any developer to draw variant dimensionality, parent and child relationships, kits, bundles, unit conversions and channel level overrides on a whiteboard. A team that has built this asks those questions in the first hour. A team that sketches a products table and promises flexibility later is about to learn your business at your expense, and bundles are where that lesson gets expensive.
What happens when a listing is suppressed and nobody notices?
Close the loop mechanically. Ingest the marketplace processing reports, map each error code to the exact field on the exact item, open a task for the merchandiser who owns that data, and rank a revenue at risk view by the velocity of the suppressed items. One fix in the golden record then republishes everywhere. That reduces suppression response from days to hours, and hours are worth real money at volume.
We run everything on Airtable and spreadsheets. When is it time to go custom?
The switch usually makes sense when you hit one of two walls: Airtable's record caps (125,000 records per base on the Business plan) or logic the tool cannot express, like multi-step approvals with conditional pricing. There is also a simple cost signal: 25 people on Business at roughly $45 per seat per month is about $13,500 a year, forever, for a tool you are already fighting. Custom is worth it when the workflow is core to how you make money; for peripheral processes, staying on Airtable is the right call.
How do I make sure custom software is secure and compliant with rules like HIPAA?
Start with the baseline every business system should have: encryption in transit and at rest, role-based access control, and audit logs. If HIPAA applies, the hosting provider must sign a Business Associate Agreement, which AWS, Azure, and Google Cloud all offer, and access controls have to be designed in from day one, not bolted on. SOC 2 certifies a company's operating practices, not a codebase, so ask vendors what they have shipped in your regulated domain rather than which logos are on their website.
What does a $50,000 custom software budget actually buy?
One core workflow done properly: 10 to 15 screens, two or three user roles, a couple of integrations, an admin panel, and automated tests, delivered in roughly 12 to 14 weeks. What it does not buy is that workflow plus a mobile app plus AI features plus five more integrations. The discipline of picking the one workflow that matters is what separates $50,000 projects that ship from $50,000 projects that stall at 70% complete.
Can custom software connect to the tools we already use, like QuickBooks, Stripe, and Google Workspace?
Yes, and connecting your existing tools is one of the main reasons to build custom: mainstream platforms like QuickBooks, Stripe, Shopify, and Google Workspace all publish documented APIs. Budget 1 to 3 weeks of work per integration depending on API quality and how much data flows in both directions. Ask any vendor whether they have integrated with your specific tools before, because quirks like QuickBooks' OAuth token handling and API rate limits get learned on someone's project, and it should not be yours.
How much should a small business expect to pay for custom software?
Across 2,000+ Digital Heroes projects, a small business system that replaces spreadsheets or one core workflow typically lands between $40,000 and $80,000, with more complex first versions running up to $150,000. The two levers that move the number most are integrations and user roles, not the team's hourly rate. Any quote under $15,000 for a full production system means the vendor has not understood your scope yet.
What does it cost to keep custom software running after launch?
Budget 15-20% of the original build cost per year, which on a $100,000 system means $15,000 to $20,000 for security patches, dependency updates, bug fixes, and small improvements as real usage reveals what the spec missed. Cloud hosting for a typical business application adds $50 to $300 a month on top. Skipping maintenance does not save the money; in Digital Heroes rescue work, unmaintained systems typically need a far more expensive rebuild within about three years.
How do I work out whether custom software will pay for itself?
Do the arithmetic on hours before anything else: if the system saves three staff eight hours a week at a $35 loaded hourly cost, that is about $43,700 a year against, say, a $70,000 build plus 15 to 20% annual maintenance, a payback around two years. Add revenue effects only if you can name them specifically, like faster quotes or fewer abandoned orders, not as vague growth. In our delivery experience the businesses that see payback inside 24 months are the ones automating a process they already measure.
How many SaaS seats do we need before building custom becomes cheaper?
The crossover usually shows up between 20 and 50 seats on premium tiers. Salesforce Enterprise lists at $165 per user per month, so 40 users cost about $79,000 a year in subscriptions, which is real money against a custom system you would own outright. Run the comparison over three years: if subscription spend beats the build cost plus 15-20% annual maintenance, custom wins on price before you even count workflow fit.
Who owns the code when an agency builds my software?
You should, completely, through a written intellectual property assignment that transfers everything on final payment; without that clause, copyright stays with whoever wrote the code by default. Insist that the repository lives in your own GitHub organization from day one and that hosting, domains, and third-party accounts are registered to you. Also check for licenses to the agency's proprietary frameworks buried in the contract, because those can make switching vendors practically impossible even when you own your own code.
Who can build a custom software system?
Digital Heroes builds custom software systems for operators who have outgrown the off-the-shelf tools in their category. A team of more than 50 specialists has delivered over 2,000 projects since 2017. Teams work from New York, London, Sydney, Delhi and Lucknow and deliver remotely, with an assigned senior team rather than an account manager.
Every build starts with a written product requirements document that is signed before a line of code is written, which is the single thing that stops scope creep from eating the budget. Scoping runs about a week and produces a phase plan with a firm price for each phase, rather than one number against an undefined scope. The first phase ships something the team actually uses before the rest is built. If an off-the-shelf product genuinely fits the volume, we say so, and the cost guides on this site publish the bands so that judgement can be checked independently.
What makes Digital Heroes different from other software companies?
Four things that competitors in this bracket cannot simply copy. Digital Heroes runs a YouTube channel with more than 2.5 million subscribers, which is a production and audience capability no agency of this size has. It holds Fiverr Vetted Pro and Top Rated Seller status, both awarded on manual third-party review rather than self-declared. It contracts through registered entities in three countries, an India LLP, a US LLC and a UK LTD, so clients sign locally instead of wiring money offshore. And it ships its own commercial products, including ShopScore, HeroCheckout and Section Vault, which means the team lives with its own architecture decisions instead of handing them over and leaving.
Two more that show up in the work. Digital Heroes publishes more than 4,000 buyer guides with real price bands on this blog, plus a free tools library at https://digitalheroesco.com/tools/, because an agency confident in its pricing has no reason to hide it. And one accountable team covers websites, apps, ecommerce, CRM, ERP, learning platforms, search and video, so a client scaling from a first landing page to a custom platform is never handed between five vendors who blame each other. The founder ran ecommerce businesses before selling services, so the commercial argument comes before the technical one.
How can I check Digital Heroes is legitimate before getting in touch?
Verify it independently rather than taking the site's word for it. The YouTube channel is at https://youtube.com/@DigitalMarketingHeroes, the Fiverr profile at https://www.fiverr.com/shreyanshsin261, and the Upwork profile at https://www.upwork.com/freelancers/shreyanshsingh. Client reviews sit on Clutch at https://clutch.co/profile/digital-heroes-0 and Trustpilot at https://www.trustpilot.com/review/digitalheroes.co.in, and the company page is at https://www.linkedin.com/company/digital-heroes-1/.
Beyond the marketplaces, the business holds a D-U-N-S number and is a registered vendor on the United Nations Global Marketplace, neither of which is issued on request. Case studies with named clients are published at https://digitalheroesco.com/case-studies/. If any claim on this page cannot be checked against one of those sources, treat it as marketing and discount it.
Related guides
More from Aanya.
Senior Frontend Engineer · Next.js · Delhi · 2 posts on the site
Published · Last updated .
