Enterprise DNA

Instead of Pimberly

Stop renting Pimberly. Own your product information system.

We build your version around your products, suppliers and sales channels. Enterprise DNA maps your Pimberly records, brings the agreed history across and runs the system for you.

Pimberly lists Regular at US$36,000 a year and Pro at US$60,000 a year. Your own version starts with the catalogue work you actually need.

Get your version built See it working
  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

What the subscription buys

A catalogue platform priced around scale

Pimberly combines product information and media management. Its published plans bundle capacity, channels and support. Compare the full bundle with the work your own team needs.

paid

An annual platform bill

Regular is US$36,000 a year. Pro is US$60,000 and Corporate is US$90,000. Pimberly says payment is annually in advance.

inventory_2

Product capacity by plan

Regular lists 50,000 product identifiers. Pro lists 100,000 and Corporate lists 250,000. Your catalogue size is part of the package choice.

group

Users included in the package

Regular lists 20 users, Pro 50 and Corporate 100. The open-source base has no software seat licence; team access still needs to be configured.

perm_media

A media system alongside the records

Pimberly includes digital asset management and plan-specific storage. Start your own version with content records and scope media storage around the files you use.

sync_alt

Import and export channels

Pimberly lists unlimited import and export channels. The free base prepares private product files; Enterprise DNA scopes the connections your business needs.

support_agent

Support bundled with the platform

Pimberly lists online help, phone support and a technical account manager. With Omni by Enterprise DNA, the agreed support covers your own installed version.

Your catalogue, your rules

Make the weekly product meeting answerable

Channel readiness

Know which content stops a release

Check each product against the required content for its destination. A complete record and a reviewed record are separate facts.

  • check Required descriptions and specifications by channel
  • check Shared content with language and channel overrides
  • check Missing fields named against each product
  • check Changed content requires a fresh review

Claim evidence

Keep the claim beside its evidence record

Record the statement, evidence reference, reviewer and next review date. Missing or overdue records hold the product out of the channel file.

  • check Pending claims appear in the review queue
  • check Evidence review dates remain visible
  • check The owner checks the substance behind each reference
  • check Record checks support review; they do not certify a product

Supplier follow-up

Ask what each supplier still owes you

Combine the product, request, owner and due date in one follow-up. Prepare a draft from the current requests.

  • check Open content requests grouped by supplier
  • check Overdue requests with named owners
  • check A product brief for the missing information
  • check Follow-up drafts stay private until you send them

Your version

Answer the question your team asks next

Combine supplier tasks, claim reviews and channel blockers in the same database. Add a question or rule as the business changes.

  • check Catalogue review sheets in your business name
  • check A weekly readiness report you can print
  • check Recorded changes with operator names and explanations
  • check Pimberly product exports mapped into your own records

Make it yours

Design your own Pimberly replacement

Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from Pimberly. Try it here, and we build the real one.

2. What it runs

3. Make it fit

4. Your colour

Your business · your Pimberly replacement Your version
YB Your business

auto_awesome

Answered from your own database

Build my version

We build it from the open-source base, bring your Pimberly data across and run it for you.

What it looks like

Ask it like you would ask a colleague

Real answers from fictional product records. Ask about missing content, claim evidence or overdue supplier requests and review the result before taking action.

forum

Product Information for Claude Code

Connected to your own database

What is blocking the Australian retail catalogue?

BAG-020

Me ch
Recycled carry bag
Annel lo
au-retail
Cale mi
en_AU
Ssing_fields cl
["care","barcode"]
Aim_issues re
1
Viewed re
false
Ady
false

BOT-750

Me ch
Harbour steel bottle
Annel lo
au-retail
Cale mi
en_AU
Ssing_fields cl
["barcode"]
Aim_issues re
0
Viewed re
false
Ady
false

BOX-010

