Demonstrated workflow
From a product PDF into an ERP.
When product details arrive in a familiar PDF format, Memric can read the document and enter those details through the software interface. In the recorded demo, it creates one product record in an environment modeled on DDI.
1
The demonstrated path
- 1
A person attaches a PDF and gives Memric the task.
- 2
Memric opens Product Inquiry and starts a new product record.
- 3
It enters the first product’s details from the PDF.
- 4
It creates the record for a person to review.
After creating the product record, the recorded task continues into a catalog sheet and a follow-up email, with separate approval points before those actions.
2
A sensible first fit
Start with product documents that follow a familiar format, fields the team already knows and a result that someone can check before it becomes part of the normal process.
Frequent
The same kind of request keeps returning.
Familiar
The normal path and exceptions can be explained.
Reviewable
A person can tell whether the result is right.
3
What we need to learn first
- Which fields are required?
- What does the normal document look like?
- Which exceptions does the team already know?
- Which accounts and applications are involved?
- Where must Memric stop for approval?
- How does a person decide the result is correct?
4
The boundary of this example
The demo does not establish duplicate detection, production accuracy, batch volume or support for every ERP. Those questions require the real documents, real interface and review criteria for the proposed task.
Show us how product setup works today.
A short walkthrough of the normal task and its exceptions is enough to decide whether it is worth testing.