> For the complete documentation index, see [llms.txt](https://hub.equipme.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.equipme.io/pro/fulfillment/picking-production-shipping.md). # Picking, production and shipping The "Picking", "Production" and "Shipping" work lists: withdraw goods from the warehouse, work through production steps, create parcels, send shipments and maintain shipment tracking. **Path:** "Fulfillment" → "Picking" / "Production" / "Shipping" These three lists are the workstations for physical provisioning. Which steps a position goes through is defined by the service's **service mapping** (see [Service portfolio](/pro/portfolio/service-portfolio.md)). Equipme Pro moves each position automatically into the matching list: ``` Confirmed → Picking (withdraw stock items) → Production (complete steps) → Shipping (send parcel) → Completed ``` If a step is missing in the mapping, it is skipped. ## When the lists are visible The three menu items appear when both conditions are met: 1. You are allowed to process positions (role "Fulfillment Operator", "Fulfillment Manager" or "Administrator"). 2. Your organization uses warehouse management, i.e. at least one warehouse has been created or you have access to the warehouse (e.g. as "Warehouse controller" or "Warehouse Manager"). You set up the warehouse under [Warehouse](/pro/warehouse.md). Without this, you process all positions directly in [Open positions](/pro/fulfillment/open-positions.md). All three lists are sorted by "Planned provision" in ascending order, so the most urgent item is at the top. Clicking a row opens the detail view of the service instance. ## Picking The list shows all positions with the processing status "Ready for picking": the required stock items are available and reserved for the position. **How to withdraw the goods:** 1. Click the position. On the "Order" tab, the "Picking" section is expanded. 2. The table shows "Service name", "Name", "Part number", "Storage location" and "Order number" for each article. 3. Under "Stock withdrawal" you enter the attributes of the withdrawn goods, e.g. the serial number. Required fields are marked with \*. 4. Click "Confirm withdrawal". "Picking registered" then appears with the next processing step, e.g. "Continue to production", "Continue to dispatch", "Continue to service completion" or "Next picking". Withdrawals already done are listed under "Stock withdrawals" with "Picked by" and "Picked on". An overview of all withdrawals is under [Stock withdrawals](/pro/warehouse/stock-withdrawals.md). {% hint style="warning" %} If someone manually advances the status of a position in "Ready for picking", the stock withdrawal is skipped. The reserved article is released again without being assigned to the service. {% endhint %} ## Production The list shows positions with the processing status "Ready for production" as well as workplace services with "Upgrade required". Production steps are work steps from the service mapping, e.g. "Set up device" or "Install software". On the "Order" tab you find the "Production steps" section with "Name", "Part number", "Status", "Processed by" and a comment. If a link is stored on the step (e.g. to instructions), you open it via the icon. | Button | Effect | | ------------------ | --------------------------------------------------------------------------- | | "Start" | You take over the step and are entered as the processor. | | "Remove processor" | Releases the step again. | | "Continue" | Resumes a paused step. | | "Complete" | Confirms the step ("Production step completed"). Processing then continues. | When all steps are done, the position moves to shipping or is completed. A dialog offers you "To shipping" or "Continue production". {% hint style="info" %} If the service has a "Pending dependency", you can't complete the steps yet: the other service (e.g. the base service) has to be provided first. {% endhint %} ## Shipping The list shows orders, returns and delivery call-offs with the status "Ready for delivery" and "Delivery requested (outgoing)". Pre-orders don't appear here, because they are stored and only shipped via a delivery call-off. ### Create parcels There are two ways: * **"Ship selected"**: select positions and click. You can only ship positions of the same customer together that have not yet been shipped. If they have different delivery addresses, you choose the destination address in the "Select shipping address" dialog. * **"Create parcel"** (without a selection): a dialog lists all open positions ready for shipping. You choose the ones you want. Only positions with the same delivery address that have not yet been shipped are possible. Alternatively, open a position and click "Prepare shipment" in the "Shipping" section. ### Send shipment The "Send shipment" page has several sections: 1. **"Sender"**: the "Sender address", e.g. your warehouse. 2. **"Recipient"**: "Recipient (name)", "Company name", "Email", "Phone" and "Reference text, e.g., order no.". Pro suggests possible recipients for the delivery address. 3. **"Shipping items"**: for each position you choose which components of the bill of materials are stored as information on the parcel. The selection appears on the delivery note and packing list. Reserved stock items are preselected. With "Add" you add further open positions for the same location; with "Remove position from shipment" you take one out. 4. **"Shipping details"**: "Shipping carrier", "Shipment number", "Shipment tracking (link)", "expected delivery date", "Delivered on", "Status" and "Comment". With **"Send shipment"** you save the parcel. The position then counts as shipped. If it runs via the service mapping, it is then completed automatically. ### Shipping integration If a shipping integration is set up for your organization, you can send the parcel directly through it (switch in the shipping details). Then: * The recipient name is limited to 25 characters. * Under "Shipping items" you choose which attribute information (e.g. serial numbers) is transmitted to the integration and printed on the accompanying documents. * Status, expected delivery date and shipment tracking are updated automatically as soon as you complete the shipment in the integration. ### Outgoing parcels Via **"Outgoing parcels"** in the shipping list you see all parcels with "Reference number", "Recipient", "Delivery address", "Status", "Shipment number", "Created on", "expected delivery date" and "Delivered on". Use the search to find, for example, a shipment number. Clicking a parcel opens "Update package". There you maintain status, shipment number, tracking link, dates and comment. Possible parcel statuses: "new", "Ready to ship", "Picked up", "In transit", "delayed", "delivered", "Acceptance refused", "Back to sender", "Failed", "cancelled". For parcels sent via the shipping integration, there are additionally: * **"Update status"**: fetches the current state from the integration. * **"Transfer again"**: cancels the parcel with the shipping carrier and resubmits it with the same positions. {% hint style="info" %} If you change values manually on a parcel from the shipping integration, they are overwritten at the integration's next update. {% endhint %} ## Frequently asked questions **Why don't I see the "Picking", "Production" and "Shipping" menu items?** You lack the processing role in fulfillment, or your organization doesn't use warehouse management. See [When the lists are visible](#when-the-lists-are-visible). **Why is "Ship selected" grayed out?** The selected positions belong to different customers, or one of them already has a parcel. **A position doesn't show up in shipping. Why?** It is not yet "Ready for delivery" (e.g. because picking or production is missing), it is a pre-order, or it has no delivery address. **Does the customer see the shipment tracking?** The customer sees the delivery status of their order in the customer portal (see customer guide). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://hub.equipme.io/pro/fulfillment/picking-production-shipping.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.