> 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/documentation/fulfillment/picking.md). # Picking Picking is where goods leave your warehouse and become the customer's. The physical part is straightforward: fetch the article, record which one you took. What makes it worth doing carefully is that this is the only moment where a device gets its identity in the system. Everything that happens to it later, an exchange, a return, an audit, relies on what you enter here. A position arrives here whether the article was already in stock or was bought in for this order. Once the goods are in the warehouse, the two are indistinguishable. Picking is not a list you act on. Open a position and do the work there. ## Taking goods out of stock The Picking block on the position tells you where the article is and what has to be recorded. The **storage location** is unambiguous because of batch purity: one location holds one batch, so there is never a question of which of several identical devices you are meant to take. **Stock withdrawal** is where you record the device you actually took. Those fields are not fixed. They come from the attributes defined on the product, so a notebook might ask for a serial number while a phone asks for a serial number, an IMEI and a PIN. A field marked with a star is mandatory, and **Confirm withdrawal stays disabled until it is filled**. That is deliberate. A device without a recorded serial number cannot be identified later, which means an exchange cannot be traced to the right unit and an audit has nothing to check against. If a field you need is missing, or one you do not need is blocking you, that is configured on the product in Product master data. It cannot be changed here, and it should not be: the same product has to be recorded the same way every time. {% @arcade/embed url="" flowId="F1BkwDv0MlkPGoBr2rEM" %} ## What confirming actually does Three things change at once, and only one of them is visible. **The position moves on.** To [Production](/documentation/fulfillment/production.md) if the mapping defines production steps, otherwise to [Shipping](/documentation/fulfillment/shipping.md). A dialog offers to take you straight there rather than back to the list, which is worth using if you are working through a queue. **A service component is created.** It carries the serial number you entered and a link to the purchase order the device came from. This record stays with the device for the rest of its life and is what every later exchange or return refers back to. It is also where you look when you need to know which specific unit went out. **The stock is gone.** Not reduced to zero, gone: the batch disappears from the warehouse list entirely. The withdrawal is logged in [Stock withdrawals](/documentation/warehouse/stock-withdrawals.md) with your name, and the storage location stays and can be reused. ## If a position is not here Positions appear in Picking only once the goods are physically in stock. A position that is missing is almost always waiting somewhere earlier in the chain: | It is waiting for | Look in | | -------------------------- | --------------------------------------------------------------- | | A released mapping | Portfolio Management, the service, Mapping | | A purchase order | [Order proposals](/documentation/purchasing/order-proposals.md) | | The distributor to deliver | [Goods receipt](/documentation/warehouse/goods-receipt.md) | Dropshipping positions never appear here at all. The distributor ships straight to the customer, so nothing passes through your warehouse and there is nothing to pick. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://hub.equipme.io/documentation/fulfillment/picking.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.