Version: 1.0
Date: January 9, 2026
Status: Draft
Document Type: PRINCE2 Project Vision
1. Executive Summary
Forma3D.Connect is an integration platform designed to bridge the gap between Forma 3D's print farm management system (SimplyPrint) and its e-commerce platform (Shopify). The system will automate the entire print-on-demand workflow, from order placement to product fulfillment and shipping initiation.
This document defines the vision, objectives, scope, and success criteria for the Forma3D.Connect integration services, following the PRINCE2 methodology framework.
2. Background
2.1 Current Situation
Forma 3D operates a 3D print farm ecosystem consisting of:
- SimplyPrint: Cloud-based print farm management software connected to multiple 3D printers via Raspberry Pi controllers
- Shopify: Online sales platform with connections to multiple marketplace integrators (Koongo) and shipping providers (Sendcloud)
- Supporting Infrastructure: UPS systems, filament dryers, air quality monitors, and environmental controls
The current ecosystem (as illustrated in assets/ecosystem.jpg) shows disconnected operational flows between:
- Sales channels (Shopify → Koongo → bol., Kaufland.de, CDiscount, Amazon)
- Production systems (SimplyPrint → 3D Printers)
- Business operations (Slicing Pie equity calculator, Matomo analytics, Statping-ng monitoring)
2.2 Business Services Structure
As shown in assets/business-overview.jpg, Forma 3D's business operates across three layers:
| Layer |
Services |
| Strategy Layer |
R&D, Strategic Marketing |
| Growth Layer |
Operational Marketing, Sales |
| Execution Layer |
Production, Storage, Fulfilment, Shipping |
All services feed into Customer Success as the ultimate outcome.
2.3 Problem Statement
Currently, when an order is placed on Shopify:
- Manual intervention is required to create print jobs in SimplyPrint
- Print completion status is not automatically communicated to Shopify
- Order fulfillment must be manually triggered
- Shipping labels and tracking information are manually processed
This creates delays, potential errors, and limits scalability.
3. Vision Statement
"To create a seamless, automated bridge between e-commerce orders and 3D print production, enabling true print-on-demand operations where every Shopify order automatically triggers production, and every completed print automatically fulfills customer orders."
4. Project Objectives
4.1 Primary Objectives
| ID |
Objective |
Success Measure |
| O1 |
Automated Order-to-Print Pipeline |
100% of Shopify orders automatically create SimplyPrint jobs within 60 seconds |
| O2 |
Automated Print-to-Fulfillment Pipeline |
100% of completed prints trigger Shopify fulfillment within 60 seconds |
| O3 |
Real-Time Status Synchronization |
Order status updates reflected across platforms within 30 seconds |
| O4 |
Zero Manual Intervention |
Standard orders processed without human intervention |
4.2 Secondary Objectives
| ID |
Objective |
Success Measure |
| O5 |
Operational Visibility |
Dashboard showing real-time production status |
| O6 |
Error Resilience |
99.9% system uptime with graceful error handling |
| O7 |
Scalability |
Handle 1,000+ orders/day without performance degradation |
| O8 |
Auditability |
Complete audit trail of all automated actions |
| O9 |
Security Compliance |
Continuous security monitoring with Aikido platform |
| O10 |
Observability |
Full-stack observability with Sentry error tracking, performance monitoring, and distributed tracing |
5. Scope
5.1 In Scope
5.1.1 Core Integration Features
- ✅ Shopify Webhook Listener: Capture new orders in real-time — Implemented (Phase 1)
- ✅ Order Parser & Mapper: Extract print-relevant information from orders — Implemented (Phase 1)
- SimplyPrint Job Creator: Automatically queue print jobs — Phase 2
- Print Status Monitor: Track job progress via SimplyPrint API/webhooks — Phase 2
- Fulfillment Trigger: Mark orders fulfilled in Shopify upon print completion — Phase 3
- Shipping Integration: Trigger Sendcloud shipping label generation — Phase 5
5.1.2 Supporting Features
- Admin Dashboard: Web interface for monitoring and manual overrides — Phase 4
- ✅ Event Logging: Comprehensive logging of all integration events — Implemented (Phase 1)
- Error Handling: Retry mechanisms and failure notifications — Phase 3
- ✅ Configuration Management: Map Shopify products to SimplyPrint print profiles — Implemented (Phase 1)
5.1.3 Technical Infrastructure
- NestJS API backend with PostgreSQL database
- React 19 admin dashboard
- Socket.IO for real-time updates
- Webhook endpoints for both Shopify and SimplyPrint
- ✅ OpenAPI/Swagger interactive documentation (
/api/docs)
- ✅ Aikido Security Platform for continuous security monitoring and SBOM generation
- Sentry Observability Platform — Error tracking, performance monitoring, and distributed tracing (Phase 1b)
5.2 Out of Scope
| Item |
Reason |
| Multi-tenant support |
Single printfarm operation |
| Payment processing |
Handled by Shopify |
| Customer-facing interfaces |
Orders placed via Shopify |
| Inventory management system |
Future phase consideration |
| Custom slicer integration |
SimplyPrint handles slicing |
| Marketplace integrations |
Handled by Koongo |
5.3 Future Considerations (Post-MVP)
- Inventory forecasting: Predict filament and material needs
- Production scheduling optimization: Intelligent job assignment
- Quality control workflows: Inspection checkpoints
- Customer notification system: Automated progress updates
- Analytics and reporting: Production efficiency metrics
- Multi-location support: Distributed print farm coordination
6. Stakeholders
6.1 Internal Stakeholders
| Stakeholder |
Role |
Interest |
| Forma 3D Management |
Project Sponsor |
Business efficiency, ROI |
| DevGem Development Team |
Technical Delivery |
Quality implementation |
| Operations Team |
End Users |
Daily operations efficiency |
6.2 External Stakeholders
| Stakeholder |
Role |
Interest |
| Customers |
Order Placers |
Timely delivery, accurate orders |
| SimplyPrint |
Platform Provider |
Successful integration |
| Shopify |
E-commerce Provider |
Proper API usage |
| Sendcloud |
Shipping Provider |
Label generation integration |
7. Business Case
7.1 Benefits
Tangible Benefits
| Benefit |
Current State |
Target State |
Value |
| Order processing time |
15-30 min manual |
< 1 min automated |
Time savings |
| Error rate |
~5% manual errors |
< 0.1% automated |
Cost reduction |
| Orders processed/day capacity |
50 (manual limit) |
1,000+ (automated) |
Revenue growth |
| Staff hours on order processing |
4 hrs/day |
0.5 hrs/day (oversight) |
Labor cost reduction |
Intangible Benefits
- Improved customer satisfaction through faster, more reliable fulfillment
- Scalability enablement for business growth
- Competitive advantage in print-on-demand market
- Operational insights through data collection
7.2 Costs
| Category |
Estimate |
| Development (initial) |
200-300 hours |
| Infrastructure (monthly) |
€50-100 (hosting, database) |
| Maintenance (ongoing) |
10-20 hours/month |
| API costs |
Included in existing subscriptions |
7.3 Return on Investment
With an estimated labor savings of 3.5 hours/day at operational rates, the system pays for development costs within 3-6 months, with ongoing savings thereafter.
8. Technical Vision
8.1 Architecture Overview

