All applications583

Find your application

583 applications

Open full catalog

Browse applications by category or open the full catalog.

SCM with Kanban Replenishment
Start now
More

Features

Industries

Reference

More

SCM with Kanban Replenishment · Available now

Track empty-bin demand from customer order to submitted signal.

SCM with Kanban Replenishment connects customer demand to empty-bin replenishment signals. An Order Coordinator follows the customer order and its lines, records a signal against the order and organization, and submits a draft signal at its expected revision.

Start now Download Proto
  • No per-user fees
  • Manual work is free
  • Configure it in Proto
OverviewOpen Customer Orders
SCM with Kanban Replenishment · Customer orders

Open Customer Orders

Customer orders in one list

New customer order
Customer orders in view
6
Total net amount USD
2,150
Confirmed
2
Allocated
2
Confirmed2
Restock assembly fastener binsCO-66290
170
28 Oct
Supply hose clamps for line BCO-86574
940
20 Oct
Add
Allocated2
Refill maintenance glove stationCO-94167
150
21 Oct
Refill safety glasses at depotCO-57561
50
01 Nov
Add
Part shipped2
Replenish packing tape at Plant 3CO-36177
140
03 Nov
Restock filter media cartridgesCO-61387
700
31 Oct
Add
Restock assembly fastener binsCustomer orders · CO-66290
Confirmed
Promised date28 Oct
Net amount USD170
OwnerNoah Kim
Example screen with sample data
Tables, ready to use
13
Saved views
14
Roles with set permissions
5
Reports and dashboards
8
Features

Orders and pull requests in view

Every feature works on the same records. Pick one to see the screen your team works in.

Customer orders

Follow customer demand, promised dates and the order lifecycle from one owner.

  • Order identity
  • Ownership
  • Linked history
  • Customer orders
  • Customers
  • Organizations
  • Order lines
  • Replenishment signals
  • Operation receipts
Explore customer orders
OverviewDraft Orders
SCM with Kanban Replenishment · Customer orders

Draft Orders

Submission waits for the order coordinator

New
Record numberSubjectStatusPromised dateRevision
CO-27386Restock assembly fastener binsDraft28 Oct860
CO-81759Refill maintenance glove stationDraft24 Oct850
CO-93267Replenish packing tape at Plant 3Draft21 Oct660
CO-94274Supply hose clamps for line BDraft03 Nov60
CO-33524Refill safety glasses at depotDraft14 Oct340
6 of 6 records
Restock assembly fastener binsCustomer orders · CO-27386
Draft
Promised date28 Oct
Revision860
Example screen with sample data
Process

From empty bin to submitted request

From empty bin to submitted request ships ready to use.

Drag a card to another stage, or focus it and use the arrow keys. It updates to match the stage.

  1. Identify demand

    Read the customer order and line quantities behind the empty bin.

    Restock assembly fastener binsCO-66290 · Order Coordinator
    Identify demandBy Order Coordinator

  2. Prepare signal

    Record the bin, requested units and parent order on a pull card.

    Restock assembly fastener binsCO-66290 · Order Coordinator
    Prepare signalBy Order Coordinator

  3. Submit signal

    Submit the current draft revision and inspect its operation receipt.

    Restock assembly fastener binsCO-66290 · Order Coordinator
    Submit signalBy Order Coordinator

  4. Inspect receipt

    Compare the operation result with the submitted signal and stable key.

    Restock assembly fastener binsCO-66290 · Order Coordinator
    Inspect receiptBy Order Coordinator

  5. Trace outcome

    Compare later fulfillment evidence with the original order.

    Restock assembly fastener binsCO-66290 · Auditor
    Trace outcomeBy Auditor

Start with Empty-bin request

Inside a record

Keep source events tied to the order

