> For the complete documentation index, see [llms.txt](https://vu-custom.gitbook.io/vu-custom/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vu-custom.gitbook.io/vu-custom/vu-oms/factories.md). # Factories ## What is a Factory? A **Factory** is used to group, segment, and route orders. Rather than strictly representing a physical manufacturing site with inventory tracking, a Factory acts as a **logical bucket** within the system to manage workflow and data visibility. From the system's perspective: * **It is a grouping mechanism:** It is a way to place orders into specific "buckets" based on production location or any reason to group a set of orders together. * **It is a routing destination:** Once orders are imported, routing logic can be applied to place orders to certain factories based on a criteria of choice. Examples include product category, decoration techniques, or quantity. * **It is not about inventory:** VU does not track physical stock or inventory within a factory. ### Key Functions of a Factory #### **1. Order Segmentation & Routing** The primary role of a Factory is to serve as the destination for **Order Routing Rules**. * Using SKU matching or Regex patterns, the system determines which orders belong in which "bucket." * This allows a brand to separate orders by category, production type, or fulfillment partner without manual intervention. #### **2. Access Control and Visibility** Factories are the primary method for controlling what operators can see within the OMS. This is critical for brands working with multiple partners or locations. * **Restricted Views:** You can restrict a user's access so they only view orders assigned to their specific Factory. * **Operator Focus:** Operators within a single Factory bucket do not see orders that don’t belong to them, ensuring data privacy and reducing clutter on the production dashboard. #### **3. Factory-Specific Documents & Criteria** While a Factory is a logical group, it allows for specific localized configurations. Each Factory can be set up to generate its own specific documentation, such as: * **Travelers:** Instruction sheets that accompany an order through its lifecycle. * **Labels:** Specific shipping or identification labels tailored to that particular workflow. #### Summary When setting up a Factory, the goal is to define a clear boundary for **where orders go** and **who has permission to see them**. By treating a Factory as a bucket for segmenting orders rather than just a physical location, you can more effectively manage complex routing workflows and multi-operator production environments. --- # 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://vu-custom.gitbook.io/vu-custom/vu-oms/factories.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.