How blb3dprinting/filaops works
FilaOps is an ERP for 3D-print farms. Staff use the React admin application to manage customers and sales orders, plan and execute production, track inventory and quality, purchase supplies, and account for transactions. The FastAPI backend exposes the REST API, with domain services implementing business rules and PostgreSQL holding application state. The README documents the product areas; sampled source confirms application/API startup, routing editing, and inventory-service dependencies. Most domain relationships below reflect documented capabilities rather than inspected endpoint implementations.
Main entry points: __init__.py API route registry · inventory_service.py Inventory operations · sales_order_fulfillment_service.py Order fulfillment · production_orders.py Production orders
Components 23
Staff application
- Admin application
frontend/src/App.jsx - Routing editor
frontend/src/components/routing/RoutingEditorContent.jsx - API client
frontend/src/lib/apiClient.js
Sales and fulfillment
- Sales orders API
backend/app/api/v1/endpoints/sales_orders.py - Quotes and customers
backend/app/api/v1/endpoints/quotes.py - Order fulfillment
backend/app/services/sales_order_fulfillment_service.py - Invoices and payments
backend/app/api/v1/endpoints/invoices.py - Accounting
backend/app/api/v1/endpoints/accounting.py
Production operations
- Production orders
backend/app/api/v1/endpoints/production_orders.py - Routings API
backend/app/api/v1/endpoints/routings.py - Routing logic
backend/app/services/routing_service.py - Quality control
backend/app/api/v1/endpoints/quality.py - Scheduling
backend/app/api/v1/endpoints/scheduling.py
Inventory and purchasing
- Inventory API
backend/app/api/v1/endpoints/inventory.py - Inventory operations
backend/app/services/inventory_service.py - Inventory ledger
backend/app/services/inventory_ledger.py - Material planning
backend/app/services/mrp.py - Purchasing
backend/app/api/v1/endpoints/purchase_orders.py
API and persistence
- API application
backend/app/main.py - API route registry
backend/app/api/v1/__init__.py - Database sessions
backend/app/db/session.py - PostgreSQL
Other components
- Staff user
Connections 22
- Staff user → Admin application: uses
README.md - Admin application → API client: uses
frontend/src/App.jsx - Routing editor → Routings API: sends CRUD
frontend/src/components/routing/RoutingEditorContent.jsx - API application → API route registry: registers
backend/app/main.py - API route registry → Sales orders API: registers
backend/app/api/v1/__init__.py - API route registry → Routings API: registers
backend/app/api/v1/__init__.py - API route registry → Inventory API: registers
backend/app/api/v1/__init__.py - API route registry → Production orders: registers
backend/app/api/v1/__init__.py - Routings API → Routing logic: delegates to
backend/app/api/v1/endpoints/routings.py - Sales orders API → Order fulfillment: fulfills orders
- Inventory API → Inventory operations: manages stock
- Inventory operations → Inventory ledger: posts entries
backend/app/services/inventory_service.py - Order fulfillment → Inventory operations: updates inventory
backend/app/services/sales_order_fulfillment_service.py - Production orders → Quality control: supports inspection
- Production orders → Scheduling: plans work
- Material planning → Purchasing: plans shortages
- Order fulfillment → Accounting: posts shipment GL
- Database sessions → PostgreSQL: opens sessions
backend/app/db/session.py - Inventory operations → Inventory ledger: records stock changes
backend/app/services/inventory_service.py - API client → API application: calls REST API
- Quotes and customers → Sales orders API: converts to orders
- Invoices and payments → Accounting: records payments