Open any customer order to see its fulfillment events, the roles that work on it, its process stages and its approvals on one page.

  1. 1
    Record details

    Promised date, Net amount USD and Owner.

  2. 2
    Fulfillment events

    Each line is linked to this customer order.

  3. 3
    Who works on it

    Admin, each with their own permissions.

  4. 4
    Process stages

    Identify demand, with the role that acts.

  5. 5
    Approvals

    Who signed off and when.

Open Customer OrdersRestock assembly fastener bins
SCM with Kanban Replenishment · Customer orders

Restock assembly fastener bins

Confirmed

Log activity
1
Record details
Promised date28 Oct
Net amount USD170
OwnerNoah Kim
2
Fulfillment events

Restock assembly fastener bins

Event numberEvent typeQuantity
FE-57194Allocated220
FE-79413Picked930
FE-51202Shipped170
Fulfillment events
6
Total quantity
2,530
3

Who works on it

  • AdminManage Products, Customers, Organizations, team members
4

Process stages

  • Identify demandOrder Coordinator
Example screen with sample data
Roles

A workspace for each role

Everyone opens SCM with Kanban Replenishment to the work that is theirs. Pick a role to see what it starts with.

Order Coordinator

Prepare assigned operational records and execute eligible reviewed replenishment actions.

This is the first screen this role sees.

OverviewOpen Customer Orders

Open Customer Orders

Customer orders · Order Coordinator

Confirmed2
Restock assembly fastener binsCO-66290
170
28 Oct
Supply hose clamps for line BCO-86574
940
20 Oct
Add
Allocated2
Refill maintenance glove stationCO-94167
150
21 Oct
Refill safety glasses at depotCO-57561
50
01 Nov
Add
Part shipped2
Replenish packing tape at Plant 3CO-36177
140
03 Nov
Restock filter media cartridgesCO-61387
700
31 Oct
Add
Example screen with sample data

Roles and permissions

Reports

See demand and exceptions together

Read order value, unshipped units, signal demand and failed operations together.

Overview
SCM with Kanban Replenishment · Overview

SCM with Kanban Replenishment dashboard

This quarter

Replenishment signals in view
6
Total requested units
2,890
Draft
2
Submitted
1

Customer orders by status

How far records got this quarter

StageReachedStep
Draft48
Confirmed817%
Allocated338%
Part shipped133%

Net amount USD by status

Sample totals per stage

2.0k0
-2000Draft
0Confirmed
-4000Allocated
-6000Part shipped
2.0kShipped
Example screen with sample data
  1. 01Order value by status

    Which customer commitments are still active?

  2. 02Promised orders by date

    Which orders require near-term follow-up?

  3. 03Signal volume by state

    Where are pull requests waiting for review?

  4. 04Requested units by bin

    Which bins generate repeated demand?

  5. 05Order line fulfillment gap

    How much ordered quantity remains unshipped?

  6. 06Failed operations by action

    Which attempted actions need intervention?

  7. 07Review decisions by reviewer

    What outcomes and reasons were recorded?

  8. 08Fulfillment event history

    Trace events by customer order and product.

All reports and dashboards

Who it's for

Fit recurring stocked-product demand

See how SCM with Kanban Replenishment fits your kind of team.

Distribution teams

Keep customer orders and bin-triggered replenishment in the same operating scope.

Parts supply teams

Tie repeat parts demand to order lines, bin codes and dated fulfillment history.

Multi-organization operations

Separate replenishment demand by organization while keeping a common review trail.

Controls

Trace revisions and operation results

Each stage, from empty bin to submitted request, names the role that acts and the status it records, so a change is never anonymous.

OverviewFrom empty bin to submitted request
SCM with Kanban Replenishment · Process

From empty bin to submitted request

Each stage, the role that acts and the status it records

Process stages
10
Approval steps
0
Roles involved
3
Tables touched
7
Identify demand
Order Coordinator
RecordsCustomer orders, Order lines
Check customer eligibility
Order Coordinator
RecordsOrganizations, Customers
Prepare signal
Order Coordinator
RecordsReplenishment signals, Organizations
From empty bin to submitted request
  1. Start
    Identify demandOrder Coordinator
    Customer orders
  2. Step
    Check customer eligibilityOrder Coordinator
    Organizations
  3. Step
    Prepare signalOrder Coordinator
    Replenishment signals
  4. Step
    Check revisionOrder Coordinator
    Order Coordinator
  5. Step
    Submit signalDraft → Submitted
    Order Coordinator
