> ## Documentation Index
> Fetch the complete documentation index at: https://pelusium.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# After delivery — SSU consolidate

> Final step when cargo lands in your character slot but the in-game SSU UI shows primary storage only.

# After delivery — SSU consolidate

**On-chain delivery** (`execute_deliver`) can finish successfully while goods sit in your **per-character** inventory slot under the drop-off **SSU**—the same situation Datacore sometimes shows as a second **“Users storage”** row for the same assembly. The **in-game SSU panel** often lists only **primary** (anchor) storage, so your cargo can look “missing” until you move it.

This page is the **last step in the end-to-end delivery story** for many players: **after** the courier has delivered and escrow has paid out, **you** (the recipient who is also the SSU anchor, or whoever holds both caps) run one more Pelusium action to make stacks **usable in the SSU UI**.

<Note>
  On preview deployments, the consolidate screen can still show you the fields and scan flow, but the final consolidate signature may be paused along with other on-chain actions.
</Note>

## What you do in the Pelusium app

1. Open **SSU consolidate** in the web app: path **`/contracts/ssu-consolidate`** (also linked from the home page and from **[Shipping & freight jobs](/shipping)**).
2. Connect the wallet that owns the **EVE Frontier character** tied to that SSU.
3. Fill **Character**, **drop-off SSU**, and both **OwnerCap** objects (the app can detect many of these when RPC works—same pattern as **[SSU & Pelusium setup](/ssu-pelusium-setup)**).
4. **Scan character slot** to list stacks from your **per-slot** inventory on that SSU; pick a row (item names come from the same catalog as the shop when available).
5. Sign the **consolidate** transaction. It moves **one stack at a time** from your character slot into the SSU **primary** bucket (same assembly, same `type_id` / quantity rules as the world contracts).

Repeat for each stack you need in primary.

## What this is not

* **Not** part of the Pelusium **Move** `freight_contract` entrypoints—escrow and job state are already final after **Deliver**.
* **Not** a substitute for **[SSU & Pelusium setup](/ssu-pelusium-setup)** authorization on pickup/drop-off SSUs; you still need that for **pickup** and **deliver** to succeed.
* **Not** guaranteed to be needed on every network or every client build: if the game always shows both buckets, you may skip this. Use it when **your** UI or Datacore shows the split.

## See also

* **[Shipping & freight jobs](/shipping)** — Full job lifecycle (create → accept → pick up → deliver).
* **[Troubleshooting](/troubleshooting)** — Wallet, network, and explorer checks.