Procurement

Supplier quote comparison

Buyers manually rekey differently formatted supplier quotes before they can compare equivalent requirements and exceptions.

Business problem

Buyers manually rekey differently formatted supplier quotes before they can compare equivalent requirements and exceptions.

What teams see

  • Work waits between collect quotes and extract line items.
  • Owners reconstruct status from Gmail and Cloud storage.

Why it happens

  • No shared state spans Gmail, Cloud storage, ERP platform.
  • Decision and exception rules are applied inconsistently.

Why it becomes expensive

  • Capacity is consumed by coordination and rework.
  • Late exceptions weaken visibility and service quality.

Business outcomes

  • Shorter record sourcing decision cycle
  • Fewer handoff and missing-information exceptions
  • Clear ownership from collect quotes to record sourcing decision
  • Inspectable decisions and recovery

Measurable KPIs

  • Turnaround time: Elapsed time from collect quotes to record sourcing decision.
  • Manual intervention rate: Share of items needing a person outside defined review conditions.
  • Exception age: Time unresolved exceptions remain without a completed action.
  • Successful completion rate: Share of valid workflow items completing without terminal failure.

How the workflow works

  1. Collect quotes — Accept and identify the supplier quote comparison trigger. Gmail
  2. Extract line items — Execute extract line items with validated sample data and an auditable result. Gmail
  3. Normalize units — Execute normalize units with validated sample data and an auditable result. Cloud storage
  4. Map requirements — Execute map requirements with validated sample data and an auditable result. ERP platform
  5. Compare price and terms — Execute compare price and terms with validated sample data and an auditable result. Gmail
  6. Flag exceptions — Execute flag exceptions with validated sample data and an auditable result. Cloud storage
  7. Buyer review — Execute buyer review with validated sample data and an auditable result. SEIDO Review Queue
  8. Record sourcing decision — Execute record sourcing decision with validated sample data and an auditable result. SEIDO Review Queue
  9. Audit and KPI update — Persist the execution outcome, audit facts and workflow measurement events. SEIDO execution store

Integrations and ownership

  • Gmail: Provide workflow input
  • Cloud storage: Lookup and update context
  • ERP platform: Receive controlled outcome

Human responsibility: Procurement manager

Failure and recovery

Gmail is temporarily unavailable.

Retry with capped exponential backoff; preserve the run and move it to the inspectable failure queue after the limit.

Required data for extract line items is malformed or missing.

Stop downstream actions and show the missing fields, source evidence and correction action to the named reviewer.

The trigger or provider event is delivered more than once.

Return the existing execution identified by the idempotency key and do not repeat downstream business actions.

The human decision expires before completion.

Escalate to the configured substitute, retain the original request and record both expiry and reassignment.

When not to build this

  • Monthly volume is too low to justify integrating Gmail, Cloud storage, ERP platform.
  • An existing configured platform already handles supplier quote comparison with adequate ownership and reporting.
  • Reliable source data or supported API access is unavailable.
  • No business owner has authority to define the decision and exception rules.

Related workflows