For data managers

Supplier files keep coming.
Your catalogue stays correct.

openProd reads the data sheets and spreadsheets your suppliers send, maps every value to your data model and leaves you only the decisions that need a person.

Book a demo Watch the tutorial

Your week

The work between the file and the catalogue.

Supplier data rarely arrives the way your catalogue needs it. These are the moments that take the time, and what openProd does with each.

  • Every supplier sends a different layout.

    openProd reads data sheets, price lists and update files as they come, and maps each value to an attribute of your catalogue.

    2 files · one import

  • They send kilograms. We store grams.

    A conversion is asked about once per attribute, not once per product. Conversions that follow from your earlier answers are accepted for you.

    0.09 kg → 90 g

  • Where did this value come from?

    Show in source opens the supplier file where the value was read: the page of a PDF or the cell of a spreadsheet.

    Show in source · p. 1

  • Did the update overwrite something?

    Before you save, the preview lists every value that will change. After saving, each product keeps a version you can restore.

    86 g → 90 g

01AI import

Answer the questions. Skip the retyping.

Clear values go straight through. You answer only the ones that need a person, with the supplier file one click away.

One question per case A weight read in kilograms waits for your yes. The source row is one click away.

  • Several files, one import

    A data sheet and an update file are read together, from disk or from your asset library.

  • Clear decisions

    Conflicting values, missing dictionary options and conversions each come as one clear question.

  • Undo last decision

    Changed your mind? Step back one decision and choose again.

Explore AI import

02Product catalogue

Every save becomes a version.

See what an import changed on a product, compare it with the version before and restore a single field if you need to.

Every save is a version Version 6 is the weight the demo import wrote. Restore it, or any single field, as a new version.

  • Canvas for bulk edits

    Edit many products of a family in one grid, with variants under their main product.

  • Restore what you need

    Restore a whole version or one field. The restore becomes a new version too.

  • Export when asked

    Export the Canvas to CSV or XLSX for anyone who needs a file.

Explore the catalogue

03AI assistant

Fill the gaps on your terms.

Ask the assistant what is missing on a product. It proposes text from the product's own values, and nothing changes until you accept.

Nothing changes on its own The current description stays until you accept the suggested one.

  • Answers from the product

    The assistant works from the values the product already has.

  • You accept or reject

    Each suggestion shows the current value next to the suggested one.

  • Decisions on record

    Accepted suggestions stay in the decision history, with their evidence.

Explore the assistant

Scenario

One supplier, one week.

A week told with the openProd demo data: Demo Supplier A, two files and three products.

  1. Monday

    Two files arrive

    Demo Supplier A sends a data sheet for two new NPN sensors and a CSV file with a new weight for DEMO-SEN-001.

    Files to import (2)

  2. Tuesday

    One import, estimate first

    Both files go into one import. The analysis starts after you accept the credit estimate.

    5–9 credits

  3. Wednesday

    Only real questions

    Most values need no decision. The weight read in kilograms waits for yours, with the CSV row beside it.

    19 of 40 values

  4. Thursday

    Checked, then saved

    The preview shows two new products and one update. Save to catalog writes exactly that.

    86 g → 90 g

  5. Friday

    Ready for the shop

    The assistant suggests a fuller description for DEMO-SEN-009. You accept it, and the products are ready for your PIM.

    Accept

Demo data. Demo Supplier A and its products are synthetic.

Questions

Before your next supplier file.

Which files can openProd read?

PDF data sheets, spreadsheets such as XLSX and CSV, and text you paste. Several files can go into one import, and you can pick files already stored in your asset library.

Do I have to build the data model first?

openProd maps values to the families, attributes, units and dictionaries you already have. When a file brings a new kind of product, Data review can suggest a new family, and you decide.

What happens to values openProd is not sure about?

They wait in Data review as decisions: a conversion, a value without an attribute, or two values competing for one attribute. Clear values are imported without a question.

Can I check a value against the supplier file?

Yes. Show in source opens the original file where the value came from: a PDF at the cited page, a spreadsheet at its sheet and cell, with the quoted text.

Is anything saved without me?

No. The analysis only proposes data. Nothing is written until a user with permission clicks Save to catalog and confirms, and the preview shows every change first.

How do I see what the AI costs?

Before an analysis, the run dialog shows a credit estimate based on similar imports, and the analysis starts only after you accept. The top bar shows the credits used this month.

Bring this week's supplier file. See it land in your catalogue.

In the demo, we take one of your files through import, review and save, in your own data model.

Book a demo Watch the tutorial