Reads supplier files
Data sheets and spreadsheets become values with their source, not another spreadsheet to retype.
openProd for Pimcore
openProd reads supplier files, maps every value to the model you run in Pimcore and asks your team only about what is uncertain. Then the products you choose go to Pimcore.
For your Pimcore
Your team keeps working in Pimcore. openProd takes the part before it: supplier files that need reading, mapping and checking.
Data sheets and spreadsheets become values with their source, not another spreadsheet to retype.
Values land on your attributes, units and dictionaries, starting from the model openProd reads from Pimcore.
Clear values pass. Uncertain ones wait for a decision, and every change keeps its history.
Pick the products that go to Pimcore and see the state of each one.
How data flows
Two files from one supplier, checked in openProd, then synchronized to Pimcore.
Supplier files
openProd
Your Pimcore model
01Data model
A connector job reads your Pimcore definitions and prepares the matching families, attributes, units and dictionaries in openProd. What needs a business decision comes back as a question.
2 products were synchronized to Pimcore: DEMO-SEN-009 and DEMO-SEN-010. No products need attention.
The job looks at your Pimcore classes and fields before anything is created in openProd.
Name, SKU, Description and Main Image already exist in openProd, so Pimcore fields map to them.
When a mapping needs a business decision, the job ends with a clear question instead of creating it.
Viewing the Pimcore connector and running a Pimcore sync are separate permissions.
02Product sync
Pick products by family, status or search, start the sync and follow each product until Pimcore confirms it.
2 products were synchronized to Pimcore: DEMO-SEN-009 and DEMO-SEN-010. No products need attention.
Every product shows whether it is not synchronized, needs attention or synchronized.
A product counts as synchronized only after the result is verified in Pimcore.
A product that needs attention says what went wrong and what to do next.
Run the sync again for those products, on the page you see or across your filters.
Pimcore ecosystem
openProd maps supplier data to the product structure you already use. It is built by LemonMind, a team that implements Pimcore for customers.
The official Pimcore Store lists openProd.io AI Data Onboarding. Explore how supplier files become structured data mapped to your Pimcore model.
Pimcore lists LemonMind as a Platinum Partner. The team behind openProd brings that implementation experience to your onboarding workflow.
Questions
No. openProd maps supplier data to the classes and fields you already use. A connector job can read your Pimcore definitions and prepare the matching structure in openProd.
The ones you choose. Select products, or sync everything that matches a family, a status or a search.
Only after the result is verified in Pimcore. If Pimcore cannot confirm it, the product is marked as needing attention, with the reason and the next step.
Roles decide. Viewing the Pimcore connector and running a Pimcore sync are separate permissions, so you choose who does what.
That depends on your Pimcore version and the components you have installed. We agree the connection with your team during setup and test it on your own products.
Yes. The official Pimcore Store lists openProd.io AI Data Onboarding. LemonMind, the team behind openProd, is a Pimcore Platinum Partner.
In the demo, one of your supplier files goes through review, and we show the Pimcore connector.