Discuss your project
← All use cases

Use case · Supply Chain & Logistics

A risk.
Spotted early.
Rerouted in time.

We start from your stock rules, supplier data and typical delivery problems. Together with supply chain, procurement and IT we clarify which signals count, who may change orders and when people decide. The result is your workflow for predictive supply chain steering.

CORAProcess assistant

Your team

“Use our stock rules, the demand forecast and our suppliers' delivery notices. Create a workflow that detects supply risks every day: calculate the coverage of critical materials and compare it with confirmed delivery dates. Also evaluate delay notices from emails. When there is a risk, propose alternatives such as a second supplier or a stock transfer. Orders are only changed by material planning after review.”

CORA is drafting the process …

The description becomes the workflow

Describe once.
Run every time.

Your description becomes a daily workflow: from stock and delivery notices to an agreed countermeasure.

CORA builds the process. Your team reviews the test cases and approves it. Only then does it run for every matching event – with your permissions.

Calculate coverage · Detect risks · Propose alternatives

  1. Daily data
  2. Calculate coverage
  3. Detect risk
  4. Alternatives
  5. Approval
Discuss your project

One run in detail

How CORA catches a delay.

A day in material planning: from a delay notice by email to an approved stock transfer.

All names, numbers and values in this example are fictitious.

  1. TriggerWednesday, 6:00 am – daily run.
  2. AIEvaluate notice
    Email from supplier North: “The delivery is delayed by about ten days due to a port strike.” – matched to order BE-4410, material M-208, new date 2 December.
  3. CodeCalculate coverage
    MaterialCoverageNext inbound
    M-2086 daysin 14 days
    M-11521 daysin 5 days
    M-3429 daysin 4 days
  4. RuleAssess risk

    M-208 is below the minimum coverage and classified as critical: risk.

  5. CodeCalculate alternatives
    AlternativeCoverage afterwardsExtra cost
    Transfer from site South15 dayslow
    Second supplier20 daysmedium
    Reschedule production10 daysnone
  6. AIRecommend
    Recommendation: transfer 400 units from site South; this secures supply until the new delivery date. Also ask supplier North whether a partial delivery is possible – a draft is attached.
  7. HumanApprove

    Material planning approves the transfer and the inquiry.

  8. IntegrationApply

    Stock transfer created in the ERP, inquiry sent to supplier North.

From existing documents to a tested workflow

From existing documents
to a tested workflow

1Your documents and example cases

RecordDelivery notice LA-5520 (fictitious)
  • Delivery date
  • Quantity
ExampleShortage material M-208 (fictitious)
  • Cause
  • Action
DocumentStock rules
  • Safety stock

2Business systems and data

SystemERP
  • Orders
  • Forecast
SystemWarehouse management
  • Stock
  • Sites
RuleMinimum coverage
  • Defines urgency

3People, roles and rights

Role cardMaterial planning
Change order
Role cardProcurement
Switch supplier
Supplier contractBlocked
Read only
  1. Build process
  2. Test
  3. Approve

Running process

  1. Daily data
  2. Calculate coverage
Supply secured
  1. Keep monitoring
  2. Report
Risk
  1. Compare alternatives
  2. Planning approval
No confirmation
  1. Draft inquiry
  2. Send after approval

Process steps in detail

What AI does – and what rules, code and integrations handle.

CORA uses AI where language, context or unstructured information needs to be understood. Calculations run as tested code, limits and responsibilities as rules, system access through defined integrations. Approvals stay with people.

  • AILanguage model: understands, summarises, drafts2×
  • RuleFixed conditions, thresholds, responsibilities1×
  • CodeCalculations and models, versioned and testable2×
  • IntegrationRead and write access via MCP servers or interfaces2×
  • HumanReview, approval and decision1×
  1. 01

    Read daily data

    CORA reads stock, open orders, forecasts and delivery notices.

    Integration

    Implementation: MCP servers for ERP and warehouse management, interface to the supplier portal

  2. 02

    Evaluate notices

    Free text is translated into delivery date, quantity and reason and matched to the right order.

    AI

    Implementation: Language model reads delay notices from emails

  3. 03

    Calculate coverage

    This shows when a material will run short.

    Code

    Implementation: Coverage per material and site from stock, forecast and inbound

  4. 04

    Assess risk

    Shortfalls are flagged as a risk depending on criticality.

    Rule

    Implementation: Minimum coverage and material criticality

  5. 05

    Calculate alternatives

    Each alternative is rated by cost and effect on coverage.

    Code

    Implementation: Comparison of stock transfer, second supplier and expedited order

  6. 06

    Formulate recommendation

    The AI explains risk and alternatives and drafts an inquiry to the supplier if needed.

    AI

    Implementation: Language model with the comparison of alternatives

  7. 07

    Decide

    The responsible person selects the measure and approves inquiries.

    Human

    Implementation: Material planning, procurement when switching supplier

  8. 08

    Apply change

    Orders are only changed or transfers created after approval.

    Integration

    Implementation: Write access to order or stock transfer in the ERP

Connected systems

  • ERPreads orders and forecasts, writes approved changesvia MCP server
  • Warehouse managementreads stock per sitevia MCP server
  • Supplier portalreads delivery noticesvia interface (API)
  • Mailboxreads notices, sends approved inquiriesvia interface (API)
  • Company sign-inchecks identity and rolevia single sign-on

How we work

We start with your
actual work.

  1. 01

    Understand existing documents

    Stock rules, planning parameters, delivery notices and past shortages show us how steering works today. From them we derive critical materials, coverage limits and possible alternatives. We clarify deviating practice with material planning.

  2. 02

    Connect data and business systems

    With your IT we connect ERP, warehouse management, supplier portal and mailbox. Material number, order and supplier link the data. We define where data is read and where change proposals are stored.

  3. 03

    Assign identities, rights and roles

    Identity comes from your company sign-in. Material planning may change orders, procurement may switch suppliers, sites see their stock. The AI applies these rights and only writes after approval.

  4. 04

    Test together and go live

    From the description, documents and clarified system access, CORA drafts the process. Together with your business unit we select test cases and expected results. Testing runs without write access. Example tests: Normal supply, late delivery, demand peak, supplier without confirmation.

Your team decides on rules, AI steps and approvals. We activate the tested workflow, compare effort and results and practise the next changes in the skill workshop. Integrations, knowledge and reusable building blocks remain as the foundation for further processes.

Discuss your project

How the case
runs

Every day CORA reads stock, orders and delivery notices, evaluates delay messages and calculates the coverage of critical materials. For risks it compares alternatives and presents a reasoned proposal to material planning.

What it
produces

Coverage overview per material and site, detected supply risks, rated alternatives, draft inquiries to suppliers and approved changes in the ERP.

Where your team
decides

Material planning decides on changes to orders, procurement on switching suppliers. Inquiries to suppliers only go out after approval. Contracts remain unchanged.

More use cases

We show you where AI can take work off your hands right away.

Discuss your project