An operations queue can contain a revised purchase order, a vendor form, and a delivery document for the same supplier. Each has different fields and a different next action. Dynamite Docs extracts draft values into tables so a reviewer can check the document before handing data to the team that owns the decision.
Define the destination first. A purchase-order handoff might need order reference, revision, item, unit, quantity, price, currency, and delivery location. Vendor onboarding might need legal name, address, and printed identifiers. Keep those schemas separate rather than forcing unrelated documents into one import table.
Documents to prepare
Purchase orders
Capture the order reference and revision along with item descriptions, units, quantities, prices, and requested dates. A superseded order can look complete while carrying the wrong instructions.
Vendor records
Extract legal names, addresses, and document identifiers. Handle personal and financial details under your team’s access policy and verify changes through your approved process.
Delivery documents
Prepare shipment references and visible line quantities. Keep delivered quantities distinct from ordered quantities; extraction alone does not confirm receipt or resolve a shortage.
An illustrative purchase-order handoff
Fictional values. Revision and unit checks are review tasks performed by the team.
| Order | Revision | Item | Quantity | Unit | Unit price | Review note |
|---|---|---|---|---|---|---|
| PO-230 | 2 | Packaging cartons | 40 | Case | 25.00 | Confirm case size |
| PO-230 | 2 | Labels | 500 | Each | 0.20 | Check delivery location |
Review against the source
- Confirm document type, order reference, revision, and supplier before reviewing line rows.
- Compare quantities, units, currency, and price basis; a price per case differs from a price per item.
- Keep requested dates, delivery addresses, and printed conditions attached to the correct document.
- Escalate changed bank details, missing identifiers, and unreadable fields through the existing approval process.
Prepare a reviewed handoff
Choose the handoff schema
List the columns the receiving team needs. Use separate schemas for purchase orders and vendor records and specify how optional fields and missing values should appear.
Review the current source version
Check the revision and all pages. Correct shifted columns, wrapped descriptions, and units beside the document before exporting.
Deliver accepted fields
Download Excel, CSV, or JSON, or use an available integration within your plan. The receiving workflow should verify the schema and document reference before acting on the handoff.
Use the accepted output
Use Excel for a team review queue, CSV for an agreed flat import, or JSON for a structured internal application. Include a document reference and revision in the receiving record. Test the mapping with one reviewed order before processing a batch.
Processing choices and allowances
Choose hosted AI, your own provider keys, or local Ollama on an eligible plan. Each successfully processed hosted page uses one PE. Free and Hobby BYOK use the same PE allowance; Pro and Ultra BYOK cost zero PE, with provider charges and limits still applying. Failed pages cost zero PE.
Check current plans, page limits, and capabilities and review storage and data-residency policies before processing sensitive records. Local model inference is a separate choice from browser-local file storage.
Workflow boundaries
- Extraction does not approve vendors, authenticate documents, or authorize bank-detail changes.
- Purchase-order matching, inventory receipt, and purchasing decisions remain in your existing systems.
Related guides
- Purchase-order field review
Check items, quantities, prices, and delivery details.
- US W-9 vendor data guide
Review source identifiers for a distinct onboarding document.
- Signed completion-event handoffs
Plan verified event handling for an internal workflow.
Questions about this workflow
Can this approve a purchase order?
No. It prepares reviewed document data. Your purchasing system and authorized team own approvals, matching, and fulfilment.
How do I handle revised orders?
Preserve the document revision and order reference, review the current source, and mark superseded records in the destination so both versions do not trigger actions.