> For the complete documentation index, see [llms.txt](https://docs.pyck.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pyck.cloud/faq/faq-logistics.md). # FAQ for Logistics Managers Frequently asked questions about Pyck for logistics managers Audience: Logistics Manager ## Does Pyck cover the entire fulfillment process? Yes. Pyck provides data services for core fulfillment processes including **receiving** (inbound), **inventory management**, and **picking** (outbound). On top of these data services, the workflow system (powered by [Temporal.io](https://temporal.io)) can implement any fulfillment process — shipping, returns, bundling, and more. The key principle: as long as the underlying data service exists, workflows can orchestrate any process you need. If your fulfillment requirements go beyond the currently available data services, our team will support you in adding them. ## Can existing WMS processes be gradually replaced? Yes. Pyck supports a step-by-step migration approach as long as your existing system provides an API for data exchange. This allows both systems to coexist during the transition period, with data flowing between them until the full migration is complete. ## How can data structures be extended? Every entity in Pyck has a JSON `data` field that is validated against a [DataType](/graphql-api/types/datatype.md) — a JSON Schema you define. This lets you add arbitrary structured fields to customers, items, suppliers, orders, and more without changing the underlying database schema. For example, you could define a DataType for items that includes fields like `color`, `size`, `brand`, and `hazmat_class` — all validated automatically by the API. ## Is there a test instance or sandbox? Customers can create as many tenants as needed within Pyck. These tenants can serve as separate environments — for example, development, staging, and production — or any other separation your workflow requires. Each tenant is fully isolated, so testing in a dev tenant has no impact on production data. --- # 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://docs.pyck.cloud/faq/faq-logistics.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.