Pyle Domain Hierarchy

Purpose and Method

This page is the first documentation pass for understanding what the Pyle framework does at the domain level.

It is intentionally not full feature documentation. Its job is to define the hierarchy that later documentation can expand: domain, subdomain, and representative features or entities.

Sources scanned

• Canonical structure in packages/framework:
  • src/Models
  • src/Actions
  • src/Services
  • database/migrations
  • config/*.php
  • routes/*.php
• Surfaced behavior:
  • packages/admin/src/Livewire/Admin
  • packages/admin/config/admin.php
  • packages/storefront/src/Livewire/Storefront
  • packages/storefront/src/View/Components/MyAccount/Menu
• Supporting integrations:
  • packages/erp-bridge/src/Requests

Classification rules

• Confirmed: persistent framework entities or workflows, plus at least one corroborating surface or service layer.
• Likely: meaningful cluster with multiple signals, but incomplete persistence or surface evidence.
• Ambiguous: visible in code or UI, but not clearly owned as a first-class framework domain.
• Presentation-only: layout, navigation, menu, login, and shell components that expose domains but do not define them.

Reading notes

• packages/framework is the canonical source of truth.
• Admin, storefront, and ERP bridge are validation layers, not competing domain models.
• This first pass stops at three levels of depth so the taxonomy remains stable enough to reuse in later documentation.

Top-Level Hierarchy

• Catalog & Merchandising
  • Products
    • Product, ProductTerm, ProductPolicy
  • Taxonomy
    • ProductCategory, ProductCollection, ProductType, ProductManufacturer
  • Attributes and configurable grouping
    • ProductAttribute, ProductAttributeGroup, ProductGroup*
  • Media and relationships
    • ProductImage, ProductDocument, ProductVideo, ProductCrossSell, ProductUpsell
• Pricing & Promotions
  • Offer records
    • ProductOffer, FeaturedOffer, PriceHistory, PriceList
  • Targeted pricing eligibility
    • customer, group, geography, shipping zone, and inventory-location scoping
  • Promotions
    • Promotion, PromotionCode, PromotionCondition, PromotionBenefit, PromotionRedemption
• Customer Management
  • Accounts and segmentation
    • Customer, CustomerGroup, CustomerProductRestriction
  • Account data
    • CustomerAddress, CustomerList, CustomerListProduct, Wishlist
  • Customer-linked users and teams
    • customer-user relations exposed through admin and storefront account surfaces
• Order Lifecycle
  • Cart and checkout
    • Cart, CartItem
  • Orders and order items
    • Order, OrderItem
  • Commercial adjustments
    • OrderDiscountLine, OrderItemDiscountLine, OrderRisk
  • Returns and tracking
    • OrderReturn*, storefront tracking, sample-order flow
• Payments & Billing
  • Payment methods and gateways
    • PaymentGateway, CustomerCard, Stripe checkout/card flows
  • Payment and refund records
    • OrderPayment, OrderRefund
  • Billing documents
    • Invoice*
• Fulfillment & Shipping
  • Shipping configuration
    • ShippingMethod, ShippingService, ShippingZone, ShippingClass, ShippingOption, ShippingBox, ShippingPostalCode
  • Shipment execution
    • OrderShippingLine, OrderShipment, DeliveryTimingIssue
  • Fulfillment workflows
    • FulfillmentRequest*, Fulfillment*, FulfillmentService*
  • Transfer and scheduling
    • TransferLocation, TransferableLocation, CalendarRule*, UnitOfMeasure
• Inventory & Vendor Supply
  • Inventory state
    • ProductInventoryLocation, ProductInventoryItem, StockHistory
  • Vendor catalog and supply data
    • ProductVendor*, ProductManufacturerProductVendor
  • Mapping and synchronization prep
    • ProductMappingAttempt, AlternateCode
• Tax & Territory
  • Tax definitions
    • TaxRate, TaxLine, OrderTaxRateItemCode, Nexus
  • Shared territory model
    • Country, State, GeoRegion, SaleRegion, Address
• Supporting Platform Capabilities
  • Identity and access
    • User, Role, auth and permissions
  • Integration and data exchange
    • ERP bridge, data feeds, Excel import/export, file disks, SFTP
  • Search and operations
    • FastSearch, Meilisearch, Comment, ActivityLog, ActionRequest, Flag, AnalyticsAggregate, MaintenanceSchedule

Domain Details

Catalog & Merchandising

Responsibility: define sellable products, their taxonomy, their configurable structure, and the merchandising relationships around them.

Hierarchy

• Catalog & Merchandising
  • Product core
    • Product, ProductTerm, ProductPolicy
  • Taxonomy
    • ProductCategory, ProductCollection, ProductType, ProductManufacturer
  • Attributes and grouped configurability
    • ProductAttribute, ProductAttributeGroup, ProductGroup, ProductGroupAttribute, ProductGroupAttributeOption
  • Product media and relationships
    • ProductImage, ProductDocument, ProductVideo, ProductCrossSell, ProductUpsell

Evidence

Signal	Evidence
Models	packages/framework/src/Models/Product*.php, ProductCategory.php, ProductCollection.php, ProductType.php, ProductManufacturer.php, ProductAttribute*.php, ProductTerm.php, ProductPolicy.php
Actions	packages/framework/src/Actions/Product*, ProductCategory, ProductCollection, ProductType, ProductManufacturer, ProductAttribute, ProductImage, ProductDocument, ProductCrossSell, ProductTerm
Migrations	create_products_table, create_product_categories_table, create_product_collections_table, create_product_types_table, create_product_manufacturers_table, create_product_attributes_table, create_product_terms_table, create_product_documents_table, create_product_images_table, create_product_policies_table
Surfaces	Admin product routes and Livewire groups under Products, Product, Settings/Attributes, Settings/Brands, Settings/Categories, Settings/Collections, Settings/Types; storefront Product, ProductGroup, Brand, Brands, Category
Config	packages/framework/config/product-groups.php

Confidence

Confirmed

Notes

• Admin settings use the word Brands where the framework model uses ProductManufacturer.
• ProductGroup* is real framework behavior, not just storefront decoration. It has dedicated models, services, config, imports, listeners, and admin UI.

Pricing & Promotions

Responsibility: determine what price a customer is eligible to see or buy at, and manage promotional modifiers on top of that pricing.

Hierarchy

• Pricing & Promotions
  • Offer records
    • ProductOffer, FeaturedOffer, PriceHistory, PriceList
  • Targeted pricing eligibility
    • customer, customer-group, country, state, postal-code, shipping-zone, shipping-address, billing-address, and inventory-location targeting
  • Promotions
    • Promotion, PromotionCode, PromotionCondition, PromotionBenefit, PromotionRedemption

Evidence

Signal	Evidence
Models	packages/framework/src/Models/ProductOffer*.php, FeaturedOffer.php, PriceHistory.php, Promotion*.php
Actions	packages/framework/src/Actions/ProductOffer, FeaturedOffer, PriceHistory, PriceList
Services	packages/framework/src/Services/Promotion, packages/framework/src/Features/CalculateFeaturedOfferFeature.php, packages/framework/src/Features/PromotionsFeature.php
Migrations	create_product_offers_table, create_price_histories_table, create_featured_offers_table, create_promotions_table, create_promotion_codes_table, create_promotion_conditions_table, create_promotion_benefits_table
Surfaces	Admin products.offers, product_offers, price_histories, price_lists/download; storefront products/getOffers, products/{product}/offers, bestOffers; admin promotion Livewire groups under Settings/Promotion and Settings/Promotions
Config	packages/framework/config/promotions.php

Confidence

Confirmed

Notes

• ProductOffer is the pricing center of gravity in the framework.
• Pricing eligibility is implemented partly through relationships on ProductOffer and partly through traits such as IsEligibleFor and availability checks.

Customer Management

Responsibility: model customer accounts, segmentation, account-owned data, and the customer-facing team structure that surrounds commerce.

Hierarchy

• Customer Management
  • Accounts and segmentation
    • Customer, CustomerGroup, CustomerProductRestriction
  • Customer-owned data
    • CustomerAddress, CustomerList, CustomerListProduct, Wishlist
  • Customer-linked users and teams
    • account ownership, customer-linked users, storefront team and permissions surfaces

Evidence

Signal	Evidence
Models	packages/framework/src/Models/Customer*.php, CustomerAddress.php, CustomerGroup.php, CustomerList*.php, CustomerProductRestriction.php, Wishlist.php
Actions	packages/framework/src/Actions/Customer*, CustomerAddress, CustomerList, CustomerListProduct, CustomerProductRestriction
Migrations	create_customers_table, create_customer_groups_table, create_customer_customer_group_table, create_customer_lists_table, create_customer_list_products_table
Surfaces	Admin customers, customers.addresses, customer_groups; admin Livewire groups Customer, Customers; storefront customers, customers.addresses, users, MyAccount/Addresses, MyAccount/Lists, MyAccount/Team, MyAccount/Permissions
Config	packages/admin/config/admin.php customer feature flags and price-list toggle

Confidence

Confirmed

Notes

• Customer cards are surfaced through customer/account flows, but the persistent payment-method records are classified under Payments & Billing.
• Wishlist and CustomerList coexist in the framework and likely represent overlapping or evolving list-management concepts.

Order Lifecycle

Responsibility: capture the commercial lifecycle from cart through order creation, adjustments, returns, and customer-visible order history.

Hierarchy

• Order Lifecycle
  • Cart and checkout
    • Cart, CartItem, sample-order flow
  • Orders and order items
    • Order, OrderItem
  • Commercial adjustments and risk
    • OrderDiscountLine, OrderItemDiscountLine, OrderRisk
  • Returns, refunds initiation, and tracking
    • OrderReturn, OrderReturnItem, OrderReturnFeeLine, OrderReturnShippingLine, storefront order tracking

Evidence

Signal	Evidence
Models	packages/framework/src/Models/Order*.php, OrderItem*.php, OrderReturn*.php, OrderRisk.php
Actions	packages/framework/src/Actions/Cart*, Order*, OrderItem*, OrderReturn*, OrderRisk
Migrations	create_orders_table, create_order_items_table, create_order_discount_lines_table, create_order_item_discount_lines_table, create_order_returns_table, create_order_return_items_table, create_order_risks_table
Surfaces	Admin order routes for calculate/confirm/cancel/duplicate/refund/return flows; storefront carts, orders, order items, tracking, sample-order route
Features	packages/framework/src/Features/CartValidationFeature.php, order-related email features under packages/framework/src/Features/Emails

Confidence

Confirmed

Notes

• Financial settlement records such as OrderPayment, OrderRefund, and invoices are classified under Payments & Billing.
• Shipping lines and shipments are classified under Fulfillment & Shipping, even though they are deeply tied to orders.

Payments & Billing

Responsibility: manage how orders are paid, how payment methods are stored or redirected, and how billing documents are produced and retrieved.

Hierarchy

• Payments & Billing
  • Gateways and payment methods
    • PaymentGateway, CustomerCard, Stripe checkout and saved-card flows
  • Financial transaction records
    • OrderPayment, OrderRefund
  • Billing documents
    • Invoice, InvoiceItem, InvoiceDiscountLine, InvoiceFeeLine, InvoiceShippingLine

Evidence

Signal	Evidence
Models	packages/framework/src/Models/PaymentGateway.php, CustomerCard.php, OrderPayment.php, OrderRefund.php, Invoice*.php
Actions	packages/framework/src/Actions/PaymentGateway, Stripe, Invoice*, OrderPayment, OrderRefund
Migrations	create_payment_gateways_table, create_customer_cards_table, create_order_payments_table, create_order_refunds_table, create_invoices_table, invoice line tables
Surfaces	Admin payment_gateways, orders.payments, orders.refunds, orders/{id}/importStripePayment, orders/{id}/getCheckoutUrl, invoice download routes; storefront redirectToPaymentGateway, invoice download; Stripe routes under packages/framework/routes/stripe.php
Config	packages/admin/config/admin.php payment-method presentation config

Confidence

Confirmed

Notes

• Operational refund or return decisions belong to Order Lifecycle; financial refund records and settlement flows belong here.
• CustomerCard is customer-facing in storefront account pages, but the underlying capability is a payment-method concern.

Fulfillment & Shipping

Responsibility: configure shipping rules, select available shipping options, and execute fulfillment, shipment, transfer, and delivery scheduling workflows.

Hierarchy

• Fulfillment & Shipping
  • Shipping configuration
    • ShippingMethod, ShippingService, ShippingZone, ShippingClass, ShippingOption, ShippingBox, ShippingPostalCode
  • Shipment execution
    • OrderShippingLine, OrderShipment, DeliveryTimingIssue
  • Fulfillment workflows
    • FulfillmentRequest, FulfillmentRequestItem, Fulfillment, FulfillmentItem, FulfillmentService, FulfillmentServiceRequest
  • Transfer and scheduling
    • TransferLocation, TransferableLocation, CalendarRule, CalendarRuleCondition, UnitOfMeasure

Evidence

Signal	Evidence
Models	packages/framework/src/Models/Shipping*.php, OrderShippingLine.php, OrderShipment.php, DeliveryTimingIssue.php, Fulfillment*.php, TransferLocation.php, TransferableLocation.php, CalendarRule*.php, UnitOfMeasure.php
Actions	packages/framework/src/Actions/Shipping*, OrderShippingLine, OrderShipment, Fulfillment*, TransferLocation
Services	packages/framework/src/Services/CalendarRule, packages/framework/config/fulfillment-services.php
Migrations	shipping method/service/zone/class/option/box/postal-code tables, order shipment and order shipping line tables, fulfillment tables, transfer-location tables, calendar-rule tables
Surfaces	Extensive admin shipping and fulfillment routes, storefront shipping estimate and cart-item shipping methods, admin Settings/Locations, admin Inventory, storefront Cart/Shipments, storefront Product/ShippingOptions
Features	ShippingServicesLockFeature.php, fulfillment email features

Confidence

Confirmed

Notes

• CalendarRule* currently behaves more like delivery scheduling than a general-purpose rule engine, so it is classified here for now.
• UnitOfMeasure appears in supply and shipping contexts, but shipping-service restrictions make this its strongest current home.

Inventory & Vendor Supply

Responsibility: represent stock state, inventory locations, vendor-side catalog and inventory data, and the mapping layer that links supply records to sellable products.

Hierarchy

• Inventory & Vendor Supply
  • Inventory state
    • ProductInventoryLocation, ProductInventoryItem, StockHistory
  • Vendor catalog and supply records
    • ProductVendor, ProductVendorInventoryItem, ProductVendorCatalogItem, ProductVendorCatalogInventoryItem, ProductManufacturerProductVendor
  • Mapping and sync preparation
    • ProductVendorMapping, ProductMappingAttempt, AlternateCode

Evidence

Signal	Evidence
Models	packages/framework/src/Models/ProductInventory*.php, StockHistory.php, ProductVendor*.php, ProductManufacturerProductVendor.php, ProductMappingAttempt.php, AlternateCode.php
Actions	packages/framework/src/Actions/ProductInventory*, StockHistory, ProductVendor*, ProductVendorMapping, ProductMappingAttempt
Migrations	create_product_inventory_locations_table, create_product_inventory_items_table, create_stock_histories_table, create_product_vendors_table, create_product_vendor_catalog_items_table, create_product_vendor_catalog_inventory_items_table, create_product_vendor_mappings_table
Surfaces	Admin product_inventory_locations, inventory_items, product_vendors, product_vendor_inventory_items, product_vendor_catalog_inventory_items; admin Livewire groups Inventory, Vendor, Vendors; storefront public inventory_locations
ERP bridge	InventoryLocations, Products, ProductInventoryItems, ProductManufacturers request groups

Confidence

Confirmed

Notes

• AlternateCode behaves like a supply-side or sync-support identifier rather than a first-class merchandising concept.
• ProductVendorItem still appears in older naming, but newer migrations and actions clearly move toward ProductVendorMapping.

Tax & Territory

Responsibility: define tax policy and the shared geographic model used by shipping, pricing, customer addressing, and territory-based business rules.

Hierarchy

• Tax & Territory
  • Tax definitions
    • TaxRate, TaxLine, OrderTaxRateItemCode, Nexus
  • Shared territory model
    • Country, State, GeoRegion, SaleRegion, Address

Evidence

Signal	Evidence
Models	packages/framework/src/Models/TaxRate.php, TaxLine.php, OrderTaxRateItemCode.php, Nexus.php, Country.php, State.php, GeoRegion.php, SaleRegion.php, Address.php
Actions	packages/framework/src/Actions/TaxRate, TaxJar, Nexus, GeoRegion, SaleRegion, Address
Migrations	create_tax_rates_table, create_tax_lines_table, create_order_tax_rate_item_code, create_nexuses_table, create_countries_table, create_states_table, create_geo_regions_table, create_sale_regions_table, create_addresses_table
Surfaces	Admin tax_rates, geo_regions, sale_regions, nexuses, addresses; storefront and world routes for country/state lookups and geolocation helpers
Config	packages/framework/config/taxjar.php, packages/framework/routes/world.php

Confidence

Confirmed

Notes

• Address is shared infrastructure across customers, pricing, shipping, and tax. It is classified here because it participates directly in territory modeling, while CustomerAddress remains inside Customer Management.

Supporting Platform Capabilities

Identity & access

• Responsibility: authenticate users, authorize actions, manage roles and permissions, and support staff/customer impersonation flows.
• Evidence:
  • Models and actions: User.php, packages/framework/src/Actions/Auth, packages/framework/src/Actions/Role, packages/framework/src/Actions/User
  • Routes: packages/framework/routes/auth.php, admin users, roles, permissions, login/asCustomer
  • Surfaces: admin Users, Roles, Staff; storefront Login, Register, ForgotPassword, ResetPassword, MyAccount/Permissions, MyAccount/Team
• Confidence: Confirmed

Integration & data exchange

• Responsibility: move data into and out of Pyle, especially through ERP synchronization, feeds, imports, exports, and external file-backed integrations.
• Evidence:
  • Models: DataFeed.php, DataFeedRun.php, DataFeedRunError.php, ExcelExport.php, ExcelImport.php, ExcelImportLog.php, FileSystemDisk.php, SFTPDisk.php
  • Actions and services: DataFeed, Excel, Import, Exports, ErpBridge, Services/DataFeed, Services/ErpBridge, Services/SFTP
  • ERP bridge request groups: Addresses, Customers, CustomerProductRestrictions, InventoryLocations, Orders, ProductAttributes, ProductCategories, ProductCrossSells, ProductInventoryItems, ProductManufacturers, ProductOffers, ProductTypes, Products
  • Surfaces: admin Tools/Excel, Vendor/DataFeed, Settings/ErpBridge
• Confidence: Confirmed

Search, audit, and operational workflow

• Responsibility: support search, operator workflow, comment streams, request queues, analytics, and activity history across multiple business domains.
• Evidence:
  • Models and actions: Comment.php, ActionRequest.php, AnalyticsAggregate.php, Flag.php, SaleActivity.php, packages/framework/src/Actions/ActivityLog, FastSearch, Meilisearch, Searchable
  • Config and features: activity-logs.php, AdminRestrictionFeature.php
  • Surfaces: admin ActivityLog, Comments, Flags; storefront FastSearch, Search
• Confidence: Confirmed

Runtime controls, storage, and external hooks

• Responsibility: manage maintenance behavior, feature flags, file conversion/storage helpers, webhook endpoints, and low-level framework utilities.
• Evidence:
  • Models and services: MaintenanceSchedule.php, Services/FileConverter, Services/Flags, Services/AWS, Services/Pipelines, Services/Proxies
  • Features and config: maintenance.php, packages/framework/src/Features/*.php, packages/framework/routes/webhooks.php
  • External integrations: Stripe webhooks, TaxJar provider hook-up, filesystem disk management
• Confidence: Likely

Presentation-Only Surfaces

These surfaces expose domains, but they should not be treated as domain owners in documentation.

Admin shell

• packages/admin/src/Livewire/Admin/Layouts
• packages/admin/src/Livewire/Admin/AsideBar
• packages/admin/src/Livewire/Admin/Dashboard
• packages/admin/src/Livewire/Admin/Login
• packages/admin/src/Livewire/Admin/Logout
• packages/admin/resources/views/components/layouts/app/side-bar/*

Storefront shell

• packages/storefront/src/Livewire/Storefront/Navigation
• packages/storefront/src/Livewire/Storefront/Home
• packages/storefront/src/Livewire/Storefront/Login
• packages/storefront/src/Livewire/Storefront/Logout
• packages/storefront/src/Livewire/Storefront/Register
• packages/storefront/src/Livewire/Storefront/ForgotPassword
• packages/storefront/src/Livewire/Storefront/ResetPassword
• packages/storefront/src/View/Components/MyAccount/Menu/*.php

Why they stay separate

• They group or route users into domains, but they do not establish persistence boundaries.
• Menu labels often use business language that differs from the model layer, such as Brands for ProductManufacturer.
• They are valuable corroboration signals, not primary domain evidence.

Ambiguous or Legacy Areas

Price zones, custom prices, and price rules

• ProductOffer still carries price_rule_id, price_zone_id, and custom_price_id in packages/framework/src/Models/ProductOffer.php.
• The original foreign-key definitions are commented out in packages/framework/database/migrations/2022_11_26_132216_create_product_offers_table.php.
• The current framework package does not expose these as clear first-class persistent domains.
• Classification for this pass: Ambiguous

Wishlist versus customer lists

• Wishlist still exists as a model and storefront surface.
• CustomerList and CustomerListProduct represent a stronger, newer account-owned list concept.
• This looks like an overlap or migration path rather than two equally mature top-level domains.
• Classification for this pass: Ambiguous

Calendar rules as a possible future standalone engine

• CalendarRule and CalendarRuleCondition could eventually justify a separate scheduling or rule-engine domain.
• Current services, traits, and admin surfaces tie them most strongly to delivery scheduling and fulfillment timing.
• Classification for this pass: Likely subdomain of Fulfillment & Shipping

Coverage Appendix

This appendix groups framework nouns by shared workflow or naming prefix and assigns each cluster once.

Cluster	Assigned to	Primary evidence
Product, ProductTerm, ProductPolicy	Catalog & Merchandising	Product models, product actions, admin product routes
ProductCategory, ProductCollection, ProductType, ProductManufacturer	Catalog & Merchandising	Taxonomy models, settings routes, admin settings surfaces
ProductAttribute, ProductAttributeGroup	Catalog & Merchandising	Attribute models, actions, settings surfaces
ProductGroup*	Catalog & Merchandising	Product-group models, services, config, storefront/admin surfaces
ProductImage, ProductDocument, ProductVideo	Catalog & Merchandising	Media models and product media routes
ProductCrossSell, ProductUpsell	Catalog & Merchandising	Relationship models, product relationship routes
FeaturedOffer, PriceHistory, PriceList	Pricing & Promotions	Pricing actions, feature flags, price-list download route
ProductOffer*	Pricing & Promotions	Offer models, offer routes, targeted eligibility relationships
Promotion*	Pricing & Promotions	Promotion models, services, feature flag, admin promotion UI
Customer	Customer Management	Customer model, customer routes, customer admin/storefront surfaces
CustomerAddress	Customer Management	Customer address model and nested customer-address routes
CustomerGroup, CustomerCustomerGroup	Customer Management	Group model and customer-group routes
CustomerList, CustomerListProduct, Wishlist	Customer Management	List models and storefront my-account list surfaces
CustomerProductRestriction	Customer Management	Restriction model, actions, ERP bridge request group
Cart, CartItem	Order Lifecycle	Storefront cart routes and cart actions
Order, OrderItem	Order Lifecycle	Order models, actions, admin/storefront order routes
OrderDiscountLine, OrderItemDiscountLine, OrderRisk	Order Lifecycle	Discount and risk models plus admin order routes
OrderReturn*	Order Lifecycle	Return models, return actions, admin return routes
PaymentGateway, CustomerCard	Payments & Billing	Gateway and saved-card models, admin/storefront payment surfaces
OrderPayment, OrderRefund	Payments & Billing	Payment and refund models plus admin payment/refund routes
Invoice*	Payments & Billing	Invoice models, invoice actions, invoice download routes
Stripe	Payments & Billing	packages/framework/routes/stripe.php, checkout/card actions
ShippingMethod, ShippingService, ShippingZone, ShippingClass, ShippingOption, ShippingBox, ShippingPostalCode	Fulfillment & Shipping	Shipping models, shipping routes, shipping settings surfaces
OrderShippingLine, OrderShipment, DeliveryTimingIssue	Fulfillment & Shipping	Shipment models and order shipping routes
Fulfillment*, FulfillmentService*	Fulfillment & Shipping	Fulfillment models, routes, config, email features
TransferLocation, TransferableLocation	Fulfillment & Shipping	Transfer models and fulfillment/order-return transfer routes
CalendarRule*, UnitOfMeasure	Fulfillment & Shipping	Calendar-rule services, shipping-service restrictions, admin settings surfaces
ProductInventoryLocation, ProductInventoryItem, StockHistory	Inventory & Vendor Supply	Inventory models, actions, admin inventory routes
ProductVendor*, ProductManufacturerProductVendor	Inventory & Vendor Supply	Vendor models, catalog/inventory models, vendor routes
ProductVendorMapping, ProductMappingAttempt, AlternateCode	Inventory & Vendor Supply	Mapping models, mapping actions, 2024 rename/mapping migrations
TaxRate, TaxLine, OrderTaxRateItemCode, Nexus	Tax & Territory	Tax models, actions, tax and nexus routes
Country, State, GeoRegion, SaleRegion, Address	Tax & Territory	Territory models, world routes, geo-region and address surfaces
User, Role, Auth	Supporting Platform Capabilities	Auth routes, user/role actions, admin/staff/user surfaces
DataFeed*, Excel*, ErpBridge	Supporting Platform Capabilities	Data-feed models and services, Excel actions, ERP bridge requests and settings surface
FileSystemDisk, SFTPDisk, Services/SFTP, Services/FileConverter	Supporting Platform Capabilities	Disk models, SFTP service, filesystem admin routes
Comment, ActionRequest, ActivityLog	Supporting Platform Capabilities	Comment model, action-request routes, activity-log config/actions
Flag, Features/*, Services/Flags	Supporting Platform Capabilities	Flag model, feature classes, runtime gating behavior
AnalyticsAggregate, SaleActivity	Supporting Platform Capabilities	Analytics and sales-activity models plus admin analytics surfaces
FastSearch, Meilisearch, Searchable	Supporting Platform Capabilities	Search actions and storefront/admin search surfaces
MaintenanceSchedule, maintenance.php, webhooks.php	Supporting Platform Capabilities	Maintenance model/config and webhook endpoints
AWS, Blacklist, CommandLine, DevTools, Framework, Helpers, Pipelines, Proxies, Storefront	Supporting Platform Capabilities	Utility or framework-glue directories without independent domain ownership

Next Documentation Pass

The next useful step is to turn each top-level domain into its own page with the same structure:

1. Responsibility and boundaries.
2. Subdomain hierarchy.
3. Core entities and state transitions.
4. Key routes, actions, and UI surfaces.
5. External integrations.
6. Open questions or ambiguous legacy areas.

The best starting pages after this inventory are:

• Catalog & Merchandising
• Pricing & Promotions
• Order Lifecycle
• Fulfillment & Shipping

Those four areas have the deepest model density, the most surfaced workflows, and the most downstream documentation value.