Enter workspace

Workflow · Trade Readiness · Market Entry Readiness

Market Entry Readiness

For a selected market: what appears ready, what is missing and what remains unresolved — based on available evidence and the market’s known requirements.

Start — not yet availableAbout this capability
Foundation — in development

Who it is for — and what you will need

Exporters preparing a specific product for a specific destination market.

  • Company + product + origin + destination market
  • Product classification details where known
  • Existing market documentation

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. Product & market

    Company, product, origin and destination selected.

    in development
    Stage details
    What OrenAtlas already knows
    Company, product, origin from canonical records
    What you provide
    Destination market (required) — Determines the requirement universe
    Evidence used
    No evidence collected at this stage.
    What happens
    Product/market resolve canonically
    If something is missing
    Unknown product details become data tasks.
    Done when
    Product + destination fixed.
    What comes next
    Market-entry case.

  2. Classification

    Product classification and relevant market/import/licence requirements resolved.

    in development
    Stage details
    What OrenAtlas already knows
    Known classification data (HS context, product attributes)
    What you provide
    Classification details (if applicable) — Confirm/supply classification where sources cannot
    Evidence used
    Classification sources, Product specifications. Reuse: Classification bound to the product record.
    What happens
    Classification recorded with basis
    If something is missing
    Unclassifiable → specialist task, not a guess.
    Done when
    Classification recorded.
    What comes next
    Product classification.

  3. Evidence

    Product and company evidence mapped against requirements; Evidence Core reused.

    in development
    Stage details
    What OrenAtlas already knows
    Product + company evidence mapped against requirements (Evidence Core reused)
    What you provide
    Nothing — OrenAtlas assembles this stage.
    Evidence used
    Evidence Core inventory. Reuse: Full reuse with subject/market/freshness re-validation.
    What happens
    Per-requirement evidence state
    If something is missing
    Missing items become owned, actionable tasks (request evidence / assign owner) — never a dead warning.
    Done when
    Coverage mapped.
    What comes next
    Requirement coverage.

  4. Route & commercial

    Logistics/route requirements, buyer documentation expectations, specialist dependencies.

    in development
    Stage details
    What OrenAtlas already knows
    Known route context and partner dependencies
    What you provide
    Logistics/commercial specifics + specialist/partner tasks (if applicable) — Who needs to act on what before entry preparation completes
    Evidence used
    No evidence collected at this stage.
    What happens
    Dependencies owned
    If something is missing
    Unowned dependencies visibly unowned.
    Done when
    Dependency plan set.
    What comes next
    Route/commercial readiness picture.

  5. Review

    Human review of readiness and gaps.

    in development
    Stage details
    What OrenAtlas already knows
    Final-review screen: requirement coverage, evidence states, dependencies, open items
    What you provide
    Readiness review (required) — Human confirmation of what appears ready, what is missing, who must act
    Evidence used
    No evidence collected at this stage.
    What happens
    Explicit confirmation before report generation
    If something is missing
    Open items acknowledged in the review.
    Done when
    Readiness review recorded.
    What comes next
    Reviewed readiness state.

  6. Market Entry Report

    Versioned readiness report. No guarantee of market access.

    in development
    Stage details
    What OrenAtlas already knows
    Everything above
    What you provide
    Nothing — OrenAtlas assembles this stage.
    Evidence used
    No evidence collected at this stage.
    What happens
    Versioned; action plan present; no guarantee language
    If something is missing
    Missing items listed with owners.
    Done when
    Versioned Market Entry Readiness Report + action plan generated.
    What comes next
    Market Entry Readiness Report (versioned) → Trade Rescue / Sourcing / Nordic Bridge.

What you receive: Market Entry Readiness Report

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

product/market scopeclassificationrequirement coverageevidence statesroute/commercial readinessgapsspecialist dependencieshuman review

Current state

Foundation — in development.

Specified end to end; not yet implemented as a case workflow.

Where this hands off next

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

Foundation — in development

Trade Rescue

Unblock a stalled case: turn its blockers into an owned, dated action plan, resolve what can be resolved, and return the result to the originating case.

View workflow →Partially live

Sourcing Workspace

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

View workflow →Partially live

Nordic Bridge Case

Take a Nordic company from identification to a managed international market-access case — on the shared platform, never a second system.

View workflow →