MyWork24 Knowledge Base
Article

Pack Containers

Edit

Pack Containers

Packing lets you group several inventory items into one container — a pallet, a box, or a wrap — so they can be moved and tracked as a single unit. When you move the container, everything inside it moves with it. Containers can even be nested (a packed box placed onto a pallet).

You pack from My Inventory, using stock you are holding at your own location.

Pack containers lifecycle: loose stock is packed into a serialized container, which you can then move (its contents travel with it) or unpack (the items become loose again). Every step is audited.

What is a container?

A container is a real packaging item with its own serial number, shown as PKG-…. There are two kinds:

  • Reusable (e.g. a pallet) — drawn from your empty-pallet stock when you pack, and returned to stock when you unpack.
  • Consumable (e.g. bubble-wrap or a throwaway box) — created on the spot when you pack, and destroyed when you unpack.

Each container is always one physical unit.

How to pack items

  1. Open My Inventory.
  2. Tap Pack to turn on pick mode — a checkbox appears on each card.
  3. Tick the items you want to pack together. (You can also tick an existing container to place it inside another one.)
  4. Tap Pack on the action bar.
  5. Choose the container:
    • Consumable — pick a wrap/box product; it is created on demand.
    • Reusable from your stock — pick a pallet you already hold empty stock of.
  6. Confirm. The selected items are now inside the container, which appears as a single card labelled Container · PKG-….

Items must be loose (not already inside another container) and at your own location to be packed.

Viewing a container

A container card shows its PKG-… serial and a View contents expander listing what is inside (read-only). The packed items no longer appear as separate loose cards — they travel with the container.

Moving a container

Use Move on the container card to relocate it to another bin in the same warehouse. Everything inside moves with it, and every item keeps its identity and serial numbers. The container stays packed.

Containers cannot be moved to a different warehouse, and you cannot pull a single item out on its own — unpack it first.

Unpacking

Use Unpack on the container card to peel off the outer layer:

  • The items inside become loose stock again at the location.
  • A reusable pallet is returned to your empty-pallet stock; a consumable wrap is destroyed.
  • If a packed box was nested inside, it simply becomes a top-level container still holding its own contents — unpack it again to go deeper.

Everything is audited

Every pack, move and unpack writes a stock-movement record for each item — capturing who did it, what changed, and when. The container's serial ties its whole history together, so you can always trace where stock went.


For developers & integrations (REST API)

The same packing actions are available over the rich REST API under /rest/v2/containers, so the mobile app and AI agents can pack, move and unpack as the signed-in user. There is no special permission — you see and act on exactly the containers you could in My Inventory (scoped to the areas you can access). An out-of-scope id returns 404.

Read

  • GET /rest/v2/containers — list the top-level containers in your accessible areas (paginated).
  • GET /rest/v2/containers/{id} — one container with its full contents tree.

Write — each accepts an Idempotency-Key header, so a retry never moves stock twice:

  • POST /rest/v2/containerspack. Body { "rowIds": [1,2], "containerProductGuid": "…" } to create a new container, or { "rowIds": [1,2], "existingContainerId": 123 } to add to an existing one. Returns the container + contents.
  • POST /rest/v2/containers/{id}/unpackunpack one layer; returns the released rows.
  • POST /rest/v2/containers/{id}/relocatemove. Body { "destinationLocationId": 456 } (same warehouse, an area you can access).

Every write routes through the audited stock engine (one movement record per item). The full request/response shapes are in the API's OpenAPI document — GET /rest/v2/openapi.json, tag Containers.

Related articles