Questions, answered

Click Get started, then use Proto to configure SCM with Kanban Replenishment for your business. Pilot one organization, a small product family and a customer order with a partially shipped line and an empty bin.

An Order Coordinator prepares a signal for an empty bin against a customer order and organization. The signal records requested units and the bin code.

Task Board by Status on replenishment signals groups signals by their current state. The board shows which cards are Submitted.

The coordinator submits a Draft signal at its current revision. A receipt records the result under a stable operation key.

Order Reviewer can inspect the submitted revision and its order context. Submission records a request and an operation result; it does not approve replenishment.

Read order line quantities alongside dated fulfillment events and the order’s current status. The pull request itself does not record a physical shipment.

Orders, customers, signals and staff carry organization context. Agree staff assignments and access before opening the queue across organizations.

Inspect the failed operation receipt, including its expected revision and failure reason. Check the current signal before trying again.

Payment Evidence keeps the provider event type, amount, reference and verified state against the customer order. Provider confirmation supplies the verification outcome.

Manual use follows the platform pricing policy. Imports, integrations and agent work use metered credits; implementation is scoped separately. See pricing.