Skip to content

🔗 Inventory — Bridges

This folder exists as a lightweight architectural breadcrumb.

RevFramework standardizes cross-system functionality under:

Assets/RevFramework/Integrations/

As a result, Inventory-specific integrations are implemented there rather than inside the Inventory module itself.

This helps keep:

  • Inventory standalone
  • dependency direction cleaner
  • optional systems easier to remove
  • integrations centralized and predictable

🧠 Terminology Note

The term “Bridges” reflects earlier internal architecture terminology used during framework development.

RevFramework now standardizes on:

  • Integrations → optional cross-system functionality
  • Adapters → small translation layers between APIs

This folder intentionally remains to help communicate that architectural distinction.

📦 Where Inventory Integrations Live

Inventory integrations are implemented under:

Assets/RevFramework/Integrations/Inventory/

Examples:

  • PickupsIntegration
  • CurrencyIntegration

⚠ Important

No active integration code should be added here.

All new cross-system functionality belongs under the shared root-level:

Assets/RevFramework/Integrations/

🔒 Design Philosophy

Inventory itself remains:

  • standalone
  • dependency-light
  • removable
  • safe from hidden cross-system coupling

Cross-system orchestration belongs in integrations — not inside Inventory core.

This keeps the framework modular, SKU-safe, and easier to maintain long term.