Developer reference

This section documents framework-level subsystems that apply across every Commerce Connect implementation. Consult these articles when you extend the platform, configure cross-cutting behavior, or troubleshoot issues that span multiple subsystems.

Application lifecycle

These articles describe when Commerce Connect code runs and how the system reacts to events at runtime.

• Initialization system – Configure how Commerce Connect modules and dependencies start at application launch.
• Events – Subscribe to notifications fired when prices, inventory, and other commerce data change.
• Scheduled jobs (dev) – Author and configure background jobs for maintenance and batch processing.

Request handling

These articles describe how Commerce Connect maps incoming requests to catalog content and serves responses efficiently.

• Routing – Map URLs to catalog content using the Commerce Connect routing system.
• Caching – Cache product catalog data and entries to reduce database load.

Cross-cutting concerns

These articles cover behaviors that apply regardless of which feature area you are working in.

• Logging API – Emit and consume application logs to troubleshoot Commerce Connect issues.
• Globalization – Localize content and the user interface for multiple languages and regions.

Where to go next

For feature-specific developer guidance, see the following sections:

• Catalogs – Build and extend catalog content models, importers, and rendering.
• Orders – Customize order processing, payment, and shipment handling.
• Marketing – Create custom promotions, campaigns, and discount logic.
• Customers – Extend customer and organization data and authentication.