Return material analysis report intake
For Product return analysis document teams
Prepare returned part, observed failure and stated findings from an analysis report with fields you can edit. Root-cause validation external.
25 free credits/month · No card needed
See the workflow and review checksInspect a document example.
Synthetic documents · Expected output- return reference
- DEMO-RETURN-0042
- part reference
- DEMO-PART-0042
- serial number
- DEMO-SERIAL-0042
- analysis date
- 2026-09-30
- observed failure text
- Observed failure text explicitly printed in the original synthetic source for reviewer context.
- stated findings text
- Source author describes a suspected cause and recommends further testing.
- recommendation text
- Recommendation text explicitly printed in the original synthetic source for reviewer context.
{
"return_reference": "DEMO-RETURN-0042",
"part_reference": "DEMO-PART-0042",
"serial_number": "DEMO-SERIAL-0042",
"analysis_date": "2026-09-30",
"observed_failure_text": "Observed failure text explicitly printed in the original synthetic source for reviewer context.",
"stated_findings_text": "Source author describes a suspected cause and recommends further testing.",
"recommendation_text": "Recommendation text explicitly printed in the original synthetic source for reviewer context."
}A complete synthetic document with the visible values shown below. Real responses also include model-reported confidence, validation and result status. Test your own file with this schema.
When this work lands on your desk
An analysis report arrives for product return analysis document teams. The next step needs returned part, observed failure and stated findings, recorded under the correct document reference before the information enters your quality or production document register.
An analysis describes a suspected cause and asks for further tests. Preserve the uncertainty rather than labeling the cause confirmed. This schema keeps the source labels and values explicit so the reviewer can resolve the issue before downstream use.
Start with the documents you already collect
- Analysis report PDFs
- Scanned or photographed analysis report pages
PDF, JPEG, PNG, TIFF, or WEBP. Send one file per extraction call; create separate schemas when the document types need different fields.
Define the fields
Open the starter schema. Edit field descriptions, mark the values your process requires, and save it in your account.
Extract at intake
Send the document and saved schema slug to
POST /api/v1/extract, or collect the file through a branded upload site.Hand off reviewed data
After checking return reference, part reference, serial number, your application maps the reviewed record into your quality or production document register. Keep the original document reference with the result. Root-cause validation external. Dokyumi processes one file with a saved schema; your application owns record matching, business rules and updates to other systems.
A schema shaped around the next step.
Start with these fields, then adjust them to match your documents and destination system. The example above shows the data object you are asking Dokyumi to extract.
Download editable starter schemaChoose required fields for your process. The starter schema preserves any defined nested fields; refine line-item structures and test them on representative files.
| Field | Type | What to capture |
|---|---|---|
return_reference | string | Return reference exactly as printed in this analysis report. Preserve identifiers and qualifiers; do not look up or infer missing information. |
part_reference | string | Part reference exactly as printed in this analysis report. Preserve identifiers and qualifiers; do not look up or infer missing information. |
serial_number | string | Serial number exactly as printed in this analysis report. Preserve identifiers and qualifiers; do not look up or infer missing information. |
analysis_date | date | Analysis date explicitly printed in this analysis report. Keep it distinct from other dates; leave it empty if no calendar date is stated. |
observed_failure_text | string | Observed failure text exactly as printed in this analysis report. Preserve identifiers and qualifiers; do not look up or infer missing information. |
stated_findings_text | string | Stated findings text exactly as printed in this analysis report. Preserve identifiers and qualifiers; do not look up or infer missing information. |
recommendation_text | string | Recommendation text exactly as printed in this analysis report. Preserve identifiers and qualifiers; do not look up or infer missing information. |
Give exceptions a clear path to review.
Dokyumi returns a model-reported confidence map, validation details, and a completed or review status for produced results. Check required fields and your business rules before passing data onward.
A completed extraction describes the extraction result. Your application and reviewers own matching, approvals, routing, and updates to other systems.
Read the response contractChecks for this process
- An analysis describes a suspected cause and asks for further tests. Preserve the uncertainty rather than labeling the cause confirmed.
- Check analysis date against their own printed labels; leave an unstated date empty instead of deriving it.
- Resolve missing return reference, part reference, serial number against the source before using the record.
Prove the fit on a representative batch.
Test analysis report examples from the layouts your team actually receives. Include the exception described here: An analysis describes a suspected cause and asks for further tests. Preserve the uncertainty rather than labeling the cause confirmed. Compare the extracted return reference, part reference, serial number and any line rows with a reviewer's checked reference before enabling downstream actions.
Compare extracted values with a reviewer’s reference set. Record corrections, unresolved fields, review time, and credits used before connecting downstream actions.
The free plan’s credit limits apply. Assisted pilots are scoped with Dokyumi before work begins.
Expand when the next process is ready
Add recurring extraction capacity when analysis report intake becomes routine. Reuse this field contract for layouts that express the same information; create a separate schema when the next document has different fields or review requirements.
For a tailored implementation
Discuss document volume, page lengths and schema setup for product return analysis document teams. Bring difficult analysis report samples and the review requirements your implementation must preserve.
Talk through document mix and volumeStart small. Add capacity as intake grows.
All self-service plans include the REST API, upload-site webhooks, custom confidence thresholds, and schema inference. Choose by volume, schema count, and upload sites.
Each document uses one credit per 5 pages, rounded up. An 8-page file uses 2 credits. Self-service files can be up to 50 pages; larger files, custom-built schemas, and additional volume are quoted through Enterprise. Full pricing details
Questions about return material analysis report intake
Which fields can I capture from an analysis report?
The starter schema contains return reference, part reference, serial number, analysis date, observed failure text, stated findings text, recommendation text. Edit those definitions and choose your required fields before saving. Array fields include defined sub-fields so row values have a validation structure.
What needs review in return material analysis report intake?
An analysis describes a suspected cause and asks for further tests. Preserve the uncertainty rather than labeling the cause confirmed. Check the original source alongside model-reported confidence and validation output; completion status describes the extraction result, not the business decision.
How does this data reach your quality or production document register?
Save the schema, then send one supported PDF or image to POST /api/v1/extract with its slug. The response contains the data, model-reported confidence, validation and result status. Your application maps reviewed values to the destination; upload-site submissions can use a configured webhook. Root-cause validation external.
How do I test this workflow on my own documents?
Start free with 25 credits per month, 2 schemas, and 1 branded upload site. The starter schema opens in the schema builder after sign-up. Edit the fields, save it, and upload a representative file through your account or the extraction API. Account documents are stored according to Dokyumi’s privacy policy; contact hello@dokyumi.com for deletion requests and retention requirements.