Purchase Order Implementation
Business Workflow
Section titled “Business Workflow”The Procurement workflow moves kanban cards through the ordering and receiving lifecycle:
- Cards for an item are listed from the Items view.
- A card is added to the procurement queue by sending it the
ACCEPTEDsignal, which transitions it to theREQUESTEDstate. - The user reviews the procurement queue: a list of all cards in
REQUESTEDstate, grouped by Vendor and Order Method. - The user selects cards and orders them:
- For online orders: the item URL for the vendor opens.
- For other methods (e-mail, phone, etc.): a side panel displays message text for the user to send manually.
- The Order action sends a
start_processingsignal, transitioning the card toIN_PROCESS. - The Receiving view shows all
IN_PROCESScards. Receiving a card sends thereceivesignal, transitioning it toFULFILLED.
Kanban Card State Mapping
Section titled “Kanban Card State Mapping”| Workflow Step | Kanban Card State |
|---|---|
| Added to queue | REQUESTED |
| Order placed | IN_PROCESS |
| Item received | FULFILLED |
The Procurement workflow uses the standard KanbanCardLifecycle transitions.
Use Cases (Demo202509)
Section titled “Use Cases (Demo202509)”- View Procurement Queue
- Add Card to Procurement Queue
- Release Card to Production from Receiving
- Create Vendor Carts
Detailed Procurement Subtopics
Section titled “Detailed Procurement Subtopics”| Page | Contents |
|---|---|
| Order Creation | Creating purchase orders from Kanban Cards, empty orders, copy of existing order, and from prescribed header and lines |
| Order Line Management | Adding single lines, adding lines from cards or items, and removing lines from a draft order |
| Order Lifecycle | Updating order headers, viewing and listing orders, processing an order through its states, and submitting to vendors |
| Order Implementation Notes | Data model changes, UI/UX information structure, and Kanban Card/Item dependency propagation rules |
Copyright: © Arda Systems 2025-2026, All rights reserved