Skip to content

Every shortage, recall, and hold gets an owner.

Duvo turns each shortage, recall, and stock hold into a case with an owner and an outcome, works it step by step, and writes the result back to SAP.

Every event

Becomes cases

Shortages, recalls, and holds are split into cases instead of threads in a shared mailbox.

One owner

Per case

Each case names who owns it, what closes it, and when it is due.

Written back

To SAP

Assignments, pulls, and releases end up in the system, not only in email.

The same inventory agents work availability cases at Rohlik across five markets.

Read the Rohlik story

Every shortage, recall, and hold split into owned follow-ups.

Each event becomes a set of cases: what needs to happen, who owns it, what closes it, and what was written back to SAP.

Allocation & Supply Assignment · Illustrative

Shortages, recalls, and holds become owned cases with allocation rules, evidence, and SAP updates.

Adds cases
Supply Event
Processes cases
Allocation Review
Total

24

Pending

5

Postponed

2

In progress

4

Needs input

3

Failed

0

Completed

10

Add filter
Case
Case Status
Assignment status
Scope
Decision
Exceptions
Next action
Shortage 201
Needs Input
Needs Input
Order group A
Approve assignment
1
Review
Recall 202
In Progress
In Progress
Warehouse North
Confirm pull
0
Review
Hold 203
Completed
Completed
Batch B-14
Await release
0
Closed
Shortage 204
Pending
Pending
Order group C
Escalate
1
Review
Recall 205
Postponed
Postponed
Warehouse West
Chase response
0
Review

Showing 5 of 24 cases

  1. 1

    Approval

    Exceptions pause for the named owner

    Each exception carries the source records, applied rule, recommended action, and the person authorised to decide.

  2. 2

    Assignment status

    Assignment status is visible before the action

    Each case shows the affected order or batch, the applicable priority rule, and the owner who can approve an exception.

Executing an allocation, recall, or hold decision scatters across dozens of follow-ups.

Deciding to allocate, pull, or hold takes a meeting. Executing it takes dozens of follow-up steps that land in a shared mailbox.

  • Short supply is settled thread by thread.

    When stock cannot cover demand, who gets it is decided order by order, in whatever thread is loudest that day.

  • A recall is one decision and dozens of steps.

    Pulling a product or blocking a batch means confirmations from every site, carrier, and customer holding it, and each one is easy to drop.

  • No record of who got what.

    A mailbox keeps no record of which order got the stock, which site confirmed the pull, or when the hold was lifted.

The follow-up gets chased to a close, not lost in a mailbox.

Routine steps are chased and confirmed on their own. Judgement calls reach the owner with the context attached.

  1. 01Intake

    Catch the event.

    Shortages, recall notices, and stock blocks come in from SAP, quality alerts, and the mailbox where they land today.

  2. 02Split

    Split it into owned follow-ups.

    Each affected order, site, or batch becomes its own case with an owner, a due date, and the stock and order data attached.

  3. 03Work

    Run the follow-up.

    Stock is assigned by the rules that say who gets it first, sites confirm the pull, replies are chased, and everything is logged to the case.

  4. 04Approve

    Pause where judgement matters.

    Who gets the last of the stock, whether a hold can lift, or any exception to the rules waits for the named owner.

  5. 05Update

    Write it back to SAP.

    Assignments, releases, and closed cases are written back to SAP, so the system shows what actually happened.

Planning keeps authority over every assignment.

  • Approval thresholds

    Scarce stock decisions, hold releases, and exceptions to the rules pause for the named owner before anything moves.

  • Record of every step

    Each case shows the event, the steps taken, the replies received, and the reason behind the outcome.

  • Rules set against real events

    The case types, rules, and thresholds are defined against your real shortages, recalls, and holds.

Review security and assurance

No inventory transformation project required to start.

The solution runs through SAP, the order and warehouse systems, and the mailboxes your team already uses, then leaves a clear record of every case.

Works across

SAP stock, orders, and batches, order management systems, warehouse systems, quality alerts and recall notices, allocation rules and priority lists, customer and supplier portals, email and shared inboxes

Contracted guarantee

5x ROI, guaranteed.

If measured results fall below 5x the total proposal price, the whole contract is free.

What teams ask about Allocation & Supply Assignment

  • When does Allocation & Supply Assignment run?

    A shortage, recall notice, or stock hold lands.

  • Who owns Allocation & Supply Assignment?

    Supply planning, inventory, quality, order management

  • Which systems can Duvo work across?

    The solution runs through SAP, the order and warehouse systems, and the mailboxes your team already uses, then leaves a clear record of every case. Typical sources include SAP stock, orders, and batches, order management systems, warehouse systems, quality alerts and recall notices.

  • Where does a person stay in control?

    Approval thresholds: Scarce stock decisions, hold releases, and exceptions to the rules pause for the named owner before anything moves.