> For the complete documentation index, see [llms.txt](https://help.urbanpiper.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.urbanpiper.com/store-manager/prime-web/scan-and-pack-workflow.md). # Scan and Pack Workflow {% embed url="" %} **Why Use Scan and Pack?** Online orders leave little room for packing errors — a missing item means a bad customer rating, a refund request, and a dent in your platform metrics. The Scan and Pack workflow eliminates that risk by making the packing process physically verifiable, not just assumed. Here's what it solves: **Accuracy — pack the right items, every time** When Print Labels are enabled, each item in an order gets its own printed barcode label. Kitchen staff scan each label before the order is sealed, creating a physical checkpoint that catches misses before the bag is closed — not after the rider has left. No more relying on memory or visual checks during a busy rush. **Speed — keep riders moving, improve your platform standing** The moment all items are scanned and marked ready, the order status updates automatically and moves to **Waiting for Pickup**. Riders aren't left waiting for a manual food-ready confirmation, which tightens your prep-to-dispatch time. Faster turnarounds translate directly to better delivery metrics on platforms like Swiggy and Zomato — lower cancellations, better ratings, and improved ranking. > **Note:** Scan and Pack needs to be activated by the UrbanPiper team before it's available in your account. Reach out to support to get it enabled. *** **Setting It Up** **Step 1: Enable the Scan and Pack Module** 1. Contact the UrbanPiper support team to request activation. 2. Once enabled, go to **All Apps → Company Settings → Internal → Module**. 3. Search for **Scan and Pack** and activate it. **Step 2: Activate the Barcode Scan Flow** 1. Go to the **Live Orders** section. 2. Find the **Scan Barcode Flow** setting and ensure it is enabled. *** **How It Works** **With Print Labels (recommended)** When the **Print Label** toggle is on in the KDS, a separate barcode label is printed for each individual item in the order. Kitchen staff scan each label as items are packed — the order only moves to ready once every item is accounted for. **Without Print Labels** If Print Labels are turned off, a single order-level barcode is printed on the bill instead. Scanning that barcode marks the entire order as food ready in one step. *** **Testing the Workflow** 1. Head to the **Live Orders** section and acknowledge an incoming order. 2. A KOT and a barcoded bill are generated automatically. 3. Go to the **KDS** — the order will appear there. 4. Scan the barcode(s) using your connected scanner to mark the order as ready. 5. The order moves to **Waiting for Pickup**, ready for rider collection.
--- # 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://help.urbanpiper.com/store-manager/prime-web/scan-and-pack-workflow.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.