Workflow · Sourcing Workspace · Sourcing Workspace

Sourcing Workspace

Move from a requirement to a documented sourcing decision: match, shortlist, close evidence gaps, negotiate in a controlled room, decide.

Partially live

Who it is for — and what you will need

Buyers running a real sourcing process; suppliers participating in it.

  • The requirement (product, specification, origin/destination, volume, timeline, evidence and commercial requirements)
  • Responses and evidence as the process advances

Anything OrenAtlas already knows is prefilled with its evidence state — you are asked only for what is missing or unresolved.

How it works

6 stages. Save and resume at any point; each stage keeps its evidence attached to the exact item it supports.

  1. Requirement

    Captured once as a canonical Requirement — reused by every later stage.

    Tell us what you need → (live today)
    Stage details
    What OrenAtlas already knows
    Buyer context; prior requirements as templates
    What you provide
    What / where / when / how much (required) — The canonical Requirement every later stage reuses · Evidence + commercial requirements (if applicable) — What suppliers must evidence; disclosed progressively
    Evidence used
    No evidence collected at this stage.
    What happens
    Saved as canonical Requirement (requirement_id) — never retyped downstream
    If something is missing
    Optional specifics stay open, visible.
    Done when
    Requirement saved.
    What comes next
    Canonical Requirement (requirement_id).
  2. Match & shortlist

    Requirement-specific matching with explained evidence coverage — never universal quality scoring; buyer builds a shortlist preserving the evidence snapshot.

    Requirement matching → (live today)
    Stage details
    What OrenAtlas already knows
    Requirement-specific matches: supplier, why relevant, evidence coverage, gaps, constraints — no universal quality ranking
    What you provide
    Shortlist selections (required) — One-click shortlist preserving requirement + reason + evidence snapshot
    Evidence used
    Match evidence snapshots. Reuse: Snapshots preserved with the shortlist — later evidence changes never silently rewrite the shortlist basis.
    What happens
    Matches explained; snapshot preserved per shortlist entry
    If something is missing
    Thin match sets shown honestly with widening options.
    Done when
    Shortlist built.
    What comes next
    Shortlist with evidence snapshots.
  3. Evidence

    Missing evidence requested from shortlisted suppliers; lifecycle tracked.

    Request evidence → (live today)
    Stage details
    What OrenAtlas already knows
    Per-candidate gaps with request drafts
    What you provide
    Evidence requests (if applicable) — Request exactly the missing items; lifecycle tracked
    Evidence used
    Supplier submissions against requests. Reuse: Submissions attach to the requesting gap and flow into canonical evidence.
    What happens
    Requests item-specific
    If something is missing
    Waiting-on-supplier visible per candidate.
    Done when
    Requests resolved or accepted open.
    What comes next
    Updated candidate evidence.
  4. Deal Room

    Private room tied to requirement, buyer, supplier and shared canonical products — conversation with durable threads, messages linkable to products, evidence requests, RFQs, quotes, LOIs, contracts and tasks. Never chat-only.

    in development
    Stage details
    What OrenAtlas already knows
    Room tied to requirement + buyer + supplier + shared canonical products; tabs: Overview, Conversation, Products, Evidence, Documents, Commercial, Tasks, Decision
    What you provide
    Conversation + shared products (if applicable) — Fast conversation with durable threads; messages linkable to product/evidence request/RFQ/quote/LOI/contract/task — never chat-only; suppliers share canonical Product records, never a copied catalog
    Evidence used
    Room-shared documents, Linked canonical evidence. Reuse: Room links to canonical records; nothing duplicated into the room.
    What happens
    Buyer-private material never exposed to supplier by convenience
    If something is missing
    Empty tabs explain their purpose and next action.
    Done when
    Room active with participants.
    What comes next
    Deal Room (deal_room_id).
  5. Commercial terms

    Structured RFQ → versioned quotes (never overwritten) → comparison keeping commercial assessment distinct from evidence truth → LOI lifecycle (Agreed is internal, not e-signature) → contract lifecycle (e-signature is a later provider decision).

    in development
    Stage details
    What OrenAtlas already knows
    RFQ prefilled from the Requirement (product/quantity/destination/requirements never retyped)
    What you provide
    RFQ adjustments + send (required) — Structured RFQ tied to requirement/products, previewed before sending · Quotes (draft/submit/revise) (required) — Structured: product, quantity, unit, price, currency, MOQ, Incoterm, lead time, payment terms, valid-until — Quote v1 → v2 → v3, historical versions never overwritten · LOI + contract steps (if applicable) — LOI: Draft → Preview → Share → Changes requested → Revised → Agreed → Superseded/Cancelled (Agreed ≠ e-signature). Contract: Draft → Review → Revision → Internal agreement → Executed externally; versions retained
    Evidence used
    No evidence collected at this stage.
    What happens
    Preview-before-send on RFQ/quote/LOI/contract shares; comparison keeps commercial terms, evidence coverage, gaps and conditions SEPARATE — never one blended score
    If something is missing
    Unquoted candidates visible as waiting.
    Done when
    Commercial position agreed internally or explicitly parked.
    What comes next
    Versioned commercial trail (RFQ, quotes, LOI, contract states).
  6. Decision

    Documented Sourcing Decision Record: participants, evidence considered, terms, open risks, conditions, audit trail.

    in development
    Stage details
    What OrenAtlas already knows
    Decision preview: evidence considered, commercial terms, open risks, conditions, participants
    What you provide
    Decision + rationale (required) — The documented decision with why, conditions and risks
    Evidence used
    No evidence collected at this stage.
    What happens
    Versioned; participants + date + audit trail recorded; next actions present
    If something is missing
    Open risks recorded as conditions.
    Done when
    Versioned Sourcing Decision Record generated.
    What comes next
    Sourcing Decision Record (versioned) → Due Diligence / Trade Secure follow-ups; evidence and history reusable.

What you receive: Sourcing Decision Record

A versioned result — not just a PDF. It preserves:

requirementshortlist with evidence snapshotsevidence request trailcommercial terms consideredquote/LOI/contract versionsdecision + participantsopen risks and conditionsaudit trail

Current state

Partially live.

Requirement capture + explained matching are live (/match, seafood journey) and the workspace shell exists (/dashboard); shortlists, deal rooms, RFQs, quotes, LOIs and contracts are specified but not yet implemented — the Sourcing Workspace is more than /match, and nothing here pretends otherwise.

Where this hands off next

Your case context (company, product, market, requirement) travels with you — nothing is re-selected.