Skip to content
memric.
Show us a task

Recorded product demo

Watch a complete Memric run.

A user attaches a two-product PDF and asks Memric to create the first product in an environment modeled on DDI, add it to a catalog sheet and prepare an email with the product details.

The recording is silent. The player includes a written step-by-step account of the run.

Recorded product run

PDF DDI Sheet Email

1:44

This is a recorded Memric run using demo data in our own environment modeled on DDI. Repetitive data entry was sped up; no actions were removed.

See the run step by step

The recording is silent. These steps describe what Memric does on screen.

  1. 1A user attaches a two-product PDF and asks Memric to add the first product to DDI, create a catalog sheet and email the product details to Riccardo.
  2. 2Memric opens DDI on its Windows desktop and signs in.
  3. 3It opens Product Inquiry, starts a new product record and enters the product details from the PDF.
  4. 4It creates the CHM-FLR-1G record in DDI.
  5. 5Before creating a Google Sheet called “new catalog,” Memric asks for approval.
  6. 6After approval, it creates the sheet and asks again before adding the product details.
  7. 7After the second approval, it fills the sheet, shows the result and prepares an email to Riccardo.
  8. 8Memric asks one final time before sending. After approval, it sends the email and reports that the task is complete.

1

What happens in the recording

  1. 1

    Read the first product’s details from the attached PDF.

  2. 2

    Sign in to DDI and create the product record.

  3. 3

    Ask for approval before creating the catalog sheet and again before filling it.

  4. 4

    Prepare an email with the product details and wait for approval before sending it.

2

What this demonstrates

The run moves through a Windows desktop application, a web spreadsheet and email. Memric works through the interfaces, pauses at the configured approval points and keeps a record of what happened.

It is a demonstration of one defined task, not a claim that every workflow or application is ready to run without setup.

3

What the recording does not claim

The recording is not a customer workflow, a live DDI environment or evidence of a DDI partnership. Compatibility with a company’s actual software and process is established during a scoped pilot.

Keep reading

Read the demonstrated workflowSee the inputs, steps, review points and boundaries behind the product-entry run.For industrial distributorsSee which kinds of repetitive back-office tasks may be worth evaluating first.

What should Memric try in your software?

Show us one frequent task and the person who handles it today. We’ll tell you what a careful first pilot would require.

Show us a task