For the order that crosses inbox, spreadsheet and warehouse

Move purchase orders into fulfillment with an exception review.

A mailbox event, form or API upload starts the workflow. Product, customer and order records can stay in an ERP or commerce stack, or live in a complete Bondi operations system. Every mismatch still pauses for a buyer before fulfillment.

From event to outcome

Follow the work through its human decision.

The workflow reads the named fields from the document and keeps the extraction confidence beside each value. It matches customers, products and prices against the records you chose, whether they live in Bondi or a connected system. Clean lines continue; low-confidence values, unknown SKUs and price mismatches suspend for a buyer with the document attached. Only the approved order reaches fulfillment.

Illustrative workflow
Buyer review
  • Microsoft 365 or Gmail Purchase order file Built-in connector
  • Bondi Extraction, validation and buyer exception Bondi runtime
  • Custom ERP Product, price or order record Custom SDK
  • Shopify + UPS Approved fulfillment actions Built-in connector
  1. 01 Receive the purchase order mailbox event / formTrigger · file
  2. 02 Extract the fields you named extractDocumentData · confidence per field
  3. 03 Match products, prices and customer custom integration / bondiDataLookup
  4. 04 Give the mismatch to a buyer interactiveForm · document + fields side by side
  5. 05 Create the approved fulfillment work Shopify / UPS / custom ERP action

Configured human task

Buyer

A low-confidence field, unknown SKU or price mismatch waits for a buyer

Context shown

The original order, extracted fields and the item or price that needs checking.
  • Confirm corrected order
  • Keep on hold
A confirmed order continues to the configured fulfillment step.
sample_ops / automations / purchase-order-intake Illustrative execution
Run inspector

PO-1048 · 12 lines

Eleven lines matched. One unit price is below the confidence threshold and differs from the current price record.

Document
purchase-order-1048.pdf
Matched
11 of 12 lines
Current step
Review unit price on line 07
On approval
Create order + UPS shipment
Illustrative data. The connection methods, node boundaries and suspended human step reflect current product capabilities; this is not a customer implementation.
If nobody responds

The order remains blocked with its document attached and escalates to the purchasing queue.

Where the records live

Run the process beside your tools or within Bondi.

Keep one authoritative home for each business record. Choose the boundary that fits the process you are building.

Beside existing systems

Keep ERP, commerce and carrier records in place

Use built-in actions where available and API/HTTP or the SDK for a custom ERP. Bondi owns intake, validation, buyer review and the approved sequence without mirroring every database.

Inside your Bondi system

Build order operations in Bondi

Customers, products, orders, exceptions and fulfillment work can live in one custom Bondi system. External commerce, carrier, finance or statutory systems remain connected only where the process needs them.

Connection requirements

Set up the connections this example uses.

This is a worked example of a configurable workflow. Connections and decision rules must be set up for your system.

Explore integrations
  • Microsoft 365 or Gmail

    A mailbox event or file entry starts the workflow.

  • Custom ERP

    Expose typed actions and events with @bondi-labs/integration-sdk, or use its API through HTTP.

  • Shopify + UPS

    Built-in typed actions run after validation and human review.

The wider operation

See the system around this workflow.

Explore the records, screens and other decisions that can stay connected to this process.

Start with your process

Describe one handoff you want to improve.

Name the starting event, the records involved and the decision that needs a person. Review the plan before building the workflow.

No credit card required.