8.2 Tech Stack (per .cursor/rules/derived-cursor-rules.mdc)
| Layer |
Technology |
| Frontend |
React 19, TypeScript, Vite, Tailwind CSS, TanStack Query, PWA |
| Backend |
NestJS, TypeScript, REST API, Socket.IO |
| Database |
PostgreSQL, Prisma ORM |
| Cross-Platform |
Progressive Web App (installable on desktop and mobile) |
| Testing |
Vitest (frontend), Jest (backend) |
| Monorepo |
Nx |
8.3 Integration Points
Shopify API
- Authentication: OAuth 2.0 / API Key
- Webhooks:
orders/create, orders/updated, orders/cancelled
- REST/GraphQL: Order retrieval, fulfillment creation, inventory updates
- Key Endpoints:
POST /admin/api/2024-01/fulfillments.json
GET /admin/api/2024-01/orders.json
PUT /admin/api/2024-01/orders/{id}.json
SimplyPrint API
- Authentication: API Key / Bearer Token
- Webhooks: Print job status updates, completion events
- REST API: Job creation, queue management, printer status
- Key Operations:
- Create print job from file/URL
- Assign job to printer/queue
- Monitor job status
- Retrieve completion events
Sendcloud API
- Authentication: API Key
- REST API: Label creation, tracking information
- Key Operations:
- Create shipping label
- Retrieve tracking URL
9. Constraints
9.1 Technical Constraints
| Constraint |
Impact |
Mitigation |
| Shopify API rate limits |
2 requests/second (REST) |
Request queuing, batch operations |
| SimplyPrint API capabilities |
Limited to documented endpoints |
Design within API boundaries |
| Webhook reliability |
Potential missed events |
Polling fallback, idempotency |
| Network dependencies |
External service availability |
Retry logic, circuit breakers |
9.2 Business Constraints
| Constraint |
Impact |
Mitigation |
| Single operator |
No multi-user complexity |
Single-tenant design |
| Existing product catalog |
Must map to print files |
Configuration system |
| Existing processes |
Must integrate, not replace |
Gradual rollout |
9.3 Regulatory Constraints
| Constraint |
Impact |
Mitigation |
| GDPR compliance |
Customer data handling |
Minimal data storage, encryption |
| Shopify API terms |
Usage restrictions |
Adherence to guidelines |
10. Assumptions
| ID |
Assumption |
Validation Needed |
| A1 |
SimplyPrint API supports automated job creation |
API documentation review |
| A2 |
SimplyPrint provides job completion webhooks or polling |
API testing |
| A3 |
Shopify order contains sufficient data for print job creation |
Order data analysis |
| A4 |
Products have associated print files in SimplyPrint |
Configuration mapping |
| A5 |
Network connectivity is stable and reliable |
Infrastructure assessment |
| A6 |
Single currency and single warehouse operation |
Business confirmation |
11. Risks
| ID |
Risk |
Probability |
Impact |
Mitigation |
| R1 |
SimplyPrint API changes or deprecation |
Low |
High |
Monitor changelog, versioned integration |
| R2 |
Shopify webhook delivery failures |
Medium |
Medium |
Polling fallback, retry logic |
| R3 |
Print job failures not communicated |
Medium |
High |
Health checks, manual override capability |
| R4 |
Data synchronization errors |
Medium |
Medium |
Idempotent operations, reconciliation |
| R5 |
System downtime affecting orders |
Low |
High |
High availability design, monitoring |
| R6 |
Performance degradation at scale |
Low |
Medium |
Load testing, horizontal scaling design |
12. Success Criteria
12.1 MVP Success Criteria
| Criterion |
Target |
Measurement |
| Order-to-print automation |
95% success rate |
Automated monitoring |
| Print-to-fulfillment automation |
95% success rate |
Automated monitoring |
| Average processing latency |
< 2 minutes end-to-end |
Performance metrics |
| System availability |
99% uptime |
Statping-ng monitoring |
| Error notification |
100% of failures notified |
Alert system |
12.2 Post-MVP Success Criteria
| Criterion |
Target |
Measurement |
| Full automation rate |
99% success rate |
Long-term metrics |
| Daily order capacity |
1,000+ orders |
Load testing |
| User satisfaction |
Positive feedback |
Operations team survey |
| Maintenance overhead |
< 2 hours/week |
Time tracking |
13. Quality Expectations
13.1 Code Quality
- ✅ 100% TypeScript with strict mode — Implemented
- ✅ No
any types or ts-ignore comments — Enforced via ESLint
- ✅ Comprehensive error handling with typed errors — Implemented
- Unit test coverage > 80% — In progress
- ✅ Integration test coverage for all API interactions — E2E tests implemented
The project integrates Aikido Security Platform for continuous security monitoring:
| Security Check |
Status |
Description |
| Open Source Dependency Monitoring |
Active |
Monitors 3rd party dependencies for vulnerabilities |
| Exposed Secrets Monitoring |
Compliant |
Detects accidentally exposed secrets in source code |
| License Management |
Compliant |
Validates legal compliance of all dependency licenses |
| SAST |
Compliant |
Static Application Security Testing |
| IaC Testing |
Compliant |
Infrastructure as Code security analysis |
| Malware Detection |
Compliant |
Detects malware in dependencies |
| Mobile Issues |
Compliant |
Mobile manifest file monitoring |
| SBOM Generation |
Active |
Software Bill of Materials for supply chain security |
Future Enhancement: Code quality analysis will be enabled in a subsequent phase.
13.3 Documentation
- ✅ API documentation (OpenAPI/Swagger) — Implemented
- Interactive Swagger UI at
/api/docs
- OpenAPI 3.0 JSON specification at
/api/docs-json
- All endpoints documented with request/response schemas
- Grouped by feature: Health, Orders, Product Mappings, Shopify Webhooks
- Architecture decision records ✅ Implemented — See docs/03-architecture/adr/ADR.md
- 16 ADRs documenting all architectural decisions
- C4 model diagrams (Context, Container, Component, Deployment, Database)
- Runbook for operations
- Incident response procedures
13.4 Operational Quality (Sentry Observability)
The project integrates Sentry for comprehensive observability:
| Capability |
Status |
Description |
| Error Tracking |
✅ Implemented (Phase 1b) |
Unhandled and handled exceptions with stack traces |
| Performance Monitoring |
✅ Implemented (Phase 1b) |
Request latency, database query timing, custom spans |
| Distributed Tracing |
✅ Implemented (Phase 1b) |
End-to-end trace propagation across frontend and backend |
| Structured Logging |
✅ Implemented (Phase 1b) |
JSON logs with correlation IDs and trace context |
| Prisma Query Tracing |
✅ Implemented (Phase 1b) |
Database query performance insights via OpenTelemetry |
| React Error Boundaries |
✅ Implemented (Phase 1b) |
Graceful error handling with user-friendly fallback UI |
| Test Endpoints |
✅ Implemented (Phase 1b) |
API endpoints for verifying observability in non-prod |
Architecture:
- OpenTelemetry-first approach for vendor neutrality
- Traces exported to Sentry via OTLP
- 100% sampling (adjustable when traffic increases)
- Sensitive data scrubbing (PII, tokens, secrets)
- Sentry Logs integration for structured log ingestion
14. Approval
| Role |
Name |
Signature |
Date |
| Project Sponsor |
|
|
|
| Technical Lead |
|
|
|
| Operations Representative |
|
|
|
15. Document Control
| Version |
Date |
Author |
Changes |
| 1.0 |
2026-01-09 |
AI Assistant |
Initial draft |
| 1.1 |
2026-01-10 |
AI Assistant |
Marked Phase 0 & 1 features as implemented, added status |
| 1.2 |
2026-01-10 |
AI Assistant |
Added Aikido Security Platform, O9 objective, SBOM |
| 1.3 |
2026-01-10 |
AI Assistant |
Added Sentry Observability Platform, O10 objective |
| 1.4 |
2026-01-10 |
AI Assistant |
Marked Phase 1b as complete, updated sampling to 100% |
Appendix A: Glossary
| Term |
Definition |
| Print-on-Demand (POD) |
Manufacturing model where products are only produced when ordered |
| Print Farm |
Collection of 3D printers operated together for production |
| SimplyPrint |
Cloud-based print farm management software |
| Fulfillment |
Process of completing an order including packing and shipping |
| Webhook |
HTTP callback that delivers real-time notifications |
Appendix B: References
- Shopify Admin API Documentation: https://shopify.dev/docs/api/admin
- SimplyPrint Platform: https://simplyprint.io
- Sendcloud API Documentation: https://api.sendcloud.dev
- Nx Monorepo Documentation: https://nx.dev
- NestJS Documentation: https://docs.nestjs.com
- NestJS Swagger Module: https://docs.nestjs.com/openapi/introduction
- OpenAPI Specification: https://swagger.io/specification/
- Aikido Security Platform: https://www.aikido.dev/
- Sentry Documentation: https://docs.sentry.io/
- Sentry for NestJS: https://docs.sentry.io/platforms/javascript/guides/nestjs/
- Sentry for React: https://docs.sentry.io/platforms/javascript/guides/react/
- OpenTelemetry Documentation: https://opentelemetry.io/docs/