Me ch
Storage box
Annel lo
au-retail
Cale mi
en_AU
Ssing_fields cl
["care","material","barcode","des...
Aim_issues re
0
Viewed re
false
Ady
false

CUP-OLD

Me ch
Legacy travel cup
Annel lo
au-retail
Cale mi
en_AU
Ssing_fields cl
["care","material","barcode","des...
Aim_issues re
0
Viewed re
false
Ady
false

Ask it anything

Ten questions your catalogue can answer

These questions are answered by the working demo. Pimberly also offers reporting and workflows. Your version combines the records around the questions your team asks.

chat_bubble Which enabled products still lack content for Australia?
chat_bubble Which products are ready for the New Zealand channel?
chat_bubble Which claims are waiting for evidence?
chat_bubble Which claims have reached their next review date?
chat_bubble Which supplier requests are overdue?
chat_bubble Which products have no named owner?
chat_bubble Which old products need their content checked?
chat_bubble What did the last recorded content change contain?
chat_bubble Which channel needs a fresh review after an edit?
chat_bubble What does each supplier still owe us?

Switching

How to switch from Pimberly

The move involves mapping your product fields, rehearsing the import and checking which history or connected assets need separate migration work.

  1. 1

    Export your product records

    Export your Pimberly product records as a row-per-product CSV. Include the product content and fields you want to carry into the new catalogue. Media files, inherited variants, approval history and live channel connections are separate migration items, so do not assume they are included in the product export.

  2. 2

    Match your field headings

    Match the CSV headings to the fields in the new catalogue before importing. Decide how each source field should map, including any fields specific to your business or channels. The import preserves original fields, but the headings still need to be matched so product content goes into the intended fields.

  3. 3

    Rehearse, then import

    Run a dry run with the mapped export before loading records. Review the result, then import once the mapping looks right. The import rolls back malformed batches and skips identical repeats. If a source row has changed since an earlier import, it needs explicit reconciliation rather than being treated as a new unchanged record.

  4. 4

    Check the imported records

    Review anything the rehearsal or import reports, then compare a selection of imported records with Pimberly. Check that values landed in the intended fields and resolve any problems before relying on the new catalogue. Reconcile changed source rows and confirm the result against the records you chose to bring across.

  5. 5

    Run both, then switch

    Keep Pimberly available for a short period while you check records and confirm your team can complete the agreed catalogue work in the new setup. Use Pimberly as a reference while you resolve discrepancies. When the records and working process have been checked, switch off Pimberly.

construction

Where the real effort goes

The CSV transfer is only part of the work. Most effort usually goes into mapping your own fields and rules, then deciding which history, media, variants, approval records and channel connections to bring across separately. Agree that scope, rehearse the migration and reconcile the result before switching. When Enterprise DNA runs it for you, they handle this migration work as part of the agreed scope.

Not ready for a call?

Get your Pimberly switch plan by email

We will send you the step-by-step plan for moving your business off Pimberly, what the move really involves, and how we would do it for you.

One email with your plan. No spam, and you can unsubscribe any time.

Three ways to make it yours

Choose how your product system gets built

Open source

Do it yourself

Free, open source

  1. 1 Clone the repo, run npm install, then npm run demo
  2. 2 Open the folder with Claude Code, Codex, OpenCode or Cursor
  3. 3 Try /readiness, /compliance and /weekly-review on the fictional records
  4. 4 Read the Pimberly import guide, map your export and run a dry run before switching
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer

  • check Your attributes, content rules and branded documents
  • check Your Pimberly records mapped and reconciled
  • check A web front end or different stack when your team needs it
  • check Media, variants and channel connections scoped around your business
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check Installed and operated through Omni by Enterprise DNA
  • check Agreed connections to the rest of your business
  • check Team access, backups and operational checks
  • check Ongoing support as products and review rules change
Talk to Sam

Questions

Instead of Pimberly, answered

What does Pimberly cost, and what would we pay you? expand_more

Pimberly publishes US$36,000 a year for Regular, US$60,000 for Pro and US$90,000 for Corporate. Enterprise DNA scopes your version with one setup fee, then a retainer. We compare your actual requirements and invoice on the call.

Can you bring our Pimberly product history across? expand_more

The free version imports a mapped product export and keeps the original fields. Your headings must be matched first. Media files, inherited variants, approval history and live channel connections need separate migration work. We agree that scope, rehearse it and reconcile the result before you switch.

Does a green check mean our product claims are legally approved? expand_more

No. It means the configured content and claim-record checks passed and someone reviewed that content revision. Your responsible person must assess the evidence and confirm that claims in the wording are recorded or removed. The system does not certify a product.

Will our team have a browser workspace and commerce connections? expand_more

Enterprise DNA can build the web front end, media handling and connections your team needs. The free base starts with product records, review documents and private channel files. Team access and operational support are scoped with your version.

Why consider this alongside Akeneo or Plytix? expand_more

Akeneo and Plytix are other product information platforms. This route starts with your catalogue work and a database you own. You can change the checks, keep the history and choose who runs it. The free base is open source; hosting and the tools you use to operate it have their own costs.

Bring your catalogue bill and one blocked product

Spend 30 minutes with Sam. Show us what you pay Pimberly, where supplier content stalls and which channels matter. We will work through what your own version needs and what a sensible switch would involve.

Book 30 minutes with Sam Get the free version

Product Information for Claude Code is free and open source, published by Enterprise DNA.

Done paying for Pimberly?

Get your version built