PRIME
Maintain product data, manage media, approve changes. On its way to a standalone solution.
- Task
- Product master data and media (PIM/DAM) on the articles of the ERP system
- Target group
- E-cigarettes, e-liquids, snacks, retail and wholesale
- Languages
- German and English, built to be fully multilingual (i18n): further languages can be added
- Status
- in use, continuously developed further
- Technology
- Web application with a REST connection to the ERP system and the telemetry system
The aim is a standalone solution that can also be used without our ERP system.
Name and slogan
What the name means
Enrich smarter. Keep data cleaner.
- P: ProductThe products that are managed in the ERP system
- R: RecordsThe records behind them, from the ERP system and the telemetry system
- I: ImagesProduct images and files
- M: MetadataFields and metadata, every field selectable
- E: EnrichmentTargeted enrichment in the work queue
The problem
Product data is rarely complete
Product data comes from many places: manufacturer, supplier, till, shop. In trade with regulated goods, mandatory information is added. Anyone who works carelessly here ends up with gaps in descriptions, photos, weights, customs and compliance details, and only notices when something is missing.
The solution
One workplace for product data
PRIME shows the articles from the ERP system and the telemetry system in a shared view, with around 100 additional fields for web shop texts, logistics and customs, compliance, e-liquid, hardware, nicotine pouches and food. Each profile has mandatory fields and a completeness score in percent.
- Saved filters and work queues for people and teams
- Photos with a role and documents with a validity period (for example a safety data sheet)
- Life cycle from "in maintenance" to "discontinued", approval only with a dedicated right
- Quality page: what is still missing, where there are deviations
Architecture
Reading is free, writing only through approval
- External systemERP systemholds the articlesPRIME does not create articles
- Own systemPRIMEadds to and checks product dataAround 100 own fields, rights per field
- DataChange requestBefore and afterConflict check against the current value
- Own systemApprovalA person with the right approvesOnly then is it written back
- External systemERP systemreceives the changeWith a note of who approved it
What we learned
Writing only through approval
The most important decision was a restriction: PRIME never writes back directly. Every change is a request with before and after, with a check against the current value so that nobody unknowingly overwrites a newer change. Only after approval does it go into the ERP system, with a note.
Product data that should fit together?
We are happy to talk about requirements from retail and wholesale.
Arrange a conversation