Example screen with sample data

See each stage in detail

AI agent

Ask Proto about the current queue

Ask Proto to help inspect order demand, signal queues and evidence while people retain decisions.

It can

  • Order Coordinator: Show assigned customer orders with near promised dates and remaining shipped-unit gaps.
  • Order Reviewer: Summarize submitted signals with their parent order, bin and requested units for review.
  • Auditor: Trace a failed operation from receipt through the parent order and related decision.

Stays with a person

  • Proto can organize the records and help prepare a response, but the authorized person checks the order, current signal revision and evidence.
  • Order Reviewer inspects submitted scope before the team acts on it.
  • A provider event is verified from the provider source, and a fulfillment event comes from the physical event source.
  • Staff should inspect the operation key before asking for another submission.

Set up an agent

Integrations

Connects to the tools you use

Set up connections through ERP.AI and Proto workflows, with every change logged.

  • SCM with Kanban Replenishment
  • Order source
  • Warehouse event source
  • Payment provider
  • File source
Data model

Your data, in tables you can change

Every record lives in a table you can see, extend and export. Add fields or whole tables in Proto.

Browse all 13 tables
13tables
  • Customer orders6
  • Order lines5
  • Replenishment signals5
  • Review and decisions6
  • Fulfillment and payments6
  • Operations overview6
Implementation

Roll out one team at a time

Start with one team and one process, then add the rest once the basics are running.

  1. Agree the operating scope

    Choose the organizations, customers, product family and order owner for a bounded pilot. Define who prepares signals and who reviews them.

  2. Map identifiers and units

    Check customer codes, order numbers, SKU, base unit, bin codes and external event identifiers. Keep imported parent references intact.

  3. Prepare the records

    Load organizations, team members, customers and products before orders. Then link lines, signals and evidence to the correct parent order.

  4. Rehearse the pull request

    Start with a confirmed order, partially shipped line and empty bin. Submit a current draft signal, inspect its receipt, then test an earlier revision.

  5. Inspect and reconcile

    Have the reviewer explain the current request and compare it with any recorded decision. Compare line quantities with fulfillment events and payment evidence with provider verification.

Read the implementation plan

Pricing

$0per user

The base account and everyday work in the ERP.AI app are free, for every user.

  • No per-user or per-seat fees
  • Viewing, editing, approving and exporting records in the app is free
  • Pay only for machine work: API calls, imports, workflows and AI agents
  • Prepaid credits from $5. Purchased credits never expire

Pricing details

Machine work rate card Included per $1 of credit

Machine work rate card
UsagePer $1
Record reads (list, filter, get)20,000
Search or aggregate queries4,000
Record writes4,000
Imported or synced records200,000
Workflow runs2,000
AI agent runs2,000
Scheduled jobs or webhooks20,000
File uploads (MB)2,000
CSV or PDF exports100
FAQ

Questions, answered

Scope, rollout and pricing for SCM with Kanban Replenishment.

All questions
How do I get started?

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.

What starts a replenishment request?

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.

Where can the team see pull requests?

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

How is a signal submitted?

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

What happens after submission?

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

How do we follow an order after submission?

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

Can we work across organizations?

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

What if a submission fails?

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

How are payment events handled?

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

What drives cost?

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

Set up SCM with Kanban Replenishment your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

Start now Download Proto

How to get started

A personal agent for your business

Get started with Proto

Your app is selected. Download Proto, then open it with this context.

Selected appSCM with Kanban Replenishment

Choose your computer’s platform.

Download Proto

Install Proto, then return to this panel.

Already installed? Open Proto

Free to use. Your own model provider may charge for usage.