# Packing and printing

{% hint style="info" %}
This version is currently available as a [Beta release](/documentation/apps/mobile-app-availability.md) via the Google Play Store. To access it, you need to be enrolled in our beta program. If you'd like to participate, [contact us using our Support portal](https://ocfulfillment.atlassian.net/servicedesk/customer/portal/1/group/11/create/39) to request access.
{% endhint %}

Packing starts when a pack job is selected from the order list or as the next step after picking is completed.

{% hint style="info" %}
For general information about packing and pack jobs, refer to the [packing documentation](/documentation/by-pillar/store-operations/packing.md).
{% endhint %}

## Preparation

After a pack job is opened, the app might display preparatory steps, depending on the configuration. These steps provide context for packing before items are assigned to a parcel.

Preparation can include optional guidance, such as information about previously used containers or locations. This supports orientation, especially if items were prepared in earlier process steps.

If more than one parcel type is available, the user selects the appropriate type during preparation. If only one parcel type exists, it is applied automatically. At least one parcel type must be configured. Otherwise, packing can't be started.

The preparation step also provides a read-only overview of all items in the pack job. This overview serves as a reference list and does not require user interaction.

<div><figure><img src="/files/yTqOxt58xOIAJlo7v0To" alt="" width="188"><figcaption></figcaption></figure> <figure><img src="/files/I4GaJ8BoYDkpzN4k7xdd" alt="" width="188"><figcaption></figcaption></figure> <figure><img src="/files/k5cYz35IozFBPkCyRAJa" alt="" width="188"><figcaption></figcaption></figure></div>

{% hint style="info" %}
Parcel types used during packing are based on operative container types with `allowedOperativeTypes` set to `PACKING_TARGET` or `PACKING_SOURCE`. They define the characteristics of a container that can be reused across multiple processes. For more information, see [Operative container types article](/documentation/by-pillar/store-operations/packing/pack-job-endpoints.md).
{% endhint %}

## Packing

### Packing items into a parcel

Packing is performed sequentially, with items assigned to one parcel at a time. If multiple parcels are required, the current parcel must be completed before packing can continue with the next one.

Items are assigned to a parcel either by scanning or by manual selection.

If additional context is required during packing, such as order-related information, it can be accessed via the options menu.

Completing a parcel transitions the user directly to the next steps in the flow, including requesting the shipping label and printing required documents.

<figure><img src="/files/NEu1YDT5OugOaaytRwAk" alt="" width="188"><figcaption></figcaption></figure>

### Requesting a shipping label

After a parcel is completed, a shipping label request is triggered automatically.

Additional information may be required before the label can be requested.\
This information can be defined by the carrier configuration or by the Carrier Country Service Mapping ([CCSM](/documentation/by-pillar/store-operations/carrier-management/carrier-features-and-requirements.md#carrier-country-service-mapping-ccsm)) and can apply to the parcel or to individual items.

If information is already available, it is prefilled. Missing information must be provided before the process can continue. Carrier services (for example, pickup time or signature on delivery) are requested only if they are defined in the CCSM.

If the label request is successful, the label is available for the next steps. If no additional information is required, this step is skipped.

<div><figure><img src="/files/aq42G0JCk7g1WLBbBlWs" alt=""><figcaption></figcaption></figure> <figure><img src="/files/CvtdDCueFkBZ5qbtEesg" alt=""><figcaption></figcaption></figure> <figure><img src="/files/rcq0Tc75aa84PlkrJVib" alt=""><figcaption></figcaption></figure> <figure><img src="/files/CjdEkaIXO6CP9ySU2txA" alt=""><figcaption></figcaption></figure></div>

### Printing documents

The printing step is part of the packing flow for the current parcel and is shown after the label request has been triggered.

Depending on the configuration, different documents can be available for printing:

* Shipping label
* Return label
* Slipping note
* Return note
* Customs document
* Additional external documents

The shipping label (send label) is mandatory for handing over the parcel to the carrier. If it is the only required document, the user must wait until it is available. If other documents are available, they can be selected and printed while the shipping label is still pending.

Users can select a single document or multiple documents in bulk. Printing is possible as soon as at least one document is selected.

If a specific printer (for example, a label printer) is configured, available printers are displayed for selection. The Android system print dialog is always available and allows printing via Wi-Fi or network printers configured on the device.

<div><figure><img src="/files/QDdzAfRSncwPAy25g75Z" alt="" width="188"><figcaption></figcaption></figure> <figure><img src="/files/OLwjLWnGo9Cf29Zn0PCu" alt="" width="188"><figcaption></figcaption></figure></div>

### Completing packing

A pack job can only be completed once all items have been packed and assigned to a parcel. Until then, the finish action remains inactive.

After completion, the next step in the order process is available, or the user can return to the order list to start the next job.

<figure><img src="/files/MfPHuKddHHqJ3uolcSeG" alt="" width="188"><figcaption></figcaption></figure>

## Special cases

### Repacking items

Repacking is possible only if not all items in the pack job are packed, and it applies only to an existing parcel.

Users can add items to the parcel or exchange items by removing existing ones while adding new ones. Removing items without adding new ones is not supported.

If a shipping label already exists for the parcel, the user is informed that the label becomes invalid and must be disposed of.

As part of repacking, the existing parcel is discarded, and a new parcel is created with the updated item composition. Depending on the configuration, a new label request may be triggered, and additional shipping information may be required again.

<div><figure><img src="/files/EQlMZcaxwtkUdHbA9CDz" alt=""><figcaption></figcaption></figure> <figure><img src="/files/1rgNMrdl4HJREpWkUo3J" alt=""><figcaption></figcaption></figure> <figure><img src="/files/5k52JLdKwMuD5MJHESkp" alt=""><figcaption></figcaption></figure> <figure><img src="/files/fvdaLzYYCWXrl1fZpPo3" alt=""><figcaption></figcaption></figure> <figure><img src="/files/dkbkDIWgaosQdbyRpLte" alt=""><figcaption></figcaption></figure> <figure><img src="/files/qFQTFtn652mOi8EZfPzn" alt=""><figcaption></figcaption></figure></div>

### Deleting a parcel

A parcel can be deleted at any time during packing after the first parcel has been created.

Deleting a parcel is especially useful when items are already packed into one or multiple parcels, and a parcel needs to be modified, for example, due to rearrangement, weight, or cost considerations.

If a shipping label already exists, the user is informed that the label becomes invalid and must be disposed of. No new label is created as part of this action.

<div><figure><img src="/files/5kzOu21CGkUxvmL1WEzJ" alt="" width="188"><figcaption></figcaption></figure> <figure><img src="/files/TJQKWfQZN9T9SeEwygBm" alt="" width="188"><figcaption></figcaption></figure> <figure><img src="/files/OR4RxpDmE5HayoOHacDb" alt="" width="188"><figcaption></figcaption></figure></div>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.fulfillmenttools.com/documentation/apps/store-operations-app-beta/beta-packing-and-printing-android-app.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.