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) 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 — 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.