Integration Architecture
Developer entry point for FlowPOS third-party adapter patterns.
Use this section when adding or troubleshooting integrations whose domain logic must stay independent from provider HTTP details.
Current provider status
| Area | Runtime status | Primary docs |
|---|---|---|
| FEL/SAT certification | digifact is merchant-selectable; infile and rpafelapi adapters are wired for specific routes; routing depends on the FEL runtime path | FEL Provider Port, FEL Provider Matrix |
| E-commerce | Shopify is implemented; WooCommerce is reserved but not registered at runtime | Ecommerce Adapter Architecture, Ecommerce Provider Port |
| Delivery marketplace | PedidosYa is implemented and registered; uber_eats is enum-only | Marketplace Architecture, Marketplace Provider Port |
Hexagonal guidance
When documenting or extending an integration:
- keep domain behavior in entities, value objects, and ports
- keep use-case orchestration in application services
- keep provider HTTP formats, credentials, retries, and HMAC details in infrastructure adapters
- keep controller paths, request DTOs, and redirect behavior in interfaces docs
Do not describe an adapter-specific retry, URL, token, or webhook signature as domain behavior unless the domain port requires every provider to satisfy it.
Operational references
- Shopify operations runbook
- Shopify troubleshooting runbook
- WooCommerce adapter status
- Delivery marketplace troubleshooting
- Pack operations troubleshooting
- Implementation portal troubleshooting
- FEL certifier registry
- FEL network troubleshooting
Related codepaths
apps/backend/src/fel/apps/backend/src/ecommerce/apps/backend/src/delivery-marketplace/packages/global/enums/marketplace.enums.tspackages/global/consts/fel-integrated-certifiers.const.tspackages/global/consts/certifiers-urls.consts.ts