procurement:delete
Status: ❌ Not Implemented
Description
This mutation message will delete a single procurement record by its ID. Procurement records track purchases, orders, and supply acquisitions for the community.
Note: This feature is not currently planned. The procurement system is still in the design phase. This page exists to document the intended functionality for future reference.
Expected Functionality
If implemented in the future, this mutation would:
- Delete a procurement record by ID
- Handle associated line items and supplier information
- Return a message_id for async processing
- Support soft delete with audit trail
Expected Request Schema
{
"payload": {
"type": "procurement:delete",
"id": 123
},
"signature": "payload_ed25519_hex_signature",
"source_public_key": "your_client_public_key"
}
Request Attributes
-
payload.id- Integer - The procurement ID to delete
Expected Response Schema
{
"source_public_key": "community_public_key",
"source_site": {
"protocol": "https",
"fqdn": "arkipel.example.com"
},
"created_at": "2025-11-13T20:52:49Z",
"signature": "...",
"payload": {
"type": "procurement:delete",
"message_id": "abc123def456"
}
}
Async Processing
This would be an asynchronous mutation. Use arkipel_messages:query with the returned message_id to check deletion status.
Timeline
No timeline available. This feature is currently not planned.
Request This Feature
Interested in procurement management features? Contact us at devkit@arkipel.co to discuss your use case and help prioritize development.
Related Messages (Available Now)
-
procurements:upsert- Create or update procurement records (📅 Planned) -
distributions:upsert- Create distributions (available now) -
distribution:delete- Delete distributions (available now)
Procurement vs. Distribution
Understanding the difference:
| Feature | Procurement | Distribution |
|---|---|---|
| Purpose | Acquiring supplies/goods | Distributing goods to people |
| Direction | Inbound (buying) | Outbound (giving) |
| Status | 📅 Planned | ✅ Available |
Use Cases (Future)
- Order Cancellation: Cancel a procurement order that hasn’t been fulfilled
- Data Cleanup: Remove test or duplicate procurement records
- Audit Compliance: Delete records per retention policies (with audit trail)
Return to API Specifications